tyler.durden
/
audk
mirror of https://github.com/acidanthera/audk.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
audk/SourceLevelDebugPkg
History
vanjeff b6de1db3cd Update SourceLevelDebugPkg version: 0.70 -> 0.71 
Signed-off-by: vanjeff
Reviewed-by: hhtian

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@12854 6f19259b-4bc3-4df7-8a09-765794883524
 		2011-12-14 02:14:02 +00:00
..
Include 1. Fixed issue that firmware cannot boot if no USB debug cable connection. 2011-09-30 02:19:28 +00:00
Library Set the current view point to the breaking CPU if it meets breakpoint. 2011-12-02 06:07:17 +00:00
Readme.txt minor format update to make text wrap around column 80 2010-09-13 02:03:04 +00:00
SourceLevelDebugPkg.dec Update SourceLevelDebugPkg version: 0.70 -> 0.71 2011-12-14 02:14:02 +00:00
SourceLevelDebugPkg.dsc Update SourceLevelDebugPkg version: 0.70 -> 0.71 2011-12-14 02:14:02 +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.