-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drivers: serial: nrf uarte: The application receives one more byte that was received over UART #33280
Comments
@tomchy @anangl I'm seeing a similar behavior: I'm using sequences that looks like:
When using UARTE driver, there is an extra char received by the modem_receiver through This doesn't happen when using UART driver. However I'm not familiar enough with UART and NRF UARTE implementation to give you the exact event sequence. I've blindly tried your proposed patch #25975 but it didn't work on my use case. We were able to implement our driver by detecting and ignoring theses extra bytes, but we are still really interested in a real fix! |
Hi @XavierChapron! What is your UART driver configuration in the problematic scenario?
When it comes to debugging - I was using the logic probe and toggling GPIO pins on the UART events. Could you grab some traces? |
Describe the bug
The application receives one more byte that was received, due to RX counter alignment upon ENDRX event.
In case of the following sequence of UART events:
The application receives one more byte that was received, due to RX counter alignment upon ENDRX event.
Expected behavior
The application should receive the exact amount of bytes that was received by the UART peripheral.
Impact
This issue may break data transfers, that require at least two UART transmissions, with the delay between them.
Environment:
Additional context
The issue was found during Zigbee NCP serial transport development. It was mitigated by switching from
UART_ASYNC_API
to theUART_INTERRUPT_DRIVEN
mode (nrfconnect/sdk-nrf#2835).After switching, a new way of reproducing the issue was not developed.
The text was updated successfully, but these errors were encountered: