![HP 64700 series User Manual Download Page 48](http://html.mh-extra.com/html/hp/64700-series/64700-series_user-manual_161481048.webp)
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 R ESU LTS area.
Specifying a Restart
Term
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 R ESU LTS area occurred between the TWO_THR EE
and CALLER _3 states in the sequence and that the state count
associated with WR ITE_NUMBER state shows that AGAIN
occurred before the trigger. What was actually captured in the
previous trace was the flow of execution where TWO_THR EE
occurs, then CALLER _2, then WR ITE_NUMBER , then a
prefetch of CALLER _3 on the return from WR ITE_NUMBER ,
and then the capture of WR ITE_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_THR EE 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 0ffh <RETURN>
2-24 Getting Started
Summary of Contents for 64700 series
Page 2: ......
Page 19: ...Tables Table 9 1 Summary of Commands 9 4 Table 9 2 Command Assignments 9 5 Contents 11 ...
Page 20: ...1 Notes 12 Contents ...
Page 24: ...1 Notes 1 4 Introduction ...
Page 106: ...1 Notes 4 36 Performance Measurements ...
Page 118: ...Figure 5 8 True Demultiplexing 5 12 Using the External Analyzer ...
Page 128: ...1 Notes 6 6 Timing Introduction ...
Page 134: ...1 Notes 7 6 Timing Getting Started ...
Page 168: ...1 Notes 8 34 Timing Using the Analyzer ...
Page 201: ...1 find This command finds a trigger like event in trace memory Syntax Timing Commands 9 33 ...
Page 219: ...1 mark This command marks specified conditions in trace memory Syntax Timing Commands 9 51 ...
Page 254: ...1 trigger This command specifies trigger conditions Syntax 9 86 Timing Commands ...
Page 262: ...1 Notes 9 94 Timing Commands ...
Page 280: ...1 Notes B 16 Timing Diagrams and Outputs ...
Page 292: ...1 Notes C 12 Timing Messages ...