2019-03-25 06:37 AM
Hi all,
Just wondered if anyone had a similar experience with this. Currently i'm storing a devices current state and settings in the EEPROM. This information is accessed and updated at a high frequency during a part of the program. I have experienced the data becoming corrupted if I create a high number of interrupts at the same time. The interrupt route is quick, it's just setting a flag and does not have an effect on the data I'm writing to the EEPROM. Is there anyway to 'protect' the EEPROM while I'm writing to it? Any good practises to be had? It's not the end of the world it just requires the user to set the device up again and I have not experienced it happening very often but it would be nice to get rid of the problem entirely.
Thanks