r5f71374an80fpv Renesas Electronics Corporation., r5f71374an80fpv Datasheet - Page 170

• Manufacturer Part Number: r5f71374an80fpv
• Description: 32-bit Risc Microcomputer Superh?? Risc Engine Family
• Manufacturer: Renesas Electronics Corporation.

Section 7 User Break Controller (UBC)
7.4
7.4.1
The flow from setting of break conditions to user break exception processing is described below:
1. The break addresses are set in the break address registers (BARA or BARB). The masked
2. When the break conditions are satisfied, the UBC issues a user break interrupt request to the
3. The appropriate condition match flags (SCMFCA, SCMFDA, SCMFCB, and SCMFDB) can
4. There is a possibility that matches of the break conditions set in channels A and B occur
5. When selecting the I bus as the break condition, note the following:
Rev. 1.00 Sep. 21, 2007 Page 144 of 1124
REJ09B0402-0100
addresses are set in the break address mask registers (BAMRA or BAMRB). The break data is
set in the break data register (BDRA or BDRB). The masked data is set in the break data mask
register (BDMRA or BDMRB). The bus break conditions are set in the break bus cycle
registers (BBRA or BBRB). Three groups of BBRA or BBRB (L bus cycle/I bus cycle select,
instruction fetch/data access select, and read/write select) are each set. No user break will be
generated if even one of these groups is set with B'00. The respective conditions are set in the
bits of the break control register (BRCR). Make sure to set all registers related to breaks before
setting BBRA or BBRB.
CPU and sets the L bus condition match flag (SCMFCA or SCMFCB) and the I bus condition
match flag (SCMFDA or SCMFDB) for the appropriate channel.
be used to check if the set conditions match or not. The matching of the conditions sets flags,
but they are not reset. Before using them again, 0 must first be written to them and then reset
flags.
almost at the same time. In this case, only one user break interrupt request may be sent to the
CPU with both of the two condition match flags set.
 The CPU and DTC are connected to the I bus. The UBC monitors bus cycles generated by
 I bus cycles resulting from instruction fetches on the L bus by the CPU are defined as
 The DTC only issue data access cycles for I bus cycles.
 If a break condition is specified for the I bus, even when the condition matches in an I bus
all bus masters that are selected by the CPA2 to CPA0 bits in BBRA or the CPB2 to CPB0
bits in BBRB, and compares for a condition match.
instruction fetch cycles on the I bus, while other bus cycles are defined as data access
cycles.
cycle resulting from an instruction executed by the CPU, at which instruction the break is
to be accepted cannot be clearly defined.
Operation
Flow of the User Break Operation