EDK2-fork

Files

vanjeff e21048345b 1. Fixed issue that firmware cannot boot if no USB debug cable connection.

2. Fixed issue that Ovmf with debug agent cannot boot if HOST software was not connected.

Signed-off-by: vanjeff
Reviewed-by: geekboy15a
Reviewed-by: erictian




git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@12486 6f19259b-4bc3-4df7-8a09-765794883524

2011-09-30 02:19:28 +00:00

Include

1. Fixed issue that firmware cannot boot if no USB debug cable connection.

2011-09-30 02:19:28 +00:00

Library

1. Fixed issue that firmware cannot boot if no USB debug cable connection.

2011-09-30 02:19:28 +00:00

Readme.txt

…

SourceLevelDebugPkg.dec

…

SourceLevelDebugPkg.dsc

…

Readme.txt

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:

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.