September 2018 - flashrom - mail.coreboot.org

Re: [flashrom] New SPI NOR Flash product Support
by Stefan Tauner Aug. 15, 2019

Aug. 15, 2019

On Mon, 9 May 2016 20:46:18 -0700 David Hendricks <dhendrix(a)google.com> wrote: > Hi Victor, > From Flashrom's software perspective all chips with the same ID are > indistinguishable. > > Part number often includes characteristics such as package and thermal > tolerance which do not affect software compatibility. However, we will add the new names to the in-program (and hence wiki) database so that this new information becomes public. Thanks for the heads up, Victor. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

4 4

80/100/132 column line width policy
by Carl-Daniel Hailfinger Dec. 15, 2018

Dec. 15, 2018

Hi, we're hitting the 80 column limit in our code in ways which actually reduce readability for the code. Examples are various multiline messages and complicated nested code where refactoring to a separate function doesn't make sense. Keeping the old 80 column limit is not really an option anymore. Standard terminal sizes have one of 80, 100 or 132 columns. Given the monitor resolutions many people have nowadays, I think it is safe to say that you can fit two xterms with 100 columns horizonally next to each other. 100 columns should also be sufficient for a msg_p* of roughly 80 columns of text. 132 columns provide more leeway, but IMHO that would be too wide for good readability (and my screen can't fit two xterms side-by-side anymore). Of course some files have sections where any column limit is not acceptable (board lists etc.), but the column limit violations should be limited to the affected file sections, not whole files. Comments? I'd like to get this decided today or tomorrow so we know where we need line breaks in Stefan Tauner's new struct flashchip patch. Regards, Carl-Daniel -- http://www.hailfinger.org/

7 9

FOSDEM Hardware Enablement Devroom
by Paul Kocialkowski Dec. 4, 2018

Dec. 4, 2018

A Hardware Enablement devroom will be taking place at FOSDEM this year, on Sunday 10 December 2017. This newly-created devroom is the result of 3 proposals that were merged together. It is co-organized by several individuals. The devroom covers all aspects related to hardware enablement and support with free software, including aspects related to boot software, firmwares, drivers and userspace tools and adaptation. Proposals for talks related to these topics are welcome and can be submitted until Sunday 26 November 2017 via the pentabarf interface. Short talks are encouraged over longer ones in order to cover a wide range of topics. The announcement for the devroom, that contains all the useful information, was published at: https://lists.fosdem.org/pipermail/fosdem/2017-October/002649.html Cheers and see you at FOSDEM! -- Paul Kocialkowski, developer of free digital technology and hardware support Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/

3 3

Re: [flashrom] [coreboot] flashrom and 256 MiB S256FL256S
by Nico Huber Sept. 30, 2018

Sept. 30, 2018

On 9/28/18 11:20 PM, ron minnich wrote: > I spoke too soon. It just flat out does not work to have sf100 and 256Mbit > part AFAICT Ah, crap. I just gave this another thought and now I'm convinced that it can't work with the current code. dediprog_spi uses its own functions for read/write that likely don't call into the common, 4BA aware code. I'll try to provide a patch later tonight... Nico

1 1

Lenovo T430s with linux_spi programmer and internal
by Dirk M. Sept. 29, 2018

Sept. 29, 2018

Hello! successfully flashed my Lenovo T430s with a Raspberry Pi on Raspian Jessie (Raspian Stretch dont work) After Coreboot was implemented, ist was also possible to flash internal :-) Thank you very much! Greetings from Munich (Germany) Dirk Mauz

1 0

Re: [flashrom] [coreboot] flashrom and 256 MiB S256FL256S
by ron minnich Sept. 28, 2018

Sept. 28, 2018

I spoke too soon. It just flat out does not work to have sf100 and 256Mbit part AFAICT On Fri, Sep 28, 2018 at 11:19 AM ron minnich <rminnich(a)gmail.com> wrote: > Got the fix. I used dpcmd to update the firmware on the FS100 to 5.5.3 > > Then flashrom can program it with ease. > > And, ironically, while dpcmd can update the firmware, it still can't flash > the part :-) > > ron >

1 0

Re: [flashrom] [coreboot] flashrom and 256 MiB S256FL256S
by Carl-Daniel Hailfinger Sept. 28, 2018

Sept. 28, 2018

On 27.09.2018 22:34, Nico Huber wrote: > On 9/27/18 10:11 PM, ron minnich wrote: >> yeah, also is there a programmer you recommend for 32MiB parts? > Any programmer that can handle arbitrary SPI commands, e.g. single- > board computers with native SPI interface (RPi, BeagleBone Black etc.), > CH341A is popular but slow, FTDI based programmers are faster (FT232H/ > FT2232H/FT4232H), serprog programmers (some may not be too slow), Bus- > Pirate rather slow too. If you want programming to be fast (almost on par with Dediprog): Either Raspberry Pi or Beaglebone Black. The Beaglebone Black has an abysmal internal power supply and for any in-circuit flashing you'll need an additional 3.3V supply for the flash chip. For standalone chips it usually is sufficient, though. The Raspberry Pi has SPI disabled by default, you need to add dtparam=spi=on to the file /boot/config.txt . Regards, Carl-Daniel > Nico > >> thanks >> >> ron >> >> On Thu, Sep 27, 2018 at 1:10 PM Nico Huber <nico.h(a)gmx.de> wrote: >> >>> Ah, dediprog... you happen to have the one programmer that is hard to >>> support. >>> >>> On 9/27/18 9:49 PM, ron minnich wrote: >>>> hmm, is this useful? >>>> >>>> Found Spansion flash chip "S25FL256S......0" (32768 kB, SPI) on dediprog. >>>> Erasing and writing flash chip... 4-byte address requested but master >>> can't >>>> handle 4-byte addresses. >>> That is expected, native 4-byte instructions are tried first but they >>> are not implemented yet for dediprog. It should fall back to another >>> instruction though. Unless the dediprog resets the chip between in- >>> structions, it should actually work. Though, David seemed to have >>> trouble with that too, I didn't test it myself yet. >>> >>>> Looking for another erase function. >>> Can you please just post the whole log (best taken with -o logfile). >>> >>> Nico >>> >

2 1

W25Q256JVFQ
by Andrej Gornik Sept. 23, 2018

Sept. 23, 2018

Hi, I have problem with flashing W25Q256JVFQwith latest git version of flashrom. root/Temp/flashrom/flashrom -p buspirate_spi:dev=/dev/ttyACM0 -c W25Q256.V -w Upall_VTH52X1D.20180622.bin flashrom p1.0-100-gcabe320 on Linux 4.14.0-kali3-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Bus Pirate firmware 6.1 and older does not support SPI speeds above 2 MHz. Limiting speed to 2 MHz. It is recommended to upgrade to firmware 6.2 or newer. Found Winbond flash chip "W25Q256.V" (32768 kB, SPI) on buspirate_spi. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x0025d000! Expected=0xff, Found=0xf0, failed byte count from 0x0025d000-0x0025dfff: 0x31b ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x006dc800! Expected=0xff, Found=0x48, failed byte count from 0x006d8000-0x006dffff: 0x2a7 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Erase/write done. Verifying flash... FAILED at 0x002bbe59! Expected=0x3b, Found=0x00, failed byte count from 0x00000000-0x01ffffff: 0xa114 Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! Regards, Andrej

2 1

Re: [flashrom] HP 8200
by Angel Pons Sept. 19, 2018

Sept. 19, 2018

Hello Michael, What is your question about this log? Regards, Angel Pons Pons On Tue, Sep 18, 2018 at 9:14 AM, Michael Miller <mike.mikemiller(a)gmail.com> wrote: > [root@localhost ~]# flashrom -V --programmer internal > flashrom v1.0 on Linux 3.10.0-862.11.6.el7.x86_64 (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > flashrom was built with libpci 3.5.1, GCC 4.8.5 20150623 (Red Hat 4.8.5-16), > little endian > Command line (3 args): flashrom -V --programmer internal > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Initializing internal programmer > No coreboot table found. > Using Internal DMI decoder. > DMI string chassis-type: "Mini Tower" > DMI string system-manufacturer: "Hewlett-Packard" > DMI string system-product-name: "HP Compaq 8200 Elite SFF PC" > DMI string system-version: "Not Specified" > DMI string baseboard-manufacturer: "Hewlett-Packard" > DMI string baseboard-product-name: "1495" > DMI string baseboard-version: "Not Specified" > 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: 1c. > Found chipset "Intel Q67" with PCI ID 8086:1c4e. > 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 = 0xc25: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) > Top Swap: not enabled > 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 disabled > 0xff600000/0xff200000 FWH decode disabled > 0xff500000/0xff100000 FWH decode disabled > 0xff400000/0xff000000 FWH decode disabled > Maximum FWH chip size: 0x100000 bytes > SPI Read Configuration: prefetching disabled, caching enabled, > BIOS_CNTL = 0x22: BIOS Lock Enable: enabled, BIOS Write Enable: disabled > Warning: BIOS region SMM protection is enabled! > Warning: Setting Bios Control at 0xdc from 0x22 to 0x01 failed. > New value is 0x22. > SPIBAR = 0x00007fcb9274c000 + 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: 0x00001a1b (FRAP) > BMWAG 0x00, BMRAG 0x00, BRWA 0x1a, BRRA 0x1b > 0x54: 0x00000000 FREG0: Warning: Flash Descriptor region > (0x00000000-0x00000fff) is read-only. > 0x58: 0x07ff0510 FREG1: BIOS region (0x00510000-0x007fffff) is read-write. > 0x5C: 0x050f0003 FREG2: Warning: Management Engine region > (0x00003000-0x0050ffff) is locked. > 0x60: 0x00020001 FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is > read-write. > 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. > 0x74: 0x87ff07f0 PR0: Warning: 0x007f0000-0x007fffff is read-only. > 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: 0xf94240 (SSFC) > SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=2, SME=0, SCF=1 > 0x94: 0x0006 (PREOP) > 0x96: 0x043b (OPTYPE) > 0x98: 0x05200302 (OPMENU) > 0x9c: 0x0000019f (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) > PROBLEMS, continuing anyway > 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 GD25VQ21B, 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x4017 > Probing for GigaDevice GD25VQ40C, 512 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 GigaDevice GD25VQ80C, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x4017 > Probing for GigaDevice GD25VQ16C, 2048 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 W25Q128.W, 16384 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 0xff, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0x52, id2 0x43, id1 > is normal flash content, id2 is normal flash content > Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0x52, id2 0x43, id1 > is normal flash content, id2 is normal flash content > Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x52, id2 0x43, id1 is > normal flash content, id2 is normal flash content > Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, > id1 parity violation, id1 is normal flash content, id2 is normal flash > content > Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x52, id2 0x43, > id1 is normal flash content, id2 is normal flash content > Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 > 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash > content > Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x10, id2 > 0xeb, id1 is normal flash content, id2 is normal flash content > Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x52, id2 > 0x43, id1 is normal flash content, id2 is normal flash content > Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x52, id2 0x43, id1 > is normal flash content, id2 is normal flash content > Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 > 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash > content > Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x74, id2 0x4f, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x52, id2 0x43, id1 is > normal flash content, id2 is normal flash content > Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x52, id2 0x43, id1 is > normal flash content, id2 is normal flash content > Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x74, id2 0x4f, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x52, id2 0x43, id1 is > normal flash content, id2 is normal flash content > Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x52, id2 > 0x43, id1 is normal flash content, id2 is normal flash content > Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x52, id2 > 0x43, id1 is normal flash content, id2 is normal flash content > Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x52, id2 > 0x43, id1 is normal flash content, id2 is normal flash content > Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 > 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash > content > Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 > 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash > content > Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 > 0x52, id2 0x43, 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). > No operations were specified. > Restoring MMIO space at 0x7fcb9274f8a0 > Restoring PCI config space for 00:1f:0 reg 0xdc > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] (no subject)
by Angel Pons Sept. 19, 2018

Sept. 19, 2018

Hello, First of all, is your laptop a Dell Latitude D630? Specifying the model number may be ambiguous. With regard to reflashing the BIOS, may I ask how exactly would reflashing help? AFAIUI, rewriting the same code would make no difference, and there isn't a free replacement such as coreboot for this laptop. Best regards, Angel Pons Pons

1 0