Table of Contents
Advertisement
M30245 Group
(4) Isochronous Transfer
Isochronous IN Transfer
In isochronous IN transfer which data are transferred from the device to the host CPU, isochronous
(IN) transactions are repeated. Isochronous transaction does not have the handshake phase. The
data packet consists only of DATA0. Toggling with DATA1 is not performed. When transmit data is
available in IN FIFO, the M30245 group issues a data packet to the IN token. The M30245 group
executes the following responses when the data are not transmitted normally:
•When the received IN token is destroyed, the data are not issued.
•When the transmit data are not available in IN FIFO, an empty packet of data length (0) is issued.
www.DataSheet4U.com
Isochronous OUT Transfer
In isochronous OUT transfer which data are transferred from the host CPU to the device, isochro-
nous (OUT) transactions are repeated. Isochronous transaction does not have the handshake
phase. The data packet consists only of DATA0. Toggling with DATA1 is not performed.
The M30245 group has received a data packet, indicates whether or not the data content is normal
by using a status flag. The M30245 group executes the following responses when the data are not
received normally:
•When the received OUT token is destroyed, the data are not received.
•When the received data are destroyed (bit stuffing error or CRC error occur), the data are received.
•When the packet, which is exceeding receivable data size, is transmitted, the data are not received.
•When OUT FIFO of the M30245 group could not receive the full data, the data are not received.
Figure 2.8.6. Isochronous transfer
(5) Interrupt Transfer
This transfer form is same as the bulk transfer. Refer to "(3) Bulk Transfer" of this manual.
Rev.2.00 Oct 16, 2006
REJ09B0340-0200
Isochronous IN
(Idle state)
IN
DATA0
(Idle state)
page 134 of 354
Isochronous OUT
(Idle state)
OUT
DATA0
: Host issues
(Idle state)
: Device issues
2. USB function
Advertisement
Table of Contents
