User manual

MPLAB
®
X PICkit™ 3 User’s Guide
DS52116A-page 54  2013 Microchip Technology Inc.
8.2.3 Debug Failure Errors
The target device is not ready for debugging. Please check your configuration bit
settings and program the device before proceeding.
You will receive this message if you try to Run before programming your device. If you
receive this message after trying to Run, or immediately after programming your
device, please refer to Section 8.3.6 “Debug Failure Actions”.
The device is code protected.
The device on which you are attempting to operate (read, program, blank check or
verify) is code protected, i.e., the code cannot be read or modified. Check your
Configuration bits settings for code protection.
Disable code protection, set or clear the appropriate Configuration bits in code or in the
Configuration Bits window according to the device data sheet. Then erase and
reprogram the entire device.
8.2.4 Miscellaneous Errors
PICkit 3 is busy. Please wait for the current operation to finish.
If you receive this error when attempting to deselect the debugger as a debugger or
programmer:
1. Wait - give the debugger time to finish any application tasks. Then try to deselect
the debugger again.
2. Select Halt to stop any running applications. Then try to deselect the debugger
again.
3. Unplug the debugger from the PC. Then try to deselect the debugger again.
4. Shut down MPLAB X IDE.
8.3 GENERAL CORRECTIVE ACTIONS
These general corrective actions may solve your problem:
• Read/Write Error Actions
• Debugger-to-Target Communication Error Actions
• Debugger-to-PC Communication Error Actions
• Corrupted Installation Actions
• USB Port Communication Error Actions
• Debug Failure Actions
• Internal Error Actions
8.3.1 Read/Write Error Actions
If you receive a read or write error:
1. Did you hit Abort? This can produce read/write errors.
2. Try the action again. It could be a one-time error.
3. Ensure that the target is powered and at the correct voltage levels for the device.
See the device data sheet for required device voltage levels.
4. Ensure that the debugger-to-target connection is correct (PGC and PGD are
connected.)
5. For write failures, ensure that “Erase all before Program” is checked on the
Program Memory tab of the Settings dialog.
6. Ensure that the cables being used are of the correct length.