How-To Guide

Table Of Contents
R01UH0823EJ0110 Rev.1.10 Page 956 of 1852
Nov 30, 2020
RX23W Group 32. USB 2.0 Host/Function Module (USBc)
When the selected pipe is set for isochronous transfers, the USB carries out the following operation in addition to
controlling the token issuance interval. The USB issues a token even when the NRDY interrupt generation condition is
satisfied.
(a) When the selected pipe is for isochronous IN transfers
The USB generates an NRDY interrupt when the USB issues an IN token but does not receive a packet successfully from
a peripheral device (no response or packet error).
The USB sets the FRMNUM.OVRN flag to 1 generating an NRDY interrupt when the time to issue an IN token comes
while the USB cannot receive data because the FIFO buffer is full (due to the fact that the CPU or DMAC/DTC is too
slow to read data from the FIFO buffer).
(b) When the selected pipe is for isochronous OUT transfers
The USB sets the OVRN flag to 1 generating an NRDY interrupt and transmitting a zero-length packet when the time to
issue an OUT token comes while there is no data to be transmitted in the FIFO buffer (because the CPU or DMAC/DTC
is too slow to write data to the FIFO buffer).
The token issuance interval is reset on any of the following conditions.
When the USB is reset through a reset pin
(The IITV[2:0] bits are also set to 0).
When the PIPEnCTR.ACLRM bit has been set to 1 by software.
(3) Interval Counting and Transfer Control When the Function Controller is Selected
(a) When the selected pipe is for isochronous OUT transfers
The USB generates an NRDY interrupt when the USB fails to receive a data packet within the interval set by the
PIPEPERI.IITV[2:0] bits.
The USB also generates an NRDY interrupt when the USB fails to receive data because of a CRC error or other errors
contained in the data packet or because of the FIFO buffer being full.
The NRDY interrupt is generated at the timing of SOF packet reception. Even if the SOF packet is corrupted, the internal
interpolation allows the interrupt to be generated at the timing to receive the SOF packet.
However, when the IITV[2:0] bits are set to a value other than 0, the USB generates an NRDY interrupt on receiving an
SOF packet for every interval after starting interval counting operation.
When the PID[1:0] bits are set to 00b (NAK) by software after starting the interval timer, the USB does not generate an
NRDY interrupt on receiving an SOF packet.
The timing to start interval counting depends on the setting of IITV[2:0] bits as shown below.
When the IITV[2:0] = 000b: The interval counting starts when software has set the PID[1:0] bits for the selected
pipe to 01b (BUF).
Figure 32.15 Relationship between Frames and Expected Token Reception When IITV[2:0] = 000b
SOF
OUT
DATA
OUT
DATA
USB bus
PID bit setting
Token
NAK NAK BUF BUF
Token
reception
is not waited
Interval counter started
Token
reception
is not waited
Token
reception
is waited
Token
reception
is waited
SOF
SOF
SOF