flashrom May 2018

flashrom@flashrom.org

18 participants
32 discussions

jmicron SATA/IDE flashing of option rom
by Rudolf Marek 27 May '18

27 May '18

Hi, I own JMB363 SATA/IDE. I figured it out how to flash it with a flashrom. It has the parallel flash which is 512KiB (SST39VF040), but the memory BAR where the flash is visible is only 64KiB. How flashrom deals with such programmers? It looks like I just need to mask the address bits not to get out of the BAR. Maybe I need to use "layout" feature? Has someone else the jmicron SATA/IDE controller? I guess we could support similar controllers. Thanks Rudolf

1 1

Re: [flashrom] ITE 8518 flashing through keyboard port
by Curi0 26 May '18

26 May '18

According to the schematic the power lines are shared. How could I check if the EC is powered when accessing the flashing chip ? On Fri, May 25, 2018, 3:02 PM Mike Banon <mikebdp2(a)gmail.com> wrote: > > Directly flashing the SPI chip maybe be dangerous since the EC can > interfere unless the SPI chip is desoldered. > > EC will not interfere if the board will be powered off, and you could > directly flash a SPI chip without desoldering by attaching a test clip > to it (which is connected to a flashrom-supported programmer like a > cheap CH341A). Examples of the instruction: > https://www.flashrom.org/ISP , > http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate > (for CH341A its the same, just a connection scheme and flashrom > commands are a little bit different) > > On Fri, May 25, 2018 at 9:06 AM, Curi0 <zkqri0(a)gmail.com> wrote: > > Hi, > > I have a laptop with ITE 8518 and I want to try to port coreboot. The SPI > > flash chip is shared between the EC and BIOS and is connected to the ITE > > 8518. Directly flashing the SPI chip maybe be dangerous since the EC can > > interfere unless the SPI chip is desoldered. > > > > The ITE 8518 has a mode where the keyboard connector can be used a > parallel > > port for flashing > > ( > http://www.recomb-omsk.ru/published/SC/html/scripts/doc/94689_datasheet_IT8… > > similar chip) but there isn't any information on the software required. > This > > video (https://www.youtube.com/watch?v=GYedPOLiUOo) shows flashing the > BIOS > > using a proprietary programmer software so it should be possible. > > > > So is there any way I could reverse engineer the parallel port if I don't > > have access to the ITE flashing software and the programmer in the video > > costs $150 and even if it could be reverse engineered there won't be any > way > > to see the raw parallel port commands it sends.Possibly there are some > > documents floating on the internet with the information. > > > > Curi0 > > > > _______________________________________________ > > flashrom mailing list > > flashrom(a)flashrom.org > > https://mail.coreboot.org/mailman/listinfo/flashrom >

1 0

reading the flash image of my Celsius H265
by Elmar Stellnberger 26 May '18

26 May '18

When I boot with iomem=relaxed and enable flash writing in my BIOS I get the following result with my Celsius H265 notebook: > flashrom -p internal:laptop=force_I_want_a_brick --read celsius2.rom flashrom p1.0-74-g2568357 on Linux 4.17.0-rc3+ (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). ======================================================================== WARNING! You seem to be running flashrom on an unsupported laptop. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH9M-E". Enabling flash write... OK. Found Winbond flash chip "W25X32" (4096 kB, SPI) mapped at physical address 0x00000000ffc00000. Reading flash... done. However if I execute this twice I get two different images: wget https://www.elstel.org/uploads/celsius.rom wget https://www.elstel.org/uploads/celsius2.rom Using vbindiff I can see that quite a lot is different between both images. - which would be difficult to achieve if the firmware was changed while I am running my computer. The image may be somehow corrupted as me_cleaner (BIOS offers Intel AMT) can not process the image: python ../me_cleaner/me_cleaner.py -S -O celsius-no-me.rom celsius.rom Unknown image See also the dmidecode that I have attached. How can it be that both images are different? Do you think that the images are corrupted? If so what could we do about it?

3 5

Re: [flashrom] ITE 8518 flashing through keyboard port
by awokd 25 May '18

25 May '18

On Fri, May 25, 2018 9:32 am, Mike Banon wrote: >> Directly flashing the SPI chip maybe be dangerous since the EC can >> interfere unless the SPI chip is desoldered. > > EC will not interfere if the board will be powered off, and you could > directly flash a SPI chip without desoldering by attaching a test clip to > it (which is connected to a flashrom-supported programmer like a cheap > CH341A). Examples of the instruction: > https://www.flashrom.org/ISP , > http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate > (for CH341A its the same, just a connection scheme and flashrom > commands are a little bit different) FWIW, I had a cheap board without any power isolation and an SPI chip shared between EC and ME, and supplying power to the in-situ chip was enough to power up EC. That blocked me from doing anything useful. It's still on my pile to attempt to desolder some day and try again!

1 0

Technical Advisory / Gigabyte GA-F2A88XM-DS2P, Dual MX25L6406E
by Dieter Miosga 25 May '18

25 May '18

Dear all, receive the terminal output of my action to reflash the Master BIOS chip of the forenamed Motherboard, according to the advice in this output. SYMPTOMS ======= After acquiring a Gigabyte GA-F2A88XM-DS2P from mercadoactual.es, I equipped it with an AMD Athlon X4 845 Carrizo/Excavator and a pair of 4GB DDR3 1600MHz RAM (1.35V) bars together with an older GeForce NVIDIA 512MB graphics card of Chinese production. All did work very well over the Thursday evening, Friday and a weekend and I had the benefit of several kernel compilations for which I recommend this composition of Hardware. After a long session, wherein the OpenSuSE Leap 42.3 and the XUbuntu-17.10.1 installations were updated and I did experiment with the BIOS settings, I encountered the board going on in endless idle reboots after reaching the Gigabyte UEFI BIOS screen, in the next morning after switching the system on again, attempting to compile the x86-64 arch version of the kernel with enabled AVX2 instructions. For all fury and rage, the regular methods of hard resetting the BIOS to the factory defaults showed no effect. Short cutting the CMOS-Reset pin pair showed no effect and then removing the battery with short cutting the contacts without and under voltage, with running ventilator or switched off with power supply on, neither. I passed the board to the local hardware supporter for examination and remedy if possible. During the following days when I did notify the support of mercadoactual and had to support a stressing and time taking communication, I had to notice that an arbitrary administrative intervention on my publications in the github.com site did falsely edit some of the update comments, appearing behind changed sections of the contents. The communication with the mercadoactual stuff was awful and led me to the assumption that they are not authorized resellers who can merge the board into a technical support procedure of Gigabyte. Gigabyte's web support is from Google and Facebook protected and shows no local national settlement address. I did get the board returned to my hands with the unaltered symptom of endless idle looping reboot at UEFI screen and the confirmation of the symptoms, two days before the conceded 14 days of customers devolution end. A call to the Gigabyte support in Hamburg/Germany ended after some authoritative advises, that all were already anticipated by my work prudence, with no further information helping to resolve the problem. RESOLVED ======= With the FLASHROM utility of free and open source software, using a CH341A USB to SPI programmer together with a clip to seize the pins of the master MX25L6406E chip, it was possible to reset the BIOS to a reusable state. Thereafter, the BIOS did not reboot itself in an endless idle loop and the Gigabyte Dual BIOS mechanism did detect a corrupt primary BIOS on the UEFI screen and prompted for to over program the primary from the backup BIOS. After answering yes and awaiting the copy progress to finish, the Motherboard did work alike from the first moments on. I did flash in the regular and for now only one version from Gigabyte support directly from the web pages of gigabyte.com showing the technical descriptions of the GA-F2A88XM-DS2P. It remains unclear whether the FLASHROM utility does respect and handle protected areas sufficiently correct and whether the error messages do mean only the confirmation of a necessary erase to restore the BIOS by interrupting a skip over instead of erase to the sections that are zeroed or oned out. Therefore it is not comprehensible that the second and backup BIOS differs from the first and used one and I do not know what happened if I had answered the question of the DualBIOS mechanism with NO, neither what will happen if the copied BIOS contains the same corrupt sections that led to symptoms described above. URGED ===== It is necessary to forward the fore standing facts not only to the FLASHROM developers but also to Gigabyte support. Who will hook in to Facebook to roll out the necessary remedy? I don't want to. The sold hardware in use is hard to change physically to a mechanism that fully complies with the MX25L6406E BIOS chip design's architectural intentions. The BIOS has to be revised and reprogrammed, shall be edited and should contain at least a feature to seek for a connected FAT32 USB memory stick containing an original BIOS binary file, After a certain number of boot attempts to a defined boot procedure level, that binary should be reflashed to the primary BIOS chip. The technical supporter and I did encounter a restriction in the BIOS that does prohibit the use of older Radeon graphic cards. This should be alleviated. Further, it is necessary to raise the evidence level by the quality and amount of documentation to the FLASHROM utility. 'And now they stand no more to cheat on others, but ask each other "How up!" ' Greetings Dieter Miosga https://github.com/yainit/

1 0

Re: [flashrom] ITE 8518 flashing through keyboard port
by Mike Banon 25 May '18

25 May '18

> Directly flashing the SPI chip maybe be dangerous since the EC can interfere unless the SPI chip is desoldered. EC will not interfere if the board will be powered off, and you could directly flash a SPI chip without desoldering by attaching a test clip to it (which is connected to a flashrom-supported programmer like a cheap CH341A). Examples of the instruction: https://www.flashrom.org/ISP , http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate (for CH341A its the same, just a connection scheme and flashrom commands are a little bit different) On Fri, May 25, 2018 at 9:06 AM, Curi0 <zkqri0(a)gmail.com> wrote: > Hi, > I have a laptop with ITE 8518 and I want to try to port coreboot. The SPI > flash chip is shared between the EC and BIOS and is connected to the ITE > 8518. Directly flashing the SPI chip maybe be dangerous since the EC can > interfere unless the SPI chip is desoldered. > > The ITE 8518 has a mode where the keyboard connector can be used a parallel > port for flashing > (http://www.recomb-omsk.ru/published/SC/html/scripts/doc/94689_datasheet_IT8… > similar chip) but there isn't any information on the software required. This > video (https://www.youtube.com/watch?v=GYedPOLiUOo) shows flashing the BIOS > using a proprietary programmer software so it should be possible. > > So is there any way I could reverse engineer the parallel port if I don't > have access to the ITE flashing software and the programmer in the video > costs $150 and even if it could be reverse engineered there won't be any way > to see the raw parallel port commands it sends.Possibly there are some > documents floating on the internet with the information. > > Curi0 > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom

1 0

ITE 8518 flashing through keyboard port
by Curi0 25 May '18

25 May '18

Hi, I have a laptop with ITE 8518 and I want to try to port coreboot. The SPI flash chip is shared between the EC and BIOS and is connected to the ITE 8518. Directly flashing the SPI chip maybe be dangerous since the EC can interfere unless the SPI chip is desoldered. The ITE 8518 has a mode where the keyboard connector can be used a parallel port for flashing ( http://www.recomb-omsk.ru/published/SC/html/scripts/doc/94689_datasheet_IT8… similar chip) but there isn't any information on the software required. This video (https://www.youtube.com/watch?v=GYedPOLiUOo) shows flashing the BIOS using a proprietary programmer software so it should be possible. So is there any way I could reverse engineer the parallel port if I don't have access to the ITE flashing software and the programmer in the video costs $150 and even if it could be reverse engineered there won't be any way to see the raw parallel port commands it sends.Possibly there are some documents floating on the internet with the information. Curi0

1 0

Re: [flashrom] Flash T500
by Nico Huber 21 May '18

21 May '18

Hi, On 21.05.2018 11:04, Jan Zuber wrote: > I did it like in the video. > https://www.youtube.com/watch?v=CyxgYnOcsTw > > The reading of the original ROM worked. > > Now the laptop was lying around longer and I tried again with the command: > > flashrom -p linux_spi: dev = / dev / spidev0.0, spispeed = 128 * -w * > name of libreboot rom * -V -c * bios chip name * > > And it has been verified. If flashrom says "VERIFIED", it's job is done. > > Only now I have a black screen, the fan is short and nothing else happens. You should talk to libreboot folks then. The image might be incompatible with your hardware or maybe you did something wrong when preparing the image. Well, one idea I have left: You could return to the vendor BIOS, verify that everything works and then flash libreboot only without disabling the ME. For this you should add these options to your flashrom command: --ifd -i bios This way, it would only flash the BIOS part. Nico PS. Please always keep the mailing list in CC.

1 0

Re: [flashrom] hope this helps pomona soic 8 Clip raspberry pi 3
by Nico Huber 21 May '18

21 May '18

Hi, On 20.05.2018 14:41, garrett aherhgf wrote: > udo flashrom -r ~/efi/read1.bin -V -p linux_spi:dev=/dev/spidev0.0 you should always specify the `spipseed` parameter to `linux_spi` as well. The default has changed in Linux and is too high now for most flashing applications. Nico

1 0

Re: [flashrom] hope this helps pomona soic 8 Clip raspberry pi 3
by Mike Banon 21 May '18

21 May '18

Maybe you don't have enough power for this soic 8 chip, or too long wires? Could you please tell us the markings written on a chip, to confirm if it is among the chips supported by flashrom? Best regards, Mike On Sun, May 20, 2018 at 3:41 PM, garrett aherhgf <HateEVERYTHING881(a)hotmail.com> wrote: > udo flashrom -r ~/efi/read1.bin -V -p linux_spi:dev=/dev/spidev0.0 > flashrom p1.0-77-gf9a3055 on Linux 4.14.34-v7+ (armv7l) > flashrom is free software, get the source code at https://flashrom.org > > flashrom was built with libpci 3.5.2, GCC 6.3.0 20170516, little endian > Command line (5 args): flashrom -r /home/pi/efi/read1.bin -V -p linux_spi:dev=/dev/spidev0.0 > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Initializing linux_spi programmer > Using device /dev/spidev0.0 > linux_spi_init: Using value from /sys/module/spidev/parameters/bufsiz as max buffer size. > linux_spi_init: max_kernel_buf_size: 4096 > The following protocols are supported: SPI. > Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25SF041, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT25SF161, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for ESI ES25P40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for ESI ES25P80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for ESI ES25P16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25LQ40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25LQ80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25LQ64(B), 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25LQ128, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25Q128C, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25VQ21B, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25VQ40C, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25VQ41B, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25VQ80C, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for GigaDevice GD25VQ16C, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for ISSI IS25LP128, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for ISSI IS25WP128, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L25635F, 32768 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX66L51235F, 65536 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > 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 0x10, id2 0xdd0b > 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 0x10, id2 0xdd0b > 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 0x10, id2 0xdd0b > 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 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron N25Q256..3E/MT25QL256, 32768 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Micron N25Q512..3E/MT25QL512, 65536 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LQ020, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LQ040, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LQ080, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LQ016, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LQ032C, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xff, id2 0xff > Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0xff, id2 0xff > Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xff, id2 0xff > Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xff, id2 0xff > Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xff, id2 0xff > Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xff, id2 0xff > Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xff, id2 0xff > Probing for SST SST25WF020A, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25WF040B, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25WF080B, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST26VF016B(A), 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST26VF032B(A), 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST26VF064B(A), 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q256.V, 32768 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q40BW, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q80BW, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q40EW, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q80EW, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25Q128.W, 16384 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25P80, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25P16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond W25P32, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Zetta Device ZD25D20, 256 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Zetta Device ZD25D40, 512 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. > Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x10, id2 0xdd0b > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi. > Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xff, id2 0xff > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE > The test status of this chip may have been updated in the latest development > version of flashrom. If you are running the latest development version, > please email a report to flashrom(a)flashrom.org if any of the above operations > work correctly for you with this flash chip. Please include the flashrom log > file for all operations you tested (see the man page for details), and mention > which mainboard or programmer you tested in the subject line. > Thanks for your help! > Read is not working on this chip. Aborting. > > r > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom May 2018