On Wed, 2021-11-24 at 13:17 +0300, Mike Banon wrote: > Your log looks right to me, like a file has been programmed into your > chip successfully. How did you check that the writing operation was a > failure instead?
Thanks for looking into this. The error message didn't make into the log, b/c it was on stderr. The diff is: # flashrom -p ... -VVV -w 8.bin > log3 2>&1 $ diff -aU 1 log2 log3 --- log2 2021-11-23 19:06:06.693202071 +0300 +++ log3 2021-11-25 16:51:28.493684854 +0300 @@ -1084,2 +1084,6 @@ Erase/write done. -Verifying flash... programmer_unmap_flash_region: unmapped 0x00000000 +Verifying flash... FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x3489ce +Your flash chip is in an unknown state. +Please report this on IRC at chat.freenode.net (channel #flashrom) or +mail flashrom@flashrom.org, thanks! +programmer_unmap_flash_region: unmapped 0x00000000 If I read the image from chip, I get 8Mib of 0xFF. I can attach the full log if necessary. > P.S. I hope that your 1.8V chip wasn't partially damaged by a > temporary usage of 3.3V on it It is possible, but seems unlikely. The chip correctly responds to flasrom probing queries. I suspect I activated a write protection of some kind. /WP is high at 1.81V now. So I am investigation software WP in the chip now. _______________________________________________ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-le...@flashrom.org
