Greetings,
After migrating to the NCS v2.5.2, I noticed a warning that recommends using static partition management (which I have also confirmed is recommended by other Nordic engineers in various support cases).
For our use case for which we have a Bootloader (MCUBoot, non-upgradable) + Application (upgradable via OTA) is the static partition necessary because every time I perform a new build I check the current partition configuration and it is always the same and aligns with the partition configuration defined in out custom boards partition node.
Partition node:
//Relevant chosen section of the .dts file
chosen {
zephyr,console = &uart0;
zephyr,uart-mcumgr = &uart0;
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,code-partition = &slot0_partition;
};
/* Flash configuration copied from nRF52840DK */
&flash0 {
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
boot_partition: partition@0 {
label = "mcuboot";
reg = <0x00000000 0x0000C000>;
};
slot0_partition: partition@c000 {
label = "image-0";
reg = <0x0000C000 0x00067000>;
};
slot1_partition: partition@73000 {
label = "image-1";
reg = <0x00073000 0x00067000>;
};
scratch_partition: partition@da000 {
label = "image-scratch";
reg = <0x000da000 0x0001e000>;
};
/*
* The flash starting at 0x000f8000 and ending at
* 0x000fffff is reserved for use by the application.
*/
/*
* Storage partition will be used by FCB/LittleFS/NVS
* if enabled.
*/
storage_partition: partition@f8000 {
label = "storage";
reg = <0x000f8000 0x00008000>;
};
};
};
So my question is, since the partitions created are always the same (same start address and length for the application partition), is the static partition management configuration really necessary for our use case (we won't have more than one upgradable fw image in the future)?
Thank you!
Best regards,
Stavros
