MPLAB
®
ICD 4 User’s Guide
DS50002596A-page 38 2017 Microchip Technology Inc.
4.3 TOP REASONS WHY YOU CAN’T DEBUG
1. Oscillator not working. Check your Configuration bits setting for the oscillator.
If you are using an external oscillator, try using an internal oscillator. If you are
using an internal PLL, make sure your PLL settings are correct.
2. No power to the target board. Check the power cable connection.
3. Incorrect V
DD voltage. The VDD voltage is outside the specifications for this
device. See the device programming specification for details.
4. Physical disconnect. The debugger has become physically disconnected from
the computer and/or the target board. Check the communications cables’
connections.
5. Communications lost. Debugger to PC communication has somehow been
interrupted. Reconnect to the debugger in MPLAB X IDE.
6. Device not seated. The device is not properly seated on the target board. If the
debugger is properly connected and the target board is powered, but the device
is absent or not plugged in completely, you may get the message:
Target Device ID (0x0) does not match expected Device ID (0x%x)
where %x is the expected device ID.
7. Device is code-protected. Check your Configuration bits settings for code
protection.
8. No device debug circuitry. You are trying to debug a production device that
does not have debugging capabilities. Use a debug header instead. (See the
“Processor Extension Pak and Debug Header Specification” (DS50001292) in
“Recommended Reading”.)
9. Application code corrupted. The target application has become corrupted or
contains errors. Try rebuilding and reprogramming the target application. Then
initiate a Power-On-Reset of the target.
10. Incorrect programming pins. You do not have the correct PGC/PGD pin pairs
programmed in your Configuration bits (for devices with multiple PGC/PGD pin
pairs).
11. Additional setup required. Other configuration settings are interfering with
debugging. Any configuration setting that would prevent the target from
executing code will also prevent the emulator from putting the code into Debug
mode.
12. Incorrect brown-out voltage. Brown-out Detect voltage is greater than the
operating voltage V
DD. This means the device is in Reset and cannot be
debugged.
13. Incorrect connections. You have not followed the guidelines in Chapter 2.
“Operation”.