Analyzer Problems
This section lists general problems that you might encounter while
using the analyzer.
Intermittent data errors
This problem is usually caused by poor connections, incorrect signal levels, or
marginal timing.
Remove and reseat all cables and probes, ensuring that there are no bent
pins on the analysis probe or poor probe connections.
Adjust the threshold level of the data pod to match the logic levels in the
system under test.
Use an oscilloscope to check the signal integrity of the data lines.
Clock signals for the state analyzer must meet particular pulse shape and
timing requirements. Data inputs for the analyzer must meet pulse shape and
setup and hold time requirements.
See AlsoSee ?Capacitive loading? in this chapter for information on other sources of
intermittent data errors.
Unwanted triggers
Unwanted triggers can be caused by instructions that were fetched but not
executed.
Add the prefetch queue or pipeline depth to the trigger address to avoid
this problem.
The logic analyzer captures prefetches, even if they are not executed. When
you are specifying a trigger condition or a storage qualification that follows an
instruction that may cause branching, an unused prefetch may generate an
unwanted trigger.
E2459A MC68040/060 Analysis Probe5-3 |
ACEC
