flashrom

flashrom@flashrom.org

5 participants
9154 discussions

Re: Can't_erase_and_write_W25Q64BVDAIG_in_linux_only,read_O.K.
by Ivan Ivanov 18 Jan '23

18 Jan '23

Well, I avoid SystemD too, so I'm using the distros like Void and Artix (Arch without SystemD) - but never had a problem with flashrom. Didn't try Devuan yet ( I prefer the newer versions of packages than what Debian/Devuan stable could offer ) - but stuff like that may happen even to the stablest distros, and also this issue could depend on your local configuration and not reproducible i.e. on a fresh Devuan install. Maybe try a Devuan LiveCD and see if it happens there too? Best regards, Ivan Ivanov вт, 17 янв. 2023 г. в 16:22, * <alex-raude(a)mail.ru>: > > Hi, > I’ve tried that (reinstal), same. Do you think Debian stable (Devuan stable) can make such broken library? > Best regards. > Alexey > > Вторник, 17 января 2023, 15:36 +03:00 от Ivan Ivanov <qmastery16(a)gmail.com>: > > Hi there Alexey, > > Looks like you have a problem with your libusb library. Please > reinstall the libusb library (you may have to build it from source, if > your distro's libusb is broken at the moment - if that's so, make sure > to --enable-shared). > > Best regards, > Ivan Ivanov > > пн, 16 янв. 2023 г. в 23:54, * via flashrom <flashrom(a)flashrom.org>: > > > > Good day, > > > > Few days ago i've bought new Winbond W25Q64BVDAIG flash, getting errors during erasing or writing. Read is good. W25Q64FV... is errased and flashed well. W25Q64BVDAIG flashing works fine in WindowsXP by CH341A - USB Programmer 1.30. In Willem LPT Programmer set to 3.3V works fine too. CH341A - black. > > > > W25Q64BV... during error device stops respond with "run" led on, needs reinsert to USB to get it again. > > ~$ sudo flashrom --programmer ch341a_spi -r Z77EXT62.90A.bin > > [sudo] пароль для xxxxxx: > > flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) > > flashrom is free software, get the source code at https://flashrom.org > > > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > > Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. > > Reading flash... done. > > ~$ sudo flashrom --programmer ch341a_spi -r Z77EXT62.90A.rom > > flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) > > flashrom is free software, get the source code at https://flashrom.org > > > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > > Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. > > Reading flash... done. > > ~$ sudo flashrom --programmer ch341a_spi -E > > [sudo] пароль для xxxxxx: > > flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) > > flashrom is free software, get the source code at https://flashrom.org > > > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > > Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. > > Erasing and writing flash chip... > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 36 bytes > > RDSR failed! > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 4265 bytes > > Verification impossible because read failed at 0x17000 (len 0x1000) > > ERASE FAILED! > > Looking for another erase function. > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 34 bytes > > spi_write_cmd failed during command execution at address 0x0 > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 36 bytes > > RDSR failed! > > Looking for another erase function. > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 34 bytes > > spi_write_cmd failed during command execution at address 0x0 > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 36 bytes > > RDSR failed! > > Looking for another erase function. > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 34 bytes > > spi_simple_write_cmd failed during command execution > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 36 bytes > > RDSR failed! > > Looking for another erase function. > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 34 bytes > > spi_simple_write_cmd failed during command execution > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 36 bytes > > RDSR failed! > > Looking for another erase function. > > Looking for another erase function. > > Looking for another erase function. > > No usable erase functions left. > > FAILED! > > Your flash chip is in an unknown state. > > Please report this on IRC at chat.freenode.net (channel #flashrom) or > > mail flashrom(a)flashrom.org, thanks! > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > enable_pins: Failed to write 4 bytes > > Could not disable output pins. > > ~$ sudo flashrom --programmer ch341a_spi -w Z77EXT62.90A.bin -c "W25Q64.V" > > flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) > > flashrom is free software, get the source code at https://flashrom.org > > > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > > Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. > > Reading old flash chip contents... done. > > Erasing and writing flash chip... > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 36 bytes > > RDSR failed! > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 34 bytes > > spi_write_cmd failed during command execution at address 0x1500 > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 36 bytes > > RDSR failed! > > Reading current flash chip contents... > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > ch341a_spi_spi_send_command: Failed to write 4265 bytes > > Can't read anymore! Aborting. > > FAILED! > > Uh oh. Erase/write failed. Checking if anything has changed. > > Reading current flash chip contents... ch341a_spi_spi_send_command: failed to submit IN transfer: LIBUSB_ERROR_BUSY > > ch341a_spi_spi_send_command: Failed to read 4100 bytes > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > > > cb_in: error: LIBUSB_TRANSFER_TIMED_OUT > > Can't even read anymore! > > Your flash chip is in an unknown state. > > Please report this on IRC at chat.freenode.net (channel #flashrom) or > > mail flashrom(a)flashrom.org, thanks! > > > > cb_out: error: LIBUSB_TRANSFER_TIMED_OUT > > enable_pins: Failed to write 4 bytes > > Could not disable output pins. > > > > W25Q64FV... works just fine. > > ~$ sudo flashrom --programmer ch341a_spi -E > > [sudo] пароль для xxxxxx: > > flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) > > flashrom is free software, get the source code at https://flashrom.org > > > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > > Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. > > Erasing and writing flash chip... Erase/write done. > > > > ~$ sudo flashrom --programmer ch341a_spi -w Z97EX62_80.bin -c "W25Q64.V" > > flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) > > flashrom is free software, get the source code at https://flashrom.org > > > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > > Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. > > Reading old flash chip contents... done. > > Erasing and writing flash chip... Erase/write done. > > Verifying flash... VERIFIED.` > > Both chips are found as a "W25Q64.V". > > > > Best regards, > > Alexey > > > > _______________________________________________ > > flashrom mailing list -- flashrom(a)flashrom.org > > To unsubscribe send an email to flashrom-leave(a)flashrom.org > _______________________________________________ > flashrom mailing list -- flashrom(a)flashrom.org > To unsubscribe send an email to flashrom-leave(a)flashrom.org > > > > >

1 0

Can't_erase_and_write_W25Q64BVDAIG_in_linux_only,read_O.K.
by * 17 Jan '23

17 Jan '23

Good day, Few days ago i've bought new Winbond W25Q64BVDAIG flash, getting errors during erasing or writing. Read is good. W25Q64FV... is errased and flashed well. W25Q64BVDAIG flashing works fine in WindowsXP by CH341A - USB Programmer 1.30. In Willem LPT Programmer set to 3.3V works fine too. CH341A - black. W25Q64BV... during error device stops respond with "run" led on, needs reinsert to USB to get it again. ~$ sudo flashrom --programmer ch341a_spi -r Z77EXT62.90A.bin [sudo] пароль для xxxxxx: flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Reading flash... done. ~$ sudo flashrom --programmer ch341a_spi -r Z77EXT62.90A.rom flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Reading flash... done. ~$ sudo flashrom --programmer ch341a_spi -E [sudo] пароль для xxxxxx: flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Erasing and writing flash chip... cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 36 bytes RDSR failed! cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 4265 bytes Verification impossible because read failed at 0x17000 (len 0x1000) ERASE FAILED! Looking for another erase function. cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 34 bytes spi_write_cmd failed during command execution at address 0x0 cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 36 bytes RDSR failed! Looking for another erase function. cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 34 bytes spi_write_cmd failed during command execution at address 0x0 cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 36 bytes RDSR failed! Looking for another erase function. cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 34 bytes spi_simple_write_cmd failed during command execution cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 36 bytes RDSR failed! Looking for another erase function. cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 34 bytes spi_simple_write_cmd failed during command execution cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 36 bytes RDSR failed! Looking for another erase function. Looking for another erase function. Looking for another erase function. No usable erase functions left. FAILED! Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org , thanks! cb_out: error: LIBUSB_TRANSFER_TIMED_OUT enable_pins: Failed to write 4 bytes Could not disable output pins. ~$ sudo flashrom --programmer ch341a_spi -w Z77EXT62.90A.bin -c "W25Q64.V" flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 36 bytes RDSR failed! cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 34 bytes spi_write_cmd failed during command execution at address 0x1500 cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 36 bytes RDSR failed! Reading current flash chip contents... cb_out: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to write 4265 bytes Can't read anymore! Aborting. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... ch341a_spi_spi_send_command: failed to submit IN transfer: LIBUSB_ERROR_BUSY ch341a_spi_spi_send_command: Failed to read 4100 bytes cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT Can't even read anymore! Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org , thanks! cb_out: error: LIBUSB_TRANSFER_TIMED_OUT enable_pins: Failed to write 4 bytes Could not disable output pins. W25Q64FV... works just fine. ~$ sudo flashrom --programmer ch341a_spi -E [sudo] пароль для xxxxxx: flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Erasing and writing flash chip... Erase/write done. ~$ sudo flashrom --programmer ch341a_spi -w Z97EX62_80.bin -c "W25Q64.V" flashrom v1.2 on Linux 5.10.0-17.1-liquorix-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.` Both chips are found as a "W25Q64.V". Best regards, Alexey

2 1

Can't_erase_and_write_W25Q64BVDAIG_in_linux_only,read_O.K.
by * 17 Jan '23

17 Jan '23

1 0

meson build failure on 32bit [linux]
by Branden Waldner 17 Jan '23

17 Jan '23

Hi list I was testing the tag for v1.3.0-rc1 on my asus p2b recently and decided to try the meson build, which ended up failing. It built and functioned like usual with make though. It appears to halt the build because of a warning and Werror and I've attached the console log from the build process in a debian sid 686 chroot. It also fails the same way on the raspberrypi 1b. I'm not sure that there is much I can do besides reporting on it, but for now I'm fine staying with make. Branden

2 4

jenkins rust checks
by Evan Benn 17 Jan '23

17 Jan '23

Hello, I have been attempting to add some rust checks to the flashrom gerrit test script. I have 2 CLs and a request to change the jenkins job: https://qa.coreboot.org/view/Flashrom/job/flashrom_gerrit This patch installs 'cargo' to the jenkins docker image: https://review.coreboot.org/c/coreboot/+/72001 This adds something like 1Gb to the docker image. This patch adds the rust checks to the flashrom jenkins test_build script: https://review.coreboot.org/c/flashrom/+/69770 However that script runs with no network, so something like this needs to be added to the jenkins run script: find -name Cargo.toml -execdir cargo fetch ';' https://doc.rust-lang.org/cargo/commands/cargo-fetch.html cargo fetch creates a Cargo.lock file, or updates one if it exists and is no longer compatible with Cargo.toml (the checked in dependency declarations). The lock file specifies which versions of the dependencies to use. Our jenkins setup will delete the Cargo.lock file every time during `git clean`, I would like to check in the Cargo.lock file to avoid this problem. https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-… I was only able to test my changes inside a pre-built image from dockerhub, as the TOT `make coreboot-jenkins-node` was not working for me. Here is exactly what I did in the docker image: apt update; apt install cargo rustfmt rust-clippy su coreboot cd /home/coreboot/node-root/workspace/ git clone https://review.coreboot.org/flashrom git fetch https://review.coreboot.org/flashrom refs/changes/70/69770/3 && git checkout FETCH_HEAD mkdir /home/coreboot/.cargo/ git ls-files | grep Cargo.toml | xargs -r -L1 sh -xc "cargo fetch --manifest-path \$0" encapsulate "$PWD|/tmp|/home/coreboot/.ccache|/home/coreboot/.cargo/" ./test_build.sh Thanks

1 1

Intel Gemini Lake help pls
by Alice Venet 13 Jan '23

13 Jan '23

pls help i have this error what i can do? Warning: unexpected second chipset match: "Intel Gemini Lake" ignoring, please report lspci and board URL to flashrom(a)flashrom.org with 'CHIPSET: your board name' in the subject line. Found GigaDevice flash chip "GD25LQ128C/GD25LQ128D" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.

1 0

Unable to flash AT25SF641 on PC Engine APU2
by Jon Brabender 13 Jan '23

13 Jan '23

Hi, I've got a APU2.e PCB with a AT25SF641 for the serial flash (flash PN based on looking at the PCB). Trying to run flashrom (via a Debian live usb stick...I'm having no issues with APU2 booting accessing serial console) as follows yields a lot of output, but nothing useful...is this expected with a AT25SF641? Other people commenting on the interweb with the APUs seem to be seeing Winbond (and no issues) Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000 Any thoughts are greatly appreciated Jon flashrom -w apu2_v4.17.0.2.rom -p internal:boardmismatch=force flashrom v1.2 on Linux 5.10.0-20-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). coreboot table found at 0xcfec5000. Found chipset "AMD FCH". Enabling flash write... OK. Error accessing GD25Q256D, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip GD25Q256D at 0x00000000fe000000. Error accessing IS25LP256, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip IS25LP256 at 0x00000000fe000000. Error accessing IS25WP256, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip IS25WP256 at 0x00000000fe000000. Error accessing MX25L25635F/MX25L25645G, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MX25L25635F/MX25L25645G at 0x00000000fe000000. Error accessing MX25U25635F, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MX25U25635F at 0x00000000fe000000. Error accessing MX25U51245G, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MX25U51245G at 0x00000000fc000000. Error accessing MX66L51235F/MX25L51245G, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MX66L51235F/MX25L51245G at 0x00000000fc000000. Error accessing N25Q00A..1G, 0x8000000 bytes at 0x00000000f8000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q00A..1G at 0x00000000f8000000. Error accessing N25Q00A..3G, 0x8000000 bytes at 0x00000000f8000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q00A..3G at 0x00000000f8000000. Error accessing N25Q256..1E, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q256..1E at 0x00000000fe000000. Error accessing N25Q256..3E, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q256..3E at 0x00000000fe000000. Error accessing N25Q512..1G, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q512..1G at 0x00000000fc000000. Error accessing N25Q512..3G, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q512..3G at 0x00000000fc000000. Error accessing MT25QL01G, 0x8000000 bytes at 0x00000000f8000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QL01G at 0x00000000f8000000. Error accessing MT25QU01G, 0x8000000 bytes at 0x00000000f8000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QU01G at 0x00000000f8000000. Error accessing MT25QL02G, 0x10000000 bytes at 0x00000000f0000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QL02G at 0x00000000f0000000. Error accessing MT25QU02G, 0x10000000 bytes at 0x00000000f0000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QU02G at 0x00000000f0000000. Error accessing MT25QL256, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QL256 at 0x00000000fe000000. Error accessing MT25QU256, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QU256 at 0x00000000fe000000. Error accessing MT25QL512, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QL512 at 0x00000000fc000000. Error accessing MT25QU512, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QU512 at 0x00000000fc000000. Error accessing S25FL256S......0, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip S25FL256S......0 at 0x00000000fe000000. Error accessing S25FL512S, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip S25FL512S at 0x00000000fc000000. Error accessing W25Q256.V, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip W25Q256.V at 0x00000000fe000000. Error accessing W25Q256JV_M, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip W25Q256JV_M at 0x00000000fe000000. Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) mapped at physical address 0x0000000000000000. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Error: Image size (8388608 B) doesn't match the flash chip's size (0 B)!

1 0

Comet Lake U, "-p internal" not available?
by Rafael Send 09 Jan '23

09 Jan '23

Hi, I'm trying to flash laptop that has an i7-10710u on it. From what I've been told, it's not officially supported yet but works if I build from source. I did so, but when I try running it I'm told "-p internal" is not a valid programmer. How can I use that method of programming on the latest master? I've used the internal programmer on previous versions / different boards so I aware of the risks and have methods of recovery, but I'd prefer to start with flashrom for ease of use. Thanks, Rafael

1 0

Error on W25Q80
by Bernd Van Praet 09 Jan '23

09 Jan '23

Hi, I’m getting following report: Calibrating delay loop... OK. Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00007000! Expected=0x76, Found=0xff, failed byte count from 0x00000000-0x000fffff: 0x2451 Your flash chip is in an unknown state. Please report this to the mailing list at flashrom(a)flashrom.org or on IRC (see https://www.flashrom.org/Contact for details), thanks! Kind regards, Bernd Van Praet

1 0

Reporting flash error
by Steve F Dembiske 06 Jan '23

06 Jan '23

Hi: As requested at the bottom of the bios flash, the following error was reported. Appreciate any help you can provide. Thank you, S. *Error*: $ sudo flashrom -p ch341a_spi -c MX25L3273E -w bios1_wl.img flashrom v1.2 on Linux 5.4.0-136-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Macronix flash chip "MX25L3273E" (4096 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00000200! Expected=0xde, Found=0xff, failed byte count from 0x00000000-0x003fffff: 0x20c290 Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks!

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom