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 on the target board - Check the power cable connection.
  3. Incorrect VDD 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 communication 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 (POR) 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 VDD. This means the device is on Reset and cannot be debugged.
  13. Incorrect connections - For more details, see Operations.
​

  Return to Top

© 2024 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.