Using S140 with nRF52840, UART example question

RE: Using S140 with nRF52840, UART example question

jwcheon — Thu, 12 Oct 2017 04:10:46 GMT

Hi, Martin.

thank you for the reply.

I've fixed the issue. I was working on applying "uart" to the "hrs" example, and I was requesting app_uart_put using "app_uart.c".

So, as Martin puts it, If app_uart_put is requested continuously without putting, <ERROR_NO_MEM> is returned and it is confirmed that the transfer is not performed.

After changing from "app_uart.c" to "app_uart_fifo.c", I confirmed that the app_uart_put is continuously output even when it requests continuously.

RE: Using S140 with nRF52840, UART example question

jwcheon — Thu, 12 Oct 2017 01:00:15 GMT

Only 'A' is output equally.

RE: Using S140 with nRF52840, UART example question

Jakub Rzeszutko — Wed, 11 Oct 2017 13:10:14 GMT

what will happen if you will change the code in following way:

for (cnt = 0 ;; cnt ++)
{
     app_uart_put ('A');
     app_uart_put (cnt + 0x30);
     nrf_delay_ms (200);
}

RE: Using S140 with nRF52840, UART example question

MartinBL — Wed, 11 Oct 2017 12:35:05 GMT

app_uart_put is a non blocking function (see documentation). This means that if you call it many times without any delays in between the first byte you try to send ('A') may not have been transmitted before you try to transfer another. You should check the return code of app_uart_put() and see if that can give you any clue.