- flashrom - mail.coreboot.org

PATCH: Adding support for Sanyo "LE25FU206"
by The_Raven Raven 27 Feb '18

27 Feb '18

Hi I made a Patch for adding Sanyo "LE25FU206" Chip. Tested (with raspberrypi-linux_spi): - Probing - Reading (i readed the chip 3 times and make a diff, all diffs are same) - Erasing (tested all 3 erase-modes) - Writing data1 - Writing data2 (overwriting) Greets

1 0

Add support new hardware
by Алексей Болдырев 27 Feb '18

27 Feb '18

Please add support from: EC ITE IT8586E-LQFP

1 0

Trying to dump the contents of a Micron 25Q064A
by Tim Elliott 26 Feb '18

26 Feb '18

I have my SPI flash chip connected to a logic level shifter and that connected to a raspberry pi. I am running flashrom and it will find an "unknown SPI chip (RDID) (0KB, SPI)". It says that "the flash part has status NOT WORKING" for operations: PROBE READ ERASE WRITE". Is that normal that it can talk to it but can't read the contents? Thanks

1 0

Re: [flashrom] BIOS flashing on debian stretch PC HP Pavilion t817.fr
by Nico Huber 25 Feb '18

25 Feb '18

Hello Bruno, On 21.02.2018 03:42, Bruno Doutriaux - ABCD Informatique wrote: > hello, > I tried using flashrom 0.9.9 on debian stretch i686 > i typed flashrom --programmer internal -r out.rom > then the same but with -w 315.rom > but they both failed > ------------------ > output: found winbond super i/o id 0x60 > and chipset via vt8237(r) > enabling flash write ok > no eeprom/flash device found > note: flashrom can never write if the flashchip isn't found automatically > ----------------- I'm afraid this is not enough information to say anything. Though, I suspect that flashrom just doesn't know your chip (yet). Please capture a verbose log (just `flashrom -p internal -o logfile.txt`) and report back. > it's an old hp pc > pavilion t817.fr > i have the new rom file > motherboard is an asus a7v8x-LA > firefox won't let me access https://paste.flashrom.org Yes, that often makes trouble (the website is sometimes misconfigured and Firefox, like most other browsers, is broken regarding reasonable TLS security anyway). Please use another paste service, or just attach your log to an email. Nico

2 1

BIOS flashing on debian stretch PC HP Pavilion t817.fr
by Bruno Doutriaux - ABCD Informatique 21 Feb '18

21 Feb '18

hello, I tried using flashrom 0.9.9 on debian stretch i686 i typed flashrom --programmer internal -r out.rom then the same but with -w 315.rom but they both failed ------------------ output: found winbond super i/o id 0x60 and chipset via vt8237(r) enabling flash write ok no eeprom/flash device found note: flashrom can never write if the flashchip isn't found automatically ----------------- it's an old hp pc pavilion t817.fr i have the new rom file motherboard is an asus a7v8x-LA firefox won't let me access https://paste.flashrom.org Cordialement, ----------------------------- Bruno DOUTRIAUX Ligne Domicile: 03 27 40 22 66 Mobile: 06 61 17 38 95<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table style="border-top: 1px solid #D3D4DE;"> <tr> <td style="width: 55px; padding-top: 18px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-anima…" alt="" width="46" height="29" style="width: 46px; height: 29px;" /></a></td> <td style="width: 470px; padding-top: 17px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Garanti sans virus. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…" target="_blank" style="color: #4453ea;">www.avast.com</a> </td> </tr> </table> <a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>

1 0

ACER C720 chromebook (Peppy) / Warning: Management Engine region (0x00001000-0x001fffff) is locked /
by Robert Rimke 17 Feb '18

17 Feb '18

Dear John, Thanks for your great intitiative which allows us freeing our chromebooks from GoogleOS :-) Highly appreciated. When flashing my peppy chromebook to the latest coreboot-peppy version today, I can observe that flashrom complains about something like an incomplete flash operation due to Intel ME. Are you aware if my peppy will survive the following command, which - if I understood correctly - will try to force the update? sudo flashrom -w coreboot-peppy-seabios-latest.rom -V -f -p ich_spi Below you will find verbose log from the last flash operation. Best regards Robert --- robert@C720 ~/Downloads $ sudo flashrom -w coreboot-peppy-seabios-latest.rom -p internal -V flashrom v0.9.9-rc1-r1942 on Linux 4.13.0-32-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 20160225, little endian Command line (5 args): flashrom -w coreboot-peppy-seabios-latest.rom -p internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 1395M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1003 us, 10000 myus = 10017 us, 4 myus = 4 us, OK. Initializing internal programmer Found candidate at: 00000500-00000510 Found coreboot table at 0x00000500. Found candidate at: 00000000-00000194 Found coreboot table at 0x00000000. coreboot table found at 0x7becf000. coreboot header(24) checksum: 1d58 table(404) checksum: 4f5c entries: 10 Vendor ID: GOOGLE, part ID: Peppy Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "GOOGLE" DMI string system-product-name: "Peppy" DMI string system-version: "1.0" DMI string baseboard-manufacturer: "GOOGLE" DMI string baseboard-product-name: "Peppy" DMI string baseboard-version: "1.0" Found chipset "Intel Lynx Point LP Mainstream" with PCI ID 8086:9c45. 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 = 0x21: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x0 (SPI) Top Swap: enabled (A16(+) inverted) 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 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: 0x100000 bytes SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x09: BIOS Lock Enable: disabled, BIOS Write Enable: enabled SPIBAR = 0x00007f6e33a9b000 + 0x3800 0x04: 0xe008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 Warning: SPI Configuration Lockdown activated. Reading OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x50: 0x00004a4b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x4a, BRRA 0x4b 0x54: 0x00000000 FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x07ff0200 FREG1: BIOS region (0x00200000-0x007fffff) is read-write. 0x5C: 0x01ff0001 FREG2: Warning: Management Engine region (0x00001000-0x001fffff) is locked. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME for details. 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: 0x84 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf97f20 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=2, DBC=63, SME=0, SCF=1 0x94: 0x5006 (PREOP) 0x96: 0xb32d (OPTYPE) 0x98: 0x05030201 (OPMENU) 0x9C: 0x0bd89f20 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x80000000 (LVSCC) LVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=0 0xC8: 0x00000000 (UVSCC) UVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0 0xD0: 0x50444653 (FPB) OK. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 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: probe_spi_rdid_generic: id1 0xef, id2 0x4017 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: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ESI ES25P40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ESI ES25P80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ESI ES25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ64(B), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q128C, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25VQ41B, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ032C, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 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: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 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: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 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: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25LF020A, 256 kB: Invalid OPCODE 0x90, will not execute. 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: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF010(A), 128 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF020, 256 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF040, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF040B.REMS, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25WF020A, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF040B, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Chip status register is 0x00. Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 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: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Generic unknown SPI chip (REMS), 0 kB: Invalid OPCODE 0x90, will not execute. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0x49, 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 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 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 0xe6, id2 0xab, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0x49, 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 Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xe6, id2 0xab, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0x49, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x89, id2 0xe1, 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 0xe6, id2 0xab, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xe6, id2 0xab, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x65, id2 0xcd, id1 parity violation, 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 0xe6, id2 0xab, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xe6, id2 0xab, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0x49, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x65, id2 0xcd, id1 parity violation, 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 0xe6, id2 0xab, 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 W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 0x49, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xe6, id2 0xab, 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 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). Write/erase is not working yet on your programmer in its current configuration. Aborting. Restoring MMIO space at 0x7f6e33a9e8a0

2 1

Dos Build of flashrom 1.0 unsuccessful
by Rahngue NGARIERA 14 Feb '18

14 Feb '18

I'm trying to build flashrom 1.0 for Dos on Ubuntu. But I'm still failing. At first, I was having problems at the Checking for libpci/libz step. Despite all the changes I made to the makefile, I always ended up with Not sufficient. Then I commented that part out. Because all my library files (libpci, libz, libgetopt, librt,...) are in the lib/ folder of my LIBS_BASE (../libpci) which has the same parent folder as flashrom directory. I followed the instructions of the README. For compiling pciutils, the instructions say to apply the pciutils.gz.patch I don't know if I got that part right. I just copy-pasted the file inside pciutils.gz.patch into pciutils/ Then went on to compile pciutils, libz and libgetopt. And I copied all the necessary header and library files into libpci/. After commenting out the part that checks libpci, I then had to comment out the real time clock test portion of makefile as well, because it was always returning Not found. Compilation now proceeded but ended with errors, many undefined references. All having to do with pci. I'm looking forward to ur advices. Etonam

1 0

Re: [flashrom] Help required for GD25LB64C
by Nico Huber 12 Feb '18

12 Feb '18

On 11.02.2018 12:53, CyberPK wrote: > Thank you for the reply. You are true, it only takes a lot of time. Good to hear it's working. > > Finally I've used the older flashrom 0.9.7 successfully. > I've noticed that using this version with -VVV flags give me a feedback of > the progresses printing 'pickit2_spi_send_command' > > Also, there is a way to use flashrom to read the OTP and write it to a new > flash? No. > > It's a GD25LB64C, cannot find its datasheet but has the same id of the > supported GD25LB64C Same here. Only clue I could find was a product list from GigaDevice [1]. No datasheet though, and their webpage also doesn't find it. At least, in that list, the GD25LB64C and GD25LQ64C have the same voltage and erase block organization. So they might be compatible indeed (some vendors release incompatible chips with the same id...). Nico [1] "https://www.endrich.com/fm/2474/GIGADEVICE - SPI NOR FLASH PRODUCT LIST.pdf" PS. You dropped the mailing list, please keep it always in CC.

1 1

Try to add support for "MX25U4032E" chip
by The_Raven Raven 12 Feb '18

12 Feb '18

Hi I have two of these chips (found on a HDD) and try to add it to flashrom. My "problem" is the device id. It says: id1 0x40, id2 0x11 This looks very strange to me, because normally it should look something like this: Ex: "MX25U8032E" -> id1 0xc2, id2 0x2534 Any idea why i get this "strange" ID?

1 0

Re: [flashrom] Help required for GD25LB64C
by Nico Huber 11 Feb '18

11 Feb '18

Hello CyberPK, On 11.02.2018 02:37, CyberPK wrote: > Hello, I'm trying to read and write the flash memory into a GD25LB64C which > is automatically recognized as GD25LQ64C. Did it really say GD25LQ64C? I could only find an entry for GD25LQ64(B), wondering what version of flashrom you are using. > I'm using a pickit2 setting 1.8V and flashrom 1.0 compiled from source > release. > I'm using the -VVV flag, but the read process remains stuck in reading and > the writing process remains stuck in "reading old flash chip contents". > I've also tried to erase the content using the -E flag in addition to the > verbose -VVV flag and I can see the slow advancements through the > addresses appearing to n the screen. > But I'm still unable to read or write. What I can do? Any idea? You probably just need more patience. Reading has no progress indication (because most programmers are fast). Maybe the pickit is just slow. Nico

1 0

Help required for GD25LB64C
by CyberPK 11 Feb '18

11 Feb '18

Hello, I'm trying to read and write the flash memory into a GD25LB64C which is automatically recognized as GD25LQ64C. I'm using a pickit2 setting 1.8V and flashrom 1.0 compiled from source release. I'm using the -VVV flag, but the read process remains stuck in reading and the writing process remains stuck in "reading old flash chip contents". I've also tried to erase the content using the -E flag in addition to the verbose -VVV flag and I can see the slow advancements through the addresses appearing to n the screen. But I'm still unable to read or write. What I can do? Any idea? Regards

1 0

Re: [flashrom] CrOS flashrom compatibility and upstreaming of CrOS features
by Nico Huber 08 Feb '18

08 Feb '18

Hi David, sorry for taking that long. I guess I was waiting for more people to chime in (I'll still not abandon that hope, generally). On 25.01.2018 08:12, David Hendricks wrote: > On Wed, Jan 24, 2018 at 10:36 AM, Nico Huber <nico.h(a)gmx.de> wrote: > >> Hey folks, >> >> during review of commits that port per-region file arguments [1] from >> CrOS flashrom over here, we ran into a discussion about the command line >> interface changes. The basic question that arose is >> >> Do we want to maintain full CLI compatibility to CrOS flashrom? >> >> This would have the upside, that it would ease remerging of the two >> flashrom versions (in some unknown future). And anybody currently >> using CrOS flashrom could transition more smoothly. OTOH, depending on >> how the compatibility is achieved, it might increase the costs for >> review and development heavily (for a project with 0 spare resources). >> >> To not have to discuss this each and every time when some non-trivial >> feature is ported over from CrOS, I'd like to have some opinions, how >> valuable CLI compatibility is to you all and how we want to achieve it. >> I have currently some alternative ideas in mind that I'll sketch below. >> Feel free to add other ideas or just to comment them. >> > > Option #2 seems pretty good IMHO. I suspect that CrOS will need to maintain > their legacy behavior for a while longer, but that does not need to hold > back upstream. We should of course improve our testing to avoid breaking > one or the other, at least without sufficient reason and time to adjust. Sounds good to me. Though for testing, we'd have to implement the CrOS compatible CLI rather sooner than later. > > Some background on this: CrOS currently maintains a separate CLI in their > tree, cli_mfg.c, specifically because the upstream CLI was not well-suited > for their manufacturing needs. Things like syntax changes, additional > options, verbosity, error handling, etc. were simply different from what > typical users expect. The partial read/write/verify syntax was developed to > meet specific needs of the manufacturing flow, and the write-protection > syntax was added specifically to address the way write-protection works on > Chromebooks. Stuff like "combining multiple files" was done to avoid > wasting valuable time on the assembly line and at runtime during normal OS > maintenance (yes, seconds really do matter). Hmmm, that valuable-time requirement is really something that would suffer with a wrapper script. So let's try to keep compatibility inter- nally. > > I'd still like to see CrOS converge with upstream so we share development > and testing efforts. It would also be great to have more device > manufacturers working with upstream. Having an alternate CLI coexist > alongside the "classic" CLI seems like a decent compromise IMO. Both sides > will benefit from a converged codebase, let's not make the CLI a blocking > issue. Agreed. Though, convergence will need effort on both sides... Nico

1 0

Adding support for "MX25U8032E"
by The_Raven Raven 05 Feb '18

05 Feb '18

Hi I made a Patch for adding "MX25U8032E" Chip. Hope the Patch is ok, i took the data from "MX25U1635E" and changed it to fit the "MX25U8032E". Tested (with arduino-serprog): - Probing - Reading (i readed the chip 3 times and make a diff, all diffs are same) - Erasing - Writing data1 - Writing data2 (overwriting) Important: The Vcc must be at max 2V, it does NOT work if Vcc is at 3.3V! This ends in read and write errors (data corruption)! Tested ;-) Greets

1 0

Pm25LD020(C) Chip tested -> OK
by The_Raven Raven 05 Feb '18

05 Feb '18

Hi I have tested Chip "Pm25LD020(C)" with Arduino (serprog). Chip works fine. Test Steps: - Readed - Erased - Written Data1 - Written Data2 (overwritten) Data1 and Data2 generated with "dd" from "/dev/urandom". Greets

1 0

Re: [flashrom] Github PRs
by Miklos Marton 03 Feb '18

03 Feb '18

Thank you for your answer David, I will follow your hint! Best regards, Miklos Marton 2018-01-30 22:54 keltezéssel, David Hendricks írta: > > Hi Miklos, > > Yes, coreboot's gerrit system is likely where the review will take > place. The github repository is a mirror of coreboot's flashrom > repository, however we recognize that a lot of people do development > on github so we work with pull requests as well. We also still have > patch submissions via e-mail. > > > You may receive comments to your pull request on github, however if > the patch is small enough (like PR33) then it might just be sent > directly to review.coreboot.org for final review before being merged > and ultimately mirrored in the github repo. > > > As usual the bottleneck is the amount of spare time reviewers have and > we've been juggling some large changes lately. We do appreciate the > contributions, and please feel free to nudge us if there is urgency or > if things simply linger for too long. > > ------------------------------------------------------------------------ > *From:* flashrom <flashrom-bounces(a)flashrom.org> on behalf of Miklos > Marton <martonmiklosqdev(a)gmail.com> > *Sent:* Tuesday, January 30, 2018 12:47:44 PM > *To:* flashrom > *Subject:* [flashrom] Github PRs > Hello flashrom developers! > > I have submitted two PRs to github (as the wiki mentions it is also a > possible contribution channel). > > Do I need to do anything else with that? I am not intended to seems to > be impatient I just would like to make sure that everything is in place > (this is my first contribution to flashrom this way). > > If I remember correctly the coreboot gerrit was used to do code review. > Is it going to be moved there or we will perform the code review at the > github? > > -- > Best regards, > Miklos Marton > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.coreboot.org_mail…

1 0

Re: [flashrom] Failed flash on Intel Bay Trail platform
by Quinn Plattel 03 Feb '18

03 Feb '18

Hi, I fixed the bad flash by using a Beaglebone Black and the OpenWRT screwdriver package (recommended by the coreboot project). Luckily, the board had pins directly to the flash via an SPI interface otherwise I might have had to use a Pomona clip. Quinn On 01/02/18 08:00, David Hendricks wrote: Hi Quinn, On Wed, Jan 31, 2018 at 5:01 AM, Quinn Plattel <q(a)bluetown.com<mailto:q@bluetown.com>> wrote: 13:56 < quinn> flashrom shows warning when reading or writing: BIOS region SMM protection is enabled! Did you have any luck with this? There might be a BIOS setting in the menu that allows you to disable the SMM lock, and as icon suggested on IRC the speed racer exploit might also be a feasible workaround. Another idea might be to try using coreboot on this board and simply not set the SMM lock bit until you need to do so ;-) There's a decent chance the Bayley Bay CRB implementation will work, though you may need to do some customization for your board: https://review.coreboot.org/cgit/coreboot.git/tree/src/mainboard/intel/bayl… Best regards, Quinn Plattel Senior Network Engineer - BLUETOWN +45 53 70 85 67 - q(a)bluetown.com - Skype ID: dalilai Per Henrik Lings Allé 4, 3rd Floor - 2100 Copenhagen O - DK - +45 31 66 00 07 - www.bluetown.com [https://i.imgur.com/ZPkPX8i.png]<https://www.youtube.com/watch?v=AqERoJFeQNU>

1 0

Failed flash on Intel Bay Trail platform
by Quinn Plattel 01 Feb '18

01 Feb '18

Hi, Just tried to contact you guys via irc chat. Here is the transcript: 13:47 -!- Irssi: Join to #flashrom was synced in 1 secs 13:47 < quinn> hello, need help with a failed flash on an Intel Bay Trail platform. 13:48 < quinn> Detected flash chip is Winbond W25Q64.W 8192 kB, SPI mapped at phy addr 0xff800000 13:50 < quinn> System is an industry pc with model LEC-3030T 13:51 < quinn> Bios made by Aptio. 13:52 < quinn> dmidecode says Vendor is AMI with bios version 5.6.5 and release date 05/05/2016 13:52 < quinn> BIOS revision 5.6 according to dmidecode 13:54 < quinn> Re-reading the flash results in same size rom file but filled with "ff". 13:55 < quinn> I have the original rom saved. 13:56 < quinn> flashrom shows warning when reading or writing: BIOS region SMM protection is enabled! 13:57 < quinn> flashrom version used is v0.9.9-rc1-r1942 Regards, Quinn Best regards, Quinn Plattel Senior Network Engineer - BLUETOWN +45 53 70 85 67 - q(a)bluetown.com - Skype ID: dalilai Per Henrik Lings Allé 4, 3rd Floor - 2100 Copenhagen O - DK - +45 31 66 00 07 - www.bluetown.com [https://i.imgur.com/ZPkPX8i.png]<https://www.youtube.com/watch?v=AqERoJFeQNU>

2 2

Github PRs
by Miklos Marton 30 Jan '18

30 Jan '18

Hello flashrom developers! I have submitted two PRs to github (as the wiki mentions it is also a possible contribution channel). Do I need to do anything else with that? I am not intended to seems to be impatient I just would like to make sure that everything is in place (this is my first contribution to flashrom this way). If I remember correctly the coreboot gerrit was used to do code review. Is it going to be moved there or we will perform the code review at the github? -- Best regards, Miklos Marton

2 1

What's the intended license for flashrom?
by Nico Huber 30 Jan '18

30 Jan '18

Hi folks, I've just noticed that most of flashrom is licensed under GPLv2 + any later version, while about a third of the code base is GPLv2 only. I wonder if that is intentional, or if any of the license headers was just copy pasted and spread too much? Does somebody know any previous discussion on the topic? Nico

3 4

new whitelists for thinkpad r400, t500
by Leah Rowe 28 Jan '18

28 Jan '18

Hi, Here are some patches for flashrom, which adds whitelist for: ThinkPad R400 ThinkPad T500 Also Taurinus X200, which is a version of the ThinkPad X200 with libreboot, with boardinfo modified slightly

1 0

x1 Carbon 1st Gen Boots to Black Screen
by realraw＠tuta.io 27 Jan '18

27 Jan '18

Followed the coreboot wiki entry perfectly, and had no issues reading the flash chip. The 4MB Bios chip in my x1 differs from the Wiki Entry: Found Micron/Numonyx/ST flash chip "N25Q032..3E" (4096 kB, SPI) on linux_spi. Not sure if that impacts anything, however booting I am faced with a Black Screen. Fan is not running at all, and appears nothing is happening. I found this link as well: http://coreboot.coreboot.narkive.com/zUOsG1zN/lenovo-x1-carbon-3460-screen-… Flashed the rom at the end of the suggested mailing list comment, and still black screen. I have included the vbios in my build, so I'm not sure what's wrong. -realraw

2 1

Re: [flashrom] ERASE FAILED on Macronix Bios Chip x220 (Expected 0xff, Found=0x5a)
by Nico Huber 27 Jan '18

27 Jan '18

Hi realraw, you dropped the mailing list in your reply; by accident, I assume. On 27.01.2018 11:01, realraw(a)tuta.io wrote: > The stock bios is currently set at 1.40 and I decided I was going to try > to update to the latest BIOS. However the stock BIOS update utility > does not work, and neither does the USB Bios Boot Utility. Now I see an > error pop up on boot saying, 'Intel ME is in Recovery Mode'. The ME is a microcontroller built into the chipset. You always have to assume that it's running while you flash externally, so it's not unlikely that it gets confused. > > I believe the BIOS has some sort of write protection on, that will not > allow me to erase the BIOS. Is there anything that can be done besides > physically removing the BIOS chip and swapping it for another? The BIOS has no means to control the flash chip, while the system is shut down. Removing the chip to flash, should always work, though. I don't see any reason to swap the chip. > > My setup is the Pomona SOIC 8 Pin clip, female to female jumpers and the > RPi3. I am SSHing into the Pi3 from my w530, and issuing the commands > through that. The RPi3 is connected via the standard power cable that > came with it, and the Thinkpad has Wake - On LAN enabled, but at this > point I believe the issue had to do with something other than my > equipment. Currently the BIOS is on version 1.40, and it was a custom > BIOS that had been floating around the internet. What I missed was what device you are trying to flash. I figured it now from the subject line. I little hidden, IMHO. You should always mention what you are trying to do in the email's body. I'm confident that your problem is not related to any write-protection (nobody else run into such issues with an X220, AFAIK). There are basi- cally two ways to flash an X220: 1. Remove all power (battery + AC) from the board and power the flash chip over the clip. This is generally discouraged unless you know exactly that the other chips on your board are protected against powering up as well (some ThinkPads have a diode on the VCC trace to the flash chip for that). You connect VCC to the clip in this case. 2. Wake-on-LAN state: Use the regular AC to power the board but keep the machine shut down. In this state a lot of components on the board are already active, including the flash chip. Do not attach VCC through the clip, if you do this! I would generally recommend 2. if you have a multimeter and can check that the flash chip is indeed powered. When you attach a network cable you can also see if the LEDs at the ethernet port light up, but this is no 100% reliable indication. Last but not least, the flash chip has two pins /HOLD and /WP that should be pulled up (to VCC). The mainboard should already take care of that, but you should check with a multimeter if that is the case. If not, or if you can't verify it, you should pull these two pins high. Hope that helps, Nico

1 0

ERASE FAILED on Macronix Bios Chip x220 (Expected 0xff, Found=0x5a)
by The_Raven Raven 26 Jan '18

26 Jan '18

I had similar problems. See here: https://www.mail-archive.com/flashrom@flashrom.org/msg13042.html To keep a long story short: As i can remember, i had 4 chips, 2 working and 2 not working. Dont know why. Option 1: Parts of the chip is write protected Option 2: Chip is broken. BTW: Strange "spispeed". Try with "30000"

1 0

ERASE FAILED on Macronix Bios Chip x220 (Expected 0xff, Found=0x5a)
by realraw＠tuta.io 26 Jan '18

26 Jan '18

After having tried all 4 options of flashchips on my bios, they will all fail to erase and then finally write the new Coreboot ROM I've compiled. I have changed power sources, methods of powering the Pi3, as well as all the different SPI speeds. Found Macronix flash chip "MX25L6405" (8192 kB, SPI) on linux_spi.Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on linux_spi.Found Macronix flash chip "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E" (8192 kB, SPI) on linux_spi.Multiple flash chip definitions match the detected chip(s): "MX25L6405", "MX25L6405D", "MX25L6406E/MX25L6408E", "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E" I noticed while Googling flashrom troubleshooting it said something about 'turning write-protection off'. I have absolutely no issues reading the BIOS, and I have md5sum checked it multiple times and they all give the same reading. It seems as if something else is missing that's not allowing the chip to be erased. Here is a log I've included from one of the many failed attempts: flashrom v0.9.9-r1954 on Linux 4.9.77-v7+ (armv7l)flashrom was built with libpci 3.3.1, GCC 5.3.1 20160205, little endianCommand line (8 args): flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w /home/pi/coreboot/coreboot.rom -c MX25L6406E/MX25L6408E -o logfile.txtCalibrating delay loop... OS timer resolution is 1 usecs, 595M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 998 us, 10000 myus = 10035 us, 4 myus = 5 us, OK.Initializing linux_spi programmerUsing device /dev/spidev0.0Using 4096 kHz clockThe following protocols are supported: SPI.Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on linux_spi.Chip status register is 0x00.Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not setChip status register: Bit 6 is not setChip status register: Block Protect 3 (BP3) is not setChip status register: Block Protect 2 (BP2) is not setChip status register: Block Protect 1 (BP1) is not setChip status register: Block Protect 0 (BP0) is not setChip status register: Write Enable Latch (WEL) is not setChip status register: Write In Progress (WIP/BUSY) is not setThis chip may contain one-time programmable memory. flashrom cannot readand may never be able to write it, hence it may not be able to completelyclone the contents of this chip (see man page for details).Block protection is disabled.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: 0xe8ERASE FAILED!Reading current flash chip contents... done. Looking for another erase function.Trying erase function 1... 0x000000-0x00ffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x0000ffff: 0x299dERASE 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: 0x299dERASE 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: 0x5d0197ERASE 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: 0x5d0197ERASE FAILED!Looking for another erase function.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) betweenthe programmer and the flash chip. If you think the error is caused by flashromplease report this on IRC at chat.freenode.net (channel #flashrom) ormail flashrom(a)flashrom.org, thanks!

2 1

AT45DB081D Chip tested -> OK
by The_Raven Raven 26 Jan '18

26 Jan '18

Hi I have tested Chip "AT45DB081D" (found on a NIC). Chip works fine. Test Steps: - Read - Erase - Written Data1 - Written Data2 (overwritten) Data1 and Data2 generated with "dd" from "/dev/urandom". Greets

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom