MCUBoot not outputting via UART on boot

RE: MCUBoot not outputting via UART on boot

Kazi Afroza Sultana — Tue, 29 Nov 2022 13:40:56 GMT

You are welcome. Great that it is fixed now.

RE: MCUBoot not outputting via UART on boot

Ryisen — Tue, 29 Nov 2022 09:10:26 GMT

Well, I was able to fix it.

As expected, it had to do with our devicetree overlay. I took a look at the generated zephyr.dts file of the central_bas project as well as the MCUBoot child image and the UART_0 tx and rx pins where configured differently.

After some checks I added the content of our devicetree overlay to the dts.overlay in bootloader/mcuboot/boot/zephyr and now it works. I get the expected MCUBoot output when I start/reset our board.

Thank you for your time.

Best regards,

Alex

RE: MCUBoot not outputting via UART on boot

Ryisen — Tue, 29 Nov 2022 08:06:54 GMT

That's what I get on the development kit too, right.

But on our custom board the MCUBoot output is missing.

My best guess is that it has to do with our devicetree overlay. It is needed to correctly run the project on our custom board. Do I need to add the devicetree overlay to the MCUBoot too?

RE: MCUBoot not outputting via UART on boot

Kazi Afroza Sultana — Tue, 29 Nov 2022 08:01:14 GMT

I have run the sample central_bas on nRF5340 DK using version NCS V2.1.2. The only change I made on the prj.conf file by this adding CONFIG_BOOTLOADER_MCUBOOT=y. I have this output where MCU boot output is ok.

My team member has also tried with v1.6.1 and it showed the correct output. I will look into few other issues for your case. I will get back to you later.

RE: MCUBoot not outputting via UART on boot

Ryisen — Mon, 28 Nov 2022 16:32:14 GMT

This would be the putty output from our custom board with MCUBoot enabled:

*** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***

I: 2 Sectors of 4096 bytes

I: alloc wra: 0, fd8

I: data wra: 0, 1c

I: HW Platform: Nordic Semiconductor (0x0002)

I: HW Variant: nRF53x (0x0003)

I: Firmware: Standard Bluetooth controller (0x00) Version 239.2307 Build 3063314844

W: ECC HCI commands not available

I: No ID address. App must call settings_load()

Bluetooth initialized

I: Identity: F4:0F:80:D0:C0:B3 (random)

I: HCI: version 5.2 (0x0b) revision 0x222b, manufacturer 0x0059

I: LMP: version 5.2 (0x0b) subver 0x222b

Scanning successfully started

...

As you can see, the MCUBoot output is missing. So my best guess was that there might be some missing configuration that tells MCUBoot to output there as the usual application output works.

RE: MCUBoot not outputting via UART on boot

Kazi Afroza Sultana — Mon, 28 Nov 2022 16:26:52 GMT

output from terminal like putty. Also you can find it nRF terminal in VS Code.

RE: MCUBoot not outputting via UART on boot

Ryisen — Mon, 28 Nov 2022 13:59:59 GMT

Which log exactly do you mean? Where do I get it?

RE: MCUBoot not outputting via UART on boot

Kazi Afroza Sultana — Mon, 28 Nov 2022 13:58:44 GMT

Can I get the log of this version (1.6.1)?

RE: MCUBoot not outputting via UART on boot

Ryisen — Mon, 28 Nov 2022 13:42:36 GMT

Running our code on a newer NCS version produces lots of function undefined errors, therefore I would like to keep it at v1.6.1 for now.

RE: MCUBoot not outputting via UART on boot

Kazi Afroza Sultana — Mon, 28 Nov 2022 13:33:13 GMT

Hello,

Have you tried to run this sample other version (upgraded) than v1.6.1?

Thanks.

Best Regards,

Kazi Afroza Sultana