MCBSTM32EXL Keil, MCBSTM32EXL Datasheet - Page 535

• Manufacturer Part Number: MCBSTM32EXL
• Description: BOARD EVALUATION FOR STM32F103ZE
• Manufacturer: Keil

Specifications of MCBSTM32EXL

• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

RM0008
Bits 5:4 STAT_TX [1:0]: Status bits, for transmission transfers
Bits 3:0 EA[3:0]: Endpoint address
Table 156. Reception status encoding
Table 157. Endpoint type encoding
STAT_RX[1:0]
Bit 6 DTOG_TX: Data Toggle, for transmission transfers
EP_TYPE[1:0]
00
01
10
11
00
01
If the endpoint is non-isochronous, this bit contains the required value of the data toggle bit
(0=DATA0, 1=DATA1) for the next data packet to be transmitted. Hardware toggles this bit
when the ACK handshake is received from the USB host, following a data packet
transmission. If the endpoint is defined as a control one, hardware sets this bit to 1 at the
reception of a SETUP PID addressed to this endpoint.
If the endpoint is using the double buffer feature, this bit is used to support packet buffer
swapping too (Refer to
If the endpoint is Isochronous, this bit is used to support packet buffer swapping since no
data toggling is used for this sort of endpoints and only DATA0 packet are transmitted (Refer
to
packet transmission, since no handshake is used for Isochronous transfers.
This bit can also be toggled by the software to initialize its value (mandatory when the
endpoint is not a control one) or to force a specific data toggle/packet buffer usage. When
the application software writes ‘0’, the value of DTOG_TX remains unchanged, while writing
‘1’ makes the bit value toggle. This bit is read/write but it can only be toggled by writing 1.
These bits contain the information about the endpoint status, listed in
can be toggled by the software to initialize their value. When the application software writes
‘0’, the value remains unchanged, while writing ‘1’ makes the bit value toggle. Hardware
sets the STAT_TX bits to NAK, when a correct transfer has occurred (CTR_TX=1)
corresponding to a IN or SETUP (control only) transaction addressed to this endpoint. It
then waits for the software to prepare the next set of data to be transmitted.
Double-buffered bulk endpoints implement a special transaction flow control, which controls
the status based on buffer availability condition (Refer to
endpoints).
If the endpoint is defined as Isochronous, its status can only be “VALID” or “DISABLED”.
Therefore, the hardware cannot change the status of the endpoint after a successful
transaction. If the software sets the STAT_TX bits to ‘STALL’ or ‘NAK’ for an Isochronous
endpoint, the USB peripheral behavior is not defined. These bits are read/write but they can
be only toggled by writing ‘1’.
Software must write in this field the 4-bit address used to identify the transactions directed
to this endpoint. A value must be written before enabling the corresponding endpoint.
Section 21.4.4: Isochronous
DISABLED: all reception requests addressed to this endpoint are ignored.
STALL: the endpoint is stalled and all reception requests result in a STALL
handshake.
NAK: the endpoint is naked and all reception requests result in a NAK handshake.
VALID: this endpoint is enabled for reception.
BULK
CONTROL
Section 21.4.3: Double-buffered
Doc ID 13902 Rev 9
Universal serial bus full-speed device interface (USB)
transfers). Hardware toggles this bit just after the end of data
Meaning
Meaning
endpoints)
Section 21.4.3: Double-buffered
Table
159. These bits
535/995