
6
Using the Bus State Analyzer
This chapter explains how to use the bus state analyzer (BSA). This chapter contains the
following sections:
? Overview
? Using the Bus State Analyzer
Overview
The bus state analyzer (BSA) shows the logical state of the target MCU bus and external
signals during program execution. The BSA takes a snapshot of the MCU bus. It also
captures the signals from the external logic clips Pods A, B, and C of the FSICBASE (24
lines in total). This capturing of data enables you to determine what is occurring in a
system without actually disturbing the system.
At the end of each MCU clock cycle, the BSA takes a snapshot of the logical states of the
target MCU bus and external inputs. The analyzer stores the snapshots in the trace buffer,
according to its mode. (This action is known as storing cycles.)
NOTE
The analyzer is a bus state analyzer: It does not show signal hold or setup
times.
To start using the BSA, you need to define patterns of logical states as events (or terms).
You also need to specify the analyzer mode: continuous, counted, or any of five sequential
modes. This determines which cycles the analyzer stores.
Data collection (cycle storage) begins when you arm the analyzer and start program
execution, depending on the triggering mode and state. Data collection continues until
execution stops, through a specified number of events, or through a defined sequence of
events, or optionally until the trace buffer is full.
Using the Bus State Analyzer
To use the bus state analyzer (BSA) to produce useful data that you can view and analyze,
you must:
? define events (terms) and/or triggering sequence, and
? arm the BSA.
Freescale In-Circuit Emulator Base User Manual, Rev. 1.1
Freescale Semiconductor
67