nRF52 FDS application size

[Rajneesh]

Hello Nordic team,

I am working on ble_peripheral example. Initially application binary file size is 100 KB but after adding support of FDS application size increased to 156KB. That mean FDS increase the application size to 56KB?

After adding support of FDS in any BLE_Peripheral example code, application code size increased by approximate 56KB?

Any information will be appreciated.

Regards,

Rajneesh

[Einar Thorsrud]

Hi,

This seems a bit odd. Both because 56 kB is huge, but also because most BLE peripheral examples already use FDS via the Peer manager. Can you explain in detail what you are doing and which SDK version you are using?

[Rajneesh]

Thanks for the quick reply.

I am using SDK-11.0.0 and hrs_with_dfu example on nRF52832 and S132 softdevice. My application size is 100KB after adding support of FDS application output file (Hex) file increase to 156KB. Then I removed FDS support and add fstorage support it increase from 100 KB to 136KB.

I don't think FSD or fstorage increase this much amount of file size.

Any highlight in this is appreciated.

[Einar Thorsrud]

Ah, I see. FDS was experimental and quite unfinished in SDK 11. I do not have an explanation for the large increase in size, but I suggest that you move to a newer SDK (particularly if you want to use FDS or fstorage, or any of the other experimental features). The latest SDK for nRF52832 is version 15.

[Rajneesh]

ok thanks.

[Rajneesh]

Found the reason, For using fstorage I need to change optimization level from LEVEL-3 to LEVEL-0 and it increase code size. Do you know at what optimization level fstorage/FSD works?

[Einar Thorsrud]

There have been some issues with the early SDK's with experimental support, but storage (and FDS) is used with optimization level 3 in most SDK examples since SDK 12.0.0.