Hi all,

I'm storing data (3 bytes per data-set) into EEPROM, and I need some way to 
later validate that none of the bytes are corrupt.  So I'm investigating 
checksums, raid, etc.

Haven't found much info on checksum algorithms that would be useful for this 
simple application, or more importantly how to develop a good checksum 
application for just 3 bytes.

But I've got quite a bit of EEPROM space at my disposal now (using a serial 
EEPROM), so wondering if it would be better to skip the checksum computations 
altogether (which would be nice in freeing up some CPU cycles during that 
time) and simply duplicate or even triplicate the dataset so on read-back I 
would be able to restore valid data if one of 3 sets does not match.  Also if 
I save in triplicate, it would be quite fast using the page-write mode, but 
is there any advantage to saving the repeated datasets in different pages?  
Data integrity is key here, but if it costs me some CPU cycles, that's fine.

Any ideas on what's better?  Perhaps something other that these 2 options?

Cheers,
-Neil.




-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist