Table of Contents
Advertisement
Chapter 7: Using the Emulation Analyzer
Using the Sequencer
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 finally the
"do_sort" function. Also, suppose you wish to store only opcode fetches of the
assembly language PUSH BP instruction (whose opcode is 55H) to show function
entry addresses.
To set up the sequencing trace specification, enter the following trace command.
trace find_sequence save_points status exec then
interrupt_sim status exec trigger about do_sort status
exec only data 0xx55h status procopf <RETURN>
set source off <RETURN>
Notice the states that contain "sq adv" in the first column (you may have to press
<PREV> in order to see the states captured prior to the trigger). 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.
Note that, when using a 80186 processor (with a 16-bit data bus), the trace
command above does not prestore all function entries because only low byte reads
of 55H are captured. You can qualify high byte reads of 55xxH or low byte reads
of 0xx55H by using the storage qualifier only data 0xx55h status procopf or data
55xxh status procopf.
216
Advertisement
Table of Contents
