VOLTAGES=Voltages
WOULD_YOU_LIKE_TO_CONTINUE=Would you like to continue?
WRONG_PICKit 4_FLAVOR=Your PICKit 4 hardware needs updating please contact PICKit
[email protected] to get a replacement.
8.2
General Corrective Actions
8.2.1
Read/Write Error Actions
If you receive a read or write error:
1.
Did you click
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
).
6.
Ensure that the cable(s) are of the correct length.
8.2.2
Debugger to Target Communication Error Actions
If the MPLAB PICkit 4 In-Circuit Debugger and the target device are
not
communicating with each other:
1.
Select
Debug > Reset
and then try the action again.
2.
Ensure that the cable(s) are of the correct length.
8.2.3
Debugger to Computer Communication Error Actions
If the MPLAB PICkit 4 In-Circuit Debugger and MPLAB X IDE or MPLAB IPE are not communicating 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 or MPLAB IPE installed may be incorrect for the version of firmware loaded on
theMPLAB PICkit 4 In-Circuit Debugger. Follow the steps outlined in
8.2.4 Corrupted Installation Actions
5.
There may be an issue with the computer USB port. See section
8.2.5 USB Port Communication Error
8.2.4
Corrupted Installation Actions
The problem is most likely caused by a incomplete or corrupted installation of MPLAB X IDE or MPLAB IPE.
1.
Uninstall all versions of MPLAB X IDE or MPLAB IPE from the computer.
2.
Reinstall the desired MPLAB X IDE or MPLAB IPE version.
3.
If the problem persists, contact Microchip Support.
8.2.5
USB Port Communication Error Actions
The problem is most likely caused by a faulty or non-existent communications port.
1.
Reconnect to the MPLAB PICkit 4 In-Circuit Debugger.
2.
Make sure the debugger is physically connected to the computer on the appropriate USB port.
3.
Make sure the appropriate USB port has been selected in the debugger options (see
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.
Error Messages
©
2020 Microchip Technology Inc.
User Guide
DS50002751D-page 47
