Most of the first 32-bits of the corrupted range are actually correct. Also, for all 64 bits, of those that are incorrect, they are always 1 when they ought to be 0. Maybe just a coincidence.
In both hex and binary with incorrect binary bits highlighted:At first I thought this might be a rogue write command accidentally issued to the flash chip but it's backwards; a flash erase command initializes bits to all 1s and then write commands can only transition them from 1 to 0, not 0 to 1.
In both hex and binary with incorrect binary bits highlighted:
Code:
Should be:10003eec: 1b061f68 ba001d4b10003eec: 00011011000001100001111101101000 10111010000000000001110101001011 ^ ^ ^ ^ ^ ^ ^^^^^^^^^^^^ ^ ^ ^^ ^Corrupted:10003eec: 5b461fea ffffffff10003eec: 01011011010001100001111111101010 11111111111111111111111111111111 ^ ^ ^ ^ ^ ^ ^^^^^^^^^^^^ ^ ^ ^^ ^Statistics: Posted by alastairpatrick — Sun Mar 24, 2024 8:46 pm