User Guide

MPLAB
®
PICkit™ 4 User’s Guide
DS50002751C-page 34  2018 Microchip Technology Inc.
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 following 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. The production device may not have debugging
capabilities. Use a debug header instead. (See the “Processor Extension Pak
and Debug Header Specification” (DS50001292) in “Recommended Supple-
mental Reference.”
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. The PGC/PGD pin pairs are not correctly pro-
grammed 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. Review the guidelines in Chapter 2. “Operation” for
the correct communication connections.
14. Invalid request. The debugger cannot always perform the action requested. For
example, the debugger cannot set a breakpoint if the target application is cur-
rently running.
4.4 OTHER THINGS TO CONSIDER
4.4.1 General
1. It is possible the error was a one-time event. Try the operation again.
2. There may be a problem programming in general. As a test, switch to Run mode
using the icon and program the target with the simplest application possible
(e.g., a program to blink an LED). If the program will not run, then you know that
something is wrong with the target setup.
3. It is possible that the target device has been damaged in some way (e.g., over
current.) Development environments are notoriously hostile to components.
Consider trying another target board.
4. Microchip Technology Inc. offers demonstration boards to support most of its
microcontrollers. Consider using one of these applications, which are known to
work, to verify correct MPLAB PICkit 4 In-Circuit Debugger functionality.
5. Review debugger setup to ensure proper application setup. For more informa-
tion, see Chapter 2. “Operation”.
6. Your program speed may be set too high for your circuit. In MPLAB X IDE, go to
File>Project Properties
, select PICkit 4 in Categories, then Program Options in
Option categories, Program Speed and select a slower speed from the
drop-down menu. The default is Normal (see figure below).