13.07.2015 Views

MPLAB ICD 3 In-Circuit Debugger User's Guide

MPLAB ICD 3 In-Circuit Debugger User's Guide

MPLAB ICD 3 In-Circuit Debugger User's Guide

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>MPLAB</strong> ® <strong>ICD</strong> 3 IN-CIRCUITDEBUGGER USER’S GUIDEChapter 6. Frequently Asked Questions (FAQs)6.1 INTRODUCTION6.2 HOW DOES IT WORKLook here for answers to frequently asked questions about the <strong>MPLAB</strong> <strong>ICD</strong> 3 in-circuitdebugger system.• How Does It Work• What’s Wrong• What's in the silicon that allows it to communicate with the <strong>MPLAB</strong> <strong>ICD</strong> 3in-circuit debugger?<strong>MPLAB</strong> <strong>ICD</strong> 3 in-circuit debugger can communicate with Flash silicon via theICSP interface. It uses the debug executive located in test memory.• How is the throughput of the processor affected by having to run the debugexecutive?• The debug executive doesn't run while in Run mode, so there is no throughputreduction when running your code, i.e., the debugger doesn’t ‘steal’ any cyclesfrom the target device. How does the <strong>MPLAB</strong> <strong>ICD</strong> 3 in-circuit debuggercompare with other in-circuit emulators/debuggers?Please refer to Section 2.2 “<strong>MPLAB</strong> <strong>ICD</strong> 3 <strong>In</strong>-<strong>Circuit</strong> <strong>Debugger</strong> vs. <strong>MPLAB</strong> ICE2000/4000 <strong>In</strong>-<strong>Circuit</strong> Emulators” and Section 2.3 “<strong>MPLAB</strong> <strong>ICD</strong> 3 <strong>In</strong>-<strong>Circuit</strong><strong>Debugger</strong> vs. <strong>MPLAB</strong> <strong>ICD</strong> 2 <strong>Debugger</strong>”.• How does <strong>MPLAB</strong> IDE interface with the <strong>MPLAB</strong> <strong>ICD</strong> 3 in-circuit debugger toallow more features than <strong>MPLAB</strong> <strong>ICD</strong> 2?<strong>MPLAB</strong> <strong>ICD</strong> 3 in-circuit debugger communicates using the debug executivelocated in the test area. The debug exec is streamlined for more efficient communication.The debugger contains an FPGA, large SRAM Buffers (1Mx8) and aHigh Speed USB interface. Program memory image is downloaded and is containedin the SRAM to allow faster programming. The FPGA in the debuggerserves as an accelerator for interfacing with the device in-circuit debuggermodules.• On the <strong>MPLAB</strong> ICE 2000/4000 debuggers, the data must come out on thebus in order to perform a complex trigger on that data. Is this also requiredon the <strong>MPLAB</strong> <strong>ICD</strong> 3 in-circuit debugger? For example, could I halt based ona flag going high?The <strong>MPLAB</strong> ICE 2000/4000 debuggers use a special debugger chip (-ME) formonitoring. There is no -ME with the <strong>MPLAB</strong> <strong>ICD</strong> 3 in-circuit debugger so thereare no busses to monitor externally. With the <strong>MPLAB</strong> <strong>ICD</strong> 3 in-circuit debugger,rather than using external breakpoints, the built-in breakpoint circuitry of thedebug engine is used – the busses and breakpoint logic are monitored inside thepart.© 2008 Microchip Technology <strong>In</strong>c. DS51766A-page 49

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!