HP 16600A Series User Manual page 214

Chapter 9: Using the Analysis Probe and Emulation Module Together
Triggering the Logic Analyzer from the Emulation Module
For example, suppose you have the following IMB measurement set up:
Clicking the Group Run button (at the very top of the Intermodule
window or a logic analyzer window) will start the analyzer running. The
analyzer will then wait for an arm signal. Now when the emulation
module transitions into "Monitor" from "Running" (or from "Reset"), it
will send the arm signal to the analyzer. If the emulation module is "In
Monitor" when you click Group Run, you will then have to go to the
emulation module or your debugger interface and manually start it
running.
Debuggers can cause triggers
Emulation module user interfaces may introduce additional states into
your analysis measurement and in some cases falsely trigger your
analysis measurement.
When a debugger causes your target to break into monitor it will
typically read memory around the program stack and around the
current program counter. This will generate additional states which
appear in the listing.
You can often distinguish these additional states because the time tags
will be in the ms and ms range. You can use the time tag information to
determine when the processor went into monitor. Typically the time
between states will be in the nanoseconds while the processor is
running and will be in the ms and ms range when the debugger has
halted the processor and is reading memory.
Not also that some debugger commands may cause the processor to
break temporarily to read registers and memory. These states that the
debugger introduces will also show up in you trace listing.
Solutions for CPU32 213