diff options
| author | niruiyu <niruiyu@6f19259b-4bc3-4df7-8a09-765794883524> | 2011-12-14 07:51:54 +0000 |
|---|---|---|
| committer | niruiyu <niruiyu@6f19259b-4bc3-4df7-8a09-765794883524> | 2011-12-14 07:51:54 +0000 |
| commit | e7b100fac86547d5729c14103aabec2218966062 (patch) | |
| tree | fabe53957c7ad20eff172aad187bc55f50dc14dd /SourceLevelDebugPkg | |
| parent | e5b317d06e85ab8c21d6f339d81e3554a75c3c31 (diff) | |
| download | edk2-platforms-e7b100fac86547d5729c14103aabec2218966062.tar.xz | |
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
Diffstat (limited to 'SourceLevelDebugPkg')
| -rw-r--r-- | SourceLevelDebugPkg/Readme.txt | 22 |
1 files changed, 10 insertions, 12 deletions
diff --git a/SourceLevelDebugPkg/Readme.txt b/SourceLevelDebugPkg/Readme.txt index a1a2ffe18d..7dcd6d538b 100644 --- a/SourceLevelDebugPkg/Readme.txt +++ b/SourceLevelDebugPkg/Readme.txt @@ -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.
|