HP 64780A, User Manual

Page: 242 / 546

To capture a continuous stream of program
execution no matter how large your program
The following example can be performed in emulation systems using the deep
analyzer (it cannot be done with the 1K analyzer). It shows you how to capture all
of the execution of your target program. You may wish to capture target program
execution for storage, for future reference, and/or for comparison with execution
after making program modifications. The execution of a typical target program
will require more memory space than is available in the trace memory of an
analyzer. This example shows you how to capture all of your target program
execution while excluding unwanted execution of the emulation monitor.
1 Choose Trace
→
Display Options ..., and in the dialog box, enter 0 or the total
depth of your deep analyzer trace memory in the entry field beside Unload Depth.
Then click OK or Apply. This sets unload depth to maximum.
2 For this measurement, the analyzer will drive trig1 and the emulator will receive
trig1 from the trigger bus inside the card cage. The trig1 signal is used to cause the
emulator to break to its monitor program shortly before the trace memory is filled.
This use of trig1 is not supported in workstation interface commands. Therefore,
terminal interface commands (accessible through the pod command feature) must
be used. Enter the following commands:
Settings
→
Pod Command Keyboard
tgout trig1 -c <states before end of memory> (trigger output trig1 before trace
complete)
bc -e trig1 (break conditions enabled on trig1)
Click the suspend softkey
Note that "tgout trig1 -c <states...>" means generate trig1 as an output when the
state that is <states...> before the end of the trace memory is captured in the trace
memory; "bc -e trig1" means enable the emulator to break to its monitor program
when it receives trig1.
Select a value for <states before end of memory> that allows enough time and/or
memory space for the emulator to break to its monitor program before the trace
memory is filled. Otherwise, some of your program execution will not be captured
in the trace. Many states may be executed before the emulation break occurs,
depending on the state of the processor when the trig1 signal arrives. Also, if your
program executes critical routines in which interrupts are masked, the occurrence
Chapter 7: Using the Emulation-Bus Analyzer
Making Complex Trace Measurements
222