- flashrom - mail.coreboot.org

[RFC PATCH 0/2] Experimental Developerbox/CP2102 bitbang programmer
by Daniel Thompson 04 Jun '18

04 Jun '18

This patchset contains a couple of experimental patches to allow me to recover the ROM of a 96Boards Developerbox. Basically I've hacked something together that appears to work and am interested in thoughts and opinions before I invest time to clean it up or optimize it any further. The two patches are entirely separable; the only commonality is that both are needed for Developerbox tool-free recovery to work (and that both currently contain questions in the patch description). Daniel Thompson (2): programmer: Add Developerbox/CP2104 bit bang driver flashchips: Add Macronix MX25U51245G Makefile | 24 +++- developerbox_spi.c | 296 +++++++++++++++++++++++++++++++++++++++++++++ flashchips.c | 40 ++++++ flashchips.h | 1 + flashrom.c | 12 ++ programmer.h | 12 ++ 6 files changed, 383 insertions(+), 2 deletions(-) create mode 100644 developerbox_spi.c -- 2.17.0

1 2

Re: [flashrom] Fail to flash W25X40
by David Hendricks 31 May '18

31 May '18

On Wed, May 30, 2018 at 9:03 AM, Yang Hu <yh2948(a)columbia.edu> wrote: > Hi, > > I'm trying to rewrite a W24X40AL flash on a Seagate hard drive motherboard. > I can successfully read the data, although some weird things happened. > (First dumped code is nonsense, second time works fine, third or the rest > are just partial corrupted code). > > Then I want to flash the code back but get the following error, > > parallels@ubuntu:~/Desktop$ sudo flashrom -p > buspirate_spi:dev=/dev/ttyUSB0,spispeed=2M -E > flashrom on Linux 4.4.0-59-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Found Winbond flash chip "W25X40" (512 kB, SPI) on buspirate_spi. > Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, > Found=0x7f, failed byte count from 0x00001000-0x00001fff: 0x1 > ERASE FAILED! > Looking for another erase function. > FAILED at 0x00001800! Expected=0xff, Found=0x00, failed byte count from > 0x00000000-0x0000ffff: 0x42b > ERASE FAILED! > Looking for another erase function. > FAILED at 0x00002000! Expected=0xff, Found=0x00, failed byte count from > 0x00000000-0x0007ffff: 0x6596 > ERASE FAILED! > Looking for another erase function. > Looking for another erase function. > Looking for another erase function. > No usable erase functions left. > FAILED! > 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! > > My connection right now is: the motherboard is not powered, using bus pirate > 3.3v directly connects to VCC, /WP and /HOLD. I've tried to add 10k, 20k > resistor between 3.3v and /WP, /HOLD pin but the chip won't be recognized > then. > > I don't have much experience in electronics. Is this do with write > protection? Is there anything I can do with this? Hi Yang, It sounds like your Bus Pirate is backpowering other electronics on the board (e.g. an embedded controller), which in turn try to access the SPI flash and interfere. This happens when the vendor does not isolate the SPI flash circuitry. Determine what other electronics might be powered by the Bus Pirate and see if you can hold them in reset so that they don't try to access the SPI flash.

1 0

how to have a log from the program
by nicola scattolin 30 May '18

30 May '18

Hi, i'm using a ch341a programmer to flash my motherboard bios with your program, but i have the followin error: flashrom v0.9.9-97-g29333a0 on Windows 6.2 (x86) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Error: Image size (6815744 B) doesn't match the flash chip's size (8388608 B)! C:\Users\Marco\DOWNLO~1\FLASHR~1\FLASHR~1>flashrom.exe -w E7917IMS.1D0.bin flashrom v0.9.9-97-g29333a0 on Windows 6.2 (x86) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Reading old flash chip contents... done in 4 min and 37 sec. Erasing and writing flash chip... Erase/write done in 19 min and 7 sec. Verifying flash... FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x66847a 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! How can i extract some more logs? could it be a bad clip positioning? Thanks for your time and for your useful program Regards Nicola

1 0

Fail to flash W25X40
by Yang Hu 30 May '18

30 May '18

Hi, I'm trying to rewrite a W24X40AL flash on a Seagate hard drive motherboard. I can successfully read the data, although some weird things happened. (First dumped code is nonsense, second time works fine, third or the rest are just partial corrupted code). Then I want to flash the code back but get the following error, parallels@ubuntu:~/Desktop$ sudo flashrom -p buspirate_spi:dev=/dev/ttyUSB0,spispeed=2M -E flashrom on Linux 4.4.0-59-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25X40" (512 kB, SPI) on buspirate_spi. Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x7f, failed byte count from 0x00001000-0x00001fff: 0x1 ERASE FAILED! Looking for another erase function. FAILED at 0x00001800! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0x42b ERASE FAILED! Looking for another erase function. FAILED at 0x00002000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0007ffff: 0x6596 ERASE FAILED! Looking for another erase function. Looking for another erase function. Looking for another erase function. No usable erase functions left. FAILED! 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! My connection right now is: the motherboard is not powered, using bus pirate 3.3v directly connects to VCC, /WP and /HOLD. I've tried to add 10k, 20k resistor between 3.3v and /WP, /HOLD pin but the chip won't be recognized then. I don't have much experience in electronics. Is this do with write protection? Is there anything I can do with this? Thanks for your help. Yang Hu

1 0

Re: [flashrom] Update bios (not full flash) with flashrom
by Mike Banon 30 May '18

30 May '18

It could be that a manufacturer has released the same motherboards with two various sizes of a BIOS chip. You could try padding your 256 KB image with FF's to increase its' size up to 512 KB and then flash to the chip, after making a full backup ofcourse. Also you could look through your existing backup, to see how much of your 512 KB image is really occupied with anything thats not FF's, especially at the end. Could use some simple hex editor like Okteta to quickly check this On Tue, May 29, 2018 at 10:45 PM, Skoll RC <amisbievre(a)hotmail.fr> wrote: > I have an external programmer and a full backup of my current bios. nothing > writen, there was a label but it had to come off with time. > How can I concatenate images? The update is not a full bios, is it? > ________________________________ > De : David Hendricks <david.hendricks(a)gmail.com> > Envoyé : mardi 29 mai 2018 19:19 > À : Skoll RC > Cc : flashrom(a)flashrom.org > Objet : Re: [flashrom] Update bios (not full flash) with flashrom > > On Sun, May 27, 2018 at 11:44 AM, Skoll RC <amisbievre(a)hotmail.fr> wrote: >> Hi everyone, >> >> I would like to update my GA-8I915P-MF's bios with flashrom but Gigabyte >> only provide updates and no full bios so when I try to update with >> flashrom -p internal -w 8i9pmf.f2 I have an error message: Error: Image >> size >> (262144 B) doesn't match the flash chip's size (524288 B)! >> How can I fix it? > > That's unfortunate. Do you have an external programmer (something like > a buspirate) that can be used in case things go wrong? Can you tell if > there is anything written to the lower half of the chip? It could be > as simple as concatenating the 256KB image to itself to create a 512KB > image. But I wouldn't recommend trying that unless you have a good > means of recovering. > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] Update bios (not full flash) with flashrom
by Skoll RC 29 May '18

29 May '18

I have an external programmer and a full backup of my current bios. nothing writen, there was a label but it had to come off with time. How can I concatenate images? The update is not a full bios, is it? ________________________________ De : David Hendricks <david.hendricks(a)gmail.com> Envoyé : mardi 29 mai 2018 19:19 À : Skoll RC Cc : flashrom(a)flashrom.org Objet : Re: [flashrom] Update bios (not full flash) with flashrom On Sun, May 27, 2018 at 11:44 AM, Skoll RC <amisbievre(a)hotmail.fr> wrote: > Hi everyone, > > I would like to update my GA-8I915P-MF's bios with flashrom but Gigabyte > only provide updates and no full bios so when I try to update with > flashrom -p internal -w 8i9pmf.f2 I have an error message: Error: Image size > (262144 B) doesn't match the flash chip's size (524288 B)! > How can I fix it? That's unfortunate. Do you have an external programmer (something like a buspirate) that can be used in case things go wrong? Can you tell if there is anything written to the lower half of the chip? It could be as simple as concatenating the 256KB image to itself to create a 512KB image. But I wouldn't recommend trying that unless you have a good means of recovering.

1 0

Re: [flashrom] Update bios (not full flash) with flashrom
by David Hendricks 29 May '18

29 May '18

On Sun, May 27, 2018 at 11:44 AM, Skoll RC <amisbievre(a)hotmail.fr> wrote: > Hi everyone, > > I would like to update my GA-8I915P-MF's bios with flashrom but Gigabyte > only provide updates and no full bios so when I try to update with > flashrom -p internal -w 8i9pmf.f2 I have an error message: Error: Image size > (262144 B) doesn't match the flash chip's size (524288 B)! > How can I fix it? That's unfortunate. Do you have an external programmer (something like a buspirate) that can be used in case things go wrong? Can you tell if there is anything written to the lower half of the chip? It could be as simple as concatenating the 256KB image to itself to create a 512KB image. But I wouldn't recommend trying that unless you have a good means of recovering.

1 0

Update bios (not full flash) with flashrom
by Skoll RC 27 May '18

27 May '18

Hi everyone, I would like to update my GA-8I915P-MF's bios with flashrom but Gigabyte only provide updates and no full bios so when I try to update with flashrom -p internal -w 8i9pmf.f2 I have an error message: Error: Image size (262144 B) doesn't match the flash chip's size (524288 B)! How can I fix it? thx

1 0

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

hope this helps pomona soic 8 Clip raspberry pi 3
by garrett aherhgf 20 May '18

20 May '18

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

1 0

MX66L51235F+ch341a prog
by cel366 16 May '18

16 May '18

Hello, I'm Nick Tested a spi-flash MX66L51235 on the programmer h341a ,log file in the attachment. Version flashrom p1.0-76-g291764a build from Fedore 27 x64 Bye.

1 0

Re: [flashrom] program MX25R3235F
by David Hendricks 14 May '18

14 May '18

Hi Daniel, Thanks for the report and confirming getting it initially working. I filed an issue on github to add support: https://github.com/flashrom/flashrom/issues/43 If you have time, send a patch: https://www.flashrom.org/Development_Guidelines#Patch_submission. On Sun, May 13, 2018 at 9:13 AM, Daniel Gomez <mercuriom(a)gmail.com> wrote: > > I have added a new entry for ID 0x2816 with the same parameters as > MX25L3235D creating MX25R3235F and it works correctly, thanks. > > 2018-05-13 17:42 GMT+02:00 Daniel Gomez <mercuriom(a)gmail.com>: > >> >> Hello, I am trying to program an MX25R3235F memory with flashrom. Report >> attached. Is there any way to force the operation? >> Thanks in advance. >> >> Daniel >> >> > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom >

1 0

Re: [flashrom] MX66l51235f
by Nico Huber 14 May '18

14 May '18

Hi Ron, On 14.05.2018 18:01, ron minnich wrote: > anyone got the incantation to flash this with an sf100 ;-) TLDR; If it doesn't work with current master, you can try [1]. 512M, huh? what's that for, UbuntuBoot? xD You need 4-byte addresses to access the full chip and that's rather delicate with Dediprog (because we don't control the SPI commands directly for read and write). The chip supports an extended address register for the most significant byte, though it's unclear to me if this register's state is maintained between Dediprog commands. So it might just work with flashrom master, or might wreak havoc ;) [1] https://review.coreboot.org/19858/

2 1

MX66l51235f
by ron minnich 14 May '18

14 May '18

anyone got the incantation to flash this with an sf100 ;-)

1 0

Re: [flashrom] program MX25R3235F
by Daniel Gomez 13 May '18

13 May '18

I have added a new entry for ID 0x2816 with the same parameters as MX25L3235D creating MX25R3235F and it works correctly, thanks. 2018-05-13 17:42 GMT+02:00 Daniel Gomez <mercuriom(a)gmail.com>: > > Hello, I am trying to program an MX25R3235F memory with flashrom. Report > attached. Is there any way to force the operation? > Thanks in advance. > > Daniel > >

1 0

program MX25R3235F
by Daniel Gomez 13 May '18

13 May '18

Hello, I am trying to program an MX25R3235F memory with flashrom. Report attached. Is there any way to force the operation? Thanks in advance. Daniel

1 0

Re: [flashrom] [coreboot] flashrom on osx ...
by David Hendricks 11 May '18

11 May '18

[+flashrom, coreboot --> bcc] What version of OSX? I looked at this a bit last year, and they changed their frameworks in Sierra such that DirectHW needs to be updated. Stefan Tauner mentioned using osxcross ( https://github.com/tpoechtrager/osxcross.git) to build for OSX, but I've never used it. Here's some more background: https://mail.coreboot.org/pipermail/flashrom/2017-June/015033.html https://mail.coreboot.org/pipermail/flashrom/2017-June/015034.html On Fri, May 11, 2018 at 10:42 AM, ron minnich <rminnich(a)gmail.com> wrote: > if I just want to use a dediprog sf100 what's the best way to build > flashrom on osx? > > besides "throw the macbook in the trash and get a real computer" :-) > > ron > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot >

1 0

Re: [flashrom] Flashing Lenovo Tiny device fails
by Nico Huber 11 May '18

11 May '18

Hello Hubert, you'll find a patch attached and here [1]. If you do test it, please always keep a verbose log (e.g. using flashrom's `-o logfile` option), so we can mark your chipset as tested if it works, or help you out if not ;) Let me know if you need help applying the patch and compiling flashrom. Some remarks on flashing your system (generally applies to modern Intel systems): - If Lenovo enforced some write-protection (they do on their Think- Pads), you won't be able flash (the whole) firmware. - You'll need a full BIOS image that can be directly flashed, e.g. not just an update that only contains changed portions. OEMs sometimes only provide the latter. - The "BIOS" flash is usually shared with the Management Engine (ME). If configured correctly, you can't access the ME parts of the flash. You can add these options to make flashrom only access the BIOS region: `--ifd -i BIOS -N`. And additionally `-p internal:ich_spi_force=yes` if you want to write. - Always make a backup first. Nico PS. Please always keep the mailing list in CC. [1] https://review.coreboot.org/26232 On 11.05.2018 08:49, H. Scherrer-Paulus wrote: > Hello Nico, > > thank you for the quick reply. Here comes the output from lspci -nn: > > 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM > Registers [8086:191f] (rev 07) > 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake > Integrated Graphics [8086:1912] (rev 06) > 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a2af] > 00:14.2 Signal processing controller [1180]: Intel Corporation Device > [8086:a2b1] > 00:16.0 Communication controller [0780]: Intel Corporation Device > [8086:a2ba] > 00:17.0 SATA controller [0106]: Intel Corporation Device [8086:a282] > 00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:a2eb] (rev f0) > 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a2c8] > 00:1f.2 Memory controller [0580]: Intel Corporation Device [8086:a2a1] > 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a2f0] > 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a2a3] > 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet > Connection (2) I219-V [8086:15b8] > 01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co > Ltd Device [144d:a804] > > Kind regards, > Hubert > > On 05/10/2018 11:52 PM, Nico Huber wrote: >> Hello Hubert, >> >> On 09.05.2018 13:24, H. Scherrer-Paulus wrote: >>> Dear Sir, >>> >>> i am trying to find a way to flash the Bios/UEFI of Lenovo Tiny >>> devices (M710q) from >>> Linux. As the vendor does not supply a tool to do that (except for >>> Windows/DOS) >>> i tried flashrom, unfortunately with no success. This is what i get with >>> a verbose flag set: >>> >> >> looking at Lenovo's website the M710q seems to be rather new and often >> comes with a Kaby Lake SoC. But I don't see why flashrom doesn't detect >> that. It might just miss the PCI ID for the chipset. Can you please send >> us the output of `lspci -nn`. >> >> Thanks >> Nico >> > >

2 1

Flashing Lenovo Tiny device fails
by H. Scherrer-Paulus 10 May '18

10 May '18

Dear Sir, i am trying to find a way to flash the Bios/UEFI of Lenovo Tiny devices (M710q) from Linux. As the vendor does not supply a tool to do that (except for Windows/DOS) i tried flashrom, unfortunately with no success. This is what i get with a verbose flag set: flashrom v1.0 on Linux 4.4.126-48-default (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.5, little endian Command line (3 args): ./flashrom -p internal -V 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: "Desktop" DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "10MQS4Y300" DMI string system-version: "ThinkCentre M710q" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "3111" DMI string baseboard-version: "SDK0J40709 WIN 3259617498480" WARNING: No chipset found. Flash detection will most likely fail. The following protocols are supported: Non-SPI. Probing for AMD Am29F010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0x5d, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49(H)F010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F080T, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ESMT F49B002UA, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV040(A), 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0x0000, id2 0x0000 Probing for Eon EN29GL064(A)B, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Eon EN29GL064(A)T, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Eon EN29GL064H/L, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Eon EN29GL128, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400TC, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29LV160BE, 2048 kB: probe_jedec_common: id1 0x5d, id2 0xb3, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29LV160TE, 2048 kB: probe_jedec_common: id1 0x5d, id2 0xb3, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ISSI IS29GL064B, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for ISSI IS29GL064T, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for ISSI IS29GL064H/L, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for ISSI IS29GL128H/L, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F022(N)B, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F022(N)T, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29GL320EB, 4096 kB: probe_jedec_29gl: man_id 0x17, dev_id 0x675869, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL320ET, 4096 kB: probe_jedec_29gl: man_id 0x17, dev_id 0x675869, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL320EH/L, 4096 kB: probe_jedec_29gl: man_id 0x17, dev_id 0x675869, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL640EB, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL640ET, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL640EH/L, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL128F, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10ms/40us. probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information, using default 10ms/40us. probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: 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 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF080, 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 SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x85, id2 0xc1, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x5d, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10ms/40us. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0x5d, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BT, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x5d, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0x5d, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C512A/W29EE512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old Winbond W29* probe method disabled because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29GL032CB, 4096 kB: probe_jedec_29gl: man_id 0x17, dev_id 0x675869, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL032CT, 4096 kB: probe_jedec_29gl: man_id 0x17, dev_id 0x675869, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL032CH/L, 4096 kB: probe_jedec_29gl: man_id 0x17, dev_id 0x675869, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL064CB, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL064CT, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL064CH/L, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL128C, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W39F010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L020, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x5e, id2 0x5b, 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 0xc9, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. Kind regards, Hubert Scherrer-Paulus -- MPI für Physik komplexer Systeme Nöthnitzer Str. 38 01187 Dresden Tel. (0351) 871 2106

2 1

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

10 May '18

Hello Kamil, your message was filtered due to its excessive size. Please do not send big attachments to the mailing list. On 10.05.2018 11:33, Jan Zuber wrote: > yesterday I wanted to flash the bios on my t500 with libreboot and it > did not work. > In the picture you see the error message. Which was: >> Verifying flash... FAILED at 0x00003401! Expected=0x5f, Found=0x6e, failed byte count from 0x00000000-0x007fffff: 0x179 >> Your flash chip is in an unknown state. Also, it's hard to say what is going on as you didn't even tell us the command you used. All I can see is that you are using a Raspberry Pi for external flashing. > I tried to play the oroginal rom again but then the same mistake was shown. That address (0x3401) might be used by the ME (a micro controller embed- ded into the chipset). And the ME can cause corruption while it's still active. You might have woken it up by applying power (even if you just connected VCC to the flash chip; it's connected through the board to the chipset). So the BIOS can share the flash chip with the ME, it is partitioned and I suspect libreboot also messes with the partitioning. If you have a valid backup of the original flash contents: flashrom is accompanied by a tool called `ich_descriptors_tool` it can tell you a lot about the firmware configuration and partitioning. I don't know what libreboot puts at that address. Generally it's a bad idea to flash the ME region and libreboot in one go. > Can you help with please? I would try again to see if the "failed byte count" gets lower, and if, try again until it's 0. If that doesn't help, you can try to remove all power from the mainboard, wait some minutes or an hour and try again. Maybe the ME calms down. I could also be very wrong and this might not be about the ME at all in case your hardware setup is unreliable. Did you validate your backup with some verification runs (i.e. tried to read multiple times to make sure that reading works? Nico > > Best Regards > > Kamil >

1 0

Flash serial number change how to
by Lab | LHR | Digital Links 05 May '18

05 May '18

Dear Sir, Flash serial number change how to 25q128 flash Best regard Fayyaz

1 0

Re: [flashrom] FAILED: Soraka DVT1
by David Hendricks 27 Apr '18

27 Apr '18

Hello Hongxia, Were you able to get in touch with someone on the chromiumos team? It appears that you attempted to write the entire firmware ROM, but it failed to write the flash descriptor region. You should target the region(s) you want updated using the -i option, along with --fast-verify, so that flashrom does not attempt to write and verify regions that it might not have access to. On Mon, Apr 23, 2018 at 11:54 PM, Gao, HongxiaX <hongxiax.gao(a)intel.com> wrote: > Hi, > > > > It is failed on my board when flashing firmware R68 10599. Can you help me > on it? > > > > *HW:* Soraka DVT1 > > > > *Issue description:* > > Flash firmware 10431 without any problems, but it is failed when flashing > firmware R68 10599. Steps are: > > > > 1. Download firmware R68 10599 > <https://www.google.com/chromeos/partner/fe/#download:event=IMAGE_DOWNLOAD&u…>, > then extract it. > > 2. Enter board terminal > > localhost /home # flashrom -w 10599/image.bin > > flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 > (x86_64) > > flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 > (x86_64) > > Calibrating delay loop... OK. > > coreboot table found at 0x7aac5000. > > WARNING: SPI Configuration Lockdown activated. > > Erasing and writing flash chip... Verifying flash... VERIFY FAILED at > 0x00000081! Expected=0xff, Read=0x0b, failed byte count from > 0x00000000-0x00ffffff: 0x9 > > Your flash chip is in an unknown state. > > Get help on IRC at irc.freenode.net (channel #flashrom) or > > mail flashrom(a)flashrom.org with FAILED: your board name in the subject > line! > > ------------------------------------------------------------ > ------------------- > > DO NOT REBOOT OR POWEROFF! > > FAILED > > > > 3. Try to update firmware > > localhost /home/10599 # chromeos-firmwareupdate -m autoupdate > > Starting Google_Soraka firmware updater v4 (autoupdate)... > > - Updater package: [Google_Soraka.10431.32.0 / > EC:soraka_v1.1.8047-2c5917d7d] > > - Current system: [RO:Google_Soraka.10431.32.0 , > ACT:Google_Soraka.10431.32.0 / EC:soraka_v1.1.8047-2c5917d7d] > > - Write protection: Hardware: ON, Software: Main=off > > * invoke: flashrom -p host -r _current/bios.bin > > RO Contents are different. > > autoupdate(recovery): update RO+RW > > * invoke: flashrom -p host --fast-verify -w bios.bin > > autoupdate(recovery): update ec/RO+RW > > * invoke: flashrom -p ec --fast-verify -w ec.bin > > autoupdate(recovery): EC may be restored or updated in next boot. > > Firmware update (autoupdate) completed. > > > > 4. Reboot the board, then power off and power on > > 5. Flash fw 10599 again > > localhost /home # flashrom -w 10599/image.bin > > flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 > (x86_64) > > flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 > (x86_64) > > Calibrating delay loop... OK. > > coreboot table found at 0x7aac5000. > > WARNING: SPI Configuration Lockdown activated. > > Erasing and writing flash chip... Verifying flash... VERIFY FAILED at > 0x00000081! Expected=0xff, Read=0x0b, failed byte count from > 0x00000000-0x00ffffff: 0x9 > > Your flash chip is in an unknown state. > > Get help on IRC at irc.freenode.net (channel #flashrom) or > > mail flashrom(a)flashrom.org with FAILED: your board name in the subject > line! > > ------------------------------------------------------------ > ------------------- > > DO NOT REBOOT OR POWEROFF! > > FAILED > > > > > > Thanks > > > > Br, > > Hongxia > > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom >

1 0

Re: [flashrom] Flash support FT25H04
by Balázs Vinarz 26 Apr '18

26 Apr '18

Sorry, I made a mistake when applying the patch. So the patch works with read, erase and write functions. 2018-04-26 11:34 GMT+02:00 Balázs Vinarz <vinibali1(a)gmail.com>: > Hello there! > > I have the following chip: FT25H04. This is not yet supported even with > the following: patch > <https://raw.githubusercontent.com/tomaskovacik/kicad-library/master/library…>. > Can I help you anyhow to let this type supported? > > Regards >

1 0

Flash support FT25H04
by Balázs Vinarz 26 Apr '18

26 Apr '18

Hello there! I have the following chip: FT25H04. This is not yet supported even with the following: patch <https://raw.githubusercontent.com/tomaskovacik/kicad-library/master/library…>. Can I help you anyhow to let this type supported? Regards

1 0

FAILED: Soraka DVT1
by Gao, HongxiaX 24 Apr '18

24 Apr '18

Hi, It is failed on my board when flashing firmware R68 10599. Can you help me on it? HW: Soraka DVT1 Issue description: Flash firmware 10431 without any problems, but it is failed when flashing firmware R68 10599. Steps are: 1. Download firmware R68 10599<https://www.google.com/chromeos/partner/fe/#download:event=IMAGE_DOWNLOAD&u…>, then extract it. 2. Enter board terminal localhost /home # flashrom -w 10599/image.bin flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 (x86_64) flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 (x86_64) Calibrating delay loop... OK. coreboot table found at 0x7aac5000. WARNING: SPI Configuration Lockdown activated. Erasing and writing flash chip... Verifying flash... VERIFY FAILED at 0x00000081! Expected=0xff, Read=0x0b, failed byte count from 0x00000000-0x00ffffff: 0x9 Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! FAILED 3. Try to update firmware localhost /home/10599 # chromeos-firmwareupdate -m autoupdate Starting Google_Soraka firmware updater v4 (autoupdate)... - Updater package: [Google_Soraka.10431.32.0 / EC:soraka_v1.1.8047-2c5917d7d] - Current system: [RO:Google_Soraka.10431.32.0 , ACT:Google_Soraka.10431.32.0 / EC:soraka_v1.1.8047-2c5917d7d] - Write protection: Hardware: ON, Software: Main=off * invoke: flashrom -p host -r _current/bios.bin RO Contents are different. autoupdate(recovery): update RO+RW * invoke: flashrom -p host --fast-verify -w bios.bin autoupdate(recovery): update ec/RO+RW * invoke: flashrom -p ec --fast-verify -w ec.bin autoupdate(recovery): EC may be restored or updated in next boot. Firmware update (autoupdate) completed. 4. Reboot the board, then power off and power on 5. Flash fw 10599 again localhost /home # flashrom -w 10599/image.bin flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 (x86_64) flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 (x86_64) Calibrating delay loop... OK. coreboot table found at 0x7aac5000. WARNING: SPI Configuration Lockdown activated. Erasing and writing flash chip... Verifying flash... VERIFY FAILED at 0x00000081! Expected=0xff, Read=0x0b, failed byte count from 0x00000000-0x00ffffff: 0x9 Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! FAILED Thanks Br, Hongxia

1 0

Re: [flashrom] WinBond Chip Support
by Nico Huber 17 Apr '18

17 Apr '18

Hi Jordan, On 17.04.2018 14:40, Jordan Hill wrote: > Hello there, > > I have a Dell Inspiron 5559 Laptop which contains a Winbond 25Q128FVSQ > Chip. I tried running flashrom natively on the laptop and got the usual EC > warning so i stopped there. I then desoldered the SMD chip off the > motherboard and hooked it up to a RPI and connected it through the SPI > protocol. Flashrom then recognized it as a "Generic" flash chip and would > not allow the data to be read as it was still unrecognized. did you connect all input pins of the flash chip? A common error is to leave /HOLD and /WP floating. But they need a defined state. /HOLD has to be pulled up (towards VCC). /WP up too (might as well be down depen- ding on the chip's configuration, but up always works). Nico

1 0

WinBond Chip Support
by Jordan Hill 17 Apr '18

17 Apr '18

Hello there, I have a Dell Inspiron 5559 Laptop which contains a Winbond 25Q128FVSQ Chip. I tried running flashrom natively on the laptop and got the usual EC warning so i stopped there. I then desoldered the SMD chip off the motherboard and hooked it up to a RPI and connected it through the SPI protocol. Flashrom then recognized it as a "Generic" flash chip and would not allow the data to be read as it was still unrecognized. Unfortunately I do not have any logs. I believe that this chip is on the list of supported hardware yet it was not recognized in flashrom. I am using the latest version as of April 18th 2018. Any suggestions or help would be appreciated. Thank You

1 0

Re: [flashrom] no spi flash IS25LP128
by Nico Huber 17 Apr '18

17 Apr '18

On 16.04.2018 05:07, 山中老虎 wrote: > no spi flash IS25LP128 This chip is supported on our master branch only. You'd have to clone the repository and build flashrom yourself, see [1]. Nico PS. Please don't send unnecessary large attachments to the mailing list. [1] https://flashrom.org/Downloads

1 0

As requested, W25Q256.V works perfectly with Bus Pirate
by Richard Hughes 04 Apr '18

04 Apr '18

Using git master: 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... Erase/write done. Verifying flash... VERIFIED. Richard.

1 0

NVIDIA CK804: TYAN VX50 B4985: unexpected second chipset match: "NVIDIA CK804"
by Paul Menzel 03 Apr '18

03 Apr '18

Dear flashrom folks, As asked by flashrom, here is the output for the TYAN VX50 B4985 [1]. ``` $ sudo flashrom -p internal flashrom v1.0 on Linux 4.14.30.mx64.211 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "NVIDIA CK804". Enabling flash write... OK. Warning: unexpected second chipset match: "NVIDIA CK804" ignoring, please report lspci and board URL to flashrom(a)flashrom.org with 'CHIPSET: your board name' in the subject line. Found SST flash chip "SST49LF080A" (1024 kB, LPC) mapped at physical address 0x00000000fff00000. No operations were specified. $ lspci 00:00.0 Memory controller: NVIDIA Corporation CK804 Memory Controller (rev a4) 00:01.0 ISA bridge: NVIDIA Corporation CK804 ISA Bridge (rev f1) 00:01.1 SMBus: NVIDIA Corporation CK804 SMBus (rev a2) 00:02.0 USB controller: NVIDIA Corporation CK804 USB Controller (rev a2) 00:02.1 USB controller: NVIDIA Corporation CK804 USB Controller (rev a4) 00:06.0 IDE interface: NVIDIA Corporation CK804 IDE (rev f3) 00:07.0 IDE interface: NVIDIA Corporation CK804 Serial ATA Controller (rev f3) 00:08.0 IDE interface: NVIDIA Corporation CK804 Serial ATA Controller (rev f3) 00:09.0 PCI bridge: NVIDIA Corporation CK804 PCI Bridge (rev f2) 00:0a.0 Bridge: NVIDIA Corporation CK804 Ethernet Controller (rev f3) 00:0b.0 PCI bridge: NVIDIA Corporation CK804 PCIE Bridge (rev f3) 00:0c.0 PCI bridge: NVIDIA Corporation CK804 PCIE Bridge (rev f3) 00:0d.0 PCI bridge: NVIDIA Corporation CK804 PCIE Bridge (rev f3) 00:0e.0 PCI bridge: NVIDIA Corporation CK804 PCIE Bridge (rev a3) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 00:19.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:19.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:19.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:19.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:19.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 00:1a.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:1a.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:1a.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:1a.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:1a.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 00:1b.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:1b.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:1b.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:1b.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:1b.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 00:1c.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:1c.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:1c.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:1c.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:1c.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 00:1d.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:1d.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:1d.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:1d.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:1d.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 00:1e.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:1e.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:1e.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:1e.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:1e.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 00:1f.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:1f.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:1f.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:1f.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:1f.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 01:06.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05) 01:09.0 VGA compatible controller: XGI Technology Inc. (eXtreme Graphics Innovation) Z7/Z9 (XG20 core) 05:00.0 RAID bus controller: 3ware Inc 9650SE SATA-II RAID PCIe (rev 01) 0a:00.0 RAID bus controller: 3ware Inc 9690SA SAS/SATA-II RAID PCIe (rev 01) 80:00.0 Memory controller: NVIDIA Corporation CK804 Memory Controller (rev a4) 80:01.0 Memory controller: NVIDIA Corporation CK804 Memory Controller (rev f1) 80:0a.0 Bridge: NVIDIA Corporation CK804 Ethernet Controller (rev f3) 80:0b.0 PCI bridge: NVIDIA Corporation CK804 PCIE Bridge (rev f3) 80:0c.0 PCI bridge: NVIDIA Corporation CK804 PCIE Bridge (rev f3) 80:0d.0 PCI bridge: NVIDIA Corporation CK804 PCIE Bridge (rev f3) 80:0e.0 PCI bridge: NVIDIA Corporation CK804 PCIE Bridge (rev a3) ``` Kind regards, Paul [1] https://www.tyan.com/Barebones_VX50B4985_Transport%20VX50

1 0

Re: [flashrom] Winbond 25Q40EWNIG
by Nico Huber 30 Mar '18

30 Mar '18

Hello Matt, your mail never made it to the list, due to it's excessive size. Please don't send such huge attachments. On 20.03.2018 00:10, Matt Risen wrote: > Is there any chance we could get support for the Winbond 25Q40EWNIG SPI > eeprom? Yes, we recently added support for the next bigger version 25Q80EW, and I just pushed a patch for 25Q40EW [1]. With Git, you can fetch / apply it as follows: git fetch https://review.coreboot.org/flashrom refs/changes/62/25462/1 git cherry-pick FETCH_HEAD It's still untested, though. Nico [1] https://review.coreboot.org/25462/

1 0

Re: [flashrom] Can't Flash on AOpen i965GMt-LA motherboard
by Luc Verhaegen 29 Mar '18

29 Mar '18

On Wed, Mar 28, 2018 at 04:24:25PM +0200, Idwer Vollering wrote: > I took the liberty to submit this change to gerrit; > https://review.coreboot.org/#/c/flashrom/+/25396/ Please fix the author. Luc Verhaegen.

1 1

Re: [flashrom] Can't Flash on AOpen i965GMt-LA motherboard
by Luc Verhaegen 28 Mar '18

28 Mar '18

On Tue, Mar 20, 2018 at 12:22:02PM +0100, Björn Tantau wrote: > > > Am 19. März 2018 18:21:36 MEZ schrieb Luc Verhaegen <libv(a)skynet.be>: > >On Mon, Mar 19, 2018 at 05:01:06PM +0100, Björn Tantau wrote: > >> Am 19.03.2018 um 00:08 schrieb Luc Verhaegen: > >> > > >> >My current hypothesis: smsc at 0x480 > >> > > >> >Action required: 0x48E |= 0x10. > > > >> Do you want to scan for Super I/O sensors? (YES/no): Probing for > >Super-I/O at 0x2e/0x2f > >> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes > >> Found `Winbond W83627DHG Super IO Sensors' Success! > >> (address 0x290, driver `w83627ehf') > > > >Hrm. Perpendicular to what the bios that i got from AOpen tells me. > > > >Please mail a copy of your existing rom to me personally (exclude the > >flashrom ml, binary blobs should not go there). > > Here you go. Thanks for your help! Ok, this shows how rusty i am with respect to flashrom. Not recognizing the + 0x0C as the typical offset for intel gpio line toggle. What this board needs is a call to intel_ich_gpio20_raise(); Will provide a patch later today. I am a bit worried though that the lpc io BAR is empty in your lspci. I am not sure whether that is handled in any way, and i do not think the intel gpio code in flashrom will deal with an empty bar gracefully. Luc Verhaegen.

3 3

In situ Thinkpad E420 Sandy Bridge/Cougar Point PCH
by awokd 24 Mar '18

24 Mar '18

Having trouble getting a good read from a Macronix MX25L3206E in situ Thinkpad E420 Sandy Bridge/Cougar Point PCH. Don't believe it's a programmer problem because I used the same programmer and pinouts to successfully flash a Winbond W25Q32.V in a different system. I found the Wistron LLW-1/LGG-1 schematic and matched the flash chip up with the silk-screened label. Tried it in system with system power. I've pulled the board and RAM. Also tried removing CPU. Symptoms of the problem are: - On system power, doesn't detect chip. - Using an external PS, when I restrict the current to the point there's a vdroop to ~3.0v-3.2v, flashrom detects the chip. If I give it more current (at 3.3v), the chip disappears and flashrom no longer sees it. - Occasionally it acts like a successful read, WRSR updates correctly but resulting file is mostly FF with a section of pages of 00 and some with alternating bit patterns. Oddly, the file is consistent over multiple runs and diff reports no differences, but there is nothing in it that looks like actual data and ifdtool says there's no descriptor. Suspect the issue is as described on https://www.flashrom.org/ISP- that ME is getting powered and locking/hiding the chip. It suggests connecting the reset line to CS. Searching the schematic for RST results in numerous pages. How can I identify the right place to accomplish this, preferably without soldering? Alternatively, I see in the SPI programming guide there might be a couple other ways to disable ME? 1. Temporarily disable the Intel® ME through the MEBX. Power off or cold reset. - This option is only applicable to non-Intel ME Ignition firmware. 2. HDA_SDO(Manufacturing mode jumper or Flash descriptor override jumper) asserted HIGH on the rising edge of PWROK. Power off or cold reset. Note: this is only valid as long as you do not specifically set the variable Flash Descriptor Overrride Pin-Strap Ignore in the Flash Image Tool to false. I found #2 on the schematic with a not installed resistor (what does "DY" stand for anyways, "Damn You"?) but can't find the label for it on the motherboard and it looked like it would also need soldering beyond my capability. Any suggestions?

2 2

Re: [flashrom] Thinkpad T420
by Ivan Ivanov 22 Mar '18

22 Mar '18

Sorry for late reply. Yes, it looks like your connection is bad. Try using the shorter wires, and hopefully of a good quality ( e.g. pure copper wires could be 1.5 longer than the cheap aluminium wires and still have the same conductivity given the same internal thickness ) You have mentioned that you have updated the Bus Pirate firmware. To what version did you upgrade? I always recommend upgrading to the latest Bus Pirate community firmware (the old official one is dead) You could obtain it here - https://github.com/BusPirate/Bus_Pirate Alternatively, you may try a $3 very cheap CH341A USB programmer, which is also supported by flashrom project and has a much simpler hardware, i.e. it does not have the internal firmware, just a tiny EEPROM of 20 or 32 bytes size + 8 bit CFG register. The board of CH341A usb programmer is small and extremely simple, and the simplicity could be a key to success Best regards, Ivan 2018-03-17 14:31 GMT+03:00 <aadu(a)airmail.cc>: > > I apologise if I should write to flashrom mailing list instead and not you > directly. > > It was night when I wrote that message and I was tired. Bit more of what I > was doing. > > I was trying to do external flashing following instructions from coreboot > wiki. > I used command "sudo flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -r > filename", and I got: > Calibrating delay loop... OK. > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on > buspirate_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 part. Please include the flashrom > output with the additional -V option for all operations you tested (-V, -Vr, > -VE, -Vw), and mention which mainboard or programmer you tested. > Please mention your board in the subject line. Thanks for your help! > Read is not working on this chip. Aborting. > > Was that because it had bad connection or am I doing something really > stupid? > Then I used "flashrom -L" and it showed that T420 support was marked as > "BAD". > I bought Bus Pirate v3b and Pomona 5250 SOIC test clip. Have updated the Bus > Pirate firmware. > > Aadu >

1 0

Unsupported laptop - output
by Leya 21 Mar '18

21 Mar '18

Hello team Here's the output of flashrom on my machine, as well as my system information. I will of course not use it, I am sharing this based on your request in here https://www.flashrom.org/Board_Testing_HOWTO This is the manufacturer website https://www.acer.com/ac/en/US/content/support-product/5977?b=1 Let me know if you need further, Thank you, sudo flashrom -p internal flashrom p1.0-22-g0bfa819 on Linux 4.14.27-1-MANJARO (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). ======================================================================== 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. ======================================================================== Aborting. Error: Programmer initialization failed. inxi -Fx System: Kernel: 4.14.27-1-MANJARO x86_64 bits: 64 gcc: 7.3.0 Desktop: Xfce 4.12.4 (Gtk 2.24.31) Distro: Manjaro Linux Machine: Device: laptop System: Acer product: Aspire E5-573G v: V3.72 serial: N/A Mobo: Acer model: ZORO_BH v: Type2 - A01 Board Version serial: N/A UEFI [Legacy]: Insyde v: V1.15 date: 05/27/2015 Battery BAT1: charge: 33.1 Wh 100.0% condition: 33.1/37.0 Wh (90%) model: SANYO AL15A32 status: Full CPU: Dual core Intel Core i7-5500U (-MT-MCP-) arch: Broadwell rev.4 cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9580 clock speeds: max: 3000 MHz 1: 2794 MHz 2: 2718 MHz 3: 2738 MHz 4: 2940 MHz

1 0

Can't Flash on AOpen i965GMt-LA motherboard
by Björn Tantau 19 Mar '18

19 Mar '18

Hi! I tried to flash a new BIOS to my AOpen i965GMt-LA motherboard. Reading the ROM worked, but flashing did not. I'll gladly give you more information, just tell me what you need. :-) Cheers, Björn $ sudo flashrom --programmer internal -c "W39V040FA" -w IGC1B.BIN flashrom v0.9.9-rc1-r1942 on Linux 4.4.0-112-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH8M". Enabling flash write... OK. Found Winbond flash chip "W39V040FA" (512 kB, FWH) mapped at physical address 0x00000000fff80000. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x49, failed byte count from 0x00000000-0x00000fff: 0x463 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x49, failed byte count from 0x00000000-0x0000ffff: 0x463 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x49, failed byte count from 0x00000000-0x0007ffff: 0x60915 ERASE 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. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running.

4 7

copying flashrom from USB
by Shenol 18 Mar '18

18 Mar '18

Hello, I have mini laptop GPD ONE, I turned option USB off at boot, from BIOS and because laptop uses USB keyboard! I cannot enter BIOS. My only chance is flashing BIOS, however I only have a half working linux installation which does not connect to Wifi, so I cannot use apt to install flashrom. I tried copying it but I don't know how to copy depending libraries. Can I can copy the full program from USB? Sincerely, Shenol Mustafov -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com

2 1

will compatible chips flash?
by Jamie Stewart 18 Mar '18

18 Mar '18

I have flashrom 1.0 setup on a ubuntu box flashing with an intel 82558B NIC. I originally had a winbond W29EE512-p chip that has basically failed due to my SCSI2CF not consistently working and the fact flashrom won't "see" it. I luckily had an extra SCSI2CF device that was working and was able to read the contents of this flash to a file with flashrom. Looking for another W29EE512 chip seems rather difficult and was wondering if this chip from mouser will accept writing to it even though I haven't heard of GreenLiant GLS29EE512-70-4I-NHE and it makes no appearance on the supported list of flash chips. https://www.mouser.com/ProductDetail/Greenliant/GLS29EE512-70-4I-NHE?qs=sGAE piMZZMs6Aik9Fp479rd2sHbznrET1yc%2fcKK18Mo%3d Thanks so much for the info. Jamie

1 0

Re: [flashrom] Surface UEFI Bios flash
by Márton Miklós 18 Mar '18

18 Mar '18

> What chip? never heard that Microsoft would manufacture chips. According to this image: https://www.ifixit.com/Teardown/Microsoft+Surface+Pro+4+Teardown/51568#s112… it has a Winbond 25Q128FV SPI flash which is marked as tested in flashrom. Miklos

1 0

Spansion FL064PIF loader Tools
by Ikram dirujii 18 Mar '18

18 Mar '18

Hey Sir I have Digital Satellite Receiver Neosat 9900 Spectra with Flash IC Spansion FL064PIF .. I want to recover This Please Guid me how i can do it? With loader tools or with Programmer.. I'll be Very thankful to you Sir IKram dirujii

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom