-
On a self-assembled megadesk, which works just fine, I occasionally seem to loose the eeprom settings. Reading the Atmega's datasheet the most likely cause of eeprom corruption would be the execution of random code due to supply going down/coming up. The BOD protection of the Atmega will keep the processor in reset when power levels are too low. I will perform some tests with BOD enabled, but wondered if there is a good reason it is disabled by default ? -- |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
Interesting! Let me know how things go. Do you have any references for the datasheet where it mentions not using BOD can cause eeprom corruption? |
Beta Was this translation helpful? Give feedback.
-
Thanks! I've pushed some updates based on your recommendation :) Do you plan on building a companion? |
Beta Was this translation helpful? Give feedback.
-
After 2 weeks of testing I think it's safe to conclude that enabling BOD fixes the issue of eeprom loosing its settings. |
Beta Was this translation helpful? Give feedback.
-
This is fantastic news. This has been an issue for me for awhile. Is there a guide to updating? (I do not have a companion.) |
Beta Was this translation helpful? Give feedback.
After 2 weeks of testing I think it's safe to conclude that enabling BOD fixes the issue of eeprom loosing its settings.
Not a single loss occurred with BOD enabled, while before about every other day I had to re-store the desk levels.