Feedback on nrf_serial API - process for detecting transmission complete

RE: Feedback on nrf_serial API - process for detecting transmission complete

fkoran — Thu, 09 Jan 2020 18:47:49 GMT

My current solution works. I have two goals in posting:

1. Help other users who are using nrf_serial

2. Provide feedback that nrf_serial is missing a basic feature and suggest that this could be included in the documentation

RE: Feedback on nrf_serial API - process for detecting transmission complete

Simon — Thu, 09 Jan 2020 18:27:02 GMT

I am not too familiar with the nrf_serial library and was not able to find a solution, does your current solution work ok, or should I move on with it?

Best regards,

Simon

RE: Feedback on nrf_serial API - process for detecting transmission complete

fkoran — Mon, 06 Jan 2020 22:40:08 GMT

The key is that it's a half duplex serial link, I need to switch the direction as soon as the transmission is complete

RE: Feedback on nrf_serial API - process for detecting transmission complete

Simon — Sat, 04 Jan 2020 15:17:08 GMT

Couldn't you simply add some logging after the call to nrf_serial_write()? Then you will know when the transmission is completed. If you provide a size_t pointer in the fourth position of the function, you can check its content after function return to see how many bytes are transmitted. If all the bytes aren't transmitted (if size - bytes-written > 0) you may have to increase the timeout.

Best regards,

Simon

RE: Feedback on nrf_serial API - process for detecting transmission complete

Simon — Mon, 30 Dec 2019 09:47:50 GMT

A huge portion of the support team is currently on Christmas vacation and you may experience delayed answers. Most of the staff will be back 6 of January 2020 and you can be sure to get an answer shortly after that.

However, it may be worth looking into the UART driver, due to the reasons mentioned in this ticket.

Best regards,

Simon