Removing the storage partition

RE: Removing the storage partition

AHaug — Tue, 10 Feb 2026 11:15:17 GMT

Noted, make sure that you properly evaluate that you will not need bonding/persistant BLE settings data and/or that you include it in a different storage partition since this will not be possible to add through DFU at a later point in time.

Kind regards,
Andreas

RE: Removing the storage partition

Narendra — Tue, 10 Feb 2026 10:16:58 GMT

Hi Andreas,

Please note we are using pm_static.yml file for flash mapping and have set the CONFIG_SETTINGS=n

We have removed settings_storage partition from pm_static.yml file. And firmware build without error.

Thanks,

Narendra

RE: Removing the storage partition

AHaug — Tue, 10 Feb 2026 10:03:24 GMT

Hi Narendra,

[quote user=""]What will be the downside of removing setting_storage? Will it create any issue?[/quote]

The settings_storage partition is automatically included when you add BLE to the project because this is where Bluetooth settings and persistant data such as bonding information is stored. The partition is by default 4kB or 8kB if I remember correct and can be reduced if you don't need to store large amount of BLE settings/bonding information. You use roughly about 80 bytes per bonding, plus at least one flash page for garbage collection.

Bluetooth settings can be stored in a different partition than the default settings_storage, but only if you reconfigure where the Zephyr settings subsystem stores its data.

Kind regards,
Andreas