TC1796
System Units (Vol. 1 of 2)
On-Chip System Buses and Bus Bridges
User’s Manual 6-31 V2.0, 2007-07
Buses, V2.0
6.5.4.5 BCU Breakpoint Generation Examples
This section gives three examples of how BCU debug trigger events are programmed.
OCDS Debug Example 1
• Task: Generation of a BCU debug trigger event on any SPB write access to address
00002004
H
or 000020A0
H
by SPB masters PCP or LFI Bridge.
For this task, the following programming settings for the BCU breakpoint logic must be
executed:
1. Writing SBCU_DBADR1 = 0000 2004
H
2. Writing SBCU_DBADR2 = 0000 20A0
H
3. Writing SBCU_DBCNTL = C1115010
H
:
ONBOS[3:0] = 1100
B
means that no signal status trigger is generated (disabled) for
a read signal match AND write signal match condition according to the settings of bits
RD and WR in register SBCU_DBBOS. Debug trigger event generation for
supervisor mode signal match and opcode signal match condition is disabled.
ONA2 = 01
B
means that the equal match condition for debug address 2 register is
selected.
ONA1 = 01
B
means that the equal match condition for debug address 1 register is
selected.
ONG = 1 means that the grant debug trigger is enabled.
CONCOM[2:0] = 101
B
means that the address trigger is created by address trigger 1
OR address trigger 2 (CONCOM1 = 0), and that the grant trigger is ANDed with the
address trigger (CONCOM0 = 1), and that the signal status trigger is ANDed with the
address trigger (CONCOM2 = 1).
RA = 1 means that the BCU breakpoint logic is rearmed.
4. Writing SBCU_DBGRNT = FFFFFFD7
H
means that the grant trigger for the SPB
masters PCP and LFI Bridge is enabled.
5. Writing SBCU_DBBOS = 00001000H means that the signal status trigger is
generated on a write transfer and not on a read transfer.
To Next Page
Loading...
Need help?
General