MPLAB
®
ICD 4 User’s Guide
DS50002596A-page 54 2017 Microchip Technology Inc.
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 ICD 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 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 ICD 4 In-Circuit Debugger was unable to perform a debugging operation.
There are numerous reasons why this might occur. See Chapter 4. “Troubleshooting
First Steps”.
6.3.7 Internal Error Actions
Internal errors are not expected and should not happen. They are 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 Support.
6.4 INFORMATION MESSAGES
MPLAB ICD 4 In-Circuit Debugger informational messages are listed below:
ICD4Info0001: ICD4 is functioning properly. If you are still having problems with
your target circuit please check the Target Board Considerations section of the
online Help.
See Section B.7 “Target Board Considerations”.
To Next Page
Loading...
Need help?
General
