User manual

 iSYSTEM, September 2014 15/23
9.3 Trace Examples
Analyzer window is opened from the View menu.
Before using trace for the first time please refer to winIDEA Contents Help, Analyzer Window section
(or alternatively to the standalone Analyzer.pdf document).
A screenshot of the Trigger dialog shows that any trigger item can also function as a qualifier, as a
Trace On or Off switch, or as an input to the Trigger Sequence Engine coupled with an event counter.
Trace Trigger
Example 1: Trace records the program execution (instructions, no data accesses) until the CPU is
stopped.
First example explains how to record a complete program flow either from the application or trace start
on or up to the moment, when the program stops. In first case, the trace would record and display
program flow from the start until the trace buffer is full. Alternatively, the trace can stop recording on a
program stop. The ‘Continuous mode’ option allows roll over of the trace buffer, which results in the
trace recording up to the moment when the application stops. In practice, the trace displays the
program flow just before the program stops, for instance, due to a breakpoint hit or due to the
Debug/Stop command issued by the user.
 Use ‘Record everything’ operation type in the ‘Analyzer’ window and make sure that ‘Continuous
mode’ is configured to ensure that the trace buffer rolls over while recording the running program.
The trace will stop as soon as the CPU is stopped.
 Define reasonable buffer size depending on the required depth of the trace record. Have in mind
that a smaller buffer uploads faster. You can start with e.g. 16MB.