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
Summary of Contents for 64780A
Page 1: ...Graphical User Interface User s Guide MC68360 68EN360 Emulator Analyzer HP 64780A ...
Page 20: ...xx ...
Page 21: ...Part 1 Quick Start Guide 1 ...
Page 23: ...1 Getting Started 3 ...
Page 45: ...Part 2 Using The Emulator 25 ...
Page 47: ...2 Plugging into a Target System 27 ...
Page 55: ...Chapter 2 Plugging into a Target System Plugging into the Motorola QUADS Target System 35 ...
Page 59: ...3 Starting and Exiting HP 64700 Interfaces 39 ...
Page 69: ...4 Entering Commands 49 ...
Page 103: ...5 Configuring the Emulator 83 ...
Page 122: ...102 ...
Page 123: ...6 Using the Emulator 103 ...
Page 193: ...7 Using the Emulation Bus Analyzer How to record program execution in real time 173 ...
Page 249: ...8 Making Software Performance Measurements 229 ...
Page 279: ...9 Making Coordinated Measurements 259 ...
Page 295: ...Part 3 Reference 275 ...
Page 297: ...10 Setting X Resources 277 ...
Page 312: ...292 ...
Page 313: ...11 Emulator Analyzer Interface Commands 293 ...
Page 391: ...set Chapter 11 Emulator Analyzer Interface Commands set 371 ...
Page 405: ... SYMB Chapter 11 Emulator Analyzer Interface Commands SYMB 385 ...
Page 422: ...402 ...
Page 460: ...440 ...
Page 461: ...Part 4 Concept Guide 441 ...
Page 463: ...13 Concepts of the EMSIM and EMRAM 443 ...
Page 471: ...Part 5 Installation and Service Guide 451 ...
Page 473: ...14 Installation 453 ...
Page 491: ...Chapter 14 Installation Verifying the Installation 471 ...
Page 493: ...15 Installing Updating Emulator Firmware 473 ...
Page 500: ...480 ...
Page 516: ...496 ...
Page 540: ...520 ...