Issues going from SDK 2.6.3 to 2.9.1

RE: Issues going from SDK 2.6.3 to 2.9.1

jvermillard — Fri, 22 Aug 2025 15:49:18 GMT

had a similar issue, a pristine build fixed it (just in case someone stumble on this)

RE: Issues going from SDK 2.6.3 to 2.9.1

JonathanRJ — Tue, 24 Jun 2025 13:20:24 GMT

After a complete reinstall of the SDK is everything working as expected

RE: Issues going from SDK 2.6.3 to 2.9.1

Vidar Berg — Wed, 23 Apr 2025 09:27:21 GMT

Excellent. Just address the ticket to me and let me know if there are any special steps required to build the project.

RE: Issues going from SDK 2.6.3 to 2.9.1

JonathanRJ — Wed, 23 Apr 2025 09:24:59 GMT

I can share it in a private support ticket, anything special i need to do when submitting it?

RE: Issues going from SDK 2.6.3 to 2.9.1

Vidar Berg — Wed, 23 Apr 2025 09:21:20 GMT

I can't think of any obvious reason why these partitions are not generated after migrating your project to SDK v2.9.1, and I wasn't able to reproduce the issue using the board you defined. Are you able to share your project here or in a private support ticket so I can have a look at the configuration?

RE: Issues going from SDK 2.6.3 to 2.9.1

JonathanRJ — Wed, 23 Apr 2025 08:55:39 GMT

The application is not included in the SDK. When i look at the partitions from the memory report from the working version (SDK 2.6.3) is it close to the same as you have in your example. However i can't see the partitions using the 2.9.1 version of the SDK, since i can't build succesfully.

As previously states is the only difference between the two version that i used the updated version of how to make a custom board, but with the same device tree declerations, and the SDK version. It just seems odd to me that it doesn't work with the change in SDK.

RE: Issues going from SDK 2.6.3 to 2.9.1

Vidar Berg — Wed, 23 Apr 2025 05:20:46 GMT

[quote user=""]However another more advanced application gives me[/quote]

Is this application included in the SDK? I tried reproducing the issue with a simple application that has the MCUBoot primary and secondary slot.

RE: Issues going from SDK 2.6.3 to 2.9.1

JonathanRJ — Tue, 22 Apr 2025 13:25:13 GMT

I've attached my board files:

devzone.nordicsemi.com/.../3122.board.zip

RE: Issues going from SDK 2.6.3 to 2.9.1

JonathanRJ — Tue, 22 Apr 2025 13:16:23 GMT

Yes the following is from a dtsi file:

&flash0 {

partitions {

compatible = "fixed-partitions";

#address-cells = <1>;

#size-cells = <1>;

boot_partition: partition@0 {

label = "mcuboot";

reg = <0x00000000 0x10000>;

};

slot0_partition: partition@10000 {

label = "image-0";

reg = <0x00010000 0x40000>;

};

slot0_ns_partition: partition@50000 {

label = "image-0-nonsecure";

reg = <0x00050000 0x35000>;

};

slot1_partition: partition@85000 {

label = "image-1";

reg = <0x00085000 0x40000>;

};

slot1_ns_partition: partition@c5000 {

label = "image-1-nonsecure";

reg = <0x000c5000 0x35000>;

};

storage_partition: partition@fa000 {

label = "storage";

reg = <0x000fa000 0x00006000>;

};

RE: Issues going from SDK 2.6.3 to 2.9.1

Vidar Berg — Tue, 22 Apr 2025 11:56:24 GMT

Hello,

It looks like the problem arises when you build a project that includes MCUBoot, but was unable to reproduce this here. I tested with a test board I created using the Board generator wizard in VS code:

devzone.nordicsemi.com/.../5481.boards.zip

Does your board dts include the mcuboot partition as shown here:

Best regards,

Vidar