Hello Osark, I assume your flash chip is still on the mainboard and you have a clip or something attached to it? Unless a board is designed for this, YMMV from board to board and programmer to programmer. On 11.03.25 02:51, Osark Vieira wrote:

Reading EEPROM contents was not a problem,

This can be deceiving as there are no integrity checks on the transferred data. Did you try to verify the read? e.g. `-v` instead of `-r` or read twice and compare. In case reading turns out to be unreliable, you could try again with shorter wires (we recommend <20cm from programmer to chip), or a slower `spispeed` setting.

But when erasing such error occurs. [...] Erasing flash chip... FAILED at 0x00002005! Expected=0xff, Found=0xdd, failed byte count from 0x00000000-0x000fffff: 0x4b9

Chances are high that this is actually a read failure. The byte count shows that only about 1KiB out of 1MiB failed. Erase usually either works completely or not at all. You could also try to verify this again and see if the byte count changes, e.g. create a file with all ff that looks erased, and verify against that: $ dd if=/dev/zero bs=1M count=1 | tr '\000' '\377' >erased.rom $ flashprog -p ... -v erased.rom If the byte count changes, the chip is most likely erased, but reading fails. You could try to trick flashprog into writing in this case, but verifying the write would fail again and we wouldn't know if it succeeded: $ flashprog -p ... --flash-contents erased.rom -w ... Hope this is of any help, Nico