| ??? 08/16/07 11:03 Read: times |
#143331 - It's an "either - or" ... Responding to: ???'s previous message |
You mean a checksum byte with the 2s complement of the sums lsb and one checksum byte with the 1s complement of the lsb of the sum?
No, those are just different examples on how to avoid getting a "correct" checksum result if all the bytes are zero. Taking the 1's or the 2's complement of the LSB of the sum will accomplish this, or adding a constant to the result. |
| Topic | Author | Date |
| Simple EEPROM checksumming | 01/01/70 00:00 | |
| Pitfalls | 01/01/70 00:00 | |
| a checksum out of 2 bytes? | 01/01/70 00:00 | |
| It's an "either - or" ... | 01/01/70 00:00 | |
| code sketch | 01/01/70 00:00 | |
| a simple checksum | 01/01/70 00:00 | |
| CRC8 instead of CR32 | 01/01/70 00:00 | |
| I am talking about CRC-16 not CRC-8 | 01/01/70 00:00 | |
| oups | 01/01/70 00:00 | |
| how much data? | 01/01/70 00:00 | |
| approx 40-60 bytes | 01/01/70 00:00 | |
| I use 2 copies and a counter for that | 01/01/70 00:00 | |
| adding to Jan's post | 01/01/70 00:00 | |
| Here's one method | 01/01/70 00:00 | |
| another interesting scheme! | 01/01/70 00:00 | |
| Try the Dallas 1-wire CRC | 01/01/70 00:00 | |
| another good idea but... | 01/01/70 00:00 | |
| I just meant the CRC | 01/01/70 00:00 | |
oups | 01/01/70 00:00 |