6.1 How Does it Work?

What's in the silicon that allows it to communicate with the MPLAB Snap In-Circuit Debugger?

MPLAB Snap 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, that is, the debugger doesn’t ‘steal’ any cycles from the target device.

Does the MPLAB Snap 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.

Does the MPLAB Snap In-Circuit Debugger have complex breakpoints?

Yes. You can break based on a value in a data memory location. You can also do sequenced breakpoints, where several events have to occur before it breaks. However, you can only do two sequences. You can also do the AND condition and do PASS counts.

Is the MPLAB Snap In-Circuit Debugger optoisolated or electrically isolated?

No. You cannot apply a floating or high voltage (120V) to the current system.

Will the MPLAB Snap In-Circuit Debugger 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 device running at any speed?

The MPLAB Snap In-Circuit Debugger is capable of debugging at any device speed as specified in the device’s data sheet.