HP MC68360 User Manual page 243

of trig1 may be ignored until the critical routine is completed (when using a
foreground monitor).
3 If you are using a foreground monitor, enter the following additional pod
commands to prevent the trace memory from capturing monitor execution. The
following example commands will obtain this result in some emulators:
Settings→Pod Command Keyboard
trng addr=<address range occupied by your monitor> (trigger on range address
= <address range>)
where <address range> is expressed as <first addr>..<last addr>
tsto !r (trace store not range)
Click the suspend softkey
Note that "trng addr=<addr>..<addr>" means define an address range for the
analyzer; "tsto !r" means store all trace activity except activity occurring in the
defined address range.
4 Start the analyzer trace with the command, Trace→Again
5 Start your program running using Execution→Run→from(), from Transfer
Address, or from Reset, as appropriate.
The Trace→Again (or trace again) command starts the analyzer trace with the
most recent trace specifications (including the pod_command specifications you
entered). The trace command cannot be used by itself because it defaults the "bc
-e trig1", "trng addr=...", and "tsto !r" specifications, returning them to their default
values before the trace begins.
You can see the progress of your trace with the command, Display→Status. A
line in the Trace Status listing will show how many states have been captured.
6 The notation "trig1 break" usually followed by "Emulation trace complete" will
appear on the status line. If "trig1 break" remains on the status line without
"Emulation trace complete", manually stop the trace with the command:
Trace→Stop
You must wait for the notation "trig1 break" and/or "Emulation trace complete" to
appear on the status line; this ensures the trace memory is filled during the trace
(except for the unfilled space you specified in Step 2 above).
Chapter 7: Using the Emulation-Bus Analyzer
Making Complex Trace Measurements
223