- flashrom - mail.coreboot.org

Trying to use your utility script
by Andre Polidoro 22 Sep '21

22 Sep '21

Came across this error message when I was attempting to run your script on my google pixelbook. Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... 000000-0xffffff:R Reading 16777216 bytes starting at 0x000000. ignoring error when reading 0x0-0xffffff done. Good, writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! This is the set that the program said it didn't recognize. Intel Kaby Lake Y w/ iHDCP2.2 Prem

1 0

L380 bios help
by Bardi Band 21 Sep '21

21 Sep '21

Hi, Could you please help to fix my L380 bios? Thx

1 0

Fwd: ADVANTECH ASMB-825 SMM BIOS protection
by Nico Huber 17 Sep '21

17 Sep '21

Hi Simone, forwarding your message as it has been filtered due to the attachment. The mailing list has a limit of 200KiB. This is the most interesting line out of the picture: > Warning: BIOS region SMM protection is enabled! Well, this is unfortunate. You may not be completely out of luck, though. Sometimes the BIOS setup provides options to toggle flash protection. And sometimes a simple trick helps to get around it: suspend (to RAM) and resume before you try to flash. Some BIOSes simply forget to enables the protection during resume. If you removed the SPI flash from the board anyway, you can also use very simple / cheap SPI programmers without the need of hot swapping. Many SBCs (Raspberry Pi and the like) can serve as programmer, for instance. Or, if you have an old PC with a legacy parallel port, that can be hooked up to a SPI flash with a few resistors. Let us know if you need more infos. Nico -------- Forwarded Message -------- Subject: ADVANTECH ASMB-825 SMM BIOS protection Date: Wed, 15 Sep 2021 09:14:37 +0200 From: Simone Arinci <simone.arinci(a)gmail.com> To: flashrom(a)flashrom.org Good morning, see attached screenshot for the motherboard ASMB-825. I tried flashrom as I have a bricked motherboard and a good one, and tried to revive the bad one with the SPI flash hot swap trick, but no success. Tried flashrom, AFUEFI, AFUDOS, Intel FPT...but none of these are able to reprogram the damaged flash chip... I'm going to send it to the manufacturer to have it repaired. Thanks for your help, have a nice day. Simone [image: ADVANTECH ASMB-825.png]

2 1

PUYA P25D21H
by Alexander Neilson 17 Sep '21

17 Sep '21

Hi Team Thank you very much for your awesome tool. I have been starting to get a better understanding of these chips etc using it and a CH341a programmer. So far when it reads the chip (PUYA P25D21H) I get the message reporting an unsupported chip and to send you the following output. To date my testing has reported differences in the output files I have read. Not yet sure if this is related to my clip (have a "pogo" pin style alternative on the way to test this) or the chip itself or me doing something wrong. Please let me know if I can be of assistance. I believe I have found the datasheet for this chip as well if that is helpful. Thank you alexander@Argo ~ % flashrom -VV --programmer ch341a_spi --read bad_chip_4.bin flashrom v1.2 on Darwin 20.6.0 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with LLVM Clang 12.0.0 (clang-1200.0.32.27), little endian Command line (5 args): flashrom -VV --programmer ch341a_spi --read bad_chip_4.bin Calibrating delay loop... OS timer resolution is 1 usecs, 1862M loops per second, 10 myus = 10 us, 100 myus = 125 us, 1000 myus = 1034 us, 10000 myus = 9615 us, 4 myus = 15 us, OK. Initializing ch341a_spi programmer Device revision is 3.0.4 The following protocols are supported: SPI. Probing for AMIC A25L010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L032, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L05PT, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L05PU, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L10PT, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L10PU, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L16PT, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L16PU, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L20PT, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L20PU, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L40PT, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L40PU, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L80P, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25LQ64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF021, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF021A, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF041A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF321, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF321A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF641(A), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DL081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DL161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DQ161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25FS010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25FS040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25SF041, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25SF081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25SF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25SF321, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25SL128A, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF041, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ESI ES25P16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ESI ES25P40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ESI ES25P80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25B128B/GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25LQ128C/GD25LQ128D, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25LQ40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25LQ64(B), 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25LQ80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q127C/GD25Q128C, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q256D, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25VQ16C, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25VQ21B, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25VQ40C, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25VQ41B, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for GigaDevice GD25VQ80C, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ISSI IS25LP064, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ISSI IS25LP128, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ISSI IS25LP256, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ISSI IS25WP032, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ISSI IS25WP064, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ISSI IS25WP128, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ISSI IS25WP256, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L25635F/MX25L25645G, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25R6435F, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25U25635F, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25U51245G, 65536 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX25U8032E, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix MX66L51235F/MX25L51245G, 65536 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q00A..1G, 131072 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q00A..3G, 131072 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q256..1E, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q256..3E, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q512..1G, 65536 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron/Numonyx/ST N25Q512..3G, 65536 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QL01G, 131072 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QU01G, 131072 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QL02G, 262144 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QU02G, 262144 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QU128, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QL128, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QL256, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QU256, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QL512, 65536 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Micron MT25QU512, 65536 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LQ016, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LQ020, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LQ032C, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LQ040, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LQ080, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x85, id2 0x11 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0x85, id2 0x11 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x85, id2 0x11 Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x85, id2 0x11 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x85, id2 0x11 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0x85, id2 0x11 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25WF020A, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25WF040B, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25WF080B, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST26VF016B(A), 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST26VF032B(A), 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST SST26VF064B(A), 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ST M95M02, 256 kB: probe_spi_st95: id1 0xff, id2 0xffff Probing for Sanyo LE25FU106B, 128 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for Sanyo LE25FU206, 256 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for Sanyo LE25FU206A, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x11, id2 0x11 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL256S......0, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Spansion S25FL512S, 65536 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25P16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25P32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25P80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q128.V..M, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q128.W, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q128.JW.DTR, 16384 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q256.V, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q256JV_M, 32768 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q40BW, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q40EW, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q80BW, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25Q80EW, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Zetta Device ZD25D20, 256 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Zetta Device ZD25D40, 512 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.0 SFDP number of parameter headers is 2 (NPH = 1). SFDP parameter table header 0/1: ID 0x00, version 1.0 Length 36 B, Parameter Table Pointer 0x000030 Parsing JEDEC flash parameter table... 3-Byte only addressing. Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR. Write chunk size is at least 64 B. Flash chip size is 256 kB. Block eraser 0: 64 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 64 x 4096 B with opcode 0x20. Block eraser 1: 8 x 32768 B with opcode 0x52 Block eraser 2: 4 x 65536 B with opcode 0xd8 Block eraser 3: 1024 x 256 B with opcode 0x81 done. SFDP parameter table header 1/1: ID 0x85, version 1.0 Length 12 B, Parameter Table Pointer 0x000060 === SFDP has autodetected a flash chip which is not natively supported by flashrom yet. All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually. You can help us by mailing us the output of the following command to flashrom(a)flashrom.org: 'flashrom -VV [plus the -p/--programmer parameter]' Thanks for your help! === Found Unknown flash chip "SFDP-capable chip" (256 kB, SPI) on ch341a_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x85, id2 0x4012 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x85, id2 0x11 Found Unknown flash chip "SFDP-capable chip" (256 kB, SPI). Some block protection in effect, disabling... disabled. Reading flash... done. alexander@Argo ~ % Regards Alexander Alexander Neilson Neilson Productions Limited alexander(a)neilson.net.nz 021 329 681 022 456 2326

1 0

[PATCH] add support for IS25LP016
by Ondrej Hennel 12 Sep '21

12 Sep '21

Hi. I added support for IS25LP016 by copying the configuration from IS25LP064 and modifying it. I'm not sure if the feature_bits are set correctly, but writing, reading and erasing works fine. Ondrej Hennel From af04e4f19ff01084be6b4bbb69cf1bdb7513cf67 Mon Sep 17 00:00:00 2001 From: Ondrej Hennel <ondrej.hennel(a)gmail.com> Date: Thu, 9 Sep 2021 14:24:36 +0200 Subject: [PATCH] add support for IS25LP016 Signed-off-by: Ondrej Hennel <ondrej.hennel(a)gmail.com> --- flashchips.c | 41 +++++++++++++++++++++++++++++++++++++++++ flashchips.h | 1 + 2 files changed, 42 insertions(+) diff --git a/flashchips.c b/flashchips.c index 3187a49..467e55d 100644 --- a/flashchips.c +++ b/flashchips.c @@ -7301,6 +7301,47 @@ const struct flashchip flashchips[] = { .voltage = {4500, 5500}, }, + { + .vendor = "ISSI", + .name = "IS25LP016", + .bustype = BUS_SPI, + .manufacture_id = ISSI_ID_SPI, + .model_id = ISSI_IS25LP016, + .total_size = 2048, + .page_size = 256, + /* OTP: 1024B total; read 0x48; write 0x42 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 512} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {4 * 1024, 512} }, + .block_erase = spi_block_erase_d7, + }, { + .eraseblocks = { {32 * 1024, 64} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 32} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .unlock = spi_disable_blockprotect, + .write = spi_chip_write_256, + .read = spi_chip_read, + .voltage = {2300, 3600}, + }, + { .vendor = "ISSI", .name = "IS25LP064", diff --git a/flashchips.h b/flashchips.h index e190dca..f87e30e 100644 --- a/flashchips.h +++ b/flashchips.h @@ -472,6 +472,7 @@ #define ISSI_ID 0xD5 /* ISSI Integrated Silicon Solutions, see also PMC. */ #define ISSI_ID_SPI 0x9D /* ISSI ID used for SPI flash, see also PMC_ID_NOPREFIX */ +#define ISSI_IS25LP016 0x6015 #define ISSI_IS25LP064 0x6017 #define ISSI_IS25LP128 0x6018 #define ISSI_IS25LP256 0x6019 -- 2.25.1

3 2

Re: Fwd:
by Nico Huber 12 Sep '21

12 Sep '21

On 10.09.21 00:44, Jack Fivedock wrote: > Much appreciated. Sorry for the lack of knowledge here, I'm very new to > this. > I see in the data sheet the command I need to enter to enable WREN but I'm > not sure how to issue this command to the chip? Sorry, you're on the wrong track. This command is simply send before every attempt to write, always. So that's nothing specific to your chip that flashrom could miss. Maybe we should back up. You mentioned you were using a special connec- tor: > Using this cable from Chipset pro to connect to the hirose 12 pin EFI > connector on the macbook pro. This made me assume that there can't be any physical issue because this connector is made for flashing. But maybe it isn't, or maybe you are using it wrong. Is there any public documentation about this connector? One thing that could go wrong is the voltage supply. If you can, you should check if the voltage drops once the flash is connected. If it drops below a certain level, it's possible that the chip would still answer to commands, but a protection circuit would prevent any write attempt. Looking at the datasheet, this chip has a "individual block protection" mode, selected by a write-once WPSEL bit in a security register. AIUI, the state can be read with the RDSCUR (read security register) command. If WPSEL (bit 7) is set, a WREN + GBULK (gang block unlock) command sequence should allow to write. I'm sorry, I can't provide any patch or details about the code right now. But the above should provide a starting point for anyone else who wants to help. You could also drop in on IRC, especially helpful if you want to talk about the code. Nico

1 0

eeprom
by fajar sidiq 07 Sep '21

07 Sep '21

eeprom 24co2bn not detected how to fix ? thanks

2 3

Fwd:
by Nico Huber 06 Sep '21

06 Sep '21

Hi Jack, forwarding your message as it was filtered due to your big attachment. The limit for this list is 256KiB. I guess the picture doesn't matter much as this might be a software problem. Nico -------- Forwarded Message -------- Date: Mon, 6 Sep 2021 16:10:15 +1000 From: Jack Fivedock <jackfivedock(a)gmail.com> To: flashrom(a)flashrom.org Hi, I'm trying to write to a MX25L6473E using a raspberry pi and the latest flashrom. I'm able to read correctly each time but writing fails. I have attached below the cable setup I'm using. Using this cable from Chipset pro to connect to the hirose 12 pin EFI connector on the macbook pro. https://www.ebay.com.au/itm/133104579410?ssPageName=STRK%3AMEBIDX%3AIT&_trk… pi@raspberrypi:~ $ sudo flashrom -w New.bin -V -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" flashrom v1.2-471-ga69c519 on Linux 5.10.17-v7l+ (armv7l) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.5.2, GCC 8.3.0, little endian Command line (7 args): flashrom -w New.bin -V -p linux_spi:dev=/dev/spidev0.0 -c MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing linux_spi programmer Using default 2000kHz clock. Use 'spispeed' parameter to override. Using device /dev/spidev0.0 Using 2000kHz clock get_max_kernel_buf_size: Using value from /sys/module/spidev/parameters/bufsiz as max buffer size. linux_spi_init: max_kernel_buf_size: 4096 The following protocols are supported: SPI. Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: compare_id: id1 0xc2, id2 0x2017 Added layout entry 00000000 - 007fffff named complete flash Found Macronix flash chip "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" (8192 kB, SPI) on linux_spi. Chip status register is 0x40. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set 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:S, 0x001000-0x001fff:S, 0x002000-0x002fff:S, 0x003000-0x003fff:EFAILED at 0x00003000! Expected=0xff, Found=0x46, failed byte count from 0x00003000-0x00003fff: 0x70 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 1... 0x000000-0x007fff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x00007fff: 0x1093 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x0000ffff: 0x7c36 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x007fffff: 0x5568d2 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x007fffff: 0x5568d2 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 5... not defined. Looking for another erase function. Trying erase function 6... not defined. Looking for another erase function. Trying erase function 7... not defined. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Good, writing to the flash chip apparently didn't do anything. Please check the connections (especially those to write protection pins) between the programmer and the flash chip. If you think the error is caused by flashrom please report this to the mailing list at flashrom(a)flashrom.org or on IRC (see https://www.flashrom.org/Contact for details), thanks!

1 0

Your Flash Chip is in an Unknown State
by Shane Lirrie Concon 05 Sep '21

05 Sep '21

Hi Flashrom Team, Please help me with my bios chip. I am getting an error when I reprogram my bios chip using flashrom. I have already tried using different versions of AsProgrammer and CH341 Mini Programmer but still unable to verify the new rom. My Chip is an 8 pin and is removable (W25Q64BVAIG). You may refer to the command below. I hope you can help me. C:\Users\SKyFlaKes™\Downloads\Compressed\flashrom>flashrom flashrom v1.2-50-gc19aa5e on Windows 6.2 (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. No operations were specified. C:\Users\SKyFlaKes™\Downloads\Compressed\flashrom>flashrom -w MAXIMUS-IV-GENE-Z-GEN3-ASUS-3603.ROM flashrom v1.2-50-gc19aa5e on Windows 6.2 (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. 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... FAILED at 0x00180004! Expected=0x00, Found=0x08, failed byte count from 0x00000000-0x007fffff: 0xf364 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! Thank you!

2 2

new spi flash GD25Q40(B)
by mk 05 Sep '21

05 Sep '21

Dear Sir, we have this device GD25Q40(b) , while try to read n write the below message came out , i'm using ch341a_spi programmer is there update for flashrom to support it thanks a lot This flash part has status UNTESTED 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

3 3

cannot read/write thinkpad R500 chip AT25DF321
by Spenser Truex 20 Aug '21

20 Aug '21

I'm trying to libreboot my r500 thinkpad but can't do a consistent read. I've librebooted many T500s without issue. bug at libreboot https://notabug.org/libreboot/lbmk/issues/30 Issue is with flashrom though. Perhaps something about this chip in particular? Any ideas moving forward? Best regards, -- CAEE B377 FC82 BAF9 102C D22F C5CE D003 1AA8 E281 Spenser Truex https://equwal.com

3 5

Public Key
by Aleks Ozolins 17 Aug '21

17 Aug '21

Hi there! Downloading a tarball off website and trying to verify signature. Can you point me towards the public key or fingerprint? Thank you! -- Aleks Ozolins m:973.464.5242 aleks(a)aleksozolins.com https://www.aleksozolins.com

2 4

Kombi aus Leder und Holz
by Die Office Einrichter 10 Aug '21

10 Aug '21

1 0

Quotation Request
by Natalia Chernenko | Supply Chain Analyst 10 Aug '21

10 Aug '21

Good day, I tried calling your offline line yesterday, and earlier today, but couldn't get through. Please can you kindly check our attached request for an urgent quote of your products. We are a bit behind schedule on our delivery time and would appreciate it if you can treat this quotation request with priority. Hoping to hear from you soon. Kind regards, Natalia Natalia Chernenko | Supply Chain Analyst Lasante Vital SA 1st Km Markopoulou-Kalyvion , Kalivia ,Attica GR 19010 Greece , tel : +30 290 451 111 Fax: +30 229ewr0 61 443

1 0

More detailed tests with the JTAG-lock-pick Tiny 2
by Denis 'GNUtoo' Carikli 03 Aug '21

03 Aug '21

Hi, I've tried to make the Distortec JTAG-lock-pick Tiny 2[1][2] work with flashrom and for some reason it always read the same thing. Back in April there was also a thread about it[0], but not much details were shared about the setup, so since I tried things, I also took the occasion to try to share them here. The JTAG-lock-pick Tiny 2 connector is similar to the one of the Olimex ARM-USB-TINY that is described in the wiki[3]. Even if the connector is the same, there are some differences between both hardware designs: - On the JTAG-lock-pick Tiny 2, VREF and VTARGET are connected together according to its schematics that are in its manual[4]. - Users are supposed to connect a reference voltage to any of these two pins (VREF and VTARGET). - The pins 17 and 19 are not connected (NC) at all. - The JTAG-lock-pick Tiny 2 uses an FTD232HL chip (among with other chips like a CPLD and some chips to isolate the target device from it). I've made the following patch to try to use it: diff --git a/ft2232_spi.c b/ft2232_spi.c index e32d7f81..d986e0a2 100644 --- a/ft2232_spi.c +++ b/ft2232_spi.c @@ -38,6 +38,7 @@ #define FTDI_FT2232H_PID 0x6010 #define FTDI_FT4232H_PID 0x6011 #define FTDI_FT232H_PID 0x6014 +#define DISTORTEC_JTAG_LOCK_PICK_TINY_2_PID 0x8220 #define TIAO_TUMPA_PID 0x8a98 #define TIAO_TUMPA_LITE_PID 0x8a99 #define AMONTEC_JTAGKEY_PID 0xCFF8 @@ -66,6 +67,7 @@ static const struct dev_entry devs_ft2232spi[] = { {FTDI_VID, TIAO_TUMPA_PID, OK, "TIAO", "USB Multi-Protocol Adapter"}, {FTDI_VID, TIAO_TUMPA_LITE_PID, OK, "TIAO", "USB Multi-Protocol Adapter Lite"}, {FTDI_VID, AMONTEC_JTAGKEY_PID, OK, "Amontec", "JTAGkey"}, + {FTDI_VID, DISTORTEC_JTAG_LOCK_PICK_TINY_2_PID, OK, "Distortec", "JTAG-lock-pick"}, {GOEPEL_VID, GOEPEL_PICOTAP_PID, OK, "GOEPEL", "PicoTAP"}, {GOOGLE_VID, GOOGLE_SERVO_PID, OK, "Google", "Servo"}, {GOOGLE_VID, GOOGLE_SERVO_V2_PID0, OK, "Google", "Servo V2 Legacy"}, @@ -350,6 +352,13 @@ static int ft2232_spi_init(void) ft2232_vid = GOEPEL_VID; ft2232_type = GOEPEL_PICOTAP_PID; channel_count = 2; + } else if (!strcasecmp(arg, "JTAG-lock-pick")) { + ft2232_type = DISTORTEC_JTAG_LOCK_PICK_TINY_2_PID; + /* It contains an FTD232HL chip. Its datasheet has + * "FT232H SINGLE CHANNEL HI-SPEED USB TO MULTIPURPOSE + * UART/FIFO IC" + */ + channel_count = 1; } else if (!strcasecmp(arg, "tumpa")) { /* Interface A is SPI1, B is SPI2. */ ft2232_type = TIAO_TUMPA_PID; I've connected it in the same way described in the wiki for the Olimex ARM-USB-TINY[3], with wires that are about 10 centimeters, and I've provided 3.3v on VREF/VTARGET. When doing that flashrom always reads 0xff: > ./flashrom -p ft2232_spi:type=JTAG-lock-pick,divisor=131072 --verbose > [...] > Probing for Sanyo unknown Sanyo SPI chip, 0 kB: RDID byte 0 > parity violation. compare_id: id1 0xff, id2 0xffff > Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: RDID > byte 0 parity violation. compare_id: id1 0xff, id2 0xffff > Probing for Generic Variable Size SPI chip, 64 kB: Probing for Generic > unknown SPI chip (RDID), 0 kB: RDID byte 0 parity violation. > compare_id: id1 0xff, id2 0xffff > Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: > id1 0xff, id2 0xff > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found > automatically. > Releasing I/Os If instead I remove the power source, flashrom always reads zeros (0x00) instead of ones (0xff). If I go to about 1volt, flashrom still reads 0xff. That device is also supported by openocd and there I managed to use it to reprogram a microcontroller through SWD. With the same connection, on an openmoko debug board (connecting the 3.3v source to VTARGET), I get the following result: > ./flashrom -p ft2232_spi:type=openmoko,divisor=131072 --verbose > Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: > compare_id: id1 0xef, id2 0x4017 > Probing for Generic Variable Size SPI chip, 64 kB: > Probing for Generic unknown SPI chip (RDID), 0 kB: > compare_id: id1 0xef, id2 0x4017 > Probing for Generic unknown SPI chip (REMS), 0 kB: > compare_id: id1 0xef, id2 0x16 > Found Winbond flash chip "W25Q64.V" (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). > No operations were specified. > Releasing I/Os So something is probably wrong somewhere. Note that in the distribution I use (Parabola i686), the FT232H support seems to be supported in libftdi as when running make in the flashrom source directory I have: > Checking for FTDI support... found. > Checking for FT232H support in libftdi... found. I wonder if there is some easy way to make the JTAG-lock-pick Tiny 2 work, as it is quite small and it also does JTAG and SWD, and it'd probably be more reliable than the Arduino that I use at 3.3v (which also needs a 3.3v power source to run at 3.3v). References: ----------- [0]https://www.mail-archive.com/flashrom@flashrom.org/msg14801.html [1]https://distortec.com/jtag-lock-pick-tiny-2/ [2]https://shop.sysmocom.de/products/jtag-lock-pick-tiny-2 [3]https://www.flashrom.org/FT2232SPI_Programmer#Olimex_ARM-USB-TINY.2F-H_an… [4]https://distortec.com/download/70/ [5]https://ftdichip.com/products/ft232hl/ [6]https://ftdichip.com/wp-content/uploads/2020/07/DS_FT232H.pdf [7]https://www.mail-archive.com/flashrom@flashrom.org/msg14801.html Denis.

1 0

Intel Gemini Lake
by michael harris 02 Aug '21

02 Aug '21

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 Winbond flash chip "W25Q128.W" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000 im trying to change write protect it won't let me because it found second chip set sorry if i sound stupid but i bought acerspin311 chromebook because i thought it would be easy enough to get up and running i can't even get a vm to work because of kvm Reguards Nick

1 0

SMM BIOS protection Enabled!
by Munduru Avinash (Europe - iDEAS-ER&D) 28 Jul '21

28 Jul '21

HI, I am working on Intel Denverton c3558 processor and bootloader I am using is Coreboot. For this flashrom utility support is not given. But some how I added this utility. When I tried running this utility. I am getting the following output. ******************************************************************************************************************************** root@CMM2:/mnt# flashrom -p internal -w coreboot-working.rom flashrom v1.2 on Linux 4.19.198-cmm2 (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). Cannot open file stream for /dev/mtd0 coreboot table found at 0x7f76f000. Found chipset "Intel Denverton". Enabling flash write... Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0xdc from 0xab to 0x89 failed. New value is 0xab. SPI Configuration is locked down. PR0: Warning: 0x00000000-0x00000fff is read-only. PR1: Warning: 0x00000000-0x00000fff is read-only. PR2: Warning: 0x00000000-0x00000fff is read-only. PR3: Warning: 0x00000000-0x00000fff is read-only. PR4: Warning: 0x00000000-0x00000fff is read-only. At least some flash regions are write protected. For write operations, you should use a flash layout and include only writable regions. See manpage for more details. Enabling hardware sequencing because some important opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Reading old flash chip contents... Transaction error between offset 0x00ccb000 and 0x00ccb03f (= 0x00ccb000 + 63)! FAILED. root@CMM2:/mnt# The Flash chip I am having is N25Q128..3E but it is recognizing as Opaque flash chip. Could you please suggest a solution for this. Regards, Avinash. Sensitivity: Internal & Restricted 'The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com'

1 0

Unknown SPI Chip for CH341A
by Georg Urff 28 Jul '21

28 Jul '21

Hello, the following Chip is not working with latest verion of flashrom on Ubuntu and CH341A: Issi IS25WP080 DNLE Found Generic flash chip "unkown SPI chip (RDID)" (0kb, SPI) on ch341a_spi This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE Cheers Georg Urff -- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

1 0

Full UEFI firmware install error on AKEMI
by David Horner 27 Jul '21

27 Jul '21

I received the following errors when attempting to install full UEFI firmware. The statements about rebooting conflict with each other too. The first says that a reboot can be done, the second says do not reboot in CAPS. I believe I followed the instructions correctly, all of the checks matched the instructions. Thank you in advance for help with what to do next. Please note that I am not including the many lines that preceded the error lines below. Dave ** Device: Lenovo Ideapad Flex 5 Chromebook (AKEMI) ** Platform: Intel CometLake ** Fw Type: Stock ChromeOS w/RW_LEGACY ** Fw Ver: Google_Akemi.12672.375.0 (12/16/2020) ** Fw WP: Disabled ==================================================== HSFC used for block erasing: HSFC: FGO=1, HSFC=3, WET=0, FDBC=63, SME=0 Transaction error between offset 0x00ad0000 and 0x00ad0fff (= 0x00ad0000 + 4095)! HSFS: FDONE=1, FCERR=1, AEL=0, SCIP=0, PRR34_LOCKDN=0, WRSDIS=0, FDOPSS=1, FDV=1, FLOCKDN=1 HSFC: FGO=0, HSFC=3, WET=0, FDBC=63, SME=0 ERASE_FAILED FAILED! Uh oh. Erase/write failed. Checking if anything changed. Reading current flash chip contents... 000000-0xffffff:R Reading 16777216 bytes starting at 0x000000. ignoring error when reading 0x0-0xffffff done. Good, writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. FAILED Restoring PCI config space for 00:1f:5 reg 0xdc restore_power_management: Re-enabling power management. An error occurred flashing the Full ROM firmware. DO NOT REBOOT! Press [Enter] to return to the main menu.

3 4

flashrom -p internal does not work on HP 8200 SFF Elite
by karmo 24 Jul '21

24 Jul '21

Hi Please take a look at the error log. PC is running HP BIOS J01_0233.bin, ME cleaned, HAP bit Set (me_cleaner.py). Chipset: Intel Q67. BIOS Chip is Macronix MX25L6406E. BB and FDO Jumpers are both set on the Mainboard. Can you help me, please? Thank you very much... A. P.

1 0

all 1's - parity violation - No EEPROM/flash device found - compare_id: id1 0xff, id2 0xffff for *every* device tested
by James Feeney 17 Jul '21

17 Jul '21

Where to look for a cause? I have an only partially booting coreboot firmware image on a Geminilake Chromebook, apparently with a bad payload, but the flash device is obviously being read on boot, as can be seen on the AP console. Short version: Chromebook boot can read the flash device, but flashrom, through SuzyQable, only reads all "1's". Have a sparkfun SuzyQable connected to an Arch Linux box, and to the Chromebook. Have the desired result after running on the Cr50 console: > ccd reset factory > ccd testlab enable > ccd open Previously running flashrom from the stock ChromeOS would give 'Found GigaDevice flash chip "GD25LQ128C/GD25LQ128D"'. I have flashrom from both: git clone https://chromium.googlesource.com/chromiumos/third_party/flashrom WARNERROR=no CONFIG_MEC1308=no CONFIG_ENE_LPC=no make and git clone https://chromium.googlesource.com/chromiumos/platform/standalone-hdctools flashrom install These appear to both act exactly the same. Then: sudo ./flashrom -V -p raiden_debug_spi:target=AP results in "No EEPROM/flash device found", where: $ sudo ./flashrom -V -p raiden_debug_spi:target=AP |sed -n 's/.*$compare.*$/\1/p'|sort|uniq compare_id: id1 0xff, id2 0xff compare_id: id1 0xff, id2 0xffff From running flashrom, the Cr50 console says: [10398.332186 enable_spi_pinmux: AP] [10398.445490 usb_spi_board_disable] [10399.512358 AP UART on] [10399.514036 CCD state: UARTAP+TX UARTEC+TX I2C SPI USBEC+TX] [10399.728811 deferred_tpm_rst_isr] [10399.730025 AP on] [10399.730757 tpm_reset_request(0, 0)] [10399.731775 tpm_reset_now(0)] [10399.735335 tpm_init] tpm_manufactured: manufactured [10399.737601 tpm_reset_now: done] [10402.488852 PinWeaver: Loading Tree!] [10402.511275 PinWeaver: Loaded Tree. restart_count = 88] [10402.513121 Skipping commit] [10402.738718 Committing NVMEM changes.] This causes the Chromebook to boot, so then: [10408.218302 power button pressed] [10408.355704 tpm_rst_asserted] [10409.356714 AP off] [10418.538157 AP UART off] [10418.540362 CCD state: UARTEC+TX I2C SPI USBEC+TX] I don't know whether or not there should be a report of "usb_spi_board_enable" being called, but it is conspicuously not seen. If I understand, it appears as if flashrom reads and caches the flash device ID, but is just seeing all "1's". So - where is the problem? ... the flash device? the "pinmux" accessing the flash? the SPI channel? the USB channel? the Cr50? the raiden_debug_spi driver? some Cr50 configuration variable? some nasty hardware problem? I did run-across this odd thread: https://groups.google.com/a/chromium.org/g/chromium-os-discuss/c/yFevUZz9aac where running flashrom first gives "No EEPROM/flash device found", but subsequently reports, in that case, "Found Winbond flash chip "W25Q256JV_M" (32768 kB, SPI) on raiden_debug_spi." But, the reason for the different consecutive responses from flashrom were not explored there. Any thoughts about why the boot process can read the flash device, while flashrom only reads "1's" for the device ID? I did try running flashrom while specifying the device and forcing a read, but again, it just sees all "1's". Thanks James

1 0

Flashrom asked me to do this
by havsfrun＠topchan.eu 17 Jul '21

17 Jul '21

flashrom v1.2 on Linux 5.13.1-1-default (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 SST flash chip "SST25VF016B" (2048 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x4e, failed byte count from 0x00000000-0x00000fff: 0xfb8 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000003! Expected=0xff, Found=0x7f, failed byte count from 0x00000000-0x00007fff: 0x1e76 ERASE FAILED! Reading current flash chip contents... cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to read 4100 bytes libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 libusb: warning [handle_timeout] async cancel failed -5 Can't read anymore! Aborting. 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. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks!

1 0

FAILED: apu2e4
by Stephen Hladysh 17 Jul '21

17 Jul '21

flashrom -w /tmp/apu2_v4.14.0.1.rom -p internal flashrom v1.2 on FreeBSD 12.2-STABLE (amd64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 4, resolution: 2ns). coreboot table found at 0xcfec1000. Found chipset "AMD FCH". Enabling flash write... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x0000e000! Expected=0xff, Found=0x00, failed byte count from 0x0000e000-0x0000efff: 0x217 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x2f, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x101cb1 Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF!

2 1

Unknown programmer "ft2232_spi"
by Michael Leukert - AMPEGON 15 Jul '21

15 Jul '21

Hello! Do you have any idea why our flashrom v0.9.9 won't accept ft2232_spi as a programmer? We want to use flashrom for our ft2232_spi devices and the website flashrom.org/Flashrom/0.9.9/Supported_Hardware claims that flashrom v0.9.9 supports ft2232_spi. However, for some reason it just won't accept ft2232_spi as a programmer: - flashrom -p ft2232_spi flashrom v0.9.9-rc1-r1942 on Linux 4.15.0-45-generic (i686) flashrom is free software, get the source code at https://flashrom.org Error: Unknown programmer "ft2232_spi". Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, ch341a_spi. Please run "flashrom --help" for usage info. Surprisingly, even the man page claims that ft2232_spi is supported: - man flashrom ... -p, --programmer <name>[:parameter[,parameter[,parameter]]] Specify the programmer device. This is mandatory for all operations involving any chip access (probe/read/write/...). Currently supported are: ... * ft2232_spi (for SPI flash ROMs attached to an FT2232/FT4232H/FT232H family based USB SPI programmer), including the DLP Design DLP-USB1232H, FTDI FT2232H Mini-Module, FTDI FT4232H Mini-Module, openbiosprog-spi, Amontec JTAGkey/JTAGkey-tiny/JTAGkey-2, Dangerous Prototypes Bus Blaster, Olimex ARM-USB-TINY/-H, Olimex ARM-USB-OCD/-H, TIAO/DIYGADGET USB Multi-Protocol Adapter (TUMPA), TUMPA Lite, GOEPEL PicoTAP and Google Servo v1/v2. ... This is how we installed it: - sudo apt install flashrom Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: flashrom 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 169 kB of archives. After this operation, 868 kB of additional disk space will be used. Get:1 http://ch.archive.ubuntu.com/ubuntu xenial/universe i386 flashrom i386 0.9.9~rc1+r1942-1 [169 kB] Fetched 169 kB in 0s (1'116 kB/s) Selecting previously unselected package flashrom. (Reading database ... 165415 files and directories currently installed.) Preparing to unpack .../flashrom_0.9.9~rc1+r1942-1_i386.deb ... Unpacking flashrom (0.9.9~rc1+r1942-1) ... Processing triggers for man-db (2.7.5-1) ... Setting up flashrom (0.9.9~rc1+r1942-1) ... This is our system: - cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" - uname -m i686 We don't understand why our flashrom won't accept ft2232_spi or how to proceed. And would appreciate any assistance, if you have the resources to assist or even just point us in the right direction here we can fix this ourselves. Freundliche Grüsse | Best regards, Michael Leukert | Software Developer R&D-ES Direct +41 58 710 4469 michael.leukert(a)ampegon.com Ampegon Power Electronics AG Kreuzweg 11 | 5400 Baden, Switzerland Tel.+ 41 58 710 44 00 | Fax +41 58 710 44 01 info(a)ampegon.com | ampegon.com MWST Nr. CHE-310.342.455 MWST | UID: CHE-310.342.455 Follow Ampegon's latest news online via our website<https://ampegon.com/news/> or LinkedIn<https://ch.linkedin.com/company/ampegon> group

3 6

Why not use usleep() instead of clock_gettime() loop for delay ?
by Patrick Star 13 Jul '21

13 Jul '21

I saw flashrom process use too many cpu time when I use it to write flashchip. Then I strace the process, and found too many "clock_gettime(CLOCK_MONOTONIC...)" system call. And located it to udelay.c line 39, in function clock_usec_delay(). So I replace the code with just usleep(), as below, static void clock_usec_delay(int usecs) { usleep(usecs); } And it still worked well, and use much less cpu time, and the time spend on erase&write a chip is basicly the same as before. Also I write image to a flashchip and read it out with the modified flashrom many times, and the read out results are always same as the original image. So why not use usleep() to save cpu time ? BTW: I have used flashrom many years, it helped me a lot, thanks for your work, very grateful.

5 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom