tyler.durden
/
audk
mirror of https://github.com/acidanthera/audk.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Refine wording in SourceLevelDebugPkg/Readme.txt. 

Signed-off-by: niruiyu
Reviewed-by: vanjeff

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@12857 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
niruiyu 2011-12-14 07:51:54 +00:00
parent e5b317d06e
commit e7b100fac8
1 changed files with 10 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
SourceLevelDebugPkg/Readme.txt
View File

@ -1,16 +1,14 @@
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 can be debugged with
SourceLevelDebugPkg in conjunction with 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.
The Intel(R) UDK Debugger Tool and its detailed user manual can be obtained
from: http://www.intel.com/technology/efi.
NOTE: In addition to the known issues listed in the user manual, the following
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. A work around for this issue is to unplug the USB debug cable and then
plug the cable back in. A new debug session can then be started.