MCUBOOT not loging, serial DFU not compile

RE: MCUBOOT not loging, serial DFU not compile

Vidar Berg — Mon, 15 Sep 2025 17:24:02 GMT

I'm glad to hear you found the problem, though it's unfortunate that you had to spend this much time to figure out what it was. Thank your for updating the ticket.

Yes, both TF-M and MCUBoot will run in the Secure Processing environment while the app will run the in the non-secure domain.

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/security/tfm/index.html

RE: MCUBOOT not loging, serial DFU not compile

szyss — Mon, 15 Sep 2025 16:41:57 GMT

Problem solved – it turned out that mcuboot is being compiled using:
Plytka_IOT_V1.dts and Plytka_IOT_V1_defconfig.
These files were almost empty because I was compiling my projects using:
Plytka_IOT_V1_ns.dts and Plytka_IOT_V1_ns_defconfig.

After some experimentation (with help from ChatGPT), I figured out that mcuboot uses different files for compilation than the non secure version.

It took me almost 3 days 😢. We eventually realized that the more data we added to mcuboot.overlay, the more things started to work.

Cheers!

RE: MCUBOOT not loging, serial DFU not compile

Vidar Berg — Mon, 15 Sep 2025 13:31:07 GMT

Hello,

When you include MCUboot in your build (SB_CONFIG_BOOTLOADER_MCUBOOT=y) without adding any configuration overlays in your mcuboot.conf, what happens? Does the bootloader fail to boot the application? Do you see any build errors or warnings?

Best regards,

Vidar