tyler.durden/audk
1
0
Fork 0
mirror of https://github.com/acidanthera/audk.git synced 2025-07-28 16:14:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

minor format update to make text wrap around column 80

Browse Source 
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@10869 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
hhtian 2010-09-13 02:03:04 +00:00
parent c6efcc2aa9
commit 1c5709f25e
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
SourceLevelDebugPkg/Readme.txt
View File

@ -1,8 +1,16 @@
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). 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: The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:
http://www.intel.com/technology/efi. http://www.intel.com/technology/efi.
NOTE: In addition to the known issues listed in the user manual, the following anomalies have been observed: 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. 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.