diff options
| author | hhtian <hhtian@6f19259b-4bc3-4df7-8a09-765794883524> | 2010-09-13 02:03:04 +0000 |
|---|---|---|
| committer | hhtian <hhtian@6f19259b-4bc3-4df7-8a09-765794883524> | 2010-09-13 02:03:04 +0000 |
| commit | 1c5709f25eefcbe14a4e79e819870373270e492d (patch) | |
| tree | 74e9d0b685821185ce5109d57ac0303a7a6ac229 | |
| parent | c6efcc2aa97436f81628c38b85b858e0f955b40a (diff) | |
minor format update to make text wrap around column 80
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@10869 6f19259b-4bc3-4df7-8a09-765794883524
| -rw-r--r-- | SourceLevelDebugPkg/Readme.txt | 14 |
1 files changed, 11 insertions, 3 deletions
diff --git a/SourceLevelDebugPkg/Readme.txt b/SourceLevelDebugPkg/Readme.txt index e43ed18b4..a1a2ffe18 100644 --- a/SourceLevelDebugPkg/Readme.txt +++ b/SourceLevelDebugPkg/Readme.txt @@ -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:
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.
\ No newline at end of file +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.
|