USB full speed device interface (USB) RM0008
486/690
Only the bits related to events, which are serviced, are cleared. At the end of the service
routine, another interrupt will be requested, to service the remaining conditions.
To avoid spurious clearing of some bits, it is recommended to clear them with a load
instruction where all bits which must not be altered are written with 1, and all bits to be
cleared are written with ‘0’ (these bits can only be cleared by software). Read-modify-write
cycles should be avoided because between the read and the write operations another bit
could be set by the hardware and the next write will clear it before the microprocessor has
the time to serve the event.
The following describes each bit in detail:
Bit 15 CTR: Correct Transfer
This bit is set by the hardware to indicate that an endpoint has successfully completed a transaction;
using DIR and EP_ID bits software can determine which endpoint requested the interrupt. This bit is
read-only.
Bit 14 PMAOVR: Packet Memory Area Over / Underrun
This bit is set if the microcontroller has not been able to respond in time to an USB memory request.
The USB peripheral handles this event in the following way: During reception an ACK handshake
packet is not sent, during transmission a bit-stuff error is forced on the transmitted stream; in both
cases the host will retry the transaction. The PMAOVR interrupt should never occur during normal
operations. Since the failed transaction is retried by the host, the application software has the chance
to speed-up device operations during this interrupt handling, to be ready for the next transaction
retry; however this does not happen during Isochronous transfers (no isochronous transaction is
anyway retried) leading to a loss of data in this case. This bit is read/write but only ‘0’ can be written
and writing ‘1’ has no effect.
Bit 13 ERR: Error
This flag is set whenever one of the errors listed below has occurred:
NANS: No ANSwer. The timeout for a host response has expired.
CRC: Cyclic Redundancy Check error. One of the received CRCs, either in the token or in the data,
was wrong.
BST: Bit Stuffing error. A bit stuffing error was detected anywhere in the PID, data, and/or CRC.
FVIO: Framing format Violation. A non-standard frame was received (EOP not in the right place,
wrong token sequence, etc.).
The USB software can usually ignore errors, since the USB peripheral and the PC host manage
retransmission in case of errors in a fully transparent way. This interrupt can be useful during the
software development phase, or to monitor the quality of transmission over the USB bus, to flag
possible problems to the user (e.g. loose connector, too noisy environment, broken conductor in the
USB cable and so on). This bit is read/write but only ‘0’ can be written and writing ‘1’ has no effect.
Bit 12 WKUP: Wake up
This bit is set to 1 by the hardware when, during suspend mode, activity is detected that wakes up
the USB peripheral. This event asynchronously clears the LP_MODE bit in the CTLR register and
activates the USB_WAKEUP line, which can be used to notify the rest of the device (e.g. wakeup
unit) about the start of the resume process. This bit is read/write but only ‘0’ can be written and
writing ‘1’ has no effect.
Bit 11 SUSP: Suspend mode request
This bit is set by the hardware when no traffic has been received for 3mS, indicating a suspend mode
request from the USB bus. The suspend condition check is enabled immediately after any USB reset
and it is disabled by the hardware when the suspend mode is active (FSUSP=1) until the end of
resume sequence. This bit is read/write but only ‘0’ can be written and writing ‘1’ has no effect.
To Next Page
Loading...
Need help?
General
