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.
No power to the target board.
Check the power cable connection to the target or the emulator if powered by the emulator.
Incorrect VDD voltage. The VDD voltage is outside the specifications for this
device. See the device programming specification for details.
Physical disconnect. The debugger has become physically disconnected from the
computer and/or the target board. Check the communications cables’ connections.
Communications lost. The PC to
emulator communication has somehow been
interrupted. Reconnect to the emulator in MPLAB X IDE.
Device not seated. The device
is not properly seated on the target board. If the emulator is properly connected and the target board is powered, but the
device is absent or not plugged in completely, you may receive the message: Target
Device ID (0x0) does not match expected Device ID (0x%x) , where %x is the expected
device ID.
Device is code-protected. Check your Configuration bits settings for code
protection.
No device debug circuitry. The
production device may not have debugging capabilities. Use a Processor Extension Pak
(DS50001292) or Emulator Extension Pak (DS50002243) as required.
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.
Incorrect programming pins. The PGC/PGD pin pairs are not correctly
programmed in your Configuration bits (for devices with multiple PGC/PGD pin
pairs).
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.
Incorrect brown-out voltage. Brown-out Detect voltage is greater than the
operating voltage VDD. This means the device is in Reset and cannot be
debugged.
Incorrect connections. Review the guidelines in Target Connections for the correct
communication connections.
Invalid request. The emulator cannot always perform the action requested.
For example, the emulator cannot set a breakpoint if
the target application is currently running.
The online versions of the documents are provided as a courtesy. Verify all content and data in the device’s PDF documentation found on the device product page.
