Motorola CPU32 User's Guide download pdf (Page 145)

144 CPU32 Emulation

Chapter 8: Using the Analysis Probe and Emulation Module Together

Triggering the Logic Analyzer from the Emulation Module

If you define a trigger on some state and the debugger happens to read

the same state, then you may falsely trigger your analyzer

measurement. In summary, when you are making an analysis

measurement be aware that the debugger could be impacting your

measurement.

To trigger the analyzer when the processor

halts

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.

Set the logic analyzer to trigger on

anystate

Set the trigger point to

center

end

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.

Click

Group Run

to start the analyzer(s).

Click Run in the Emulation Control Interface or use your

debugger to start the target processor running.

Clicking

Group Run

will not start the emulation module. The

emulation module run, break, step, and reset are independent of the

Group Run of the analyzers.

Wait for the Run Control window in the Emulation Control

Interface or the status display in your debugger to show that the

processor has stopped.

The logic analyzer will store states up until the processor stops, but

may continue running.

You may or may not see a “slow clock” error message. In fact, if you are

1 2 ... 140 141 142 143 144 145 146 147 148 149 150 ... 204 205

No comments

Motorola CPU32 User's Guide Page 145