Recieving data with libuarte

RE: Recieving data with libuarte

Susheel Nuguru — Tue, 08 Dec 2020 08:04:51 GMT

[quote user="Leogean"]Thanks for your detailed explanation. So in my handler, because I do not want to send the received data back to the transmitter, the "nrf_uarte_async_tx" function is not necessary. Also, because I process the received data immediately, the queue functions are also not necessary. Am I right? [/quote]

Yes , your understanding is correct.

[quote user="Leogean"]Ah, the data type of the received data is "uint8_t*", I have just realized that, sorry.[/quote]

No worries. Good luck with your project.

RE: Recieving data with libuarte

Leogean — Tue, 08 Dec 2020 04:33:29 GMT

Ah, the data type of the received data is "uint8_t*", I have just realized that, sorry.

RE: Recieving data with libuarte

Leogean — Mon, 07 Dec 2020 04:50:57 GMT

Thanks for your detailed explanation. So in my handler, because I do not want to send the received data back to the transmitter, the "nrf_uarte_async_tx" function is not necessary. Also, because I process the received data immediately, the queue functions are also not necessary. Am I right? I have one last question. I guess the data I receive is "p_evt->data.rxtx.p_data". Is the data type of it is "char*", so that I can directly set "rxdata = p_evt->data.rxtx.p_data" (which rxdata is "char*"), and process it?

Thanks again for the help you provide.

RE: Recieving data with libuarte

Susheel Nuguru — Fri, 04 Dec 2020 07:42:58 GMT

[quote user="Leogean"] In my uarte handler, do you mean if I only want to process the received data, line 12 is actually not necessary? Or the queue push is also not necessary and I only need to start from line 27 to check if there is data in the rx buffer and process it?[/quote]

What I mean to say is that when processing NRF_LIBUARTE_ASYNC_EVT_RX_DATA event, you are pushing the received data to the end of the queue using nrf_queue_push. And at line 27, you are checking if the queue is empty. The queue will never be empty at this instance, since you just pushed the received data to the queue. And you pop the queue immediately.

I do not think you need to push and pop the data to the queue at this instance. The reference code that you took from SDK\examples\peripheral\libuarte shows you a a loop back data through uarte. So the processing of uart_event_handle in that example is not something you would like to use as it is.

In your case, you do not need to use nrf_queue_xxx at all, since you are processing the incoming data immediately.

RE: Recieving data with libuarte

Leogean — Thu, 03 Dec 2020 16:09:56 GMT

Thanks for your reply, the information is very helpful. In my uarte handler, do you mean if I only want to process the received data, line 12 is actually not necessary? Or the queue push is also not necessary and I only need to start from line 27 to check if there is data in the rx buffer and process it?

RE: Recieving data with libuarte

Susheel Nuguru — Thu, 03 Dec 2020 08:41:44 GMT

Hi Leogean,

nrf_libuarte_async_enable is the API that enables and starts the receiver and most likely you should start this along with the tx by calling nrf_libuarte_async_tx, which will work only with the transmitter.

In your uart_event_handler. When you get an event that there is a new RX_DATA available, you are starting the next transaction of the TX and also checking to see if there is any data in the buffer queue (which most likely there will as you are processing EVT_RX_DATA).

It looks like your state machine does not depend on the EVT_TX_DONE. This could work as long as you are sure that the peer will transmit data so that your application will process it and kick the next TX transaction.