Switch over to something that does not wear out THAT quickly... tha's why some IoT MC chip maker use non-volatile RAM so they can power off / down anytime without saving to (FLASH)EEPROM. See FRAM/MRAM - 256-Kbit (32 K × 8) Serial (SPI) F-RAM - Ferroelecric, non-volative RAM - SPI: something that behaves like EEPROM AND RAM at the same time. For your needs, a 32KB works just fine and runs with @DrAzzy's EEPROM lib... and with the same driver but without wait-after-write (and no page erase), it's even better... you can write and write and write... For 'production' runtime EEPROM may work... it got corrupted at development time because of the unusual high rate of retries... ;)
That sounds great! I could never think about that I would face with such a problem... Maybe we can replace original flash chip or add another one to the board on our next release.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Switch over to something that does not wear out THAT quickly... tha's why some IoT MC chip maker use non-volatile RAM so they can power off / down anytime without saving to (FLASH)EEPROM. See FRAM/MRAM - 256-Kbit (32 K × 8) Serial (SPI) F-RAM - Ferroelecric, non-volative RAM - SPI: something that behaves like EEPROM AND RAM at the same time. For your needs, a 32KB works just fine and runs with @DrAzzy's EEPROM lib... and with the same driver but without wait-after-write (and no page erase), it's even better... you can write and write and write... For 'production' runtime EEPROM may work... it got corrupted at development time because of the unusual high rate of retries... ;)