Checking if data is correct in pstorage callback

RE: Checking if data is correct in pstorage callback

Susheel Nuguru — Tue, 02 Jun 2015 10:42:43 GMT

Is there anything else you are looking for in this thread? if not can you please accept and close this case.

RE: Checking if data is correct in pstorage callback

Konrad Traczyk — Tue, 02 Jun 2015 10:24:55 GMT

Ok, many thanks :)

RE: Checking if data is correct in pstorage callback

Susheel Nuguru — Tue, 02 Jun 2015 10:20:25 GMT

Hi You are right, The callback does not provide any information on the offset used. So if you want to verify data then offset has to be remembered so how.

RE: Checking if data is correct in pstorage callback

Konrad Traczyk — Tue, 02 Jun 2015 10:09:08 GMT

Thanks for reply. You're right, I didn't set the guardian counter which guards against infinit flash update. The data_len is never bigger than 8, so it is ok. I just realised, that when I register one block with sufficient size, where I store different data, the callback doesn't provide any information about offset where I've just stored the data in flash. Am I correct that for that reason I am not able to check if the data wasn't corrupted?

RE: Checking if data is correct in pstorage callback

Susheel Nuguru — Mon, 01 Jun 2015 18:26:08 GMT

for(uint8_t i=0; i<8; i++)
{
     p_dataCheck[i] = p_data[i];       //  Copy the data which were just stored, for debug
}

you are copying only 8 bytes to p_data_check but

for(uint8_t i=0; i<data_len; i++)
{
   if(p_dataCheck[i] != temp[i])

you are comparing data_len bytes, this is fine if you are sure that data_len will always be 8.

Why do you have a waiting 'for loop' for the second update to complete? I think it is best to break out of this handler as fast as possible without waiting.

You have written very dangerous code. If something goes wrong, you could end up in endless loop of flash writes, damaging flash memory within hour if not minutes.