User`s guide

CPU32 Emulation 145
Chapter 8: Using the Analysis Probe and Emulation Module Together
Triggering the Logic Analyzer from the Emulation Module
using a state analyzer on the processor bus the status may never
change upon receiving the emulation module trigger (analysis arm).
This occurs because the qualified processor clock needed to switch the
state analyzer to the next state is stopped. For example, the state
analyzer before the arm event may have a status of “Occurrences
Remaining in Level 1: 1” and after the arm event it may have the same
status of “Occurrences Remaining in Level 1: 1”.
7
If necessary, in the logic analyzer window, click
Stop
to complete
the measurement.
If you are using a timing analyzer or oscilloscope the measurement
should complete automatically when the processor halts. If you are
using a state logic analyzer, click
Stop
if needed to complete the
measurement.
To trigger the analyzer when the processor
reaches a breakpoint
This measurement is exactly like the previous one, but with the one
additional complexity of setting breakpoints. Be aware that setting
breakpoints may cause a false trigger and that the breakpoints set may
not be valid after a reset.
Remember: if you are only using a state analyzer to capture the
processor bus then it will be much simpler to use “Tracing until
processor halts” as described on page 140.
1
Set the logic analyzer to trigger on
anystate
.
2
Set the trigger point to
center
or
end
.
3
In the Intermodule window, click on the logic analyzer you want
to trigger and select the emulation module.
The logic analyzer is now set to trigger on a processor halt.
4
Set the breakpoint.