User Guide

MPLAB
®
PICkit™ 4 USER’S GUIDE
 2018 Microchip Technology Inc. DS50002751C-page 37
Chapter 5. Frequently Asked Questions (FAQs)
5.1 INTRODUCTION
Look here for answers to frequently asked questions about the MPLAB PICkit 4
In-Circuit Debugger system.
• How Does It Work
• What’s Wrong
5.2 HOW DOES IT WORK
• What's in the silicon that allows it to communicate with the MPLAB PICkit 4
In-Circuit Debugger?
MPLAB PICkit 4 In-Circuit Debugger can communicate with Flash silicon via the
ICSP™ interface. It uses the debug executive downloaded into program or test
memory.
• How is the throughput of the processor affected by having to run the debug
executive?
The debug executive doesn’t run while in Run mode, so there is no throughput
reduction when running your code, i.e., the debugger doesn’t ‘steal’ any cycles
from the target device.
• Does the MPLAB PICkit 4 In-Circuit Debugger have complex breakpoints
like other in-circuit emulators/debuggers?
No. But you can break based on a value in a data memory location or program
address.
• Is the MPLAB PICkit 4 optoisolated or electrically isolated?
No. You cannot apply a floating or high voltage (120V) to the current system.
• Will the MPLAB PICkit 4 slow down the running of the program?
No. The device will run at any device speed as specified in the data sheet.
• Is it possible to debug a dsPIC DSC running at any speed?
The MPLAB PICkit 4 is capable of debugging at any device speed as specified in
the device’s data sheet.
5.3 WHAT’S WRONG
• Performing a Verify fails after programming the device. Is this a
programming issue?
If Run Main Project icon ( )is selected, the device will automatically run
immediately after programming. Therefore, if your code changes the flash
memory, verification could fail. To prevent the code from running after
programming, select 'Hold in Reset'.