search

SourceArcade / flashprog

Mirror of review.sourcearcade.org/flashprog
GNU General Public License v2.0
25 stars 2 forks source link

Your flash chip is in an unknown state. - N25Q064..3E #3

Open ds2k5 opened 2 months ago

ds2k5 commented 2 months ago 
$ ./flashprog -p ch341a_spi -E --progress -f
flashprog p1.2-2-gc6a924a on Linux 6.1.0-25-amd64 (x86_64)
flashprog is free software, get the source code at https://flashprog.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Micron/Numonyx/ST flash chip "N25Q064..3E" (8192 kB, SPI) on ch341a_spi.
Erasing flash chip... 
Erasing... [==================================================] 100% FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x7cbca3
ERASE FAILED!
FAILED!
Your flash chip is in an unknown state.
Please report this to the mailing list at flashprog@flashprog.org
or on IRC (see https://www.flashprog.org/Contact for details), thanks!

$ ./flashprog -p ch341a_spi  --progress -f -w ~/w541/coreboot-bottom.rom 
flashprog p1.2-2-gc6a924a on Linux 6.1.0-25-amd64 (x86_64)
flashprog is free software, get the source code at https://flashprog.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Micron/Numonyx/ST flash chip "N25Q064..3E" (8192 kB, SPI) on ch341a_spi.
Reading old flash chip contents... 
Reading... [==================================================] 100% done.
Erasing and writing flash chip... 
Erasing... [==================================================] 100% 
Writing... [==================================================] 100% Erase/write done.
Verifying flash... 
Reading... [==================================================] 100% FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x30a136
Your flash chip is in an unknown state.
Please report this to the mailing list at flashprog@flashprog.org
or on IRC (see https://www.flashprog.org/Contact for details), thanks!

What can I do ?

i-c-o-n commented 1 month ago

Hi @ds2k5, sorry for the late reply. Such failures are usually the result of physical issues, either with the signal integrity or problematic powering.

It looks like it eventually managed to erase, which makes it more likely to be a signal problem. Did you test if reading works reliably? You can read once with -r dump.rom and then try to verify multiple times with -v dump.rom. If this doesn't work reliably, all bets are off.