Debug Log not shown in RTT either Uart in custom pcb of 9160

Question

Hello Nordic Team, 
 My application is cellular asset tracker type and we have design custom pcb using nRF9160 device. 
 I am using ncs SDK version: v2.8.0 and toolchain version: v2.8.0 and I have flased latest modem firmware nrf9160dk_mfw-1.3.7_sdk-2.8.0 in my PCB. 
 
 Now, I am try to flash default example code like asset_tracker_v2,at_monitor,gnss according to my use cases. 
 I have manage proper build configuration and also added my custom cellular_telemetric_devise.overlay file for change default Uart0 pin to my custom pcb. I have a ttached file for your reference. 
 
 cellular_telemetric_devise.overlay 
 But I can't see log over Uart to TTL. I have also try using RTT enable and try to view NRF log in RTT viewer but not showing any log. I have try same build and .overlay file in nRF9160 dk Kit in that all things working properly it's redirect log default Uart0 to my custom defined Uart1 pin and i can see log and also RTT log on RTT viwer. 
 
 Below are main changes made in different example code in default prj.conf file for RTT Log and Uart Log. I have attached asset_tracker_v2 prj.conf file for your reference 
 70678.prj.conf 
 ### Logger module CONFIG_USE_SEGGER_RTT=y CONFIG_RTT_CONSOLE=y CONFIG_LOG_BACKEND_RTT=y CONFIG_LOG=y CONFIG_LOG_MODE_DEFERRED=y CONFIG_LOG_BACKEND_UART=n CONFIG_LOG_SPEED=y CONFIG_UART_CONSOLE=n 
 Meanwhile after flashing I showed Uart log which i share below, 
 In GNSS example : 
 All pins have been configured as non-secure [1;34mBooting TF-M v2.1.1-ncs1[0m [1;34m[Sec Thread] Secure image initializing![0m TF-M Float ABI: Hard Lazy stacking enabled 
 In at_monitor : 
 All pins have been configured as non-secure [1;34mBooting TF-M v2.1.1-ncs1[0m [1;34m[Sec Thread] Secure image initializing![0m Kindely help me to enable both Uart log and RTT log in my custom PCB. Is there any additional macro add into prj.conf file? or any other changes. 
 It will really help me to move forward my task.

Håkon Alseth · Accepted Answer

Hi,

Thank you for sharing the .dts file.

You are trying to redefine the pinctrl entires, but you are reusing the same name. However, this is only possible if you follow the exact same setup as the original definition.

I would rather recommend that you rename your uart0_default and uart1_default to for instance "my_uart0_default" / "my_uart1_default".

Something like this:

...


&uart0 {
    compatible = "nordic,nrf-uarte";
    current-speed = <115200>;
    status = "okay";
    hw-flow-control;

    pinctrl-0 = <&my_uart0_default>;
    pinctrl-1 = <&my_uart0_sleep>;
    pinctrl-names = "default", "sleep";
};

&uart1 {
    compatible = "nordic,nrf-uarte";
    current-speed = <115200>;
    status = "okay";
    hw-flow-control;

    pinctrl-0 = <&my_uart1_default>;
    pinctrl-1 = <&my_uart1_sleep>;
    pinctrl-names = "default", "sleep";
};


&pinctrl {

    // Communication uart0
	my_uart0_default: my_uart0_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 29)>,
				<NRF_PSEL(UART_RX, 0, 28)>;
		};
	};

	my_uart0_sleep: my_uart0_sleep {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 29)>,
				<NRF_PSEL(UART_RX, 0, 28)>;
			low-power-enable;
		};
	};
    my_uart1_default: my_uart1_default
    {
        group1 {
            psels = <NRF_PSEL(UART_TX, 0, 1)>,
                <NRF_PSEL(UART_RX, 0, 0)>;
        };
    };

    my_uart1_sleep: my_uart1_sleep
    {
        group1 {
            psels = <NRF_PSEL(UART_TX, 0, 1)>,
                    <NRF_PSEL(UART_RX, 0, 0)>;
            low-power-enable;
        };
    };
};

Could you try this and see if it works as expected now?

Kind regards,

Håkon

Debug Log not shown in RTT either Uart in custom pcb of 9160

Top Replies