Manualshelf

User Guide

ManualsBrandsWaveshare ManualsPICMPLAB PICkit 4 In-Circuit Debugger
31323334353637383940
MPLAB
®
PICkit™ 4 USER’S GUIDE
2018 Microchip Technology Inc. DS50002751C-page 33
Chapter 4. Troubleshooting First Steps
4.1 INTRODUCTION
If you are having problems with MPLAB PICkit 4 In-Circuit Debugger operation, start
here.
• Some Questions to Answer First
• Top Reasons Why You Can’t Debug
• Other Things to Consider
- General
- How to Invoke the Bootloader Mode
- How to Use the Hardware Tool Emergency Boot Firmware Recovery Utility
4.2 SOME QUESTIONS TO ANSWER FIRST
1. What device are you working with? Often an upgrade to a newer version of
MPLAB X IDE is required to support newer devices.
2. Are you using a Microchip demo board or one of your own design? Have
you followed the guidelines for resistors/capacitors for communications
connections? See Chapter 2. “Operation”.
3. Have you powered the target? The debugger cannot power the target if greater
than 50 mA. For applications needing more than 50 mA, use an external power
supply to power the target board.
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
computer.)
5. Are you using the USB cable shipped with the debugger? Other USB cables
may be of poor quality, too long or do not support USB communication.
4.3 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 to the target board. Check the power cable connection.
3. Incorrect V
DD 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 communications cables’
connections.
5. Communications lost. Debugger to PC communication has somehow been
interrupted. Reconnect to the debugger in MPLAB X IDE.