cmdEraseMemory(): fix incorrect crc calculation

Open liamstask opened this issue 11 years ago • 2 comments

Dec 30 '14 01:12 liamstask

@jsnyder is this correct?

May 25 '17 21:05 kuraga

Basically, this includes N (the number of pages) in the checksum whereas previously it would include value 0xFF instead, which would only be correct for N=255, which is impossible because that's reserved for global erase.

ST application note 3155 says "((...) checksum XOR (N, N+1 bytes))" so this seems to be correct now.

Mar 07 '18 10:03 florisla