FDS_ERR_NO_PAGES problem

[Hansome]

Based on nRF5_SDK_15.3.0_59ac345 for nRF52810 application,

a. With s112_nrf52_6.1.1_softdevice.hex and app.hex, it works normally
b. Add bootloader, fds_init function will return FDS_ERR_NO_PAGES
c. Under bootloader + softdevice + application, all other functions are normal except FDS

So, How to define the FDS pages on the secure_bootloader project?

[bjorn-spockeli]

Hi Hansome,

How large is your application when its compiled? Remember that the nRF52810 only has 192kB of flash, 100kB will be used by the S112, around 24kB will be used by the bootloader. So if the application is using up most of the remaining space, then you will not have enough free memory to allocate three 4kB flash pages, i.e. 12kB flash for the FDS pages. 

Best regards

Bjørn 

[Hansome]

linking...
Program Size: Code=53364 RO-data=5520 RW-data=644 ZI-data=7308
FromELF: creating hex file...
".\_build\nrf52810_xxaa.axf" - 0 Error(s), 0 Warning(s).

[bjorn-spockeli]

Ok, so your application will need 66 192bytes of flash ( Code+RO+ZI), i.e. ~64kB.

So adding on the flash required by the SoftDevice and bootloader, i.e. 100kB and 24kB, we end up at 188kB. So there is a total of 4kB left, i.e. one flash page. So there is not any room left for the FDS pages. 

Best regards

Bjørn

[Hansome]

So what are your suggestions? My user data actually takes only a few dozen bytes.

[bjorn-spockeli]

Are you using the Peer Manager in your application? If not then I would look at fstorage over FDS as its flash footprint is mush smaller and more suitable for storing smaller chunks of data, see nRF5 SDK v15.3.0: Flash storage (fstorage).