uart_console error

RE: uart_console error

chris_h — Thu, 13 Jul 2023 17:15:40 GMT

Hi Lam,

The purpose of overlays is to override hardware properties, and prj.conf to override software properties through kconfig fragments. This way you don't have to hack away at the original device tree / config files that would affect other projects too.

Think of the case where you want to use one of the Nordic / Zephyr examples on your DK - the build configuration will source your modified device tree files from your sdk folder, and potentially cause errors before you've even started.

As for re-purposing uart0, that's fairly simple. As you noted, uart0 is currently assigned to the console messages in the device tree and this is enabled by default in the nrf9160dk_nrf9160_ns_defconfig file. You can override these default settings by disabling it on the prj.conf file.

Add the following lines to prj.conf to disable the console.

# disable console
CONFIG_CONSOLE=n
CONFIG_UART_CONSOLE=n

As per the example I uploaded: modify the overlay file to uart0 (instead of uart1), and modify the device pointer in main.c to

const struct device *uart= DEVICE_DT_GET(DT_NODELABEL(uart0));

then the uart tx_start_msg should instead print out via uart0 to the same pins 14 and 15, and uart0 will not contain any console messages.

Regards,

Chris

RE: uart_console error

Lamdev — Thu, 13 Jul 2023 15:33:45 GMT

Hi chris_h,

Thanks for your help,

i assume that it's better to let uart0 for uart_console but i need to disable the "chosen" content.

It's because i have work in a bigger project where this part is disable but i have problem with MCUBOOT to do FOTA.

So to understand step after step, i have recreate a project where i reimplement each part after each part.

Could you tell me if you can advice me an other way ?

For information my other topic with MCUBOOT issue for my biggest soft, the main problem is stillthe same:

https://devzone.nordicsemi.com/f/nordic-q-a/99692/nrf9160-bootloader-issue

Best regards,

Lam

RE: uart_console error

chris_h — Thu, 13 Jul 2023 15:22:01 GMT

Hi Lam, so there's not a whole lot in that project! If you're working with the DK, its best to modify overlay files, rather than the actual device tree files in your sdk directory.

I've mainly been working with uart1 on the 9160, which seems to work well. It's good to reserve uart0 for terminal messages. I've modified one of my projects (attached) which serves as a basic uart handler with your custom uart pins on the 9160, achieved through the overlay. This should be a good starting point which you can build on - let me know if that helps.

devzone.nordicsemi.com/.../uart_5F00_basics.zip

RE: uart_console error

Lamdev — Thu, 13 Jul 2023 14:28:09 GMT

Hey Kenneth,

Here an example when i meet the problem,

For the moment my objectif is to build correctly this example without using uart_console because all my debug go on RTT and uart0 i used for my peripheral.

devzone.nordicsemi.com/.../antenna_2D00_sensor_2D00_lte_5F00_nrf9160.rar

Best regards,

Lam

RE: uart_console error

Kenneth — Thu, 13 Jul 2023 14:17:47 GMT

Hi,

I think if you want us to look into this please provide an example we can compile to recreate it here.

Kenneth

RE: uart_console error

Lamdev — Thu, 13 Jul 2023 09:35:20 GMT

Hello chris_h ,

Thanks for your help,

Yes i have define my device tree for all the peripheral that i need.

There my device tree :

//nrf9160dk_nrf9160_ns.dts

/dts-v1/;
#include <nordic/nrf9160ns_sica.dtsi>
#include "nrf9160dk_nrf9160_common.dts"

/ {
	chosen {
		zephyr,flash = &flash0;
		zephyr,sram = &sram0_ns;
		zephyr,code-partition = &slot0_ns_partition;
	};
};

/* Disable UART1, because it is used by default in TF-M */
// &uart1 {
// 	status = "disabled";
// };

//nrf9160dk_nrf9160_common.dts

#include "nrf9160dk_nrf9160_common-pinctrl.dtsi"

/ {
	model = "Nordic nRF9160 DK NRF9160";
	compatible = "nordic,nrf9160-dk-nrf9160";

	chosen {
		//zephyr,console = &uart0;
		//zephyr,shell-uart = &uart0;
		//zephyr,uart-mcumgr = &uart0;
	};

	aliases{
		swin0 = &button0;
		swin1 = &button1;
		swin2 = &button2;
		swin3 = &button3;
		swin4 = &button4;
		intaccel = &intaccel;
	};

	buttons {
		 
		compatible = "gpio-keys";
		button0: button_0 {
			gpios = <&gpio0 3 (GPIO_ACTIVE_LOW)>;
			label = "SWIN0";
		};
		button1: button_1 {
			gpios = <&gpio0 4 (GPIO_ACTIVE_LOW)>;
			label = "SWIN1";
		};
		button2: button_2 {
			gpios = <&gpio0 5 (GPIO_ACTIVE_LOW)>;
			label = "SWIN2";
		};
		button3: button_3 {
			gpios = <&gpio0 6 (GPIO_ACTIVE_LOW)>;
			label = "SWIN3";
		};
		button4: button_4 {
			gpios = <&gpio0 7 (GPIO_ACTIVE_LOW)>;
			label = "SWIN4";
		};
		intaccel: intaccel {
			gpios = <&gpio0 10 (GPIO_ACTIVE_LOW)>;
			label = "INTACCEL";
		};

	};

};

/{
	zephyr,user{
		io-channels = <&adc 0>;
	};
};

&adc {
	status = "okay";
	#address-cells = <1>;
	#size-cells = <0>;
	channel@0 {
		reg = <0>;
		zephyr,gain = "ADC_GAIN_1_6";
		zephyr,reference = "ADC_REF_INTERNAL";
		zephyr,acquisition-time = <ADC_ACQ_TIME(ADC_ACQ_TIME_MICROSECONDS, 20)>;
		zephyr,input-positive = <NRF_SAADC_AIN0>;
	};
};

&uart0 {
	status = "okay";
	current-speed = <9600>;
	pinctrl-0 = <&uart0_default>;
	pinctrl-1 = <&uart0_sleep>;
	pinctrl-names = "default", "sleep";
};

&i2c1 {
	status = "okay";
	clock-frequency = <I2C_BITRATE_FAST>;
	pinctrl-0 = <&i2c1_default>;
	pinctrl-1 = <&i2c1_sleep>;
	pinctrl-names = "default", "sleep";
};

&gpiote {
	status = "okay";
};

&gpio0 {
	status = "okay";
};

&timer0 {
	status = "okay";
};

&timer1 {
	status = "okay";
};

&timer2 {
	status = "okay";
};

&flash0 {

	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x00000000 0x10000>;
		};
		slot0_partition: partition@10000 {
			label = "image-0";
		};
		slot0_ns_partition: partition@50000 {
			label = "image-0-nonsecure";
		};
		slot1_partition: partition@80000 {
			label = "image-1";
		};
		slot1_ns_partition: partition@c0000 {
			label = "image-1-nonsecure";
		};
		scratch_partition: partition@f0000 {
			label = "image-scratch";
			reg = <0x000f0000 0xa000>;
		};
		storage_partition: partition@fa000 {
			label = "storage";
			reg = <0x000fa000 0x00006000>;
		};
	};
};

/ {

	reserved-memory {
		#address-cells = <1>;
		#size-cells = <1>;
		ranges;

		sram0_s: image_s@20000000 {
			/* Secure image memory */
		};

		sram0_modem: image_modem@20016000 {
			/* Modem (shared) memory */
		};

		sram0_ns: image_ns@20020000 {
			/* Non-Secure image memory */
		};
	};
};

/* Include partition configuration file */
#include "nrf9160dk_nrf9160_partition_conf.dts"

//nrf9160dk_nrf9160_common-pinctrl.dtsi

&pinctrl {

	uart0_default: uart0_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 7)>;
		};
		group2 {
			psels = <NRF_PSEL(UART_RX, 0, 6)>;
			bias-pull-up;
		};
	};

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

	uart2_default: uart2_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 15)>,
				<NRF_PSEL(UART_RX, 0, 14)>;
		};
	};

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

	i2c1_default: i2c1_default {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 0, 11)>,
				<NRF_PSEL(TWIM_SCL, 0, 12)>;
		};
	};

	i2c1_sleep: i2c1_sleep {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 0, 11)>,
				<NRF_PSEL(TWIM_SCL, 0, 12)>;
			low-power-enable;
		};
	};
	
};

My prj.conf is the following :

#prj.conf

# nothing here

#MCUBOOTLOADER
CONFIG_BOOTLOADER_MCUBOOT=y

#LOG
CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=4
CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_LOG_PRINTK=y
CONFIG_STDOUT_CONSOLE=y

#Segger RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_LOG_BUFFER_SIZE=4096

Maybe i missing someting, i have try to define an uart for the console but i still have the same problem but with an other reference of the device tree.

I add this into my nrf9160dk_nrf9160_common.dts :

chosen {
		zephyr,console = &uart2;
		zephyr,shell-uart = &uart2;
		zephyr,uart-mcumgr = &uart2;
	};
	
	
&uart2 {
	 	pinctrl-0 = <&uart2_default>;
	 	pinctrl-1 = <&uart2_sleep>;
	 	pinctrl-names = "default", "sleep";
	 };

The error :

In file included from C:\ncs2\v2.2.0\zephyr\include\zephyr\toolchain\gcc.h:88,
                 from C:\ncs2\v2.2.0\zephyr\include\zephyr\toolchain.h:50,
                 from C:\ncs2\v2.2.0\zephyr\include\zephyr\kernel_includes.h:19,
                 from C:\ncs2\v2.2.0\zephyr\include\zephyr\kernel.h:17,
                 from C:\ncs2\v2.2.0\zephyr\drivers\console\uart_console.c:16:
C:\ncs2\v2.2.0\zephyr\include\zephyr\device.h:83:41: error: '__device_dts_ord_80' undeclared here (not in a function); did you mean '__device_dts_ord_8'?
   83 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)

I have made a very basic hello_world project and delete and reupload SDK2.2.0, to reproduce my issue:

When i put in comment this line in nrf9160dk_nrf9160_common.dts, i can reproduce my issue.

	chosen {
		//zephyr,console = &uart0;
		//zephyr,shell-uart = &uart0;
		//zephyr,uart-mcumgr = &uart0;
	};

Could it be possible to just disable uart_console, because i only use RTT for debugging and uart0 for one of my peripheral ?

Best regards,

Lam

RE: uart_console error

chris_h — Wed, 12 Jul 2023 15:38:14 GMT

Hi Lam, I am by no means a Nordic expert, but I did encounter and resolve a very similar problem in my own project recently. This looks to be a device tree / overlay error. You didn't specify which UART you are using, but you'll need to enable it in the device overlay. If its uart1, this is done as follows:

&uart1 {
    status = "okay";
};

To use uart in your application, you'll need to get the device pointer which can be done in a number of ways, with the "uart1" example below

#include <zephyr/device.h>

const struct device *uart= DEVICE_DT_GET(DT_NODELABEL(uart1));

Hope that helps!