When I use RxIrq scheme with Serial::attach(), I often get unexpected and endless Serial Rx Interruption which is never stopped without resetting mbed.
I use Serial class to communicate with a device which returns received data immediately, like echo.
So, I have to use RxIrq to send data bigger than 16 Byte (Rx FIFO size) at once.
And I often get endless Rx Interruption with a data '0xFF', which means no signal.
This endless Interruption is never stopped even though I call NVIC_ClearPendingIRQ() when I find '0xFF' in my Rx Interruption handler.
As a result of my study with oscilloscope, I guess that this situation occurs when Rx interruption is rising when I sending a data by Serial::putc().
Is this a known bug ? Or a limitation of mbed Serial library ?
When I use RxIrq scheme with Serial::attach(), I often get unexpected and endless Serial Rx Interruption which is never stopped without resetting mbed.
I use Serial class to communicate with a device which returns received data immediately, like echo. So, I have to use RxIrq to send data bigger than 16 Byte (Rx FIFO size) at once. And I often get endless Rx Interruption with a data '0xFF', which means no signal. This endless Interruption is never stopped even though I call NVIC_ClearPendingIRQ() when I find '0xFF' in my Rx Interruption handler.
As a result of my study with oscilloscope, I guess that this situation occurs when Rx interruption is rising when I sending a data by Serial::putc().
Is this a known bug ? Or a limitation of mbed Serial library ?