The MPLAB ICD 3 In-Circuit Debugger generates many different error messages; some of them are special and others can be resolved with normal corrective actions. The MPLAB ICD 3 In-Circuit Debugger generates many different error messages; some of them are special and others can be resolved with normal corrective actions. The MPLAB ICD 3 In-Circuit Debugger generates many different error messages; some of them are special and others can be resolved with normal corrective actions.
The MPLAB ICD 3 In-Circuit Debugger error messages are listed below by number. In the error message, the text listed under the form %x (variable) is displayed as text related to the special case in the actual error message.
Note: The numbers may not appear in the displayed message. Use the Search tab on the Help viewer to find the message and highlight it as follows.
ICD3Err0001: Failed while wriTIng to program memory. (Write program memory failed.)
ICD3Err0002: Failed while wriTIng to EEPROM. (Write EEPROM failed.)
ICD3Err0003: Failed while wriTIng to configuraTIon memory. See "Read/Write Error Corrective Action".
ICD3Err0005: ICD 3 is currently busy and cannot be unloaded at this time. (ICD 3 is currently busy and cannot be uninstalled at this time.)
You receive this error if you try to deselect the debugger as a debugger or programmer:
1. Wait - give the debugger time to complete all application tasks. Then try again to deselect the debugger.
2. Select Halt to stop any running applications. Then try again to deselect the debugger.
3. Unplug the debugger from the PC. Then try again to deselect the debugger.
4. Close MPLAB IDE.
ICD3Err0006: Failed while writing to user ID memory. (Write user ID memory failed.)
ICD3Err0007: Failed while reading program memory. (Read program memory failed.)
ICD3Err0008: Failed while reading EEPROM. (Read EEPROM failed.)
ICD3Err0009: Failed while reading configuration memory. (Read configuration memory failed.)
ICD3Err0010: Failed while reading user ID memory. See "Read/Write Error Corrective Action".
ICD3Err0011: Bulk erase failed. See "Read/Write Error Corrective Action". If none of this solves the problem, try using a different device.
ICD3Err0012: Download debug exec failed (Download debug executor failed)
You receive this error if you try to program from the Debugger menu:
1. Deselect the debugger as a debugging tool.
2. Close the project and close MPLAB IDE.
3. Restart MPLAB IDE and reopen the project.
4. Reselect the debugger as a debugging tool and try to program the target device again.
If this does not solve the problem, see "Installer Damage Corrective Action."
ICD3Err0013: NMMR register write failed. (NMMR register write failed.)
ICD3Err0014: File register write failed. See "Debugger - Target Device Communication Error Corrective Action".
ICD3Err0015: Data transfer was unsuccessful. %d byte(s) expected, %d byte(s) transferred. (Data transfer failed. %d bytes required, %d bytes transferred.) See "Debugger-PC Communication" Error corrective action".
ICD3Err0016: Cannot transmit. ICD 3 not found. The debugger is not connected to the PC.
ICD3Err0017: File register read failed. (File register read failed.)
ICD3Err0018: NMMR register read failed. (NMMR register read failed.)
ICD3Err0019: Failed while reading emulation registers. (Reading the emulator register failed.)
ICD3Err0020: Failed while writing emulation registers. See "Debugger - Target Device Communication Error Corrective Action".
ICD3Err0021: Command not echoed properly. Sent %x, received %x. (The command could not be returned correctly. %x was sent, %x was received.)
ICD3Err0022: Failed to get ICD 3 version information. (ICD 3 version information cannot be obtained.)
ICD3Err0023: Download FPGA failed. (Download FPGA failed.)
ICD3Err0024: Download RS failed. (Download RS failed.)
ICD3Err0025: Download AP failed. See "Debugger - PC Communication Error Corrective Action".
ICD3Err0026: Download program exec failed. (Downloading the programming executive failed.)
You receive this error if you try to program from the Debugger menu:
1. Deselect the debugger as a debugging tool.
2. Close the project and close MPLAB IDE.
3. Restart MPLAB IDE and reopen the project.
4. Reselect the debugger as a debugging tool and try to program the target device again.
If this does not resolve the issue, see "Installer Damage Corrective Actions."
ICD3Err0027: Bulk transfer failed due to invalid checksum See "Debugger - PC communication error corrective action". Also, be sure to use the correct length of the cable.
ICD3Err0028: Download device database failed (failed to download device database)
If you receive this error:
1. Try downloading again. May be a one-time error.
2. Try to download manually. Select the Debugger Settings, Configuration tab and click Manual Download. Select the highest numbered .jam file and click Open.
ICD3Err0029: Communication failure. Unexpected command echo response %x received from ICD 3. (Communication failed. Received an undesired command return response %x from ICD 3.) See "Debugger - PC Communication Error Corrective Action".
ICD3Err0030: Unable to read/find firmware File %s. (Cannot read/find firmware file %s.)
If this Hex file exists:
• Reconnect and try again.
• If this does not solve the problem, the file may be damaged. Reinstall MPLAB IDE.
If the Hex file does not exist: • Reinstall MPLAB IDE.
ICD3Err0031: Failed to get PC. ICD3Err0032: Failed to set PC. See "Debugger - Target Device Communication Error Corrective Action".
ICD3Err0033: %d bytes expected, %d bytes received. (%d bytes are required, %d bytes are received.) See "Debugger-PC Communication Error Corrective Actions".
ICD3Err0034: This version of MPLAB IDE does not support hardware revision %06x. Please upgrade to the latest version of MPLAB IDE before continuing. (This version of MPLAB IDE does not support hardware version %06x. Please upgrade to the latest version of MPLAB IDE, then Go ahead.) Find the latest MPLAB IDE on it.
ICD3Err0035: Failed to get Device ID. See "Read/Write Error Corrective Actions".
ICD3Err0036: MPLAB IDE has lost communication with ICD 3. (MPLAB IDE loses communication with ICD 3.) See "Debugger - PC Communication Error Corrective Action".
ICD3Err0037: Timed out waiting for response from ICD 3. (Wait for ICD 3 response timeout.)
ICD3Err0038: Failed to initialize ICD 3. (Unable to initialize ICD 3.)
ICD3Err0039: ICD 3 self-test failed. (ICD 3 self-test failed.)
The debugger does not respond to this error:
1. Unplug the debugger and insert it.
2. Reconnect to the debugger in MPLAB IDE.
3. If the problem persists, please contact Microchip.
ICD3Err0040: The target device is not ready for debugging. Please check your configuration bit settings and program the device before proceeding. (Check the configuration bit settings and program the device, then continue.)
You receive this message when you first use the device without programming it and trying to run it. If you receive this message later, or if you receive this message immediately after programming the device, see "Debugging Fault Corrective Actions."
ICD3Err0041: While receiving streaming data, ICD 3 has gotten out-of-sync with MPLAB IDE. To correct this you must reset the target device. (ICD 3 is not synchronized with MPLAB IDE when receiving streaming data. To correct this problem, You must reset the target device.)
First try to pause, reset and run again. If this does not solve the problem:
1. Unplug the debugger and insert it.
2. Reconnect to the debugger in MPLAB IDE.
3. Check if the speed of the target device 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. (You must be connected to the target device to use MPLAB ICD 3.)
Power not found.
1. Make sure VDD and GND are connected between the debugger and the target device. 2. Ensure that the target device is powered.
3. Make sure the target power is sufficient to be detected by the debugger.
ICD3Err0046: An error occurred while trying to read the stopwatch count. The stopwatch count may not be accurate. (An error occurred while trying to read the stopwatch count. The stopwatch count may be inaccurate.) See "Debugger - Target Device Communication Error Correction" Measures".
ICD3Err0047: Bootloader download failed. See "Debugger - PC communication error corrective action".
ICD3Err0052: The current ICD 3 hardware version %x, is out of date. This version of MPLAB IDE will support only version %x or higher. (The current ICD 3 hardware version %x is obsolete. This version of MPLAB IDE only supports %x Version or higher.)
Did you click Cancel when asked to download the latest firmware? If so, you will need to download it now. Select the Debugger Settings, Configuration tab and click Manual Download. Select the highest numbered .jam file and click Open.
If you can't find any files to download or if this doesn't solve the problem (file corruption), you'll need to get the latest version of MPLAB IDE and install it. Find the latest MPLAB IDE on it.
ICD3Err0053: Unable to get ICD 3 protocol versions. (Unable to get ICD 3 protocol version.) See "Debugger - PC Communication Error Corrective Action".
ICD3Err0054: MPLAB IDE's ICD 3 protocol definitions are out of date. You must upgrade MPLAB IDE to continue. (MPLAB IDE's ICD 3 protocol definition is outdated. You must upgrade MPLAB IDE and continue.) Find the latest MPLAB IDE on it.
ICD3Err0055: Unable to set firmware suite version. ICD3Err0056: Unable to get voltages from ICD 3. (Cannot get ICD 3 voltage.) See "Debugger - PC Communication Error Corrective Action".
ICD3Err0057: Self-test could not be completed. Make sure you are using the ICD3 self-test board. See also "Debugger - Target Device Communication Error Corrective Action".
ICD3Err0063: Test interface clock write failure. Please ensure that the tester is properly connected. (Test interface clock write failed. Please make sure the tester is properly connected.)
ICD3Err0064: Test interface data write failure. ICD3Err0065: Test interface clock read failure.
ICD3Err0066: Test interface data read failure. The clock/data was not output from the debugger. Check the connection and try again.
ICD3Err0067: Failed to set/clear software breakpoint. Reprogram and try again.
ICD3Err0068: Failed while writing to boot FLASH memory. (Write boot flash failed.)
ICD3Err0069: Failed while reading boot FLASH memory. (Read boot flash failed.)
ICD3Err0070: Failed while writing peripheral memory. (Write peripheral memory failed.)
ICD3Err0071: Failed while reading peripheral memory. See "Read/Write Error Corrective Action".
ICD3Err0072: Unable to send freeze peripheral information. See "Debugger - PC communication error corrective action".
ICD3Err0073: Device is code protected. (The device is code protected.)
Devices that you attempt to operate (read, program, blank check, or verify) are code-protected, that is, you cannot read or modify the code. Check the configuration bit settings to see if code protection is enabled.
To disable code protection, set or clear the appropriate configuration bits in the code or in the Configuration Bits window (Configure Configuration Bits) according to the device data sheet. Then erase and reprogram the entire device.
ICD3Err0082: Test interface LVP failure. (Test interface LVP failed.)
ICD3Err0083: Test interface MCLR failure. (Test interface MCLR failed.)
Second, the general corrective measuresThe following general corrective actions can solve your problem: • Read/write error corrective actions
• Debugger - Target Device Communication Error Corrective Action • Debugger - PC Communication Error Corrective Action • Installer Damage Corrective Action
• USB port communication error corrective action • Debug trouble corrective action • Internal error corrective action
Read/write error corrective action
If you receive a read or write error:
1. Have you clicked Abort? This will result in a read/write error. 2. Try the read/write operation again. May be a one-time error.
3. Ensure that the target device is powered and at the correct voltage value for the device. See the device data sheet for the required device voltage values.
4. Make sure the debugger is properly connected to the target device (PGC and PGD are connected).
5. For write failures, make sure to select on the Program Memory tab of the Settings dialog.
"Erase all before Program". 6. Make sure that the length of the cable used is correct.
Debugger - Target Device Communication Error Corrective Action
The MPLAB ICD 3 In-Circuit Debugger and target devices are out of sync with each other. 1. Select Reset and try this again. 2. Please make sure that the length of the cable used is correct.
Debugger - PC communication error corrective action
The MPLAB ICD 3 In-Circuit Debugger and MPLAB IDE are out of sync with each other.
1. Unplug the debugger and insert it. 2. Reconnect the debugger.
3. Try this again. This error may be a one-time issue.
4. The installed MPLAB IDE version may not match the firmware version loaded on the MPLAB ICD 3 In-Circuit Debugger. Follow the steps outlined in Section 7.3.4, “Installer Damage Corrective Actionsâ€.
Installer damage corrective action
This issue is most likely caused by an incomplete or corrupted MPLAB IDE installation. 1. Uninstall all versions of MPLAB IDE from your PC. 2. Reinstall the required MPLAB IDE version. 3. If the problem persists, please contact Microchip.
USB port communication error corrective action
This problem is most likely caused by a failure or non-existence of the communication port.
1. Reconnect the MPLAB ICD 3 In-Circuit Debugger.
2. Make sure the debugger is physically connected to the correct USB port on your PC.
3. Make sure the correct USB port is selected in the debugger settings.
4. Make sure that the USB port is not being used by other devices.
5. If you are using a USB hub, make sure it is powered.
6. Make sure the USB driver is loaded.
Third, debugging fault corrective measuresThe MPLAB ICD 3 In-Circuit Debugger cannot perform debugging operations. There are many reasons for this problem.
The primary reason for not being able to debug
1. The oscillator does not work. Check the configuration bit settings associated with the oscillator.
2. The target board is not powered. Check the power cable connection.
3. The MPLAB ICD 3 In-Circuit Debugger sometimes disconnects the physical connection to the PC. Check the connection of the USB communication cable.
4. The debugger sometimes disconnects the physical connection to the target board. Check the connection of the communication cable.
5. The device is code protected. Check the configuration bit settings related to code protection.
6. You are trying to recompile your project in Release mode. Select Debug from the Build Configuration drop-down list in the project toolbar and recompile the project.
7. In MPLAB IDE, the debugger is selected as a programmer rather than a debugger.
8. The communication between the debugger and the PC is sometimes interrupted. Reconnect to the debugger in MPLAB IDE.
9. The target application is sometimes corrupted or contains errors. For example, the project uses a regular linker script instead of the debugger version of the linker script (for example, using 18F8722.lkr instead of 18F8722i.lkr). Try to recompile and reprogram the target application. Then start the power-on reset of the target device.
10. Other configuration settings conflict with debugging operations. Any configuration settings that prevent the target device from executing code will also prevent the debugger from placing the code in debug mode.
11. The debugger cannot always perform the requested operation. For example, if the target application is currently running, the debugger cannot set a breakpoint.
Other matters to consider
1. The error may be a one-time problem. Try this again.
2. Under normal circumstances, it may be a programming problem. Let's do an experiment, switch to programmer mode and use
The simplest application (for example, the program used to illuminate the LEDs) to program the target device. If the program is not running, then you know that there is a problem with the target settings.
3. It is possible that the target device is damaged in some way (for example, overcurrent). The development environment is difficult to be compatible with components. Consider trying other target devices.
4. Microchip Technology Inc. provides a number of demo boards to support most of its microcontrollers. Consider using one of these known working applications to check that the MPLAB ICD 3 In-Circuit Debugger is functioning correctly. Or use the self-test board to check the debugger itself.
5. Check the debugger's debug operations to make sure the application settings are correct (Chapter 2, "How it works").
6. If the problem persists, please contact Microchip.
Fourth, internal error correction measuresInternal errors are not desirable and should not happen. They are primarily used for internal development of Microchip. The most likely cause is the installer corruption (Section 7.3.4, “Installer Damage Corrective Actionsâ€). Another possible cause is the exhaustion of system resources.
1. Try restarting the system to free up storage space.
2. Make sure you have the right amount of free space on your hard drive (and not too much disk fragmentation).
If the problem persists, please contact Microchip.
220W Medical Power Supply,220W Medical Device Power Supply,220W Medical Power Adapter,220W Rade Power Supplies
Shenzhen Longxc Power Supply Co., Ltd , https://www.longxcpower.com