Table of Contents
Advertisement
Chapter 7: Using the Emulation Analyzer
Using the Sequencer
To specify a global restart state
• Use the restart option to the trace command.
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 search for the sequence of states to start over. You can use
the restart term to make certain some state does not occur in the sequence that
triggers the analyzer.
Examples
In the demo program, suppose you wish to trigger on the following sequence of
events: the "save_points" function, the "interrupt_sim" function, and the "do_sort"
function. However, you only want to trigger when the "interrupt_sim" calls the
"do_sort" function. In other words, if the "proc_specific" function is entered before
the "do_sort" function is entered, you know "interrupt_sim" did not call "do_sort"
this time, and the analyzer should start searching again from the beginning.
Again, suppose you wish to store only opcode fetches of the assembly language
PUSH BP instruction (whose opcode is 55H).
To set up this sequencing trace specification, enter the following trace command.
trace find_sequence save_points status exec then
interrupt_sim status exec restart proc_specific status
exec trigger about do_sort status exec only data 0x55h
status procopf <RETURN>
set source off <RETURN>
217
Advertisement
Table of Contents
