Zephyr 2.4.0 with Async UART

[Canadian_EE]

Hi, 

   I am having the same problem as nRF9160 UART: Loosing data when RxData is split into 2 buffers (Async API) - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com) and ASYNC uart and UART_RX_RDY timeout - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com). I have tried the solution, namely modifying 

uart_nrfx_uarte.c

prj.config

However, I end up with this error

Ultimately, I would like this problem resolved. If I'm missing something obvious, please let me know. 

[Susheel Nuguru]

The solution that was proposed is very old and hence definitely not API compatible with the newer ncsv2.4.0.

The pull request the other thread is showing seems to be merged. So I am confused that you are using ncsv2.4.0 and still have to patch the files with the PR changes? Shouldn't the changes be already in?

[Canadian_EE]

I am trying a re-install of the NCSV 2.4.0 library. Perhaps that will resolve the issue. 

[Canadian_EE]

Do I need these additional lines in the prj.conf file to make UART ASYNC behavior work properly? 

"

CONFIG_UART_0_ASYNC=y

CONFIG_UART_0_NRF_HW_ASYNC=y

CONFIG_UART_0_NRF_HW_ASYNC_TIMER=1

CONFIG_NRFX_TIMER1=y

"

It seems that having these lines in the prj.config file helps it all run better. Which I do not understand. I would think that the ASYNC uart would either work or not work. Not varying levels of somewhat work. 

[Canadian_EE]

I modified DEVZONE Academy lesson 5 to echo back received data. I found that the echo shows data is getting missed. I am not sure how to resolve this issue. 

It makes sense that data is being missed when the RECEIVE_BUFF_SIZE is less then the length of the data being sent. However, I notice missed data even when I increase the buffer size. 

What is going on here? 

3583.fund_less5_exer1_solution.zipI  

[Canadian_EE]

Also, I would like to get two UART's working in ASYNC mode with high data reliability. What would I need to set in the prj.config file to enable both UART's in ASYNC mode? Does each UART need a different timer? 

For example: 

#UART0 Config

CONFIG_UART_0_ASYNC=y

CONFIG_UART_0_NRF_HW_ASYNC=y

CONFIG_UART_0_NRF_HW_ASYNC_TIMER=1

CONFIG_NRFX_TIMER1=y

#UART1 Config

CONFIG_UART_1_ASYNC=y

CONFIG_UART_1_NRF_HW_ASYNC=y

CONFIG_UART_1_NRF_HW_ASYNC_TIMER=2

CONFIG_NRFX_TIMER2=y

[Susheel Nuguru]

Yes, Async mode in the UART needs a timer for each instance. It is a bit resource intensive. Why do you need two UARTs in Async mode? What is the use case here?