-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
+1) When using a USB debug cable, after the TARGET completes a reset during\r
+ memory initialization, the connection between the HOST and the TARGET may be\r
+ lost. A work around for this issue is to unplug the USB debug cable and then\r
+ plug the cable back in. A new debug session can then be started.\r