mcuboot differences between 2.5.0 to ncs2.8.0 breaks stuff

RE: mcuboot differences between 2.5.0 to ncs2.8.0 breaks stuff

ziv123 — Thu, 27 Mar 2025 13:44:57 GMT

issue was solved by explicitly defining a gpio that can be both NFC and gpio as gpio..

https://docs.zephyrproject.org/latest/releases/migration-guide-3.5.html#recommended-changes

this need was introduced after ncs2.5.0

so just added this to relevant dts solved it

&uicr {
	nfct-pins-as-gpios;
};

best regards

Ziv

RE: mcuboot differences between 2.5.0 to ncs2.8.0 breaks stuff

AHaug — Wed, 26 Mar 2025 11:14:22 GMT

Hi,

The reason is most likely that the things you've previously defined in child_images/mcuboot.conf is not picked up. Could you share your project structure? I'm expecting to see something like this with mcuboot.conf inside the sysbuild folder as explained here https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/

Kind regards,
Andreas

RE: mcuboot differences between 2.5.0 to ncs2.8.0 breaks stuff

ziv123 — Wed, 26 Mar 2025 07:45:24 GMT

working with sysbuild in ncs2.8.0

i really think its about the mcuboot change when i run the same application (app is based on v2.8.0) with mcuboot of 2.5.0 it works and when i flash mcuboot of 2.8.0 it does not work

i see a lot of diffs between .config file of the mcuboot in 2.5.0 and 2.8.0 builds

RE: mcuboot differences between 2.5.0 to ncs2.8.0 breaks stuff

AHaug — Wed, 26 Mar 2025 07:42:04 GMT

Hi,

Is the new firmware in NCS v2.8.0 based on sysbuild or are you still using child and parent images (deprecated in 2.9.0)?

Kind regards,
Andreas