>This has an impact on my current project where I have a fixed "table"
>in EEPROM. Maybe better to move the table (64 bytes) to Flash space.

Or just keep a 24 bit counter somewhere, and when it overflows on being
incremented by each eeprom write, then refresh the table by reading the
value in a location, and rewriting the same value back to that location.

If you want to be pedantic you may wish to rewrite the table by doing an xor
0xff, and have a flag saying if the table is true or complement. But that
would involve no table accesses while the table is being refreshed, where
the other way it could happen as an "idle process" job a location at a time,
and any valid accesses during the refresh would not matter.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads