29.01.2015 Views

STM32F101xx, STM32F102xx, STM32F103xx, STM32F105xx and ...

STM32F101xx, STM32F102xx, STM32F103xx, STM32F105xx and ...

STM32F101xx, STM32F102xx, STM32F103xx, STM32F105xx and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

RM0008<br />

USB on-the-go full-speed (OTG_FS)<br />

●<br />

●<br />

Interrupt IN transactions<br />

The assumptions are:<br />

– The application is attempting to receive one packet (up to 1 maximum packet size)<br />

in every frame, starting with odd (transfer size = 1 024 bytes).<br />

– The receive FIFO can hold at least one maximum-packet-size packet <strong>and</strong> two<br />

status DWORDs per packet (1 031 bytes).<br />

– Periodic request queue depth = 4.<br />

Normal interrupt IN operation<br />

The sequence of operations is as follows:<br />

a) Initialize channel 2. The application must set the ODDFRM bit in<br />

OTG_FS_HCCHAR2.<br />

b) Set the CHENA bit in OTG_FS_HCCHAR2 to write an IN request to the periodic<br />

request queue. For a high-b<strong>and</strong>width interrupt transfer, the application must write<br />

the OTG_FS_HCCHAR2 register MCNT (maximum number of expected packets<br />

in the next frame times) before switching to another channel.<br />

c) The OTG_FS host writes an IN request to the periodic request queue for each<br />

OTG_FS_HCCHAR2 register write with the CHENA bit set.<br />

d) The OTG_FS host attempts to send an IN token in the next (odd) frame.<br />

e) As soon as the IN packet is received <strong>and</strong> written to the receive FIFO, the OTG_FS<br />

host generates an RXFLVL interrupt.<br />

f) In response to the RXFLVL interrupt, read the received packet status to determine<br />

the number of bytes received, then read the receive FIFO accordingly. The<br />

application must mask the RXFLVL interrupt before reading the receive FIFO, <strong>and</strong><br />

unmask after reading the entire packet.<br />

g) The core generates the RXFLVL interrupt for the transfer completion status entry<br />

in the receive FIFO. The application must read <strong>and</strong> ignore the receive packet<br />

status when the receive packet status is not an IN data packet (PKTSTS in<br />

GRXSTSR 0b0010).<br />

h) The core generates an XFRC interrupt as soon as the receive packet status is<br />

read.<br />

i) In response to the XFRC interrupt, read the PKTCNT field in OTG_FS_HCTSIZ2.<br />

If the PKTCNT bit in OTG_FS_HCTSIZ2 is not equal to 0, disable the channel<br />

before re-initializing the channel for the next transfer, if any). If PKTCNT bit in<br />

OTG_FS_HCTSIZ2 = 0, reinitialize the channel for the next transfer. This time, the<br />

application must reset the ODDFRM bit in OTG_FS_HCCHAR2.<br />

Doc ID 13902 Rev 9 805/995

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!