audk/SourceLevelDebugPkg
vanjeff 18b144ea42 Import SourceLevelDebugPkg.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@10867 6f19259b-4bc3-4df7-8a09-765794883524
2010-09-12 06:43:36 +00:00
..
Include Import SourceLevelDebugPkg. 2010-09-12 06:43:36 +00:00
Library Import SourceLevelDebugPkg. 2010-09-12 06:43:36 +00:00
Readme.txt Import SourceLevelDebugPkg. 2010-09-12 06:43:36 +00:00
SourceLevelDebugPkg.dec Import SourceLevelDebugPkg. 2010-09-12 06:43:36 +00:00
SourceLevelDebugPkg.dsc Import SourceLevelDebugPkg. 2010-09-12 06:43:36 +00:00

Readme.txt

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

UDK based firmware on UEFI IA-32 and UEFI x64 platforms may be debugged using Microsoft(R) Debugging Tools for Windows(R) (WinDbg). Debug capability is enabled with SourceLevelDebugPkg in conjunction with the Intel(R) UEFI Development Kit Debugger Tool (Intel(R) UDK Debugger Tool).

The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:
http://www.intel.com/technology/efi. 

NOTE: In addition to the known issues listed in the user manual, the following anomalies have been observed:

1) When using a USB debug cable, after the TARGET completes a reset during memory initialization, the connection between the HOST and the TARGET may be lost (e.g. WinDbg reports busy status and does not respond to a break request). A work around for this issue is to unplug the USB debug cable and then plug the cable back in. A new debug session may then be started.