Using internal flash with custom partitions and BT OTA DFU and MCUboot enabled

RE: Using internal flash with custom partitions and BT OTA DFU and MCUboot enabled

Revilo — Mon, 08 Apr 2024 13:07:35 GMT

Thank you! This did it.

RE: Using internal flash with custom partitions and BT OTA DFU and MCUboot enabled

Vidar Berg — Mon, 08 Apr 2024 12:24:12 GMT

The PM generated symbols can be found in build/zephyr/generated/pm_config.h. Here is a modified version of the soc_flash_nrf sample where I added the 'myadt_partition' partition:

devzone.nordicsemi.com/.../soc_5F00_flash_5F00_nrf.zip

RE: Using internal flash with custom partitions and BT OTA DFU and MCUboot enabled

Revilo — Mon, 08 Apr 2024 11:07:28 GMT

Thanks for that hint. I think I still have to define it in the dts with the same address ranges as in pm_static, because the child image build somehow still needs it, but this might be another thing to solve, so I think I'm good for now with keeping dts and pm_static in sync.

As you can see in my initial post, I allready defined my data partition in the pm_static. So how can the device structure be obtained? const struct device* const flash_dev = FIXED_PARTITION_DEVICE(DATAPART_DT_LABEL); obviously does not work.

RE: Using internal flash with custom partitions and BT OTA DFU and MCUboot enabled

Vidar Berg — Mon, 08 Apr 2024 09:59:19 GMT

Hello,

When you perform a multi-image build (that is, enabling the bootloader), the partition manager takes over and controls the memory partition layout. As a result, the partitions defined in the Device Tree will be ignored.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.6.0/nrf/scripts/partition_manager/partition_manager.html

Therefore, you will need to define your custom partition in your pm_static file.

Best regards,

Vidar