libuarte rx start after stop

RE: libuarte rx start after stop

Hung Bui — Thu, 10 Mar 2022 15:21:07 GMT

Hi Gnf,

Unfortunately, I haven't got any update on this issue.

RE: libuarte rx start after stop

gnf — Thu, 10 Mar 2022 13:15:09 GMT

Hung Bui, any news regarding this?

RE: libuarte rx start after stop

Hung Bui — Wed, 12 Jan 2022 16:31:32 GMT

Hi Gnf,
You are right. After compile with Debug version I can see the error.

I will check with the team but for me it seems to be a bug in the libuarte code.
I think nrfx_timer_disable(&p_libuarte->timer); need to be added inside nrf_libuarte_drv_rx_stop().

After I added that it seems to works fine.

I will keep you updated when I get the confirmation from the team.

RE: libuarte rx start after stop

gnf — Wed, 12 Jan 2022 07:52:36 GMT

I use full assert (DEBUG and DEBUG_NRF). The error is an assertion error in nrfx_timer.c:

RE: libuarte rx start after stop

Hung Bui — Tue, 11 Jan 2022 15:46:39 GMT

Please let me know which exact error you received.
In my test here I don't see any error (error_code = 0):

RE: libuarte rx start after stop

gnf — Tue, 11 Jan 2022 14:23:39 GMT

I tried creating a minimal working example of the error. Please see the attached zip file below. I used the libuarte example in SDK 17.1.0

The error occurs the second time nrf_libuarte_drv_rx_start() is executed (line 206 in main.c in the zip file):

  err_code = nrf_libuarte_drv_rx_start(&libuarte, rx_buffer, sizeof(rx_buffer), 0);
  APP_ERROR_CHECK(err_code);
  
  nrf_libuarte_drv_rx_stop(&libuarte);

// The error is on the following line:
  err_code = nrf_libuarte_drv_rx_start(&libuarte, rx_buffer, sizeof(rx_buffer), 0);
  APP_ERROR_CHECK(err_code);

devzone.nordicsemi.com/.../libuarte_5F00_start_5F00_stop_5F00_8a31e13a09.zip

RE: libuarte rx start after stop

Hung Bui — Mon, 27 Dec 2021 08:59:00 GMT

Hi Gnf,
Then it should work. Could you let me know which exact error you have ?
Can you send the code you used ?

RE: libuarte rx start after stop

gnf — Thu, 23 Dec 2021 18:52:33 GMT

Ok. I am using nrf_libuarte, not nrf_libuarte_async. Should I use init/uninit instead?

RE: libuarte rx start after stop

Hung Bui — Thu, 23 Dec 2021 13:31:52 GMT

Hi Gnf,

If you use nrf_libuarte_async, I would suggest to wait until the RX timeout occurs before you put the chip to sleep.
Otherwise you may need to call nrf_libuarte_async_uninit() to stop any timer and sleep. Next time when you want to receive you need to init the module again.