flashrom July 2018

flashrom@flashrom.org

18 participants
23 discussions

test results for -p nic3com -c Am29F010A/B
by Sergei Antonov 18 Jul '18

18 Jul '18

Hello! Since Am29F010A/B flash part has status UNTESTED, I'm sending test results. Erase, probe, read, and write work. Logs are attached.

1 0

Report ThinkPad L520
by HacKurx 17 Jul '18

17 Jul '18

flashrom v0.9.9-r1954 on Linux 4.13.0-36-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.3.1, GCC 5.3.1 20160424, little endian Command line (5 args): flashrom -p internal:laptop=force_I_want_a_brick -r backup.rom -V Calibrating delay loop... OS timer resolution is 1 usecs, 1595M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus = 10007 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Notebook" Laptop detected via DMI. DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "5015AH2" DMI string system-version: "ThinkPad L520" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "5015AH2" DMI string baseboard-version: "Not Available" W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 85. Found ITE EC, ID 0x8518, Rev 0x02 on port 0x2e. Found chipset "Intel HM65" with PCI ID 8086:1c49. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Root Complex Register Block address = 0xfed1c000 GCS = 0xc20: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x3 (SPI) Top Swap: enabled (A16(+) inverted) 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x0 0xffe00000/0xffa00000 FWH IDSEL: 0x0 0xffd80000/0xff980000 FWH IDSEL: 0x0 0xffd00000/0xff900000 FWH IDSEL: 0x0 0xffc80000/0xff880000 FWH IDSEL: 0x0 0xffc00000/0xff800000 FWH IDSEL: 0x0 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x400000 bytes SPI Read Configuration: prefetching disabled, caching enabled, BIOS_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled SPIBAR = 0x00007fa9c6c64000 + 0x3800 0x04: 0xe008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 Reading OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x50: 0x00000a0b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x0a, BRRA 0x0b 0x54: 0x00000000 0x58: 0x03ff0180 FREG1: BIOS region (0x00180000-0x003fffff) is read-write. 0x5C: 0x017f0001 0x74: 0x9fff03b0 Writes have been disabled for safety reasons. You can enforce write support with the ich_spi_force programmer option, but you will most likely harm your hardware! If you force flashrom you will get no support if something breaks. On a few mainboards it is possible to enable write access by setting a jumper (see its documentation or the board itself). 0x90: 0xc4 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf84140 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=1, SME=0, SCF=0 0x94: 0x0606 (PREOP) 0x96: 0x163b (OPTYPE) 0x98: 0x05200302 (OPMENU) 0x9C: 0x0001c790 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00802005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20 0xD0: 0x00000000 (FPB) OK. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L05PU, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L10PT, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L10PU, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L20PT, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L20PU, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L40PT, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L40PU, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L80P, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L16PT, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L16PU, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L512, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L010, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L020, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L080, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L016, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L032, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25LQ16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25LQ64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF021, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF041A, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF081, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF081A, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF161, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF321, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF321A, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF641(A), 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DL081, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DL161, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DQ161, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25F512, 64 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F512A, 64 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F512B, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25F1024(A), 128 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F2048, 256 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F4096, 512 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25FS010, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25FS040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26DF041, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26DF081A, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26DF161, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26DF161A, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26F004, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45CS1282, 16896 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB011D, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB021D, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB041D, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB081D, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB161D, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB321C, 4224 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB321D, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB321E, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB642D, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for ESMT F25L008A, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for ESMT F25L32PA, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B05, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B05T, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25P05, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B10T, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25P10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B20T, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25P20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B40T, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25P40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B80T, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25P80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B16T, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25P16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B32T, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25P32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B64T, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25P64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F05, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q80(A), 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q32(A/B), 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q128, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25QH16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25QH32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25QH64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25QH128, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for ESI ES25P40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for ESI ES25P80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for ESI ES25P16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25LQ40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25LQ80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25LQ16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25LQ32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25LQ64(B), 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25LQ128, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q512, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q20(B), 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q40(B), 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q80(B), 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q16(B), 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q32(B), 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q64(B), 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q128B, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q128C, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25T80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25VQ21B, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25VQ40C, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25VQ41B, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25VQ80C, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25VQ16C, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F160S33B8, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F160S33T8, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F320S33B8, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F320S33T8, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F640S33B8, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F640S33T8, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX23L1654, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX23L3254, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX23L6454, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX23L12854, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1605, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1635D, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1635E, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3205(A), 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3273E, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3235D, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L6405, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L6405D, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L12805D, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25U1635E, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25U3235E/F, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25U6435E/F, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25U12835F, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L6495F, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P05-A, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P05, 64 kB: Invalid OPCODE 0x9f, will not execute. Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P10, 128 kB: Invalid OPCODE 0x9f, will not execute. Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Invalid OPCODE 0x9f, will not execute. Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Invalid OPCODE 0x9f, will not execute. Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P128, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PX80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PX16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PX32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PX64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q016, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD256C, 32 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD512(C), 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD010(C), 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD020(C), 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD040(C), 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LQ020, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LQ040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LQ080, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LQ016, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LQ032C, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV512(A), 64 kB: Invalid OPCODE 0xab, will not execute. Probing for PMC Pm25LV010, 128 kB: Invalid OPCODE 0xab, will not execute. Probing for PMC Pm25LV010A, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV020, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV080B, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV016B, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo LE25FW106, 128 kB: Invalid OPCODE 0xab, will not execute. Probing for Sanyo LE25FW406A, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for Sanyo LE25FU406B, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo LE25FW203A, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo LE25FW403A, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo LE25FW418A, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for Sanyo LE25FW806, 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for Sanyo LE25FW808, 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for Spansion S25FL004A, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL008A, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL016A, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL032A/P, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL064A/P, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL204K, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL208K, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL116K/S25FL216K, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL132K, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL164K, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL127S-64kB, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL127S-256kB, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL128P......0, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL128P......1, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL128S......0, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL128S......1, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL129P......0, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL129P......1, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25LF040A, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25LF080(A), 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25VF020B, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25VF040B, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25WF020A, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF040B, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF080B, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF080B, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF016B, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF032B, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF064C, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF512, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF010, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF020, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF080, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q40.V, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q80.V, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q16.V, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q32.V, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q64.V, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q128.V, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q20.W, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q40.W, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q80.W, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q16.W, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q32.W, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q64.W, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Unknown SFDP-capable chip, 0 kB: Invalid OPCODE 0x5a, will not execute. Receiving SFDP signature failed. Probing for AMIC unknown AMIC SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel unknown Atmel SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon unknown Eon SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix unknown Macronix SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC unknown PMC SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST unknown SST SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for ST unknown ST SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo unknown Sanyo SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Generic unknown SPI chip (RDID), 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef, id2 0x15 Found Generic flash chip "unknown SPI chip (REMS)" (0 kB, SPI) mapped at physical address 0x0000000000000000. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x80, id2 0x7d, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x80, id2 0x7d, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x80, id2 0x7d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x3b, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x80, id2 0x7d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x80, id2 0x7d, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, 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 0x57, id2 0xf9, id1 is normal flash content, id2 is normal flash content Found Generic flash chip "unknown SPI chip (REMS)" (0 kB, 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! Restoring MMIO space at 0x7fa9c6c678a0 Restoring PCI config space for 00:1f:0 reg 0xdc -- Best regards, HacKurx (Loic)

1 0

Test results for -p nic3com -c Am29F010A/B
by Sergei Antonov 16 Jul '18

16 Jul '18

Hello! Since Am29F010A/B flash part has status UNTESTED, I'm sending test results. Erase, probe, read, and write work. Logs are attached.

1 0

Test-Results for EN25S40 -> All ok.
by The_Raven Raven 13 Jul '18

13 Jul '18

Hi Tested Chip "EN25S40": Everything works like it should. PROBE READ ERASE WRITE -> All ok. Logs are attached. Greets

1 0

MX25L6473F Bios
by B. Ford 13 Jul '18

13 Jul '18

Hi I am trying to read a MX25L6473F bios chip, it is in your supported list of chips. However when i read the chip (ch341a programmer) it asks to specify the chip type using the -c command, but the MX25L6473F is not in the selected ones, and therfore i cannot continue to read.. i see that the current revision on Ubuntu / Kali is 0.9.9, can you help me out, it would be greatly appreciated. and thanks for developing such a powerfull software. Kind Regards

1 0

FAILED: grunt
by Charles Marslett 12 Jul '18

12 Jul '18

Hi folks, I have, for the first time ever, tried to flash the EC firmware on a Google Grunt EVT platform. I have succeeded in the past flashing the coreboot image but the command sequence to flash the EC is somewhat different. Here is the output I see: (cr) ((8ccc569...)) cmarslett@5000G ~/trunk/src/scripts $ ../platform/ec/util/flash_ec --board=grunt --image=../../grunt-build/ec.bin INFO: Using servo_micro. INFO: Using ec image : ../../grunt-build/ec.bin INFO: Flashing chip npcx_spi. 1+0 records in 1+0 records out 16252928 bytes (16 MB, 16 MiB) copied, 0.0563104 s, 289 MB/s flashrom v0.9.9 : 622128c : Jul 05 2018 14:19:12 UTC on Linux 4.15.0-24-generic (x86_64) Calibrating delay loop... OK. Raiden: Serial number SNCQ01007 matched device bus=0x02,address=0x05 | Servo Micro Erasing and writing flash chip... Verifying flash... VERIFY FAILED at 0x00000000! Expected=0x5e, Read=0xff, failed byte count from 0x00000000-0x00ffffff: 0xc32c8 Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! FAILED INFO: Restoring servo settings... I did not reboot or poweroff, but it did finally shut down (at least all the LEDs went off). What do you recommentd next? Thanks, Charles Marslett

2 2

Re: [flashrom] Why does the flash content differ
by microsoft gaofei 11 Jul '18

11 Jul '18

Is that possible to put a virus into another hardware rather than BIOS? Why do the controller and engine write to BIOS? <a href="mailto:flashrom%40flashrom.org?Subject=Re%3A%20%5Bflashrom%5D%20Why%20does%20the%20flash%20content%20differ&In-Reply-To=%3CMWHPR02MB2463DFBA2A682AD6C00B3E25D45A0%40MWHPR02MB2463.namprd02.prod.outlook.com%3E" title="[flashrom] Why does the flash content differ">wangziheng at outlook.com </a>

1 0

Re: [flashrom] Why does the flash content differ
by microsoft gaofei 11 Jul '18

11 Jul '18

Is that possible to put a virus into another hardware rather than BIOS?

1 0

Re: [flashrom] Why does the flash content differ
by David Hendricks 10 Jul '18

10 Jul '18

On Mon, Jul 9, 2018 at 6:37 PM, microsoft gaofei <wangziheng(a)outlook.com> wrote: > The commands are just the following: > sudo flashrom -w newbios --programmer internal > The operation is successful, BIOS content is replaced and the computer can > reboot successfully. > sudo flashrom -r compare --programmer internal > I later checked their SHA256 and found they’re different. So what happened? > Did the internal programmer modify the content? It's likely that something else wrote to the ROM (management engine, embedded controller, BIOS, etc), especially during after doing a reboot cycle.

1 0

Re: [flashrom] Why does the flash content differ
by microsoft gaofei 10 Jul '18

10 Jul '18

Sorry, it probably isn’t flashrom problem. Some mainboards like ASUS put the debug information into the chip. To ensure that nothing is wrong, using an external programmer may be better.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom July 2018