Hi,
I'm using sdk14.2 peripheral examples fds and fstorage in an attempt to test flash storage persistance (with softdevice present).
The two examples are quite intuitive and easy to play with thanks to the cli interface (uart).
First i have used fstorage, wrote a long string between 2 pages and read it correctly (below screen capture of my attempt).
Next i have used fstorage and i was surprised to see that the 3 pages I have erased while using fstorage are detected in the fds example. I have modified the print command "static void print_all_cmd " to allow showing the contents of the "freq.p_data" pointer (from clic.c file) and obtained:
I wrote some records with some data strings and checked their presence:
And after I have switched power off/on, data is still present:
It looks that the config record has changed rec id value.
I have studied the post: Flash Data Storage place in memory
... and learnt how the data is organised in the non volatile memory (flash last address 0x80000).
There are some notions that I still don't understand and would like to learn more:
-
how does FDS module handle "flasharea" command effect (fstorage); how to specify number of pages; are these pages generated automaticaly upon data written; is there a limit, if yes, then how?
-
using FDS if one record is fully written and data required has no more space left, can it be possible to continue writing to a next record thus insuring contiguous data (like in fstorage) ?
-
are flash writing events critical while using the softdevice? can this cause system to reset? are there some timings to respect, maximum quantity of data to write during radio operations (advertising/connected state)?
-
i want to use sdk14.0 (my project is developed upon it); is there any difference between the two sdk versions with respect to FDS or Fstorage modules?
-
would migrating from 14.0 to 14.2 involve important changes?
Thank you in advance!
