Best way to change FS_PAGE_END_ADDR or use Peer Manager from RAM?

[Justin]

Using nRF52 with SD 132 3.0.0.

Peer manager uses fstorage to store information. I need to be able to specify the address range which fstorage can use. Is there a configurable way to do this? Right now my solution is to modify the SDK library fs_flash_page_end_addr() or FS_PAGE_END_ADDR to use a correct end address.

Alternatively, is there a way to configure peer_manager to NOT use fstorage? If we could configure it to just use RAM, that would be preferred. We don't need peer_manager data to persist.

[bjorn-spockeli]

Can you elaborate why you need to configure where the PM stores its data?

[Justin]

we store device information/configuration data in the flash space in front of the bootloader.
it is written during manufacturing. moving it is not an option.

[bjorn-spockeli]

Ok, then I understand. The solution you proposed, i.e. modify the FS_PAGE_END_ADDR to the end address of the free page below the information/configuration data is the easiest solution. As far as I know there is no easy way to modify the PM to store the data in RAM instead of in Flash.