Hi Devzone:
After searching through the forum I found out that nrf_fstorage_write can only make 1 to 0. So each write needs an erase operation preceding it.
But erase operation erases an entire page to one. How do you expect us to repeatedly write into one address without effecting other addresses in the same page?
And a few more questions:
1. How big is one page?
2. in NRF_FSTORAGE_DEF, is there any rule defining start_addr and end_addr? Does it need to be on a 32 bytes boundary? what's the range we can use for NVM?
3. Could you confirm that each address contain one byte? Like in the fstorage example, if I write One byte into address 3e000, That means 3e001 is unaffected right?
4. Could you confirm read/write operation address needs to be on 32bytes boundary? Because that's what I infered through error message CLI gave me. Does that mean if starting address is 3e000, the next address to read and write is 3e020, 3e040, 3e060, 3e080 ...etc?
I wish these basic info are provided in the infocenter. I have been searching the forum and could not find a clear and concise answer.
Thanks.