G+_Michael Prine Posted May 23, 2017 Share Posted May 23, 2017 On KNOW HOW... 313 it was mentioned that there was a way to insure different portions of the EEPROM were used rather than hard coding a location to insure more even wear but the specifics were not given. Any clue on how this is done? It doesn't seem to be a basic function in the EEPROM library. Link to comment Share on other sites More sharing options...
G+_Ben Reese Posted May 24, 2017 Share Posted May 24, 2017 I haven't watched the latest episode, but I think I have some idea of what your trying to accomplish. Here's a discussion on forum.ardino about wear leveling in EEPROM. https://forum.arduino.cc/index.php?topic=85047.0 My favorite suggestion there is to start by filing the memory with something you know, like 0xAA. Then read all the memory until you get to the first 0xAA field and you'll know where to read your value from (n-1) and where to write the next new value (n). Link to comment Share on other sites More sharing options...
G+_Michael Prine Posted May 24, 2017 Author Share Posted May 24, 2017 Thanks that sound useful. Link to comment Share on other sites More sharing options...
G+_Michael Prine Posted June 9, 2017 Author Share Posted June 9, 2017 With that as a clue I was able to develop a set of routines to allow multiple projects to share the EEPROM and not step on each other's data while insuring that all the memory can be used and freed up when no longer needed. Potentially it could also be modified to retrieve previous values store in memory that has not been over written yet. It was a fun project and may see about building it into a library to share. Link to comment Share on other sites More sharing options...
Recommended Posts