Toshiba TLCS-900/H1 Series Manual page 245

(b) Control write/request
There is no dataphase
bmRequestType bRequest
010000xxB Vendor specific
When
bmRequestType, bRequest, wValue, wIndex, wLength registers,and process
each request. According to application, access Setup_Received register after
request has been identified. UDC must also be informed that the INT_SETUP
interrupt has been recognized. If application processing is finished, write "0"
to EP0 bit of EOP register. When UDC receives this, the status stage finishes
automatically.
There is dataphase
bmRequestType bRequest
010000xxB Vendor specific
When INT_SETUP is received, identify contents of device request by
bmRequestType, bRequest, wValue, wIndex, wLength registers, and process
each request. According to application, access Setup_Received register after
request has been identified. UDC must also be informed that the INT_SETUP
interrupt has been recognized.
After receiving data prepared in application, access DATASET register, and
confirm EP0_DSET is "1". After confirming, read data FIFO of endpoint 0. If
data is more than payload, write data after it confirming whether the
EP0_DSET_A bit in DATASET register is "1". (INT_ENDPOINT0 interrupt
can be used.) If reading all data is finished, write "0" to EP0 bit of EOP
register. When UDC receives this, the status stage finishes automatically.
INT_STATUS interrupt is asserted when UDC finishes status stage
normally. If finishing status stage normally is recognized by external
application, manage this stage by using this interrupt signal. If status stage
cannot be finished normally and during status stage, a new SETUP token may
be received. In this case, when INT_SETUP interrupt signal is asserted, "1" is
set to STAGE_ERROR bit of EP0_STATUS registerinforming externally that
the status stage cannot be finished normally.
wValue
Vendor specific Vendor specific
INT_SETUP is received,
wValue
Vendor specific Vendor specific
92CH21-243
wIndex wLength
0
identify contents
wIndex wLength
Vendor specific
(Except for 0)
TMP92CH21
Data
None
of request by
Data
Vendor data
2009-06-19