RE: Libuarte

user26071 — Thu, 12 May 2022 13:01:32 GMT

Hello,

What you probably want to do is to trigger the sending using nrf_libuarte_async_tx() like it is used in this example. I don't know when you want to trigger it. Perhaps you want to start an app_timer and trigger the sending from the timeout handler, or set up a button handler and trigger it from there.

You don't need to use the queue library at all.

Then, whenever the other device replies, it will trigger the NRF_LIBUARTE_ASyNC_EVT_RX_DATA event, containing the p_evt->data.rxtx.p_data, and p_evt->data.rxtx.length with the reply starting on the ...rxtx.p_data pointer, with the length = ...rxtx.length.

If you want an example on how to set up and use the app_timer, I suggest you check out the ble_app_hrs example from SDK\examples\ble_peripheral\ble_app_hrs.

Note: If you intend to use the libuarte library in an example that uses the softdevice (bluetooth stack), then please be aware that TIMER0 and RTC0 is used by the softdevice, so you need to adjust your NRF_LIBUARTE_ASYNC_DEFINE() in that case. The macro expands to:

#define NRF_LIBUARTE_ASYNC_DEFINE(_name, _uarte_idx, _timer0_idx,\
                                  _rtc1_idx, _timer1_idx,\
                                  _rx_buf_size, _rx_buf_cnt) \

So parameter nr 3 is the timer instance, parameter 4 is the RTC instance and parameter 5 is the other timer instance. Note that the libuarte library is quite resource heavy. Unless you really need it, I would suggest you check out the ble_app_uart example from sdk\examples\ble_peripheral\ble_app_uart. It uses a UART library that is a bit more simple. If you have a reason to use the libuarte library, that is fine, but in case it was the first thing you stumbled upon, I suggest you check it out.

Best regards,

Edvin