| hhtian | 1c5709f | 2010-09-13 02:03:04 +0000 | [diff] [blame] | 1 | UDK based firmware on UEFI IA-32 and UEFI x64 platforms may be debugged using
|
| 2 | Microsoft(R) Debugging Tools for Windows(R) (WinDbg). Debug capability is enabled
|
| 3 | with SourceLevelDebugPkg in conjunction with the Intel(R) UEFI Development Kit
|
| 4 | Debugger Tool (Intel(R) UDK Debugger Tool).
|
| vanjeff | 18b144e | 2010-09-12 06:43:36 +0000 | [diff] [blame] | 5 |
|
| 6 | The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:
|
| 7 | http://www.intel.com/technology/efi.
|
| 8 |
|
| hhtian | 1c5709f | 2010-09-13 02:03:04 +0000 | [diff] [blame] | 9 | NOTE: In addition to the known issues listed in the user manual, the following
|
| 10 | anomalies have been observed:
|
| vanjeff | 18b144e | 2010-09-12 06:43:36 +0000 | [diff] [blame] | 11 |
|
| hhtian | 1c5709f | 2010-09-13 02:03:04 +0000 | [diff] [blame] | 12 | 1) When using a USB debug cable, after the TARGET completes a reset during memory
|
| 13 | initialization, the connection between the HOST and the TARGET may be lost
|
| 14 | (e.g. WinDbg reports busy status and does not respond to a break request). A
|
| 15 | work around for this issue is to unplug the USB debug cable and then plug the
|
| 16 | cable back in. A new debug session may then be started.
|