Can the internal EEPROM ever get corrupted and over write locations which were not meant to be over written.
I ask this because I am running the Bitcloud stack with some modification, such as a when a button is pressed it save the EXPANID to eeprom. Then the AVR would reset itself and it would automatically always join a particular network only.
But on a certain occasion I found that my AVR did not boot up correctly when a button was pressed, the stack does use the EEPROM . I am thinking it could be related to VCC? Can this be a possibility.
Now if VCC is lost and re applied very quicly, could that mess up some counter while writing to EEPROM is still intact. This would mean what i am writing or part of what i am writing is written to a wrong long location.
My VCC connection is bit lose and maybe in the particular case when pressing the button it done something internally
This was a odd behaviour and was wondering if anyone else has had EEPROM corruption before.
I have come to the conclusion it's a EEPROM problem because by enabling the EEPROM save in the FUSE, and then flashing the AVR made no change , but disabling EEPROM save and the RE flashing the AVR got it back to normal once again.
Maybe I could try to replicate the problem and then upload a working EEPROM file and reboot.
But i would like to know has anyone else had EEPROM issues