[solved] Aux1 SOC% in local app incorrect

[boB]

I sure hope its a good eeprom.

A few years back I had programmed a linux computer as DVR (Tivo like) system. I had made a script so it would program BIOS wakeup to 5 minutes before next scheduled recording. So it did that a few times per day. It lasted about 4 years, then it kept getting BIOS parity errors

So if you do write every few hours, can I suggest  a read-first&only-write-if-changed approach?
Maybe you are already doing that, as it is a good method for any eeprom write, but I wanted to have mentioned it anyway.

Writing the same thing doesn't hurt it either.   Writing zeros is typically what uses up the write cycles.

If it was going to be just one value being written to a block of EEprom, wear leveling takes care of any lifetime
aging issues as long as it isn't writing lots like, hundreds of times per minute.   This is because it would write to a
different area of memory every time for many times before coming back to the original write address again.

This is one of the things they have to do with flash disk drives and is why having a larger flash drive
than needed 'should' better for life-time because there is more of those blocks for the wear leveling to
work.  I would sure hate to have to deal with that on a disk drive size basis !