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
niruiyu b4ebbafff6 Generic solution to handle reset failure in some special platforms. 
Upon receiving RESET packet from HOST side, TARGET either sends OK packet and resets, or sends OK packet followed by TIMEOUT packet in 2 seconds indicating the reset failure.

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

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@12984 6f19259b-4bc3-4df7-8a09-765794883524
 		2012-02-07 01:58:30 +00:00
..
Include Generic solution to handle reset failure in some special platforms. 2012-02-07 01:58:30 +00:00
Library Generic solution to handle reset failure in some special platforms. 2012-02-07 01:58:30 +00:00
Readme.txt Refine wording in SourceLevelDebugPkg/Readme.txt. 2011-12-14 07:51:54 +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 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 can 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. 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.