UART reception end

RE: UART reception end

Susheel Nuguru — Thu, 18 Jun 2015 06:27:27 GMT

what do you mean by that?

RE: UART reception end

andrey — Wed, 17 Jun 2015 09:24:27 GMT

But that API wouldn't allow for full-duplex UART, would it?

RE: UART reception end

Susheel Nuguru — Tue, 16 Jun 2015 19:58:43 GMT

It will be blocking while there is data in RX buffers, if that blocking nature does not complicate your design, it is actually good for receive thoughput.

RE: UART reception end

andrey — Tue, 16 Jun 2015 16:22:07 GMT

You understood the question correctly and the answer is valid. It's just that I haven't considered using the API for receiving data because of it's blocking nature.

RE: UART reception end

Susheel Nuguru — Tue, 16 Jun 2015 16:14:58 GMT

Why not just use app_uart_get API? if there is nothing in RX buffer then NRF_ERROR_NOT_FOUND will be returned and the driver will be configured to generate an event on data reception. This seems to be fairly enough functionality needed. We will anyhow wont be able to tell when the other side will send more data or if it is finished. So maybe use timers to timeout if you do not get the receive event within the configured time. Did I miss something in your question?