HC08 FSICEBASE Emulator
Bus State Analyzer (BSA)
423
Microcontrollers Debugger Manual
5. Select Term or Range
A range consists of two 32-bit values. Range does not refer to a range of addresses. If
you define an event as a range, the BSA triggers every time the input falls between the
range starting term (the first 32-bit value) and the range ending term (the second 32-bit
value).
6. In Address area, specify the address(es) that the BSA monitors
7. In Data area, specify the data that the BSA monitors
8. In Access area, specify the type of access that you want the BSA to monitor
9. In Type area, specify whether the you want the BSA to record data, instructions or any
kind of value at the specified address
10. Specify Pod A signals (logic clips attach to pins of Pod A) that you want the BSA to
monitor for this event
NOTE You can use five of the pod A logic clips to define an event. The other signals
of Pod A, and the signals of Pods B and C cannot be used to define an event.
The Bus Analyzer Configuration dialog box shows the five clips that you can
use to trigger an event. The choice of these five signals is hard-set in the
FSICEBASE; you cannot choose other signals to be used as event criteria.
However, the BSA does capture data from all 24 lines of Pods A, B, and C.
11. If you want the term to also act as a breakpoint, check the Breakpoint checkbox.
12. Specify the Recording Mode
For information about the recording mode, see Recording Modes.
If you check the Stop when recording completes checkbox, the debugger stops
program execution when bus state analyzer recording is done.
13. Specify the Time Tag Clock Frequency
14. 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.
15. Click Save to save the event information to a file.
16. 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.