Table of Contents
Advertisement
Specifying a Restart
Term
2-24 Getting Started
Notice the states that contain "sq adv" in the line number column.
These are the states associated with (or captured for) each
sequence term. Just as the trigger state is always stored in trace
memory, the states captured in the sequence are always stored if
the trace buffer is deep enough.
Because the trigger is the last sequence term, the remaining states
stored after the trigger state are writes to the RESULTS area.
When using the analyzer's sequencer, an additional sequence
restart term is also allowed. This restart is a "global restart"; that
is, it applies to all the sequence terms.
The restart term is a state which, when captured before the
analyzer has found the trigger state, causes the sequencing to start
from the beginning again. You can use the restart term to make
certain some state does not occur in the sequence that triggers the
analyzer.
For example, you may have noticed in the previous trace that a
write to the RESULTS area occurred between the TWO_THREE
and CALLER_3 states in the sequence and that the state count
associated with WRITE_NUMBER state shows that AGAIN
occurred before the trigger. What was actually captured in the
previous trace was the flow of execution where TWO_THREE
occurs, then CALLER_2, then WRITE_NUMBER, then a
prefetch of CALLER_3 on the return from WRITE_NUMBER,
and then the capture of WRITE_NUMBER occurred the next time
through the program. By specifying a restart on CALLER_2, you
can fix the previous trace command so that only the flow of
execution from TWO_THREE to CALLER_3 is captured.
trace find_sequence CALLER_0 occurs 8
then TWO_THREE
then CALLER_3
restart CALLER_2
trigger about WRITE_NUMBER
only range RESULTS thru RESULTS+0ffh <RETURN>
Advertisement
Table of Contents
