ICE4000 Microchip Technology, ICE4000 Datasheet - Page 47

• Manufacturer Part Number: ICE4000
• Description: EMULATOR MPLAB-ICE 4000 POD
• Manufacturer: Microchip Technology
• Series: MPLAB® ICE 4000r
• Type: Microcontrollerr

Specifications of ICE4000

• Contents: ICE4000 POD, Parallel and USB Cable, Power Supply, MPLAB IDE CD and Documentation
• Interface Type: USB
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• For Use With/related Products: dsPIC30F & PIC18 Series
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant

 2004 Microchip Technology Inc.
To perform a continuous filter trace, check the Infinite Events check box. Infinite Events
is a special condition of capturing a filtered trace. As the trace buffer gets full, old data
is discarded and new data is read First In, First Out (FIFO). This is useful in some
special cases;
1. Capturing filtered events up until a user halt. You may wish to see the data
2. Use “Reload Data” as you are filtering events to get a trace display of the current
3. Sometimes a system misbehaves after a long period of time. Infinite events will
4. Filtered traces can output a series of triggers on the TRGOUT connector. If you
Trigger Position does not apply when filtering, as is Halt on Trigger and Halt on Trace
Buffer Full.
otherwise, the trace buffer will capture the cycle that executes after the cycle that
caused the trigger.
Also, performing a Filter Trace on Data Memory access is not recommended, since the
traced data will be one cycle after the trigger specification.
Ignore FNOP Cycles should not be specified when performing a Filter Trace;
Note: Since Ignore FNOP Cycles should not be specified with a Filter Trace,
Note: When triggering on multiple events, keep in mind that triggers on data
collected up until the system was manually halted.
trace buffer. Continue to select “Reload Data” to upload another capture of the
current data being filtered. This is useful if you are monitoring a system in real
time and just want to see what’s going on without halting the system.
continue collecting the data in your critical routine until the application is halted.
Often the misbehaving state will get into a place in the program where no events
will be collected. The trace buffer will then be a record of the data of interest
before the “glitch.”
wanted to trigger an external logic analyzer every time a particular routine is
executed, this can be achieved by filtering on that address and setting the
appropriate triggering in the Trigger In/Out tab. Infinite Events, in this case, will
allow continuous triggers to be generated on the TRGOUT connector.
prefetches will cause the trigger to fire.
memory accesses are skewed two cycles from the instructions that caused
them.
Complex and Internal Triggers
DS51490A-page 41