Peer manager, fstorage, does it have address range limitations.

[PACMAN]

We are moving from the Device Manager to Using the Peer Manager.

Up to now we have been using pstorage for

1 log files

2 configuration data

3 firmware upgrade downloads while the main application is active rather during the reboot  phase.

up to now we have used three handles for each storage area. Using fstorage we should/hope to be able to use a start and end address which covers the entire range for firmware, log file and configuration data.

The range of flash we hope to write to using fstorage is quite wide. Are there any limitations with regards to where data can and cannot be written and read.

[Einar Thorsrud]

Hi

The fstorage library just handles basic flash operations (writes and erase) in a way that is compatible with using both SoftDevice and direct access (using two different backends). It can be used to manipulate any part of the flash, with the notable exception that you cannot use it to write within the SoftDevice region, which is protected.

This is different from FDS, which is a higher level file system built on top of fstorage. FDS only use a single region of flash, which starts from the end of the application region (typically right below the bootloader) and a configured number of pages downwards.