uart0 setting in device tree

[Vassilis]

Hi I am using the aws_iot example on the nrf9160 DK.

I have opened the zephyr.dts file and in the section uart0: it has the following 

Fullscreen

1

2

3

4

5

6

7

8

9

10

11

12

uart0: uart@8000 {

compatible = "nordic,nrf-uarte";

reg = < 0x8000 0x1000 >;

interrupts = < 0x8 0x1 >;

status = "okay";

label = "UART_0";

current-speed = < 0x1c200 >;

tx-pin = < 0x1d >;

rx-pin = < 0x1c >;

rts-pin = < 0x1b >;

cts-pin = < 0x1a >;

};

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

uart0: uart@8000 {
				compatible = "nordic,nrf-uarte";
				reg = < 0x8000 0x1000 >;
				interrupts = < 0x8 0x1 >;
				status = "okay";
				label = "UART_0";
				current-speed = < 0x1c200 >;
                                tx-pin = < 0x1d >;
				rx-pin = < 0x1c >;
				rts-pin = < 0x1b >;
				cts-pin = < 0x1a >;
			};

I've reached this point trying to change the pins that the console outputs. But whatever change I may do at this point there is no effect.

I continue to get normal logging in the LTE Link monitor application. I even deleted the section and it still works as before.

It seems that it is taking this info from elsewhere but where?

[Sevn]

Hello,

I walked into this problem once.

You can change the pins with an overlay by clicking the pen icon next to the pinnumbers in the devicetree. You also need uart1 instead of uart0 if I remember correctly.

[Vassilis]

Thanks for the quick answer, 

by the "by clicking the pen icon next to the pinnumbers", it looks like you are referring to an editing tool which one is it?

[Sevn]

If you're in vscode, you should go to the nordic environment, there you will see, above actions, the device tree. open the "busses" folder, then open the uart folder of the uart you desire to use. You can see a few settings there. If you click the pensil, you will be able to edit your desired setting.

[Einarh]

Yes, this will create a devicetree overlay file for you containing the new values you set.

[Vassilis]

Thanks, I am using the Segger environment that's why I was not familiar with the tool.

It looks like I should give VS Code a try  

[Einarh]

You can also create the overlay file yourself in the Segger environment, but yes I would recommend giving VS Code a try.