Using 'nrf_fstorage' together with BLE (peer_manager)

[RoyCreemers]

I want to store data on a specific location in Flash, so it is available later on in a bootloader. The size of this data can be quite large (~ 300 kB). I'm kind of puzzled which API to use. Although there are several examples and topics on the DevZone, they seem all rather outdated.

Initial thought would be to use the sd_flash_write API directly, but that might conflict with the peer manager's use of the internal flash. I looked into the 'nrf_fstorage' package, but could not figure out how to configure the exact location in flash which is desired. 

The peer_manager already calls nrf_fstorage_init with specific locations and size (3 kB, just below the bootloader).

Im using SDK 16.0. What would be the best approach?

[Einar Thorsrud]

Hi,

If you want to store data at a specific location in a flash that is no problem. But you should keep the memory layout in mind, and make sure that you set aside reserved flash pages for this. The peer manager uses FDS, and the FDS pages (as many as you have configured) are located immediately below the bootloader. So your other user data should be below the FDS pages but above the application.

It does not matter much if you use sd_flash_* API or fstorage. The fstorage library is essentially just a slightly higher-level library that use sd_flash_* API when the SoftDevice is enabled. I would say using fstorage is cleanest, but it is not important.