User manual

Table Of Contents
Zynq-7000 AP SoC Technical Reference Manual www.xilinx.com 417
UG585 (v1.11) September 27, 2016
Chapter 15: USB Host, Device, and OTG Controller
Stall
There are two occasions where the device controller might need to return a STALL to the host:
Functional Stall: software initiated (non-control endpoints only).
Protocol Stall: hardware initiates (control endpoint).
The functional stall, which is a condition set by the DCD as described in the USB 2.0 device
framework. A functional stall is only used on non-control endpoints and can be enabled in the device
controller by setting the usb.ENDPTCTRLx [TXS] stall bit associated with the given endpoint and the
given direction. In a functional stall condition, the device controller will continue to return STALL
responses to all transactions occurring on the respective endpoint and direction until the endpoint
stall bit is cleared by the DCD.
A protocol stall, unlike a function stall, is used on control endpoints and automatically cleared by the
device controller at the start of a new control transaction (setup phase). When enabling a protocol
stall, the DCD should enable the stall bits (both directions) as a pair. A single write to the
usb.ENDPTCTRLx register can ensure that both stall bits are set at the same instant.
Note: Any write to the usb.ENDPTCTRLx register during operational mode must preserve the
endpoint type field (i.e. perform a read-modify-write of this register and preserve the [TXT] field).
Data Toggle
Data toggle is a mechanism to maintain data ordering between the host and device for a given data
pipe. For more information on data toggle, refer to the USB 2.0 specification.
The DCD can reset the data toggle state bit and cause the data toggle sequence to reset in the device
controller by writing a 1 to the data toggle reset bit in the usb.ENDPTCTRLx [TXR] register bit. This
should only be necessary when configuring/initializing an endpoint or returning from a STALL
condition.
Endpoint Type, usb.ENDPTCTRLx [TXT] Depends on the
setup request.
00: Control
01: Isochronous
10: Bulk
11: Interrupt
Endpoint Stall, usb.ENDPTCTRLx [TXS] 0 Do not force stall response.
Table 15-7: USB Device Packet Mismatch Response
USB Packet Type
Received
Endpoint Type
Stall Bit setting
[TXS]
Hardware action
on Stall bit
Bus Response
Setup
Control x Clears [TXS] ACK
Non-Control x None STALL
IN/OUT/Ping
All 0 None ACK/NAK/NYET
All 1 None STALL
Table 15-6: USB Device Endpoint Initialization (Cont’d)
Field Value Meaning