TMP92CZ26A

92CZ26A-391

STATUS [2:0]

(Bit4 to bit2)

These bits show status of end point of UDC.

The status show whether transfer it or not, or show result o

f

transfer. . These are depending on transfer type.

(For the Isochron ous transfer type, refer 3.10.6. )

000: READY Receiving: Device can be received.
In the endpoint 1 to 7, this register is initialized to “READY” by setting transfer type at
SET_CONFIGURATION.
In the endpoint 0, this register is initialized to “READY” by detecting USB reset from
the host.
This is initialized to “READY” by terminating the status stage without error.
Transmitting: Basically, this is same with “Receiving”.
But in transmitting, when data for transmission is set to FIFO and answer to token
from host and transfer data to host collect and received ACK, status register is not
change, and it keeps “READY”. In this case, EPx_Empty_A or EPx_Empty_B
interrupt show terminates transfer correctly.
001: DATAIN UDC set to DATAIN and generates EPx_FULL_A or EPx_FULL_B interrupt when
data is received from the host without error.
010: FULL Refer 3.10.8 (2) Details for the STATUS register.
011: TX_ERR After transfer data to IN token from host, UDC set TX-ER to status register when it is
not received “ACK” from host. In this case, an interrupt is not generated. The hosts
re-try and transfer IN token to this.
100: RX_ERR UDC set RX_ERR to status register without transmitting “ACK” to host when an error
(like a CRC-error) is detected in data of received token. In this case, an interrupt is
not generated. The hosts re-try and transfer IN token to this.
101: BUSY This status is used only for the control transfer type and it is set when a token of
status-stage is received from the host after terminated data-stage.
When status-stage can be finished, terminate correctly and returns to READY. This is
not used in the Bulk and interrupts transfer type.
110: STALL This status shows that applicable endpoint is STALL status.
This status, return STALL-handshake except SETUP-token. In the control endpoint,
returns to READY from stall condition when SETUP-token is received.
In the other endpoint, returns to READY when initialization command of FIFO is
received.
(Note) In Automatically answer of Set_Interface request, request to interface 4 to 6
may not become to request error. If this is problem, in Set_Interface request answer,
set Standard Request Mode <S_INTERFACE> to “1” and use software.
111: INVALID This status shows that applicable endpoint is UNCONFIGURED status.
In this status, the UDC has no reaction when token is received from the host.
By reset, all endpoint set to INVALID status. Only endpoint 0 returns to READY by
receiving USB-reset. Applicable endpoint returns to READY by configured.