Timeline for EEPROM write time
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2017 at 12:53 | comment | added | Jot | The ATmega2560 needs 4.5V to run at 16MHz. Newer chips allow a lower voltage and also write faster to EEPROM. How many bytes do you need to write ? Arduino has a function to skip the bytes that are the same: arduino.cc/en/Reference/EEPROMUpdate Perhaps there are things that you can do in software, to prepare for an emergency backup. When storing data in EEPROM, you could write it with a checksum, and have the data two times in EEPROM. | |
| Mar 15, 2017 at 16:12 | vote | accept | EffegiWeb | ||
| Mar 15, 2017 at 16:10 | vote | accept | EffegiWeb | ||
| Mar 15, 2017 at 16:12 | |||||
| Mar 15, 2017 at 15:53 | comment | added | James Waldby - jwpat7 | Re “largest gain is to have the EEPROM erased before the write”, note that AVR-level eeprom.h includes a comment, “All write functions force erase_and_write programming mode”, so having EEPROM erased before the write entails coding EEPROM routines from scratch. ¶ To some extent, separating erase and write precludes possible time savings from not rewriting cells with unchanged value. | |
| Mar 15, 2017 at 15:13 | history | edited | Mikael Patel | CC BY-SA 3.0 |
added 44 characters in body
|
| Mar 15, 2017 at 15:08 | history | edited | Mikael Patel | CC BY-SA 3.0 |
added 44 characters in body
|
| Mar 15, 2017 at 15:03 | history | answered | Mikael Patel | CC BY-SA 3.0 |