DS51795A Datasheet, PDF (49/98 Pages) Microchip Technology – PICkit™ 3 Programmer/Debugger

Error Messages
8.3.1 Read/Write Error Actions
If you receive a read or write error:
1. Did you hit Abort? This may produce read/write errors.
2. Try the action again. It may 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 used are of the correct length.
8.3.2 Debugger-to-Target Communication Error Actions
The PICkit 3 programmer/debugger and the target device are out-of-sync with each
other.
1. Select Reset and then try the action again.
2. Ensure that the cable(s) used are the correct length.
8.3.3 Debugger-to-PC Communication Error Actions
The PICkit 3 programmer/debugger and MPLAB IDE are out-of-sync with each other.
1. Unplug and then plug in the debugger.
1. Reconnect to the debugger.
2. Try the operation again. It is possible the error was a one time glitch.
3. The version of MPLAB IDE installed may be incorrect for the version of firmware
loaded on the PICkit 3 programmer/debugger. Follow the steps outlined in
Section 8.3.4 “Corrupted Installation Actions”.
8.3.4 Corrupted Installation Actions
The problem is most likely caused by a incomplete or corrupted installation of MPLAB
IDE.
1. Uninstall all versions of MPLAB IDE from the PC.
2. Reinstall the desired MPLAB IDE version.
3. If the problem persists contact Microchip.
8.3.5 USB Port Communication Error Actions
The problem is most likely caused by a faulty or non-existent communications port.
1. Reconnect to the PICkit 3 programmer/debugger
2. Make sure the debugger is physically connected to the PC on the appropriate
USB port.
3. Make sure the appropriate USB port has been selected in the debugger Settings.
4. Make sure the USB port is not in use by another device.
5. If using a USB hub, make sure it is powered.
6. Make sure the USB drivers are loaded.
8.3.6 Debug Failure Actions
The PICkit 3 programmer/debugger was unable to perform a debugging operation.
There are numerous reasons why this might occur. See Section 6.3 “Top 10 Reasons
Why You Can’t Debug” and Section 6.4 “Other Things to Consider”.
© 2009 Microchip Technology Inc.
DS51795A-page 45