RX610 Group
10. ICU
R01UH0032EJ0120 Rev.1.20
Page 254 of 1006
Feb 20, 2013
Table 10.6 Setting Conditions of the DMAC/DTC and Occurrence of the Phenomenon
Destination of Interrupt Request
from Communication Function
Chain Transfer Used or Not
Used
No.
Communication Interrupts to
CPU Issued or Not Issued
Possibility of Problem
Occurrence
DMAC
—
(Chain transfer not provided)
1
No CPU interrupt (ISEL[1:0] = 10b)
Impossible
2
CPU interrupt (ISEL[1:0] = 11b)
Possible
DTC
Chain transfer not used
3
No CPU interrupt (DISEL = 0)
Impossible
4
CPU interrupt (DISEL = 1)
Possible
Chain transfer used
5
No CPU interrupt (DISEL = 0)
Impossible
6
CPU interrupt (DISEL = 1)
Possible
Note 1. Communication interrupts include transmit data empty and receive data full interrupts from SCI and RIIC.
Note 2. In the final transfer, if the DTC is re-set too late for the transfer request of the next packet to be
transmitted/received, the same problem may occur as with the case in DESEL = 1.
•
When the DMAC is used with ISEL[1:0] =11b, use the DTC with DISEL = 1 and implement the following
preventive measures.
•
When the DTC is used with DISEL = 1, it should be used such that the transfer request is not lost, or implement the
software preventive measures of the DTC to prevent the transfer request from being lost.
(1)
Software Preventive Measures
Figure 10.10 shows the flowchart for software preventive measures to be taken for the DTC.
Summary of Contents for RX600 Series
Page 1006: ...RX610 Group R01UH0032EJ0120 ...