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

jaytroymo gravatar image

asked 2017-02-13 19:49:35 +0100

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.

edit retag flag offensive close delete report spam


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

Bjørn Spockeli ( 2017-02-14 10:36:30 +0100 )editconvert to answer

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.

jaytroymo ( 2017-02-14 18:07:22 +0100 )editconvert to answer

1 answer

Sort by » oldest newest most voted
bjorn-spockeli gravatar image

answered 2017-02-15 14:49:13 +0100

jaytroymo gravatar image

updated 2017-02-15 18:34:09 +0100

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.

edit flag offensive delete publish link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer. Do not ask a new question or reply to an answer here.

[hide preview]

Question Tools

1 follower


Asked: 2017-02-13 19:49:35 +0100

Seen: 93 times

Last updated: feb. 13 '17