Microchip Technology PICkit 3 Starter Kit DV164130 DV164130 사용자 설명서

© 2009 Microchip Technology Inc.

DS51795A-page 35

If you are having problems with PICkit 3 programmer/debugger operation, start here.

• The 5 Questions to Answer First

• Top 10 Reasons Why You Can’t Debug

• Other Things to Consider

1.

What device are you working with? Often an upgrade to a newer version of 
MPLAB IDE is required to support newer devices. That is, yellow light = untested 
support.

2.

Are you using a Microchip demo board or one of your own design? Have you fol-
lowed the guidelines for resistors/capacitors for communications connections? 
See Chapter 2. “Theory of Operation”.

3.

Have you powered the target? The debugger cannot power the target if greater 
than 30 mA.

4.

Are you using a USB hub in your set up? Is it powered? If you continue to have 
problems, try using the debugger without the hub (plugged directly into the PC.)

5.

Are you using the standard communication cable (RJ-11) shipped with debug-
ger? If you have made a longer cable, it can cause communications errors.

1.

The oscillator is not working. Check your Configuration bits setting for the 
oscillator.

2.

The target board is not powered. Check the power cable connection.

3.

The debugger has become physically disconnected from the PC and/or the tar-
get board. Check the communications cables’ connections.

4.

The device is code-protected. Check your Configuration bit’s setting for code 
protection.

5.

You are trying to rebuild the project while in Release mode. Select Debug in the 
Build Configuration drop-down list on the project toolbar, then rebuild the project.

6.

The debugger is selected as a programmer, and not as a debugger, in MPLAB 
IDE.

7.

The debugger to PC communications has been interrupted. Reconnect to the 
debugger in MPLAB IDE.

8.

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.

9.

Other configuration settings are interfering with debugging. Any configuration 
setting that would prevent the target from executing code will also prevent the 
debugger from putting the code into debug mode.

10. The debugger cannot always perform the action requested. For example, the 

debugger cannot set a breakpoint if the target application is currently running.