User manual

Error Messages
 2013 Microchip Technology Inc. DS52116A-page 55
8.3.2 Debugger-to-Target Communication Error Actions
The PICkit 3 In-Circuit Debugger/Programmer and the target device are out-of-sync
with each other.
1. Select Reset and then try the action again.
2. Ensure that the cable(s) in use are the correct length.
8.3.3 Debugger-to-PC Communication Error Actions
The PICkit 3 In-Circuit Debugger/Programmer and MPLAB X IDE are out-of-sync with
each other.
1. Unplug and then plug in the debugger.
1. Reconnect to the debugger.
2. Try the operation again. It is possible that the error was a one time glitch.
3. The version of MPLAB X IDE installed may be incorrect for the version of firm-
ware loaded on the PICkit 3 In-Circuit Debugger/Programmer. Follow the steps
outlined in Section 8.3.4 “Corrupted Installation Actions”.
8.3.4 Corrupted Installation Actions
The problem is most likely caused by a incomplete or corrupted installation of MPLAB
X IDE.
1. Uninstall all versions of MPLAB X IDE from the PC.
2. Reinstall the desired MPLAB X IDE version.
3. If the problem persists contact Microchip.
8.3.5 USB Port Communication Error Actions
The problem is most likely caused by a faulty or non-existent communications port.
1. Reconnect to the PICkit 3 In-Circuit Debugger/Programmer
2. Make sure the debugger is physically connected to the PC on the appropriate
USB port.
3. Make sure the appropriate USB port has been selected in the debugger Settings.
4. Make sure the USB port is not in use by another device.
5. If using a USB hub, make sure it is powered.
6. Make sure the USB drivers are loaded.
8.3.6 Debug Failure Actions
The PICkit 3 In-Circuit Debugger/Programmer was unable to perform a debugging
operation. There are numerous reasons why this might occur. See Section 6.3 “Top
10 Reasons Why You Can’t Debug” and Section 6.4 “Other Things to Consider”.
8.3.7 Internal Error Actions
Internal errors are unexpected and should not happen. They are primarily used for
internal Microchip development.
The most likely cause is a corrupted installation (Section 8.3.4 “Corrupted
Installation Actions”).
Another likely cause is exhausted system resources.
1. Try rebooting your system to free up memory.
2. Make sure you have a reasonable amount of free space on your hard drive (and
that it is not overly fragmented.)
If the problem persists contact Microchip.