diff options
| author | Alex Voinea <voinea.dragos.alexandru@gmail.com> | 2022-10-31 18:03:11 +0100 |
|---|---|---|
| committer | KevinOConnor <kevin@koconnor.net> | 2022-10-31 13:50:15 -0400 |
| commit | 26e6ade1757e20ce3a1253c4c4d0a915960a38d8 (patch) | |
| tree | c7ee1c259cb4eaaf21cb5a809a5fb884666c4239 /src/stm32/serial.c | |
| parent | 96ea871b355d69ae00220d14c3a9f9c4b8754337 (diff) | |
| download | kutter-26e6ade1757e20ce3a1253c4c4d0a915960a38d8.tar.gz kutter-26e6ade1757e20ce3a1253c4c4d0a915960a38d8.tar.xz kutter-26e6ade1757e20ce3a1253c4c4d0a915960a38d8.zip | |
stm32: fix USART ORE status flag handling
If an USART RX overrun happened on a stm32g0/f0/h7, the ORE flag
would get set by hardware. This flag would also trigger an interrupt.
The problem was that this flag was never cleared on these 3 mcu families
since the ORE flag clear sequence is different to all of the older
chips.
Since the ORE flag is not used in any meaningful way anyway, it was
disabled during the init sequence.
Signed-off-by: Alex Voinea <voinea.dragos.alexandru@gmail.com>
Diffstat (limited to 'src/stm32/serial.c')
| -rw-r--r-- | src/stm32/serial.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/stm32/serial.c b/src/stm32/serial.c index 5806eaab..19aa048e 100644 --- a/src/stm32/serial.c +++ b/src/stm32/serial.c @@ -57,8 +57,11 @@ void USARTx_IRQHandler(void) { uint32_t sr = USARTx->SR; - if (sr & (USART_SR_RXNE | USART_SR_ORE)) + if (sr & (USART_SR_RXNE | USART_SR_ORE)) { + // The ORE flag is automatically cleared by reading SR, followed + // by reading DR. serial_rx_byte(USARTx->DR); + } if (sr & USART_SR_TXE && USARTx->CR1 & USART_CR1_TXEIE) { uint8_t data; int ret = serial_get_tx_byte(&data); |