To Use Two State Analyzers To Monitor The Activity Of Coprocessors In A Target System - HP 16500B User Manual

Intermodule Measurements
To use two state analyzers to monitor the activity of coprocessors in a target
system
To use two state analyzers to monitor the activity of
coprocessors in a target system
Select the Intermodule menu.
1
Select the first state analyzer from the Modules list and set it to
2
Group Run. Select the second state analyzer and set it to respond to
the arm signal from the first analyzer.
Select the Trigger menu of the first analyzer.
3
Set the first analyzer to trigger on the problem condition.
4
Some problems may involve complex sequences of conditions. See chapter 1,
"Triggering," for more information on defining a trigger sequence.
Select the Trigger menu of the second analyzer.
5
Set the second analyzer to trigger on any state and store any state.
6
Select Group Run from the upper right corner of the display.
7
After the measurement is complete, you can interleave the trace lists of both
state analyzers to see the activity executed by both coprocessors during
related clock cycles.
You can use a similar procedure if you have only one processor, but wish to
monitor its activity with that of other system nodes, such as chip-select lines,
I/O activity, or behavior of a watchdog timer. In some instances it may be
easier to look at related activity with a timing analyzer.
See Also
"Special Displays" in this chapter.
"To use a state analyzer to trigger timing analysis of a count-down on a set of
data lines" in this chapter.
220
Debugging coprocessor systems can be a complex task. Replicated systems
and contention for shared resources increase the potential problems. Using
two state analyzers with preprocessors can make it much easier to discover
the source of such problems. For example, you may wish to set up one analyzer
to trigger only when a certain problem occurs, and set up the other analyzer to
be armed by the first analyzer so that it takes its trace only when the first
analyzer recognizes its trigger. This will let you observe the behavior of both
coprocessors during the occurrence of a problem.