User manual

Table Of Contents
Zynq-7000 AP SoC Technical Reference Manual www.xilinx.com 422
UG585 (v1.11) September 27, 2016
Chapter 15: USB Host, Device, and OTG Controller
15.6.4 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 device controller 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 are 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 is held ready until executed or
canceled by the DCD.
Note: If the MULT field is set to more packets than present in the dTD to be transmitted, the
controller sends zero length packets to all extra incoming IN tokens and report fulfillment error
(transaction error) in current dTD. If more dTD’s exist in memory, the controller moves to the next
dTD to be transmitted in the next (micro)frame. Because of this behavior it is recommended to
always use the correct MULT matching the number of packets to be processed for a given dTD.
An EHCI compatible host controller uses the periodic frame list to schedule data exchanges to
Isochronous endpoints. The operational model for the device controller 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 DCD 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 isochronous transaction is started in a (micro)frame it will retire the
Invalid Ignore Ignore Ignore Ignore Ignore BTO
Notes:
1. BS Error — Force Bit Stuff Error.
2. NYET/ACK — NYET unless the Transfer Descriptor has packets remaining according to the USB variable length
protocol then ACK.
3. SYSERR — System error should never occur when the latency FIFOs are correctly sized and the DCD is
responsive.
4. BTO — Bus Time Out.
Table 15-9: USB Device Interrupt and Bulk Endpoint Bus Response (Contd)
Packet
Identifier
Stall Bit
[TXS]
Endpoint
Not Primed
Endpoint
Primed
Buffer
Underflow
Buffer
Overflow
Endpoint
Not Enabled