ST7263BK4 STMicroelectronics, ST7263BK4 Datasheet - Page 101

• Manufacturer Part Number: ST7263BK4
• Description: LOW SPEED USB 8-BIT MCU FAMILY WITH UP TO 32K FLASH/ROM, DFU CAPABILITY, 8-BIT ADC, WDG, TIMER, SCI and I2C
• Manufacturer: STMicroelectronics

Specifications of ST7263BK4

• 4, 8, 16 Or 32 Kbytes Program Memory: high density Flash (HDFlash), FastROM or ROM with Read-Out and Write protection

ST7263Bxx
Note:
Interrupt Status register (ISTR)
Reset value: 0000 0000 (00h)
When an interrupt occurs these bits are set by hardware. Software must read them to
determine the interrupt type and clear them after servicing.
These bits cannot be set by software.
SUSP
7
7 SUSP Suspend mode request.
6 DOVR DMA over/underrun.
5 CTR Correct Transfer. This bit is set by hardware when a correct transfer operation
4 ERR Error.
3 IOVR Interrupt overrun.
DOVR
This bit is set by hardware when a constant idle state is present on the bus line for
more than 3 ms, indicating a suspend mode request from the USB bus. The
suspend request check is active immediately after each USB reset event and its
disabled by hardware when suspend mode is forced (FSUSP bit of CTLR register)
until the end of resume sequence.
This bit is set by hardware if the ST7 processor can’t answer a DMA request in
time.
0: No over/underrun detected
1: Over/underrun detected
is performed. The type of transfer can be determined by looking at bits TP3-TP2 in
register PIDR. The Endpoint on which the transfer was made is identified by bits
EP1-EP0 in register IDR.
0: No Correct Transfer detected
1: Correct Transfer detected
Note: A transfer where the device sent a NAK or STALL handshake is considered
This bit is set by hardware whenever one of the errors listed below has occurred:
0: No error detected
1: Timeout, CRC, bit stuffing or nonstandard
framing error detected
This bit is set when hardware tries to set ERR, or SOF before they have been
cleared by software.
0: No overrun detected
1: Overrun detected
not correct (the host only sends ACK handshakes). A transfer is considered
correct if there are no errors in the PID and CRC fields, if the DATA0/DATA1
PID is sent as expected, if there were no data overruns, bit stuffing or
framing errors.
CTR
Doc ID 7516 Rev 8
ERR
Read.write
IOVR
ESUSP
On-chip peripherals
RESET
101/186
SOF
0