ST STM32F101 Series Reference Manual page 401

Advanced arm-based 32-bit mcus
Hide thumbs Also See for STM32F101 Series:
Table of Contents

Advertisement

RM0008
Bit 9 SOF: Start Of Frame
This bit signals the beginning of a new USB frame and it is set when a SOF packet arrives through
the USB bus. The interrupt service routine may monitor the SOF events to have a 1mS
synchronization event to the USB host and to safely read the register which is updated at the SOF
packet reception (this could be useful for isochronous applications). This bit is read/write but only '0'
can be written and writing '1' has no effect.
Bit 8 ESOF: Expected Start Of Frame
This bit is set by the hardware when an SOF packet is expected but not received. The host sends an
SOF packet each mS, but if the hub does not receive it properly, the Timer issues this interrupt. If
three consecutive ESOF interrupts are generated (i.e. three SOF packets are lost) without any traffic
occurring in between, a SUSP interrupt is generated. This bit is set even when the missing SOF
packets occur while the Timer is not yet locked. This bit is read/write but only '0' can be written and
writing '1' has no effect.
Bits 7:5 Reserved.
Bit 4 DIR: Direction of transaction.
This bit is written by the hardware according to the direction of the successful transaction, which
generated the interrupt request.
If DIR bit=0, CTR_TX bit is set in the register related to the interrupting endpoint. The interrupting
transaction is of IN type (data transmitted by the USB peripheral to the host PC).
If DIR bit=1, CTR_RX bit or both CTR_TX/CTR_RX are set in the register related to the interrupting
endpoint. The interrupting transaction is of OUT type (data received by the USB peripheral from the
host PC) or two pending transactions are waiting to be processed.
This information can be used by the application software to access the bits related to the triggering
transaction since it represents the direction having the interrupt pending. This bit is read-only.
Bits 3:0 EP_ID[3:0]: Endpoint Identifier.
These bits are written by the hardware according to the endpoint number, which generated the
interrupt request. If several endpoint transactions are pending, the hardware writes the endpoint
identifier related to the endpoint having the highest priority defined in the following way: Two endpoint
sets are defined, in order of priority: Isochronous and double-buffered bulk endpoints are considered
first and then the other endpoints are examined. If more than one endpoint from the same set is
requesting an interrupt, the EP_ID bits in register are assigned according to the lowest requesting
endpoint register, EP0R having the highest priority followed by EP1R and so on. The application
software can assign a register to each endpoint according to this priority scheme, so as to order the
concurring endpoint requests in a suitable way. These bits are read only.
USB full speed device interface (USB)
401/501

Hide quick links:

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the STM32F101 Series and is the answer not in the manual?

Subscribe to Our Youtube Channel

This manual is also suitable for:

Stm32f103 series

Table of Contents