Pstorage Allocating More Flash Pages Moves Existing Pages

[Lucas]

Hello,

Setup: SDK 9.0 SD 8.0.0

I have an application where we are using Pstorage to store persistent system settings.

When I flashed the device we were using this setting in pstorage_platform.h #define PSTORAGE_NUM_OF_PAGES (2) Everything worked great. I was able to perform DFU update of the same firmware version and settings were preserved.

However, in a later version of firmware I performed a DFU update and changed the number of pstorage pages to this: #define PSTORAGE_NUM_OF_PAGES (10)

It seems that the original location of the orininal settings changes because all of them were lost. Did the change the PSTORAGE_NUM_OF_PAGES somehow change where the pages are stored in memory. I did not add any additional storage. Just changed the number of pages and this was result.

Lucas

[John]

Yes, changing the number of pstorage pages will change the start address of your allocated pstorage memory. If you look in pstorage_platform.h you can see how the start address of the pstorage memory is allocated base on the number of pages. So, when you do your pstorage_register during initialization you will end up with a different pstorage location. You could probably get back to your data location if you allocate the additional 8 pages before registering for your previous pstorage data. I have never tried that, so it is just a guess.

[Vidar Berg]

Didn't see your answer before after I posted mine. Had left this thread open in a different tab and didn't refresh it before I posted:)