MPLAB ICD 3 In-Circuit Debugger User's Guide

Error MessagesICD3Err0030: Unable to read/find firmware File %s.If the Hex file exists:• Reconnect and try again.• If this does not work, the file may be corrupted. Reinstall MPLAB IDE.If the Hex file does not exist:• Reinstall MPLAB IDE.ICD3Err0031: Failed to get PC.ICD3Err0032: Failed to set PC.See Section 7.3.2 “Debugger-to-Target Communication Error Actions”.ICD3Err0033: %d bytes expected, %d bytes received.See Section 7.3.3 “Debugger-to-PC Communication Error Actions”.ICD3Err0034: This version of MPLAB IDE does not support hardware revision%06x. Please upgrade to the latest version of MPLAB IDE before continuing.Find the latest MPLAB IDE at www.microchip.com.ICD3Err0035: Failed to get Device ID.See Section 7.3.1 “Read/Write Error Actions”.ICD3Err0036: MPLAB IDE has lost communication with ICD 3.See Section 7.3.3 “Debugger-to-PC Communication Error Actions”.ICD3Err0037: Timed out waiting for response from ICD 3.ICD3Err0038: Failed to initialize ICD 3.ICD3Err0039: ICD 3 self-test failed.For this error, the debugger is not responding:1. Unplug and plug in the debugger.2. Reconnect to the debugger in MPLAB IDE.3. If the problem persists contact Microchip.ICD3Err0040: The target device is not ready for debugging. Please check yourconfiguration bit settings and program the device before proceeding.You will receive this message when you have not programmed your device for the firsttime and try to Run. If you receive this message after this, or immediately afterprogramming your device, please refer to Section 7.3.6 “Debug Failure Actions”.ICD3Err0041: While receiving streaming data, ICD 3 has gotten out-of-sync withMPLAB IDE. To correct this you must reset the target device.First try to Halt, Reset and then Run again. If this does not work:1. Unplug and plug in the debugger.2. Reconnect to the debugger in MPLAB IDE.3. Check that the target speed is entered on the Clock tab of the Settings dialog.4. Run again.ICD3Err0045: You must connect to a target device to use MPLAB ICD 3.No power has been found.1. Ensure VDD and GND are connected between the debugger and target.2. Ensure that the target is powered.3. Ensure that the target power is sufficient to be detected by the debugger (seeChapter 10. “Hardware Specification”.)© 2008 Microchip Technology Inc. DS51766A-page 55