User Guide

Error Messages
 2018 Microchip Technology Inc. DS50002751C-page 49
6.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 MPLAB PICkit 4 In-Circuit Debugger
2. Make sure the appropriate USB port has been selected in the debugger options
(see Section A.3 “Debugger Options Selection”).
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.
6.3.6 Debug Failure Actions
The MPLAB PICkit 4 In-Circuit Debugger was unable to perform a debugging opera-
tion. There are numerous reasons why this might occur (see Section 4.3 “Top Rea-
sons Why You Can’t Debug” and Section 4.4 “Other Things to Consider”).
6.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 6.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.