User Guide

MPLAB
®
PICkit™ 4 User’s Guide
DS50002751C-page 48  2018 Microchip Technology Inc.
6.3 GENERAL CORRECTIVE ACTIONS
These general corrective actions may solve your problem:
• Read/Write Error Actions
• Debugger-to-Target Communication Error Actions
• Debugger-to-computer Communication Error Actions
• Corrupted Installation Actions
• USB Port Communication Error Actions
• Debug Failure Actions
• Internal Error Actions
6.3.1 Read/Write Error Actions
If you receive a read or write error:
1. Did you hit Debug>Reset
? This may produce read/write errors.
2. Try the action again. It may be a one-time error.
3. Ensure that the target is powered and at the correct voltage levels for the device.
See the device data sheet for required device voltage levels.
4. Ensure that the debugger-to-target connection is correct (PGC and PGD are
connected.)
5. For write failures, ensure that “Erase all before Program” is checked on the
Program Options for the debugger (see Section A.3.2 “Debug”).
6. Ensure that the cable(s) are of the correct length.
6.3.2 Debugger-to-Target Communication Error Actions
The MPLAB PICkit 4 In-Circuit Debugger and the target device are out-of-sync with
each other.
1. Select Debug>Reset
and then try the action again.
2. Ensure that the cable(s) used are the correct length.
6.3.3 Debugger-to-computer Communication Error Actions
The MPLAB PICkit 4 In-Circuit Debugger and MPLAB X IDE are out-of-sync with each
other.
1. Unplug and then plug in the debugger.
2. Reconnect to the debugger.
3. Try the operation again. It is possible the error was a one time event.
4. The version of MPLAB X IDE installed may be incorrect for the version of firm-
ware loaded on the MPLAB PICkit 4 In-Circuit Debugger. Follow the steps out-
lined in Section 6.3.4 “Corrupted Installation Actions”.
6.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 computer.
2. Reinstall the desired MPLAB X IDE version.
3. If the problem persists contact Microchip.