
Using the Bus State Analyzer
Using the Bus State Analyzer
13. Specify the Time Tag Clock Frequency
14. If an appropriate recording mode is selected, check the box to stop execution when the
trace buffer is completely filled with captured information (otherwise it will continue
to capture new information, overwriting older information, until execution is halted)
15. Click Save to apply the event information to the current debug session and close the
dialog box. The BSA uses the terms when you arm the BSA.
16. Click Save... to save the event information to a file
17. Click Arm to ready the BSA to collect data.
The BSA does not start collecting data until execution begins.The debugger indicates
that the BSA is armed by showing the word Armed in the status bar.
Recording Modes
When you define an event, you can specify the recording mode that the Bus State
Analyzer uses to collect data. This section explains how the different modes work.
Continuous: all cycles
After execution begins, the trace buffer begins storing data from the first cycle. This
continues until execution arrives at a breakpoint, or until you halt execution.
Continuous: events only
After execution begins, the trace buffer begins storing data when data matches an event
definition. This continues until execution arrives at a breakpoint, or until you halt
execution
Counted: all cycles
After execution begins, the trace buffer begins storing data until after the specified number
of cycles from first cycle. (A breakpoint can stop storage before the analyzer stores the
specified number of cycles, as can halting execution.)
Counted: events only
After execution begins, the trace buffer begins storing data that match an event definition
for the specified number until it has captured the specified number of events. (A
breakpoint can stop storage before the analyzer stores the specified number of cycles, as
can halting execution.)
Freescale In-Circuit Emulator Base User Manual, Rev. 1.1
70
Freescale Semiconductor