UARTE.h

RE: UARTE.h

user26071 — Wed, 18 May 2022 10:16:05 GMT

I don't know why setting pin14 to low works. Actually I wanted you to have a look at the ble_app_uart example, but if this is working, I guess it is fine.

Regarding pin 14, I suggest you try to debug to see why it is not working. Is the main() function reached? If yes, you should check the return values for the functions that returns something, such as nrf_uarte_configure(). What do they return? (not only nrf_uarte_configure, but pretty much all your uart related functions).

I also see that you don't have a while loop in your main function:

    while(1) {
      break;
    }

This will break out of the while loop on entry, and then skip to "return 0;", and at that point your application is "done". It is not defined what the chip should do then. Perhaps you added some more code to the while loop when you also added the pin 14 part, which made it work?

RE: UARTE.h

user116078 — Mon, 16 May 2022 22:50:47 GMT

Hello, I found out that adding the following line solves the issue:

nrf_gpio_cfg_output(14);
nrf_gpio_pin_write(14, false);

could you please explain why adding these two lines at the beginning main() function allows for successful communication? Without these 2 lines, I do not get any response. Why pin 14 exactly? I do not see anything that is connected to pin 14.

RE: UARTE.h

user116078 — Mon, 16 May 2022 15:08:37 GMT

Hello, I am found out that adding the following line solves the issue:

nrf_gpio_cfg_output(14);
nrf_gpio_pin_write(14, false);

RE: UARTE.h

user26071 — Mon, 16 May 2022 10:33:21 GMT

Hello,

It doesn't really look like there is any sensitive information in the code, but you should be able to edit the original post.

What I was thinking of when I mentioned that the libuarte was a bit resource heavy is that it requires both a timer and an RTC to operate, while for most applications this is a bit overkill.

I suggest that you look into the ble_app_uart example found in SDK\examples\ble_peripheral\ble_app_uart. Look at how it sets up the uart in uart_init() from main.c, and how the event handler, uart_event_handle() is handling the incoming bytes. Note that this interrupt will trigger on every byte, but the byte will be added to the data_array[] parameter, and it checks whether the last byte is an \n or an \r (or if the buffer is filled). If it is, then it will trigger some action, which in this case is sending the array via ble_nus_data_send(..., data_array, ...).

You can also see how it writes data on the uart using app_uart_put() inside the nus_data_handler() in main.c. You can do something similar to send the command that you need to send. Alternatively, you can see that it uses printf() in the main() function to send "\r\nUart started.\r\n" when the application is starting. This printf() function is enabled by adding the retarget.c, but if you struggle to get this working in your own custom application, I would suggest that you just use app_uart_put.

Best regards,

Edvin

RE: UARTE.h

user116078 — Sat, 14 May 2022 02:24:02 GMT

Also is there a way for me to delete this code once I get an answer?