[mirror_edk2.git] / SourceLevelDebugPkg / Readme.txt

UDK based firmware on UEFI IA-32 and UEFI x64 platforms may be debugged using \r
Microsoft(R) Debugging Tools for Windows(R) (WinDbg). Debug capability is enabled\r
with SourceLevelDebugPkg in conjunction with the Intel(R) UEFI Development Kit \r
Debugger Tool (Intel(R) UDK Debugger Tool).\r
\r
The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:\r
http://www.intel.com/technology/efi. \r
\r
NOTE: In addition to the known issues listed in the user manual, the following \r
anomalies have been observed:\r
\r
1) When using a USB debug cable, after the TARGET completes a reset during memory\r
   initialization, the connection between the HOST and the TARGET may be lost \r
   (e.g. WinDbg reports busy status and does not respond to a break request). A \r
   work around for this issue is to unplug the USB debug cable and then plug the\r
   cable back in. A new debug session may then be started.\r
Commit	Line	Data
1c5709f2 HT	1	UDK based firmware on UEFI IA-32 and UEFI x64 platforms may be debugged using \r
	2	Microsoft(R) Debugging Tools for Windows(R) (WinDbg). Debug capability is enabled\r
	3	with SourceLevelDebugPkg in conjunction with the Intel(R) UEFI Development Kit \r
	4	Debugger Tool (Intel(R) UDK Debugger Tool).\r
18b144ea	5	\r
	6	The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:\r
	7	http://www.intel.com/technology/efi. \r
	8	\r
1c5709f2 HT	9	NOTE: In addition to the known issues listed in the user manual, the following \r
1c5709f2 HT	10	anomalies have been observed:\r
18b144ea	11	\r
1c5709f2 HT	12	1) When using a USB debug cable, after the TARGET completes a reset during memory\r
	13	initialization, the connection between the HOST and the TARGET may be lost \r
	14	(e.g. WinDbg reports busy status and does not respond to a break request). A \r
	15	work around for this issue is to unplug the USB debug cable and then plug the\r
	16	cable back in. A new debug session may then be started.\r