
Universal Serial Bus Interface
MCF5253 Reference Manual, Rev. 1
Freescale Semiconductor
24-139
24.11.3.6 Isochronous Endpoint Operational Model
Isochronous endpoints are used for real-time scheduled delivery of data and their operational model is
significantly different than the host throttled Bulk, Interrupt, and Control data pipes. Real time delivery by
the USB_DR will is accomplished by the following:
•
Exactly MULT Packets per (micro)Frame are transmitted/received. Note: MULT is a two-bit field
in the device Queue Head. The variable length packet protocol is not used on isochronous
endpoints.
•
NAK responses are not used. Instead, zero length packets and sent in response to an IN request to
an unprimed endpoints. For unprimed RX endpoints, the response to an OUT transaction is to
ignore the packet within the device controller.
•
Prime requests always schedule the transfer described in the dTD for the next (micro)frame. If the
ISO-dTD is still active after that frame, then the ISO-dTD will be held ready until executed or
canceled by the DCD.
The USB_DR in host mode uses the periodic frame list to schedule data exchanges to Isochronous
endpoints. The operational model for device mode does not use such a data structure. Instead, the same
dTD used for Control/Bulk/Interrupt endpoints is also used for isochronous endpoints. The difference is
in the handling of the dTD.
The first difference between bulk and ISO-endpoints is that priming an ISO-endpoint is a delayed
operation such that an endpoint will become primed only after a SOF is received. After the DCD writes
the prime bit, the prime bit will be cleared as usual to indicate to the software that the device controller
completed a priming the dTD for transfer. Internal to the design, the device controller hardware masks that
prime start until the next frame boundary. This behavior is hidden from the DCD but occurs so that the
device controller can match the dTD to a specific (micro)frame.
Another difference with isochronous endpoints is that the transaction must wholly complete in a
(micro)frame. Once an ISO transaction is started in a (micro)frame it will retire the corresponding dTD
when MULT transactions occur or the device controller finds a fulfillment condition.
The transaction error bit set in the status field indicates a fulfillment error condition. When a fulfillment
error occurs, the frame after the transfer failed to complete wholly, the device controller will force retire
the ISO-dTD and move to the next ISO-dTD.
It is important to note that fulfillment errors are only caused due to partially completed packets. If no
activity occurs to a primed ISO-dTD, the transaction will stay primed indefinitely. This means it is up to
the software discard transmit ISO-dTDs that pile up from a failure of the host to move the data.
Finally, the last difference with ISO packets is in the data level error handling. When a CRC error occurs
on a received packet, the packet is not retried similar to bulk and control endpoints. Instead, the CRC is
noted by setting the Transaction Error bit and the data is stored as usual for the application software to sort
out.
•
TX Packet Retired
— MULT counter reaches zero.
— Fulfillment Error [Transaction Error bit is set]
— #Packets Occurred > 0 AND # Packets Occurred < MULT
Содержание MCF5253
Страница 1: ...Document Number MCF5253RM Rev 1 08 2008 MCF5253 Reference Manual...
Страница 26: ...MCF5253 Reference Manual Rev 1 xxvi Freescale Semiconductor...
Страница 32: ...MCF5253 Reference Manual Rev 1 xxxii Freescale Semiconductor...
Страница 46: ...MCF5253 Introduction MCF5253 Reference Manual Rev 1 1 14 Freescale Semiconductor...
Страница 62: ...Signal Description MCF5253 Reference Manual Rev 1 2 16 Freescale Semiconductor...
Страница 98: ...Instruction Cache MCF5253 Reference Manual Rev 1 5 10 Freescale Semiconductor...
Страница 104: ...Static RAM SRAM MCF5253 Reference Manual Rev 1 6 6 Freescale Semiconductor...
Страница 128: ...Synchronous DRAM Controller Module MCF5253 Reference Manual Rev 1 7 24 Freescale Semiconductor...
Страница 144: ...Bus Operation MCF5253 Reference Manual Rev 1 8 16 Freescale Semiconductor...
Страница 176: ...System Integration Module SIM MCF5253 Reference Manual Rev 1 9 32 Freescale Semiconductor...
Страница 198: ...Analog to Digital Converter ADC MCF5253 Reference Manual Rev 1 12 6 Freescale Semiconductor...
Страница 246: ...DMA Controller MCF5253 Reference Manual Rev 1 14 18 Freescale Semiconductor...
Страница 282: ...UART Modules MCF5253 Reference Manual Rev 1 15 36 Freescale Semiconductor...
Страница 298: ...Queued Serial Peripheral Interface QSPI Module MCF5253 Reference Manual Rev 1 16 16 Freescale Semiconductor...
Страница 344: ...Audio Interface Module AIM MCF5253 Reference Manual Rev 1 17 46 Freescale Semiconductor...
Страница 362: ...I2 C Modules MCF5253 Reference Manual Rev 1 18 18 Freescale Semiconductor...
Страница 370: ...Boot ROM MCF5253 Reference Manual Rev 1 19 8 Freescale Semiconductor...