What happens with pstorage if order of pstorage_register changes?

[Anthony Ambuehl]

I'm wondering when my firmware changes over time what will happen with information stored with pstorage? For example if I my new firmware release adds an additional pstorage_register that occurs in between several existing pstorage_register calls what will occur? Also where does the pstorage flash reside? Is it contained within the hex firmware image or is it placed in another fixed location?

BTW, Is there any persistent storage mechanism that would use a application managed ID to store data? I'm looking for something similar to TI's osal_snv_* system...

[Anthony Ambuehl]

I am definitely concerned about using pstorage then. During future development if I change the order of initialization or add an additional item in the middle then the storage will be corrupted.

The other systems I have used were more like a file system. The application provides an unique id along with each piece of data to store. Later it can retrieve that data using the id in any order. Also the data size can grow or shrink without impacting the other data stored.

I suppose a layer on top of pstorage could provide some similar capabilties, it would be helpful if it already existed...

a*