Add UART1 in Devicetree address range collides with others peripherals

RE: Add UART1 in Devicetree address range collides with others peripherals

Einar Thorsrud — Wed, 03 Apr 2024 08:02:32 GMT

Hi Tina,

I see. That sample only use one UART, and specifically the UART that is configured as the Zephyr console. So if you want to add another UART and use that you need to add code for using it. I suggest you take a look at Lesson 5 – Serial communication (UART) as well as the exercise for that module as an example of how you can do that.

RE: Add UART1 in Devicetree address range collides with others peripherals

yithwe — Tue, 02 Apr 2024 12:43:27 GMT

Hi Einar Thrsrud

I use v2.5.2\zephyr\samples\drivers\uart\echo_bot sample code, I need to open two serial terminal window and connect two uart for view the result and feedback speed.

Best Regards

Tina

RE: Add UART1 in Devicetree address range collides with others peripherals

Einar Thorsrud — Tue, 02 Apr 2024 12:34:10 GMT

Hi,

UART0 is enabled in the generated DTS you uploaded:

			uart0: uart@8000 {
				compatible = "nordic,nrf-uarte";
				reg = < 0x8000 0x1000 >;
				interrupts = < 0x8 0x1 >;
				status = "okay";
				current-speed = < 0xe1000 >;
				pinctrl-0 = < &uart0_default >;
				pinctrl-1 = < &uart0_sleep >;
				pinctrl-names = "default", "sleep";
			};

However, it is not used for anything directly, unlike uart1:

	chosen {
		zephyr,entropy = &cryptocell;
		zephyr,flash-controller = &flash_controller;
		zephyr,console = &uart1;
		zephyr,shell-uart = &uart1;
		zephyr,uart-mcumgr = &uart1;
		zephyr,bt-mon-uart = &uart1;
		zephyr,bt-c2h-uart = &uart1;
...

How do you intend to use UART0 and in what way does it not work?

RE: Add UART1 in Devicetree address range collides with others peripherals

yithwe — Tue, 02 Apr 2024 12:14:09 GMT

Hi Einar Thorsrud

I rebuild the project, but UART0 isn't activate, it seen "overridden by later entry", zephyr.dts also no uart0 inforation, attached file is zephyr.dts in build floder.

devzone.nordicsemi.com/.../8103.zephyr.dts

Best Regards

Tinadevzone.nordicsemi.com/.../8103.zephyr.dts

RE: Add UART1 in Devicetree address range collides with others peripherals

Einar Thorsrud — Tue, 02 Apr 2024 10:36:40 GMT

Hi Tina,

[quote user="yithwe"]Another question is how to set the uart as slave type?[/quote]

There is no master/slave concept in UART. Both devices are equal.

[quote user="yithwe"]but UART1 is not activate as below picture.[/quote]

Did you re-build the project? If not, the highlighting in the IDE might be incorrect (and in some other cases as well). The best way to see what you ended up with is to look at the generated zephyr.dts file in your build folder.

RE: Add UART1 in Devicetree address range collides with others peripherals

yithwe — Mon, 25 Mar 2024 05:07:54 GMT

Hi Einar Thorsrud

Another question is how to set the uart as slave type?which and where I need to config for uart slave status?and how to active UART0 and UART1 at the same time?it's need to modify nrf5340_cpuapp_common.dts file?

below is I mark for i2c and release the resource for UART1, I saw the UART1 is not address range collides, but UART1 is not activate as below picture.I also add the chosen as below picture, can't active UART0 & UART1 at the same time.

I use Uart/echo sample for this setting.

Best Regards

Tina

RE: Add UART1 in Devicetree address range collides with others peripherals

Einar Thorsrud — Fri, 22 Mar 2024 14:25:01 GMT

Hi Tina,

Yes, that is correct.

RE: Add UART1 in Devicetree address range collides with others peripherals

yithwe — Fri, 22 Mar 2024 13:38:35 GMT

So it means if I no need to use for i2c peripherals for this time,I can omit or disable for i2c and release the resource for UART1?

Best Regards

Tina

RE: Add UART1 in Devicetree address range collides with others peripherals

Einar Thorsrud — Fri, 22 Mar 2024 13:23:52 GMT

Hi,

Many peripheral shares internal resoruces and cannot be enabled at the same time. These are peripherals with the same ID. There is no way to use these simultaniously, so you need to pick a different set of instances that does not overlap.