UART0 resource always busy after integrate MCU boot in our project

RE: UART0 resource always busy after integrate MCU boot in our project

Menon — Fri, 14 Jun 2024 13:37:52 GMT

Hello,

Sorry, I was held up with some other work, which caused the delay in responding..

[quote user="Deus Matei [EMERSON]"]My current issue with UART1 is that address range collides with I2C1. There's any way to assign a different address to the UART peripheric?

By the phrase "address range colliding," I assume that you are encountering a conflict in GPIO pin assignments between UART1 and I2C1. If both UART and I2C are using the same pin, then I recommend creating an overlay file and reassigning the pins for UART and I2C. If this is not the issue, could you provide more details on the problem, such as the error message or logs?

[quote user="Deus Matei [EMERSON]"]Also because there's no mcuboot.overlay it will still use uart0 as DFU by wire? Please help to clarify this also

Yes, it is true that MCUBoot typically uses UART0 for serial recovery. However, when the booting process is over or when MCUBoot has completed its tasks, the main application takes control. When the main application starts, the peripheral resources, including UART0, are effectively reset and re-initialized.

Kind Regards,

Abhijith

RE: UART0 resource always busy after integrate MCU boot in our project

Deus Matei [EMERSON] — Mon, 10 Jun 2024 12:53:17 GMT

Also because there's no mcuboot.overlay it will still use uart0 as DFU by wire? Please help to clarify this also.

RE: UART0 resource always busy after integrate MCU boot in our project

Deus Matei [EMERSON] — Mon, 10 Jun 2024 12:49:44 GMT

Hi, first I tried to assign uart2 to all zpehyr services in app.overlay. This solved my issue.

/ {
	chosen {
		nordic,pm-ext-flash = &mx25r64;
		nordic,nus-uart = &uart2;
        zephyr,console = &uart2;
		zephyr,shell-uart = &uart2;
		zephyr,uart-mcumgr = &uart2;
		zephyr,bt-mon-uart = &uart2;
		zephyr,bt-c2h-uart = &uart2;
	};
};

Another question, I'll need UART2 for a different purpose in the app so I plan to move them to UART1. My current issue with UART1 is that address range collides with I2C1. There's any way to assign a different address to the UART peripheric?

RE: UART0 resource always busy after integrate MCU boot in our project

Menon — Mon, 10 Jun 2024 10:17:37 GMT

Hello,

Thanks for sharing the details. Please update me with the results.

Kind Regards,

Abhijith

RE: UART0 resource always busy after integrate MCU boot in our project

Deus Matei [EMERSON] — Mon, 10 Jun 2024 08:58:21 GMT

Hi, we're using nrf5340 with SDK 2.4.0. I'm trying this option, I'll come back with results

RE: UART0 resource always busy after integrate MCU boot in our project

Menon — Mon, 10 Jun 2024 07:55:14 GMT

Hello,

Could you share which SDK version you are using here? I assume that you are using nRF5340 (let me know if this is not the case). Do you have any logs to share? MCUBoot might be configured to use UART0 for logging or debugging purposes, which can cause the "resource busy" error when your application tries to use the same UART peripheral. See your mcuboot.conf file and see whether UART0 has been enabled for logging or debugging.

Try disabling the UART0 just for mcuboot. For this, create an overlay file inside the child image folder as mcuboot. overlay and disable the UART0 there, and see if this works. Make sure UART0 is enabled for the application.

Kind Regards,

Abhijith