- flashrom - mail.coreboot.org

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

21 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 02 Aug '21

02 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

Error Log
by Ionilith 07 Jul '21

07 Jul '21

sudo flashrom --programmer internalflashrom v1.0.1 on Linux 3.10.0-1160.31.1.el7.x86_64 (x86_64)flashrom is free software, get the source code at https://flashrom.orgUsing clock_gettime for delay loops (clk_id: 1, resolution: 1ns).No DMI table found.Found chipset "AMD FP4".Enabling flash write... FCH device found but SMBus revision 0x51 does not match known values.Please report this to flashrom(a)flashrom.org and include this log andthe output of lspci -nnvx, thanks!.Could not determine chipset generation.PROBLEMS, continuing anywayNo EEPROM/flash device found.Note: flashrom can never write if the flash chip isn't found automatically.

1 0

stock flashrom vs Google forked flashrom on a chromebook running "stock linux"?
by James Feeney 01 Jul '21

01 Jul '21

When flashing the boot rom or the EC rom on, particularly, an Intel SOC chromebook, and running a "stock linux", instead of the original chromeos, is there any fundamental difference between the stock flashrom and the Google forked flashrom that would prevent the stock flashrom from working properly? Thanks James

2 2

Flashroom and TUXEDO Notebook BIOS N.1.07, Date: 02/25/2020
by Miroslav Karlovsky 26 Jun '21

26 Jun '21

- Notebook: Tuxedo BA1510, CPU Ryzen5 3500U, BIOS: N.1.07, Date: 02/25/2020; Fa.: tuxedocomputers.com ----- Output: sudo dmesg -T -l err ------------------------------------- [So Jun 13 18:30:11 2021] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0._Q46], AE_ALREADY_EXISTS (20200925/dswload2-326) [So Jun 13 18:30:11 2021] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200925/psobject-220) [So Jun 13 18:30:11 2021] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SBRG.EC0._Q47], AE_ALREADY_EXISTS (20200925/dswload2-326) [So Jun 13 18:30:11 2021] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200925/psobject-220) [So Jun 13 18:30:13 2021] snd_hda_intel 0000:02:00.6: no codecs found! Hallo Flashrom Service, ------------------------------------------------------------------------ [miro@fux ~]$ sudo flashrom -p internal -r backup.bin flashrom v1.2 on Linux 5.10.42-1-MANJARO (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 chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x61 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway ======================================================================== You seem to be running flashrom on an unknown laptop. Some internal buses have been disabled for safety reasons. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. [miro@fux ~]$ ----- Output: lspci -nnvx ---------------------------------------------- 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Flags: fast devsel 00: 22 10 d0 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 d0 15 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU [1022:15d1] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU [1022:15d1] Flags: bus master, fast devsel, latency 0, IRQ 25 Capabilities: [40] Secure device <?> Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00: 22 10 d1 15 04 04 10 00 00 00 06 08 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 d1 15 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 0 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:01.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 26, IOMMU group 1 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000f000-0000ffff [size=4K] Memory behind bridge: fea00000-feafffff [size=1M] Prefetchable memory behind bridge: 00000000f0200000-00000000f03fffff [size=2M] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [370] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 d3 15 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f1 f1 00 20 20: a0 fe a0 fe 21 f0 31 f0 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 2 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A [1022:15db] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 27, IOMMU group 3 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fe500000-fe8fffff [size=4M] Prefetchable memory behind bridge: 00000000e0000000-00000000f01fffff [size=258M] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: QLogic Corp. Device [1077:1d05] Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Kernel driver in use: pcieport 00: 22 10 db 15 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 02 02 00 e1 e1 00 00 20: 50 fe 80 fe 01 e0 11 f0 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 1a 00 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B [1022:15dc] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 2 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe900000-fe9fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: QLogic Corp. Device [1077:1d05] Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Kernel driver in use: pcieport 00: 22 10 dc 15 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 03 03 00 f1 01 00 00 20: 90 fe 90 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: 66MHz, medium devsel, IOMMU group 4 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00: 22 10 0b 79 03 04 20 02 61 00 05 0c 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 05 1d 77 10 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 4 00: 22 10 0e 79 0f 00 20 02 51 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 05 1d 77 10 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 [1022:15e8] Flags: fast devsel, IOMMU group 5 00: 22 10 e8 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 [1022:15e9] Flags: fast devsel, IOMMU group 5 00: 22 10 e9 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 [1022:15ea] Flags: fast devsel, IOMMU group 5 00: 22 10 ea 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 [1022:15eb] Flags: fast devsel, IOMMU group 5 Kernel driver in use: k10temp Kernel modules: k10temp 00: 22 10 eb 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 [1022:15ec] Flags: fast devsel, IOMMU group 5 00: 22 10 ec 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 [1022:15ed] Flags: fast devsel, IOMMU group 5 00: 22 10 ed 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 [1022:15ee] Flags: fast devsel, IOMMU group 5 00: 22 10 ee 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 [1022:15ef] Flags: fast devsel, IOMMU group 5 00: 22 10 ef 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Physical Slot: 0 Flags: bus master, fast devsel, latency 0, IRQ 52, IOMMU group 6 I/O ports at f000 [size=256] Memory at fea04000 (64-bit, non-prefetchable) [size=4K] Memory at fea00000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable+ Count=4 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8169 Kernel modules: r8169 00: ec 10 68 81 07 04 10 00 15 00 00 02 10 00 00 00 10: 01 f0 00 00 00 00 00 00 04 40 a0 fe 00 00 00 00 20: 04 00 a0 fe 00 00 00 00 00 00 00 00 05 1d 77 10 30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00 02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 7 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=2M] I/O ports at e000 [size=256] Memory at fe800000 (32-bit, non-prefetchable) [size=512K] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=3 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [200] Physical Resizable BAR Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [320] Latency Tolerance Reporting Kernel driver in use: amdgpu Kernel modules: amdgpu 00: 02 10 d8 15 07 04 10 08 c2 00 00 03 10 00 80 00 10: 0c 00 00 e0 00 00 00 00 0c 00 00 f0 00 00 00 00 20: 01 e0 00 00 00 00 80 fe 00 00 00 00 05 1d 77 10 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 01 00 00 02:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller [1002:15de] Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: bus master, fast devsel, latency 0, IRQ 55, IOMMU group 8 Memory at fe888000 (32-bit, non-prefetchable) [size=16K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 02 10 de 15 07 04 10 00 00 00 03 04 10 00 80 00 10: 00 80 88 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 05 1d 77 10 30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 02 00 00 02:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df] Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 8 Memory at fe700000 (32-bit, non-prefetchable) [size=1M] Memory at fe88c000 (32-bit, non-prefetchable) [size=8K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=2 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: ccp Kernel modules: ccp 00: 22 10 df 15 07 04 10 08 00 00 80 10 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 70 fe 00 00 00 00 20: 00 00 00 00 00 c0 88 fe 00 00 00 00 05 1d 77 10 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 03 00 00 02:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e0] (prog-if 30 [XHCI]) Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: bus master, fast devsel, latency 0, IRQ 32, IOMMU group 8 Memory at fe600000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 e0 15 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 60 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 05 1d 77 10 30: 00 00 00 00 48 00 00 00 00 00 00 00 04 04 00 00 02:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e1] (prog-if 30 [XHCI]) Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: fast devsel, IRQ 24, IOMMU group 8 Memory at fe500000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 e1 15 03 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 50 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 05 1d 77 10 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 01 00 00 02:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] DeviceName: HD Audio Controller Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: bus master, fast devsel, latency 0, IRQ 56, IOMMU group 8 Memory at fe880000 (32-bit, non-prefetchable) [size=32K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 22 10 e3 15 07 04 10 00 00 00 03 04 10 00 80 00 10: 00 00 88 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 05 1d 77 10 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 03 00 00 03:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 61) (prog-if 01 [AHCI 1.0]) Subsystem: Tongfang Hongkong Limited Device [1d05:1077] Flags: bus master, fast devsel, latency 0, IRQ 30, IOMMU group 2 Memory at fe900000 (32-bit, non-prefetchable) [size=2K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=2/2 Maskable- 64bit+ Capabilities: [d0] SATA HBA v1.0 Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Kernel driver in use: ahci 00: 22 10 01 79 07 04 10 00 61 01 06 01 10 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 90 fe 00 00 00 00 05 1d 77 10 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 01 00 00

1 1

ERASE FAILED
by lautaro teta musa 24 Jun '21

24 Jun '21

Hi, Im programing a MX MX25L1606E chip with a ch341a_spi programmer in ubuntu 18.04 with flashrom utility. Im check all the connections and are correctly. when im erase the chip receive this error Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xff44 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xff44 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x001fffff: 0x15efae ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x001fffff: 0x15efae ERASE FAILED! Looking for another erase function. No usable erase functions left. whats is the problem?? thanks

1 0

ASUS PRIME TRX40-PRO S
by Stephan Hadamik 18 Jun '21

18 Jun '21

$ sudo flashrom -V -p internal flashrom v1.2 on Linux 5.4.0-66-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.6.4, GCC 9.2.1 20200304, little endian Command line (3 args): flashrom -V -p internal Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer /sys/class/mtd/mtd0 does not exist No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "ASUS" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK COMPUTER INC." DMI string baseboard-product-name: "PRIME TRX40-PRO S" DMI string baseboard-version: "Rev 1.xx" Found chipset "AMD FP4" with PCI ID 1022:790e. Enabling flash write... SPI base address is at 0xfec10000 FCH device found but SMBus revision 0x61 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.ROM strap override is not active PROBLEMS, continuing anyway The following protocols are supported: LPC, FWH. Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xfb, id2 0xfd, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10ms/40us. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xfb, id2 0xfd, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xfb, id2 0xfd, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xfb, id2 0xfd, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.

1 0

Reporting unknown chip
by Benjamin Kallus 15 Jun '21

15 Jun '21

Trying to check BIOS size on an MSI X470 motherboard. Here's the relevant output: pistachio# flashrom --programmer internal --flash-size flashrom v1.2 on Linux 5.12.10-arch1-1 (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). No DMI table found. Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x61 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway ======================================================================== You may be running flashrom on an unknown laptop. We could not detect this for sure because your vendor has not set up the SMBIOS tables correctly. Some internal buses have been disabled for safety reasons. You can enforce using all buses by adding -p internal:laptop=this_is_not_a_laptop to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. And here's lspci: ``` 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b79] Flags: fast devsel 00: 22 10 80 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 79 7b 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481] Flags: fast devsel Capabilities: [40] Secure device <?> Capabilities: [64] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [c8] Vendor Specific Information: Len=18 <?> 00: 22 10 81 14 40 00 10 00 00 00 06 08 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 81 14 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 00 00 00 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Flags: fast devsel, IOMMU group 0 00: 22 10 82 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fc400000-fc4fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1234] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [370] L1 PM Substates Capabilities: [3c4] Designated Vendor-Specific: Vendor=1022 ID=0001 Rev=1 Len=44 <?> Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: pcieport 00: 22 10 83 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f1 01 00 20 20: 40 fc 40 fc f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 0 Bus: primary=00, secondary=03, subordinate=26, sec-latency=0 I/O behind bridge: 0000f000-0000ffff [size=4K] Memory behind bridge: fb400000-fbefffff [size=11M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1234] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [370] L1 PM Substates Capabilities: [3c4] Designated Vendor-Specific: Vendor=1022 ID=0001 Rev=1 Len=44 <?> Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: pcieport 00: 22 10 83 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 03 26 00 f1 f1 00 20 20: 40 fb e0 fb f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Flags: fast devsel, IOMMU group 1 00: 22 10 82 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Flags: fast devsel, IOMMU group 2 00: 22 10 82 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 30, IOMMU group 2 Bus: primary=00, secondary=27, subordinate=27, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fa000000-fb0fffff [size=17M] Prefetchable memory behind bridge: 00000000e0000000-00000000e9ffffff [size=160M] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1234] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [370] L1 PM Substates Capabilities: [3c4] Designated Vendor-Specific: Vendor=1022 ID=0001 Rev=1 Len=44 <?> Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: pcieport 00: 22 10 83 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 27 27 00 e1 e1 00 20 20: 00 fa 00 fb 01 e0 f1 e9 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:03.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 2 Bus: primary=00, secondary=28, subordinate=28, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fc300000-fc3fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1234] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [370] L1 PM Substates Capabilities: [3c4] Designated Vendor-Specific: Vendor=1022 ID=0001 Rev=1 Len=44 <?> Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: pcieport 00: 22 10 83 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 28 28 00 f1 01 00 20 20: 30 fc 30 fc f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Flags: fast devsel, IOMMU group 3 00: 22 10 82 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Flags: fast devsel, IOMMU group 4 00: 22 10 82 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Flags: fast devsel, IOMMU group 5 00: 22 10 82 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 32, IOMMU group 6 Bus: primary=00, secondary=29, subordinate=29, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: pcieport 00: 22 10 84 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 29 29 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Flags: fast devsel, IOMMU group 7 00: 22 10 82 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 33, IOMMU group 8 Bus: primary=00, secondary=2a, subordinate=2a, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fc000000-fc2fffff [size=3M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: pcieport 00: 22 10 84 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 2a 2a 00 f1 01 00 00 20: 00 fc 20 fc f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b79] Flags: 66MHz, medium devsel, IOMMU group 9 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00: 22 10 0b 79 03 04 20 02 61 00 05 0c 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 79 7b 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b79] Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 9 00: 22 10 0e 79 0f 00 20 02 51 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 79 7b 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440] Flags: fast devsel, IOMMU group 10 00: 22 10 40 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441] Flags: fast devsel, IOMMU group 10 00: 22 10 41 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442] Flags: fast devsel, IOMMU group 10 00: 22 10 42 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443] Flags: fast devsel, IOMMU group 10 Kernel driver in use: k10temp Kernel modules: k10temp 00: 22 10 43 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444] Flags: fast devsel, IOMMU group 10 00: 22 10 44 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445] Flags: fast devsel, IOMMU group 10 00: 22 10 45 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446] Flags: fast devsel, IOMMU group 10 00: 22 10 46 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 [1022:1447] Flags: fast devsel, IOMMU group 10 00: 22 10 47 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] (prog-if 02 [NVM Express]) Subsystem: Samsung Electronics Co Ltd Device [144d:a801] Flags: bus master, fast devsel, latency 0, IRQ 42, NUMA node 0, IOMMU group 0 Memory at fc400000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [b0] MSI-X: Enable+ Count=33 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [158] Power Budgeting <?> Capabilities: [168] Secondary PCI Express Capabilities: [188] Latency Tolerance Reporting Capabilities: [190] L1 PM Substates Kernel driver in use: nvme 00: 4d 14 08 a8 06 04 10 00 00 02 08 01 10 00 00 00 10: 04 00 40 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 4d 14 01 a8 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00 03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43d0] (rev 01) (prog-if 30 [XHCI]) Subsystem: ASMedia Technology Inc. Device [1b21:1142] Flags: bus master, fast devsel, latency 0, IRQ 77, IOMMU group 0 Memory at fbea0000 (64-bit, non-prefetchable) [size=32K] Capabilities: [50] MSI: Enable+ Count=1/8 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Capabilities: [300] Latency Tolerance Reporting Capabilities: [400] L1 PM Substates Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 d0 43 06 04 10 00 01 30 03 0c 10 00 80 00 10: 04 00 ea fb 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 21 1b 42 11 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 00 00 03:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller [1022:43c8] (rev 01) (prog-if 01 [AHCI 1.0]) Subsystem: ASMedia Technology Inc. Device [1b21:1062] Flags: bus master, fast devsel, latency 0, IRQ 44, IOMMU group 0 Memory at fbe80000 (32-bit, non-prefetchable) [size=128K] Expansion ROM at fbe00000 [disabled] [size=512K] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Kernel driver in use: ahci 00: 22 10 c8 43 06 04 10 00 01 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 e8 fb 00 00 00 00 21 1b 62 10 30: 00 00 e0 fb 50 00 00 00 00 00 00 00 ff 02 00 00 03:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge [1022:43c6] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 0 Bus: primary=03, secondary=20, subordinate=26, sec-latency=0 I/O behind bridge: 0000f000-0000ffff [size=4K] Memory behind bridge: fb400000-fbdfffff [size=10M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Upstream Port, MSI 00 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:0201] Capabilities: [100] Advanced Error Reporting Kernel driver in use: pcieport 00: 22 10 c6 43 07 04 10 00 01 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 03 20 26 00 f1 f1 00 00 20: 40 fb d0 fb f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 03 12 00 20:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 35, IOMMU group 0 Bus: primary=20, secondary=21, subordinate=21, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:3306] Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 c7 43 07 04 10 00 01 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 20 21 21 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 20:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 37, IOMMU group 0 Bus: primary=20, secondary=22, subordinate=22, sec-latency=0 I/O behind bridge: 0000f000-0000ffff [size=4K] Memory behind bridge: fbd00000-fbdfffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:3306] Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 c7 43 07 04 10 00 01 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 20 22 22 00 f1 f1 00 00 20: d0 fb d0 fb f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 20:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 38, IOMMU group 0 Bus: primary=20, secondary=23, subordinate=23, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:3306] Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 c7 43 07 04 10 00 01 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 20 23 23 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 20:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 39, IOMMU group 0 Bus: primary=20, secondary=24, subordinate=24, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fb400000-fbbfffff [size=8M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:3306] Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 c7 43 07 04 10 00 01 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 20 24 24 00 f1 01 00 00 20: 40 fb b0 fb f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 20:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 0 Bus: primary=20, secondary=25, subordinate=25, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:3306] Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 c7 43 07 04 10 00 01 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 20 25 25 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 20:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 41, IOMMU group 0 Bus: primary=20, secondary=26, subordinate=26, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fbc00000-fbcfffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:3306] Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 c7 43 07 04 10 00 01 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 20 26 26 00 f1 01 00 00 20: c0 fb c0 fb f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 22:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b79] Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 0 I/O ports at f000 [size=256] Memory at fbd04000 (64-bit, non-prefetchable) [size=4K] Memory at fbd00000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable+ Count=4 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8169 Kernel modules: r8169 00: ec 10 68 81 07 04 10 00 15 00 00 02 10 00 00 00 10: 01 f0 00 00 00 00 00 00 04 40 d0 fb 00 00 00 00 20: 04 00 d0 fb 00 00 00 00 00 00 00 00 62 14 79 7b 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00 24:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7231 [1131:7231] (rev aa) Subsystem: Avermedia Technologies Inc Device [1461:1807] Flags: fast devsel, IRQ 255, IOMMU group 0 Memory at fb800000 (64-bit, non-prefetchable) [disabled] [size=4M] Memory at fb400000 (64-bit, non-prefetchable) [disabled] [size=4M] Capabilities: [40] MSI: Enable- Count=1/16 Maskable- 64bit+ Capabilities: [50] Express Endpoint, MSI 00 Capabilities: [74] Power Management version 3 Capabilities: [7c] Vendor Specific Information: Len=84 <?> Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=094 <?> 00: 31 11 31 72 00 00 10 00 aa 00 80 04 10 00 00 00 10: 04 00 80 fb 00 00 00 00 04 00 40 fb 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 61 14 07 18 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00 26:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242] (prog-if 30 [XHCI]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b79] Flags: bus master, fast devsel, latency 0, IRQ 25, IOMMU group 0 Memory at fbc00000 (64-bit, non-prefetchable) [size=32K] Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [68] MSI-X: Enable+ Count=8 Masked- Capabilities: [78] Power Management version 3 Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [280] Secondary PCI Express Capabilities: [300] Latency Tolerance Reporting Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 21 1b 42 12 06 04 10 00 00 30 03 0c 10 00 00 00 10: 04 00 c0 fb 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 79 7b 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 00 00 27:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:2765] Flags: bus master, fast devsel, latency 0, IRQ 118, IOMMU group 2 Memory at fa000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=128M] Memory at e8000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at fb000000 [virtual] [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] Secondary PCI Express Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_drm, nvidia 00: de 10 87 11 07 04 10 00 a1 00 00 03 00 00 80 00 10: 00 00 00 fa 0c 00 00 e0 00 00 00 00 0c 00 00 e8 20: 00 00 00 00 01 e0 00 00 00 00 00 00 42 38 65 27 30: 00 00 00 00 60 00 00 00 00 00 00 00 ff 01 00 00 27:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio Controller [10de:0e0a] (rev a1) Subsystem: eVga.com. Corp. Device [3842:2765] Flags: bus master, fast devsel, latency 0, IRQ 99, IOMMU group 2 Memory at fb080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: de 10 0a 0e 06 00 10 00 a1 00 03 04 10 00 80 00 10: 00 00 08 fb 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 42 38 65 27 30: 00 00 00 00 60 00 00 00 00 00 00 00 ff 02 00 00 28:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084] Flags: bus master, fast devsel, latency 0, IRQ 102, IOMMU group 2 Memory at fc300000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi 00: 86 80 23 27 06 04 10 00 1a 00 80 02 10 00 00 00 10: 04 00 30 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 84 00 30: 00 00 00 00 c8 00 00 00 00 00 00 00 ff 01 00 00 29:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] Flags: fast devsel, IOMMU group 11 Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> 00: 22 10 8a 14 00 00 10 00 00 00 00 13 10 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 8a 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 00 00 00 2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Flags: fast devsel, IOMMU group 12 Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> 00: 22 10 85 14 00 00 10 00 00 00 00 13 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 85 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 00 00 00 2a:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486] Flags: bus master, fast devsel, latency 0, IRQ 95, IOMMU group 13 Memory at fc100000 (32-bit, non-prefetchable) [size=1M] Memory at fc208000 (32-bit, non-prefetchable) [size=8K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=2 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [2a0] Access Control Services Capabilities: [370] Transaction Processing Hints Kernel driver in use: ccp Kernel modules: ccp 00: 22 10 86 14 06 04 10 08 00 00 80 10 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 10 fc 00 00 00 00 20: 00 00 00 00 00 80 20 fc 00 00 00 00 22 10 86 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 01 00 00 2a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] (prog-if 30 [XHCI]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b79] Flags: bus master, fast devsel, latency 0, IRQ 86, IOMMU group 14 Memory at fc000000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [2a0] Access Control Services Capabilities: [370] Transaction Processing Hints Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 9c 14 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 79 7b 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 03 00 00 2a:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:cb79] Flags: bus master, fast devsel, latency 0, IRQ 101, IOMMU group 15 Memory at fc200000 (32-bit, non-prefetchable) [size=32K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [2a0] Access Control Services Capabilities: [370] Transaction Processing Hints Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 22 10 87 14 06 04 10 00 00 00 03 04 10 00 80 00 10: 00 00 20 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 79 cb 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 04 00 00 ``` Thanks!

1 0

Re: Your flash chip is in an unknown state
by Mike Banon 07 Jun '21

07 Jun '21

If you have trouble using a flashrom opensource software, there are helpful instructions online. And, as for DIP8 to SOIC8 adapter: it simply allows to directly connect a chip to the programmier like CH341A without using a test clip. On Thu, Jun 3, 2021 at 10:06 PM Hermann Thomas A. Calero < hermanncalero(a)gmail.com> wrote: > I do have a DIP8 to SOIC8 adapter but dont know how to use it in > Raspian OS. I do know how to identify chip in windows but dont know how to > flash the bios chip iotself. I will try to check if i can do this directly > instead and flash in in windows the bin file i needed to eb flashed... > > On Thu, Jun 3, 2021 at 2:31 AM Mike Banon <mikebdp2(a)gmail.com> wrote: > >> Reposting your messages to a flashrom mailing list. Are you sure that a >> contact of a clip - with a chip - is good enough? If a chip is hanging in >> the air and its legs aren't mounted to the motherboard, the legs are prone >> to a tiny bending and the contact is less certain. Do you have a DIP8 to >> SOIC8 adapter - to plug this chip directly to a programmer without a test >> clip? >> >> On Wed, Jun 2, 2021 at 9:36 PM Hermann Thomas A. Calero < >> hermanncalero(a)gmail.com> wrote: >> >>> I am using flashrom v1.2 from here >>> <https://download.flashrom.org/releases/> . ALso used previous version >>> of v.0.9.9 from same directory. Utilizing raspian lite OS on a rasberry pi >>> zero w. >>> >>> On Wed, Jun 2, 2021 at 11:29 AM Hermann Thomas A. Calero < >>> hermanncalero(a)gmail.com> wrote: >>> >>>> Hello Mike, >>>> >>>> I will rewire but so far it was good the first time but i broke one of >>>> the legs of the bios pin on the board why i needed to replace the entire >>>> bios chip. Now i am flashing directly to the chip itself. with a clip. >>>> >>>> On Tue, Jun 1, 2021 at 8:07 AM Mike Banon <mikebdp2(a)gmail.com> wrote: >>>> >>>>> Are you sure that your (ISP? in-system programming) flashing set up is >>>>> reliable? Short enough wires, etc. >>>>> >>>>> On Sat, May 29, 2021 at 12:36 AM Hermann Thomas A. Calero < >>>>> hermanncalero(a)gmail.com> wrote: >>>>> >>>>>> Any reason for this? Any guidance will be greatly appreciated. >>>>>> >>>>>> On Fri, May 21, 2021 at 4:33 PM Hermann Thomas A. Calero < >>>>>> hermanncalero(a)gmail.com> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I tried to change the flash chip of my old Toshiba satellite pro a50 >>>>>>> a series with previous bios chip Winbond 25Q64CVSIG with a new Winbond >>>>>>> 25Q64FWSIG and i am getting the error "No usable erase functions left. >>>>>>> FAILED! >>>>>>> Uh oh. Erase/write failed. Checking if anything has changed. >>>>>>> Reading current flash chip contents... done. >>>>>>> Apparently at least some data has changed. >>>>>>> Your flash chip is in an unknown state. >>>>>>> Please report this on IRC at chat.freenode.net (channel #flashrom) >>>>>>> or >>>>>>> mail flashrom(a)flashrom.org, thanks!" >>>>>>> >>>>>>> Error screenshot here <https://prnt.sc/138oacn>and below. >>>>>>> >>>>>>> [image: image.png] >>>>>>> Hope you can enlighten me on this as i have used the latest flashrom >>>>>>> version. Thank you! >>>>>>> >>>>>>> _______________________________________________ >>>>>> flashrom mailing list -- flashrom(a)flashrom.org >>>>>> To unsubscribe send an email to flashrom-leave(a)flashrom.org >>>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, Mike Banon >>>>> Open Source Community Manager of 3mdeb - https://3mdeb.com/ >>>>> >>>> >> >> -- >> Best regards, Mike Banon >> Open Source Community Manager of 3mdeb - https://3mdeb.com/ >> > -- Best regards, Mike Banon Open Source Community Manager of 3mdeb - https://3mdeb.com/

1 0

Re: Your flash chip is in an unknown state
by Mike Banon 03 Jun '21

03 Jun '21

Reposting your messages to a flashrom mailing list. Are you sure that a contact of a clip - with a chip - is good enough? If a chip is hanging in the air and its legs aren't mounted to the motherboard, the legs are prone to a tiny bending and the contact is less certain. Do you have a DIP8 to SOIC8 adapter - to plug this chip directly to a programmer without a test clip? On Wed, Jun 2, 2021 at 9:36 PM Hermann Thomas A. Calero < hermanncalero(a)gmail.com> wrote: > I am using flashrom v1.2 from here > <https://download.flashrom.org/releases/> . ALso used previous version of > v.0.9.9 from same directory. Utilizing raspian lite OS on a rasberry pi > zero w. > > On Wed, Jun 2, 2021 at 11:29 AM Hermann Thomas A. Calero < > hermanncalero(a)gmail.com> wrote: > >> Hello Mike, >> >> I will rewire but so far it was good the first time but i broke one of >> the legs of the bios pin on the board why i needed to replace the entire >> bios chip. Now i am flashing directly to the chip itself. with a clip. >> >> On Tue, Jun 1, 2021 at 8:07 AM Mike Banon <mikebdp2(a)gmail.com> wrote: >> >>> Are you sure that your (ISP? in-system programming) flashing set up is >>> reliable? Short enough wires, etc. >>> >>> On Sat, May 29, 2021 at 12:36 AM Hermann Thomas A. Calero < >>> hermanncalero(a)gmail.com> wrote: >>> >>>> Any reason for this? Any guidance will be greatly appreciated. >>>> >>>> On Fri, May 21, 2021 at 4:33 PM Hermann Thomas A. Calero < >>>> hermanncalero(a)gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> I tried to change the flash chip of my old Toshiba satellite pro a50 a >>>>> series with previous bios chip Winbond 25Q64CVSIG with a new Winbond >>>>> 25Q64FWSIG and i am getting the error "No usable erase functions left. >>>>> FAILED! >>>>> Uh oh. Erase/write failed. Checking if anything has changed. >>>>> Reading current flash chip contents... done. >>>>> Apparently at least some data has changed. >>>>> Your flash chip is in an unknown state. >>>>> Please report this on IRC at chat.freenode.net (channel #flashrom) or >>>>> mail flashrom(a)flashrom.org, thanks!" >>>>> >>>>> Error screenshot here <https://prnt.sc/138oacn>and below. >>>>> >>>>> [image: image.png] >>>>> Hope you can enlighten me on this as i have used the latest flashrom >>>>> version. Thank you! >>>>> >>>>> _______________________________________________ >>>> flashrom mailing list -- flashrom(a)flashrom.org >>>> To unsubscribe send an email to flashrom-leave(a)flashrom.org >>>> >>> >>> >>> -- >>> Best regards, Mike Banon >>> Open Source Community Manager of 3mdeb - https://3mdeb.com/ >>> >> -- Best regards, Mike Banon Open Source Community Manager of 3mdeb - https://3mdeb.com/

1 0

MX25L6473E FAIL
by Andreas Lutz 01 Jun '21

01 Jun '21

Hi ROM flashers, I came accross some issue when trying to flash a BIOS image to MX25L6473E I can think of some unlock fail find attached no datasheet here is the dump Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Macronix flash chip "MX25L6405" (8192 kB, SPI) on ch341a_spi. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on ch341a_spi. Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on ch341a_spi. Found Macronix flash chip "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" (8192 kB, SPI) on ch341a_spi. Multiple flash chip definitions match the detected chip(s): "MX25L6405", "MX25L6405D", "MX25L6406E/MX25L6408E", "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" Please specify which chip definition to use with the -c <chipname> option. scorpion@scorpion-ThinkCentre-Edge72:~/Downloads$ sudo flashrom --programmer ch341a_spi -c MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F -w Z170HD3P.22g flashrom v1.2 on Linux 5.8.0-53-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 "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" (8192 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x62835a 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! let me know if you want me to try something Cheers Andreas

1 0

Difficulty installing libreboot with flashrom v.1.2 on a green ch341a programmer.
by keizerrijk 01 Jun '21

01 Jun '21

Hi, I'm attempting to install libreboot on my thinkpad x200 (soic16) with a green ch341a programmer. The reading of the flash chip works fine, but when attempting to write to the flash chip, it fails and spits out these errors: https://pastebin.com/G17JWGfQ Hoping for any help on what's going wrong. I've checked the connections are right. Thanks in advance!

2 1

Re: Your flash chip is in an unknown state
by Hermann Thomas A. Calero 01 Jun '21

01 Jun '21

Any reason for this? Any guidance will be greatly appreciated. On Fri, May 21, 2021 at 4:33 PM Hermann Thomas A. Calero < hermanncalero(a)gmail.com> wrote: > Hello, > > I tried to change the flash chip of my old Toshiba satellite pro a50 a > series with previous bios chip Winbond 25Q64CVSIG with a new Winbond > 25Q64FWSIG and i am getting the error "No usable erase functions left. > FAILED! > Uh oh. Erase/write failed. Checking if anything has changed. > Reading current flash chip contents... done. > Apparently at least some data has changed. > Your flash chip is in an unknown state. > Please report this on IRC at chat.freenode.net (channel #flashrom) or > mail flashrom(a)flashrom.org, thanks!" > > Error screenshot here <https://prnt.sc/138oacn>and below. > > [image: image.png] > Hope you can enlighten me on this as i have used the latest flashrom > version. Thank you! > >

2 1

[PATCH] add AT25DF041B to flash chip list
by Oleg Endo 29 May '21

29 May '21

Hi, The following patch adds the AT25DF041B to the flash chip list. It's copy-pasta from the definition of AT25DF041A for the most part. Please CC me in replies as I'm not subscribed to the list. Cheers, Oleg Change-Id: If0b4adeb963330614eec407687e1189aacc010fb Signed-off-by: Oleg Endo <olegendo(a)gcc.gnu.org> --- flashchips.c | 38 ++++++++++++++++++++++++++++++++++++++ flashchips.h | 1 + 2 files changed, 39 insertions(+) diff --git a/flashchips.c b/flashchips.c index 007bcc9..56d25eb 100644 --- a/flashchips.c +++ b/flashchips.c @@ -1598,6 +1598,44 @@ const struct flashchip flashchips[] = { .voltage = {2700, 3600}, /* 2.3-3.6V & 2.7-3.6V models available */ }, + { + .vendor = "Atmel", + .name = "AT25DF041B", + .bustype = BUS_SPI, + .manufacture_id = ATMEL_ID, + .model_id = ATMEL_AT25DF041B, + .total_size = 512, + .page_size = 256, + .feature_bits = FEATURE_WRSR_WREN, + .tested = TEST_OK_PREW, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 128} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 16} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 8} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {512 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {512 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_at25df, + .unlock = spi_disable_blockprotect_at2x_global_unprotect, + .write = spi_chip_write_256, + .read = spi_chip_read, + .voltage = {1650, 3600}, + }, + { .vendor = "Atmel", .name = "AT25DF081", diff --git a/flashchips.h b/flashchips.h index b6b75c8..d9b964c 100644 --- a/flashchips.h +++ b/flashchips.h @@ -130,6 +130,7 @@ #define ATMEL_AT25DF021 0x4300 #define ATMEL_AT25DF021A 0x4301 #define ATMEL_AT25DF041A 0x4401 +#define ATMEL_AT25DF041B 0x4402 #define ATMEL_AT25DF081 0x4502 /* EDI 0x00. AT25DL081 has same ID + EDI 0x0100 */ #define ATMEL_AT25DF081A 0x4501 /* Yes, 81A has a lower number than 81 */ #define ATMEL_AT25DF161 0x4602 -- 2.26.3

1 0

Re: [coreboot] Re: What should we do about freenode IRC services?
by Carl-Daniel Hailfinger 27 May '21

27 May '21

Am 27.05.21 um 11:22 schrieb Urja Rannikko: >>> Currently, on libera there are 46 people and on OFTC 2 people (me included). >>> >>> So I would say let's move to libera. >> Agreed. Let’s do what most members in #coreboot users already did. > +1 > > I know I'm not a regular contributor or anything, but fwiw currently > the only channels keeping me connected to freenode are #coreboot and > #flashrom (I assume flashrom will just tag along where coreboot goes), > so .. let's go, we've watched this long enough. The shipped flashrom binaries, the man page and the README mention IRC directly. I think we should start with pointing users to a flashrom.org web page instead of mentioning IRC in case another move (Matrix, IRC, Discord, whatever) is needed or desired. Once such a patch is committed, we would have to get all the distribution packages updated to point to the new location. Doable, but it's a lot of work. Regards, Carl-Daniel

1 0

Unknown Chip -VV Output
by Trent Strous 26 May '21

26 May '21

~$ sudo flashrom -VV --programmer ch341a_spi flashrom v1.2 on Linux 5.8.0-53-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.6.4, GCC 9.2.1 20200304, little endian Command line (3 args): flashrom -VV --programmer ch341a_spi Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing ch341a_spi programmer Device revision is 3.0.4 The following protocols are supported: SPI. Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF021A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 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: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25SF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25SF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25SF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25SF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25SL128A, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESI ES25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESI ES25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESI ES25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25B128B/GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ128C/GD25LQ128D, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ64(B), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q127C/GD25Q128C, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q256D, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ16C, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ21B, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ40C, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ41B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ80C, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25LP064, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25LP128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25LP256, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25WP032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25WP064, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25WP128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25WP256, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L25635F/MX25L25645G, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25R6435F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U25635F, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U51245G, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U8032E, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX66L51235F/MX25L51245G, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 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 0x20, id2 0x7017 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 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 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 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 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 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q00A..1G, 131072 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q00A..3G, 131072 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q256..1E, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q256..3E, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q512..1G, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q512..3G, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QL01G, 131072 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QU01G, 131072 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QL02G, 262144 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QU02G, 262144 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QU128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QL128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QL256, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QU256, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QL512, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron MT25QU512, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ032C, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF020A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST26VF016B(A), 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST26VF032B(A), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST26VF064B(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ST M95M02, 256 kB: probe_spi_st95: id1 0xff, id2 0xffff Probing for Sanyo LE25FU106B, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU206, 256 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU206A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL256S......0, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL512S, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q128.V..M, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q128.W, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q128.JW.DTR, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q256.V, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q256JV_M, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q40BW, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q40EW, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q80BW, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q80EW, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Zetta Device ZD25D20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Zetta Device ZD25D40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 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 8192 kB. Block eraser 0: 2048 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 2048 x 4096 B with opcode 0x20. Block eraser 1: 256 x 32768 B with opcode 0x52 Block eraser 2: 128 x 65536 B with opcode 0xd8 done. SFDP parameter table header 1/1: ID 0x20, version 1.0 Length 16 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" (8192 kB, SPI) on ch341a_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x20, id2 0x16 Found Unknown flash chip "SFDP-capable chip" (8192 kB, SPI). No operations were specified.

1 0

Fwd: Your flash chip is in an unknown state
by Hermann Thomas A. Calero 23 May '21

23 May '21

---------- Forwarded message --------- From: Hermann Thomas A. Calero <hermanncalero(a)gmail.com> Date: Fri, May 21, 2021 at 4:33 PM Subject: Your flash chip is in an unknown state To: <flashrom(a)flashrom.org> Hello, I tried to change the flash chip of my old Toshiba satellite pro a50 a series with previous bios chip Winbond 25Q64CVSIG with a new Winbond 25Q64FWSIG and i am getting the error "No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has changed. Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks!" Error screenshot here <https://prnt.sc/138oacn>and below. [image: image.png] Hope you can enlighten me on this as i have used the latest flashrom version. Thank you!

1 0

Exit the flashrom program on my aorus b-450m
by Romualdo Moraes Neto 23 May '21

23 May '21

"Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x61 does not match known values." Thanks -- *Conhecimento não tem dono. É patrimônio de toda a humanidade. Assim como o GNU/Linux.* “*Os idiotas vão tomar conta do mundo; não pela capacidade, mas pela quantidade. Eles são muitos*”. *Nelson Rodrigues*

1 0

Attempting to Flash Dell T620 BIOS
by Eric W. Hebert 21 May '21

21 May '21

Hi, hoping to get some help on this as I believe the BIOS is the issue on this box. I am able to see and pull down a copy of the existing code but I cannot write back as it says it is unable to unset the lock bits. I see in the documentation for the chip that it expects manipulation of the CS pin which I do not know if that is occurring but it is wired (when not wired it will not detect the chip). Chip is AT25DF641-S3H Using a Raspberry Pi (Original) with a stand-alone DC power supply to power the chip, requiring 3.5V or is not seen. Last portion of the log: Found Atmel flash chip "AT25DF641(A)" (8192 kB, SPI). Ignoring security lockdown (if present) Some block protection in effect, disabling... Need to disable the register lock first... Unsetting lock bit(s) failed. Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x00000fff: 0xb4 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 1... 0x000000-0x007fff:S, 0x008000-0x00ffff:S, 0x010000-0x017fff:EFAILED at 0x00010000! Expected=0xff, Found=0x20, failed byte count from 0x00010000-0x00017fff: 0xa5 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: 0xb6 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: 0x3f606d 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: 0x3f2b1c ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 5... not defined. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has changed. Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! Thank you, Eric

1 0

Fwd: Dell 3100 Chromebook
by Tim Tech 20 May '21

20 May '21

---------- Forwarded message --------- From: Tim Tech <agitimtim(a)gmail.com> Date: Thu, May 20, 2021 at 12:07 PM Subject: Re: [flashrom] Dell 3100 Chromebook To: Mike Banon <mikebdp2(a)gmail.com> The flashing setup seems to work fine with any other chip. The chip in question is a Winbond 25Q128FWPF. This chip is on the Dell 3100 and HP 11 G6 EE chromebooks and is the only chip we've had an issue with so far. I attached an image of the chip itself, in case there is any other info on there you need. I don't see this chip on the supported hardware, so maybe it is not yet supported? Thank you for any help Tim On Mon, May 17, 2021 at 1:17 PM Mike Banon <mikebdp2(a)gmail.com> wrote: > Are you doing the ISP (In-System Programming) ? Maybe there are > problems with the reliability of your flashing setup (i.e. too long > wires between a programmer and test clip) > > On Thu, May 13, 2021 at 2:39 AM Tim Tech <agitimtim(a)gmail.com> wrote: > > > > Are you able to help with the following issue? Thank you > > > > Calibrating delay loop... OK. > > Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, > SPI) on ch341a_spi. > > > > 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! > > Read is not working on this chip. Aborting. > > _______________________________________________ > > flashrom mailing list -- flashrom(a)flashrom.org > > To unsubscribe send an email to flashrom-leave(a)flashrom.org > > > > -- > Best regards, Mike Banon > Open Source Community Manager of 3mdeb - https://3mdeb.com/ >

1 0

Dell 3100 Chromebook
by Tim Tech 17 May '21

17 May '21

Are you able to help with the following issue? Thank you *Calibrating delay loop... OK.Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on ch341a_spi.* *This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITEThe test status of this chip may have been updated in the latest developmentversion of flashrom. If you are running the latest development version,please email a report to flashrom(a)flashrom.org <flashrom(a)flashrom.org> if any of the above operationswork correctly for you with this flash chip. Please include the flashrom logfile for all operations you tested (see the man page for details), and mentionwhich mainboard or programmer you tested in the subject line.Thanks for your help!Read is not working on this chip. Aborting.*

2 1

Minor Git hickup
by Nico Huber 13 May '21

13 May '21

Hi flashrom folks, we just had a minor accident on the master branch (a commit went around our review system). You may or may not have seen these two commits during the last hour: a2b33b9 Revert "Add Gemini Lake support" 36c401d Add Gemini Lake support They should be gone now. Nico

1 0

Found unknown SPI flash chip
by Kratzmann, Jakob 11 May '21

11 May '21

Hello flashrom team, I have detected an unknown SPI flash chip. The output of the command `flashrom -VV -p linux_spi:dev=/dev/spidev0.0,spispeed=512` can be found in the attachment. I am using a Raspberry Pi 2 B+ with flashrom on Linux 5.10.17-v7+ (armv7l). XMC 0H128AHIG P1W93800 is written on the SPI chip. Please do not hesitate to contact me if you have any further questions. Best regards Jakob Kratzmann

1 0

Chipset: Intel Comet Lake U Premium Acer KLED board
by Robert Whigham 23 Apr '21

23 Apr '21

flashrom command returns Found chipset "Intel Cometlake" Warning: unexpected second chipset match: "Intel Comet Lake U Premium"

2 1

No EEPROM/flash device found - Error log
by sven.reischauer＠googlemail.com 17 Apr '21

17 Apr '21

Dear flashrom.org attached you'll find the error log of my failed attempt to hook up flashrom with my board (AsRock Fatal1ty X370 Gaming-ITX/ac) No EEPROM/flash device found. hope this helps! Sven

1 0

xmc-qh128ahig
by Patryk P 09 Apr '21

09 Apr '21

3 4

info log for unknown chip XMC_QH64AH16
by Winfried Kybelka 08 Apr '21

08 Apr '21

hi programmer i have att log. Thanks for your work W. Kybelka

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom