TMP92CF30
2009-06-12
92CF30-391
3.16.5.2 Printer Class Request
UDC does not support “Automatic answer” of printer class request.
Processing of Class requests is the same as for vendor requests when answering
INT_SETUP interrupt.
3.16.5.3 Vendor request (Class request)
UDC does not support “Automatic answer” of Vendor requests.
According to INT_SETUP interrupt, access the register in which the device request
is stored, and identify the request. If this request is a Vendor request, control the UDC
externally, and process the Vendor request.
Below is an explanation for the case where data phase is transmitting (Control read),
and for the case where data phase is receiving (Control write).
(a) Control Read request
bmRequestType
bRequest wValue wIndex wLength
Data
110000xxB
Vendor specific
Vendor specific
Vendor specific
Vendor specific
(Expire 0)
Vendor data
When INT_SETUP is received, identify contents of request by bmRequestType,
bRequest, wValue, wIndex and wLength registers and process each request.
According to application, access Setup_Received register after request has been
identified.UDC must also be informed that INT_SETUP interrupt has been
recognized.
After transmitting data prepared in application, access DATASET register, and
confirm EP0_DSET_A bit is “0”. After confirming, write data FIFO of endpoint 0.
If transmitting data is more than payload, write data after it confirming whether
EP0_DSET_A bit in DATASET register is “0”. (INT_ENDPOINT0 interrupt can be
used.) If writing all data is finished, write “0” to EP0 bit of EOP register. When
UDC receives this, the status stage finish 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 maybe received. In this case, when
INT_SETUP interrupt signal is asserted, “1” is set to STAGE_ERROR bit of
EP0_STATUS register Informing externally that the status stage cannot be
finished normally.
The dataphase may have finished on a data number that is shorter than the
value showed to wLength by protocol of control read transfer type in USB. If the
application program is configured using only the wLength value, processing
cannot be carried out when the host shifts status stage without arriving at the
expected data number. At this point, shifting to status stage can be confirmed by
using INT_STATUSNAK interrupt signal. (However, releasing mask of
STATUS_NAK bit by using interrupt control register is needed.) In Vendor
Request, this problem will not occur because the receiving buffer size is set to host
controller by driver (In every host, data (data that is transmitted from device by
payload of 8 bytes) may be taken to be short packet until confirmation of payload
size on device side. Therefore, exercise care if controlling standard requests by
software.)
Содержание TLCS-900/H1 Series
Страница 1: ...TOSHIBA Original CMOS 32 Bit Microcontroller TLCS 900 H1 Series TMP92CF30FG Semiconductor Company ...
Страница 650: ...TMP92CF30 2009 06 12 92CF30 648 7 Package Dimensions LQFP176 P 2020 0 40F TOP VIEW BOTTOM VIEW Detail view of A 25 1 A ...
Страница 652: ...TMP92CF30 2009 06 12 92CF30 650 ...