UART and TIMER conflicts happening while receiving data

RE: UART and TIMER conflicts happening while receiving data

Dmitry — Fri, 31 Jul 2020 13:26:44 GMT

I didn't try that, but two libuarte_async instances should work as well (you'll also need two additional timers, or timer+rtc for each instance)

RE: UART and TIMER conflicts happening while receiving data

Rajat — Fri, 31 Jul 2020 12:41:28 GMT

We need to use two UARTs at once , will that be possible with that?
We also tried the nrf_Serial library and found that it is not well suited for our device that we are working on

RE: UART and TIMER conflicts happening while receiving data

Rajat — Fri, 31 Jul 2020 12:35:10 GMT

Yes , it does give me the same issues

RE: UART and TIMER conflicts happening while receiving data

Dmitry — Fri, 31 Jul 2020 12:04:20 GMT

I see, nrfx_uarte_rx_abort() doesn't clear buffer pointers. Also, you won't get stable reception with current approach - as new data can appear at any time, restarted reception will sometimes cause loss of bitstream sync and garbaged data. In your case it's better to use nrf_libuarte_async library from SDK, it can handle rx timeouts internally.

RE: UART and TIMER conflicts happening while receiving data

Simonr — Fri, 31 Jul 2020 11:45:07 GMT

Did you try adding the abort function nrfx_uarte_rx_abort() as Dmitry suggested at all? Does this still give you the same issues?

Best regards,

Simon

RE: UART and TIMER conflicts happening while receiving data

Rajat — Fri, 31 Jul 2020 09:48:58 GMT

Unfortunately , it doesn't work for me

RE: UART and TIMER conflicts happening while receiving data

Dmitry — Fri, 31 Jul 2020 08:12:26 GMT

Hi,

when your timer is triggered, UART reception stays active. Try to add nrfx_uarte_rx_abort() before returning UARTE_TIMEOUT.