STM32F0: fix issue with usarts sharing the same irq vector #5907
Conversation
| { | ||
| uart_irq(2); | ||
| } | ||
| #if defined(TARGET_STM32F091RC) |
There was a problem hiding this comment.
Does this problem only affect the STM32F091RC, or are more targets affected?
There was a problem hiding this comment.
All STM32F09x devices support this but there is only the STM32F091RC device on mbed actually.
|
/morph build |
Build : SUCCESSBuild number : 925 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 612 |
Test : FAILUREBuild number : 766 |
bcostm
force-pushed
the
fix_f0_usart_irq
branch
from
dda50cf to
9714c2c
Compare
|
/morph build |
Build : SUCCESSBuild number : 930 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 617 |
|
/morph uvisor-test |
|
testing it again /morph uvisor-test |
|
/morph uvisor-test |
Test : FAILUREBuild number : 769 |
Manage the case where both uart3 and uart4 interrupts are arriving at the same time.
bcostm
force-pushed
the
fix_f0_usart_irq
branch
from
9714c2c to
7ff1cf5
Compare
|
/morph build |
Build : SUCCESSBuild number : 944 Triggering tests/morph test |
Test : SUCCESSBuild number : 775 |
Exporter Build : SUCCESSBuild number : 632 |
Description
Issue flagged here: https://os.mbed.com/forum/mbed/topic/28545/
On some F0 devices, multiple USART are sharing the same IRQ vector and this case was not managed.
Tested on NUCLEO_F091RC and NUCLEO_F070RB boards using two usarts (USART3 and USART4).
Status
READY
Migrations
NO