Trouble flashing Winbond chip

[Johan Bergsten]

Hi!

I have trouble flashing Winbond W25Q64 BIOS chip using Rpi. Can you please advise?

Output from the verbose log:

pi@raspberrypi:~/Temp $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -w V3ZCAM10.BIN -V
flashrom  on Linux 4.19.66-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

flashrom was built with libpci 3.5.2, GCC 8.2.0, little endian
Command line (5 args): flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -w V3ZCAM10.BIN -V
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Initializing linux_spi programmer
Using device /dev/spidev0.0
Using 2000 kHz clock
The following protocols are supported: SPI.

Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on linux_spi.
Chip status register is 0x00.

Found Winbond flash chip "W25Q64.W" (8192 kB, SPI).
This chip may contain one-time programmable memory. flashrom cannot read
and may never be able to write it, hence it may not be able to completely
clone the contents of this chip (see man page for details).
Reading old flash chip contents... done.
Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00001000-0x00001fff: 0x1000
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 1... 0x000000-0x007fff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x4000
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0x9000
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x3fa01c
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x41101a
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 5... not defined. No usable erase functions left.
FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Apparently at least some data has changed.
Your flash chip is in an unknown state.

Kind regards
Johan Bergsten

[Pavel Sayekat]

Guessing that the flash chip got corrupted somehow from a similar
experience.

On Thu, Oct 3, 2019 at 6:13 PM Johan Bergsten 
wrote:
> Hi!
>
> I have trouble flashing Winbond W25Q64 BIOS chip using Rpi. Can you please
> advise?
>
> Output from the verbose log:
>
> pi@raspberrypi:~/Temp $ sudo flashrom -p
> linux_spi:dev=/dev/spidev0.0,spispeed=2000 -w V3ZCAM10.BIN -V
>
> flashrom  on Linux 4.19.66-v7l+ (armv7l)
>
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.5.2, GCC 8.2.0, little endian
>
> Command line (5 args): flashrom -p
> linux_spi:dev=/dev/spidev0.0,spispeed=2000 -w V3ZCAM10.BIN -V
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
>
> Initializing linux_spi programmer
>
> Using device /dev/spidev0.0
>
> Using 2000 kHz clock
>
> The following protocols are supported: SPI.
>
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on linux_spi.
>
> Chip status register is 0x00.
>
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI).
>
> This chip may contain one-time programmable memory. flashrom cannot read
>
> and may never be able to write it, hence it may not be able to completely
>
> clone the contents of this chip (see man page for details).
>
> Reading old flash chip contents... done.
>
> Erasing and writing flash chip... Trying erase function 0...
> 0x000000-0x000fff:W, 0x001000-0x001fff:EFAILED at 0x00001000!
> Expected=0xff, Found=0x00, failed byte count from 0x00001000-0x00001fff:
> 0x1000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase
> function.
>
> Trying erase function 1... 0x000000-0x007fff:EFAILED at 0x00001000!
> Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff:
> 0x4000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase
> function.
>
> Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00001000!
> Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff:
> 0x9000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase
> function.
>
> Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00001000!
> Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff:
> 0x3fa01c
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase
> function.
>
> Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00001000!
> Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff:
> 0x41101a
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase
> function.
>
> Trying erase function 5... not defined. No usable erase functions left.
>
> FAILED!
>
> Uh oh. Erase/write failed. Checking if anything has changed.
>
> Reading current flash chip contents... done.
>
> Apparently at least some data has changed.
>
> Your flash chip is in an unknown state.
>
> Kind regards
>
> Johan Bergsten
>
> flashrom mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Idwer Vollering]

This could be caused by electrical problems. Did you find and read
this page, https://flashrom.org/Common_problems ?
Also, the particular version of flashrom was omitted in its output. It
looks like you build the binary yourself, instead of installing
through a package manager. Please mention the version as well.

Op do 3 okt. 2019 om 13:13 schreef Johan Bergsten :
> Hi!
>
> I have trouble flashing Winbond W25Q64 BIOS chip using Rpi. Can you please advise?
>
> Output from the verbose log:
>
> pi@raspberrypi:~/Temp $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -w V3ZCAM10.BIN -V
>
> flashrom  on Linux 4.19.66-v7l+ (armv7l)
>
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.5.2, GCC 8.2.0, little endian
>
> Command line (5 args): flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -w V3ZCAM10.BIN -V
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
>
> Initializing linux_spi programmer
>
> Using device /dev/spidev0.0
>
> Using 2000 kHz clock
>
> The following protocols are supported: SPI.
>
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on linux_spi.
>
> Chip status register is 0x00.
>
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI).
>
> This chip may contain one-time programmable memory. flashrom cannot read
>
> and may never be able to write it, hence it may not be able to completely
>
> clone the contents of this chip (see man page for details).
>
> Reading old flash chip contents... done.
>
> Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00001000-0x00001fff: 0x1000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 1... 0x000000-0x007fff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x4000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0x9000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x3fa01c
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x41101a
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 5... not defined. No usable erase functions left.
>
> FAILED!
>
> Uh oh. Erase/write failed. Checking if anything has changed.
>
> Reading current flash chip contents... done.
>
> Apparently at least some data has changed.
>
> Your flash chip is in an unknown state.
>
> Kind regards
>
> Johan Bergsten
>
> flashrom mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Johan Bergsten]

Yep, the cause was electrical. I soldered 75ohm serial resistors on the bus, and it solved the problem. Thanks a lot for the help!

//Johan

-----Ursprungligt meddelande-----
Från: Idwer Vollering  
Skickat: den 3 oktober 2019 14:52
Till: Johan Bergsten 
Kopia: [e-mail]
Ämne: Re: [flashrom] Trouble flashing Winbond chip

This could be caused by electrical problems. Did you find and read this page, https://flashrom.org/Common_problems ?
Also, the particular version of flashrom was omitted in its output. It looks like you build the binary yourself, instead of installing through a package manager. Please mention the version as well.

Op do 3 okt. 2019 om 13:13 schreef Johan Bergsten :
> Hi!
>
> I have trouble flashing Winbond W25Q64 BIOS chip using Rpi. Can you please advise?
>
> Output from the verbose log:
>
> pi@raspberrypi:~/Temp $ sudo flashrom -p 
> linux_spi:dev=/dev/spidev0.0,spispeed=2000 -w V3ZCAM10.BIN -V
>
> flashrom  on Linux 4.19.66-v7l+ (armv7l)
>
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.5.2, GCC 8.2.0, little endian
>
> Command line (5 args): flashrom -p 
> linux_spi:dev=/dev/spidev0.0,spispeed=2000 -w V3ZCAM10.BIN -V
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
>
> Initializing linux_spi programmer
>
> Using device /dev/spidev0.0
>
> Using 2000 kHz clock
>
> The following protocols are supported: SPI.
>
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on linux_spi.
>
> Chip status register is 0x00.
>
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI).
>
> This chip may contain one-time programmable memory. flashrom cannot 
> read
>
> and may never be able to write it, hence it may not be able to 
> completely
>
> clone the contents of this chip (see man page for details).
>
> Reading old flash chip contents... done.
>
> Erasing and writing flash chip... Trying erase function 0... 
> 0x000000-0x000fff:W, 0x001000-0x001fff:EFAILED at 0x00001000! 
> Expected=0xff, Found=0x00, failed byte count from 
> 0x00001000-0x00001fff: 0x1000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 1... 0x000000-0x007fff:EFAILED at 0x00001000! 
> Expected=0xff, Found=0x00, failed byte count from 
> 0x00000000-0x00007fff: 0x4000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00001000! 
> Expected=0xff, Found=0x00, failed byte count from 
> 0x00000000-0x0000ffff: 0x9000
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00001000! 
> Expected=0xff, Found=0x00, failed byte count from 
> 0x00000000-0x007fffff: 0x3fa01c
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00001000! 
> Expected=0xff, Found=0x00, failed byte count from 
> 0x00000000-0x007fffff: 0x41101a
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase function.
>
> Trying erase function 5... not defined. No usable erase functions left.
>
> FAILED!
>
> Uh oh. Erase/write failed. Checking if anything has changed.
>
> Reading current flash chip contents... done.
>
> Apparently at least some data has changed.
>
> Your flash chip is in an unknown state.
>
> Kind regards
>
> Johan Bergsten
>
> flashrom mailing list -- [e-mail] To unsubscribe send an 
> email to [e-mail]