Here a piece of the code I used. It involves a majority check: the value is written to five successive locations. On a read operation, the resulting bits come from their corresponding locations in each of the five bytes. The resulting bit has the value that is most abundant: three or more bits of the same value.
Please have a look: ON 20101001@9:28:42 PM at page: On a web page you were interested in at: http://www.piclist.com/Techref/mem/eeprom/corruption.htm#40452.8949305556 Andries Tip[AT-planet-T9] See also: /Techref/member/AT-planet-T9/safeeeprom.htm In one of my applications I could not be sure whether or not the power would stay one during the eeprom writes but I still needed to update and remember some more or less important stuff.
Here a piece of the code I used. It involves a majority check: the value is written to five successive locations. On a read operation, the resulting bits come from their corresponding locations in each of the five bytes. The resulting bit has the value that is most abundant: three or more bits of the same value.
Please have a look:
ON 20101001@9:34:26 PM at page:
On a web page you were interested in at:
http://www.piclist.com/Techref/mem/eeprom/corruption.htm#40452.898912037
Andries Tip[AT-planet-T9] See also:
/Techref/member/AT-planet-T9/safeeeprom.htm
In one of my applications I could not be sure whether or not the power would stay one during the eeprom writes but I still needed to update and remember some more or less important stuff.
Here a piece of the code I used. It involves a majority check: the value is written to five successive locations. On a read operation, the resulting bits come from their corresponding locations in each of the five bytes. The resulting bit has the value that is most abundant: three or more bits of the same value.
Please have a look: