UART example - nRF 9160 DK

[pastucha.grzegorz]

Hello, I'm trying to test the UART example for nRF 9160 DK. To my understanding, any input sent through one of the ports should appear in the other one (from uart1 to uart0, being the one with "uart loopback" printf). So I set up two terminals (I was trying with multiple programs) and it seems that the "receiver" works fine, but the "sender" just won't work. I'm trying with the second port, while the third remaining spits "STATIC VERSION OF NRF52 board control Firmware" every few seconds. So i'm trying to send something through the one port that doesn't print anything, but without success. The ports are configured as 115200 8n1, no handshake. Using other programs (like at_client) work in the same terminals with the same settings. There's really not much to configure in this project and also I don't think there's much debug data that I could extract from it. What could be causing this problem? I'll upload the merged.hex file as attachment.

Firmware: 1.0.0
Board v0.7.0
SES V4.16 Nordic Edition (64-bit)

merged.hex

[Didrik Rokhaug]

Hi.

Is this the example you are using?

That example does not use multiple UART peripherals by default. It reads from UART_0, and prints the output (also to UART_0). If you change UART_0 to UART_1 in the call to device_get_binding it will read from UART_1, and print to UART_0.

While the nRF9160 opens 3 ports to the PC, only one is usable from the nRF9160 by default. One is connected to the nRF52840 acting as a board controller, while the last one is not connected by default. Take a look at the documentation here. The unconnected port can be connected to UART_1 on the nRF9160 by flashing the "hello_world" sample to the board controller as described in the nRF9160DK and NCS documentation.

Remember to configure any peripherals you use as non-secure if your application is running in non-secure mode as described in the NCS tutorial.

Best regards,

Didrik