- flashrom - mail.coreboot.org

Re: [flashrom] Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by Nico Huber 26 Jan '18

26 Jan '18

On 26.01.2018 08:41, The_Raven Raven wrote: > I think this is a bug with debian 9, with debian 8 it works without this > parameter. The only bug here is that flashrom doesn't choose a default by itself (or that we didn't tell people to set spispeed= from the very begin- ning). Currently, flashrom just leaves whatever the hardware is con- figured to, which may still work for different setups. You just don't know, and it works less likely now. So, patches are welcome. Nico

1 0

Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by The_Raven Raven 26 Jan '18

26 Jan '18

I think this is a bug with debian 9, with debian 8 it works without this parameter. Searched a long time for this solution, finally i found this report which helps me: https://github.com/flashrom/flashrom/issues/29 Now i see that Nico changed it in the wiki. -> https://flashrom.org/RaspberryPi Thanks! Too bad he changed it not a week ago, that would have me much time saved. ;-) Think you can change it from 1000 to 30000 because it is much much faster and works stable. Greets

1 0

Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by Mamoru Inugami 25 Jan '18

25 Jan '18

Thank you for your reply. I tried your suggestion, I could ientify my chip ! Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef, id2 0x16 Found Winbond flash chip "W25Q64.W" (8192 kB, SPI). Thank you for your kindly helps !

1 0

Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by The_Raven Raven 25 Jan '18

25 Jan '18

This is a problem (Bug) of raspi. Try this command: flashrom -V -p linux_spi:dev=/dev/spidev0.0,spispeed=30000

1 0

Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by Mamoru Inugami 25 Jan '18

25 Jan '18

Hi, I try to flash Winbond W25Q64FV via Raspberry Pi 3. Datasheet : http://www.alldatasheet.com/datasheet-pdf/pdf/555558/WINBOND/W25Q64FV.html It fails the same as 2016 post, "Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI)." https://mail.coreboot.org/pipermail/flashrom/2016-March/014548.html The attached file is output of flashrom 1.0 with -o option. If you have any help, please inform me.

1 0

Flashing MX 25L12873F on MSI board via Raspberry Pi SPI
by Fabian Köster 25 Jan '18

25 Jan '18

Hello list, I recently tried to update the BIOS of my MSI H87-G43 [1] from an usb disk using the "M-Flash" method. The update seemed to have succeeded, but now the board does not do anything at bootup anymore. No screen output, no beeping. At first, one of the LEDs (i guess HDD activity) blinked periodically, but after a few restarts it does not even do that anymore. After doing some research I found some guides abouting flashing the bios chip from outside. One article especially captured my interest, which described how to access the flash chip via the JSPI1 header on the mainboard from a Raspberry Pi [2]. I followed that guide, but I cannot manage to get a connection to the chip. I found out the used chip is a MX 25L12873F [3], but it is not listed as supported on [4], does this mean it will not work with Flashrom? Or is maybe something wrong with my wiring? In contrast to the description of the JSPI1 MSI connector on [5] the connector on my board has 12 pins, so I was a little bit confused. I am new to this topic and very thankful for any help! Regards Fabian [1] https://de.msi.com/Motherboard/H87-G43.html [2] https://forum-en.msi.com/index.php?topic=289550.0 [3] http://www.bios-chip24.com/MXIC-MX-25L12873F-M2I-10G-128MBit-SPI-Flash-SOIC… [4] https://www.flashrom.org/Supported_hardware [5] https://www.flashrom.org/MSI_JSPI1

3 12

CrOS flashrom compatibility and upstreaming of CrOS features
by Nico Huber 25 Jan '18

25 Jan '18

Hey folks, during review of commits that port per-region file arguments [1] from CrOS flashrom over here, we ran into a discussion about the command line interface changes. The basic question that arose is Do we want to maintain full CLI compatibility to CrOS flashrom? This would have the upside, that it would ease remerging of the two flashrom versions (in some unknown future). And anybody currently using CrOS flashrom could transition more smoothly. OTOH, depending on how the compatibility is achieved, it might increase the costs for review and development heavily (for a project with 0 spare resources). To not have to discuss this each and every time when some non-trivial feature is ported over from CrOS, I'd like to have some opinions, how valuable CLI compatibility is to you all and how we want to achieve it. I have currently some alternative ideas in mind that I'll sketch below. Feel free to add other ideas or just to comment them. 1) Integrate CLI changes from CrOS into flashrom proper's CLI. This turned out to be much harder than one might initially think: For the mentioned patches, it means that a lot of additional deve- lopment has to happen: * Restore internal behaviour in flashrom that became incompatible. * Add appropriate sanity checks for the arguments passed (yes, flashrom proper does such). * Discuss and review the additional code, too. It also restricts us to the design choices already made for CrOS flashrom and makes our review process kind of mindless. It does, however, get the job done, and everybody could just run `make` and wouldn't have to care if he's using one version of flashrom or the other. 2) Design our own interface for flashrom proper, but keep internal compatibility for an alternate CLI. It would allow us to make our own design choices at the interface level. A steady implementation might be much easier to accomplish if we keep things simple. Somebody would have to maintain an additional, CrOS compatible CLI. We could be more lax regarding to sanity checks in the alternate CLI, to speed up development. But, everybody already familiar with the CrOS flashrom CLI might get confused until he finds the alternative CLI. 3) Design our own implementation; provide compatibility with a wrapper script. The basic function of flashrom should be clear: read, write or verify the contents of a flash chip. Everything else (like com- bining multiple files in complex ways) shouldn't add unnecessary complexity to flashrom, and can likely be done in cleaner ways with other tools. In other words, we could try to keep flashrom more like a UNIX tool. IMHO, this would allow us to get new features in faster. If some- body sees a better way to implement a feature, we can just do it. Writing a wrapper script seems much easier too me than main- taining compatibility and safety in an unnecessary complex C program. Same as 2), people used to the other interface would have to learn a new one (or use the wrapper). So please let me know what you think, folks ;) Nico [1] 23021, 23022 and related 23353 in https://review.coreboot.org/

2 1

W25Q40.W Chip tested -> OK
by The_Raven Raven 24 Jan '18

24 Jan '18

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

1 0

Re: [flashrom] BIOS-Flash failed @ Asus A55BM-E
by Nico Huber 23 Jan '18

23 Jan '18

Hi Lukas, On 23.01.2018 10:02, Lukas Blacha wrote: > I have tryed to flash my BIOS via a Raspberry Pi. I have installed > flashrom via the apt-get repo. At the attachments you will find the > flashlog. you have to pass a reasonable speed (usually 1MHz to 30MHz, depending on your setup) via the spispeed parameter to linux_spi (see flashrom manpage and https://flashrom.org/FAQ). Nico

1 0

PLS add the chip WINBOND 25Q256FVFG to surport base
by 蔺红波 23 Jan '18

23 Jan '18

HI,the chip WINBOND 25Q256FVFG is not surported to your program.PLS add it .Thank you. Skywolflin.

2 1

BIOS-Flash failed @ Asus A55BM-E
by Lukas Blacha 23 Jan '18

23 Jan '18

Hello, I have tryed to flash my BIOS via a Raspberry Pi. I have installed flashrom via the apt-get repo. At the attachments you will find the flashlog. Thank you for your help. On Chip print: GigaDevice GD25B64BPIG Greetings from Germany Lukas

1 0

LE25FU406C Chip tested -> OK
by The_Raven Raven 23 Jan '18

23 Jan '18

Hi again Tested again with raspberry pi (linux_spi). All tests ok. Works fine. Greets

1 0

Pm25LD040(C) Chip tested -> OK
by The_Raven Raven 23 Jan '18

23 Jan '18

Hi I have tested Chip "Pm25LD040(C)" with Raspberry Pi (linux_spi). It is a "Pm25LD040" (without "C"). Chip works fine. Test Steps: - Readed - Erased - Written Data - Written Data1 (overwritten) Data and Data1 generated with "dd" from "/dev/urandom". Greets

1 0

Flash memory AT26SF081A
by Miloslav Semler 22 Jan '18

22 Jan '18

Hello, recently I wanted to flash AT26SF081A and it worked with same parameters like AT26DF081A, except that I had to modify ID of chip to 0x8501. Otherwise the programming of memory worked well. Can you add the chip to database. Thanks. Miloslav

1 0

Re: [flashrom] KabyLake Utilization of flashrom for BIOS update with two devices totalling 32MB.
by Nico Huber 22 Jan '18

22 Jan '18

Hello Simon, On 19.01.2018 16:23, Furlong, Simon wrote: > Can you help explain as two why the SPI region fails to program > (specifically due to the mmap failure)? the attempt to map the flash chip into flashrom's user-space is a very old relict that, I assume, doesn't apply to SPI programmers at all. It's likely that the mapping just fails because there is no contiguous 32MiB space at that address (IIRC, on Intel systems, at most 16MiB of the BIOS flash is memory mapped). You may find more information about why the mapping is rejected in your system log (e.g. dmesg). To get rid of the attempt to map, you'd have to patch and build flashrom by yourself. Here is a patch that might fix the issue for you [1]. If you use Git, you can simply check it out with the following commands: git fetch https://review.coreboot.org/flashrom.git refs/changes/44/23344/1 git checkout FETCH_HEAD Some information about build requirements can be found here [2]. Hope that helps, Nico [1] https://review.coreboot.org/23344/ [2] https://flashrom.org/Downloads

2 1

KabyLake Utilization of flashrom for BIOS update with two devices totalling 32MB.
by Furlong, Simon 19 Jan '18

19 Jan '18

Dear Flashrom, I looked to utilize the flashrom tool to program/update a BIOS for a Kabylake Intel Platform. We have two SPI devices for the When I have a simpler memory map for the BIOS regions, omitting the PDR from the second device the flashrom utility successfully programs the single 16MB file into the first device. However, in a more complex configuration where the PDR region is located in the second device and thus requiring a 32MB file, the programming fails.... The output log of the execution is below. Can you help explain as two why the SPI region fails to program (specifically due to the mmap failure)? Thanks is advance for your consideration, Simon #LOG output: flashrom v1.0 on Linux 4.9.60-std512-amd64 (x86_64) flashrom was built with libpci 3.4.1, GCC 5.4.0, little endian Command line (7 args): ./flashrom -V -p internal -w PB329108_both.bin -o output.txt Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string system-manufacturer: "Abaco Systems" DMI string system-product-name: "SBC329" DMI string system-version: "3A" DMI string baseboard-manufacturer: "Abaco Systems" DMI string baseboard-product-name: "SBC329" DMI string baseboard-version: "3A" Found chipset "Intel CM238" with PCI ID 8086:a154. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... BIOS_SPI_BC = 0xa88: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x0 (SPI) Top Swap: not enabled SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x89: BIOS Lock Enable: disabled, BIOS Write Enable: enabled SPIBAR = 0xf779d000 (phys = 0xfe010000) 0x04: 0xe804 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=1, SCIP=0, PRR34_LOCKDN=0, WRSDIS=1, FDOPSS=1, FDV=1, FLOCKDN=1 Warning: SPI Configuration Lockdown activated. Reading OPCODES... done OP Type Pre-OP op[0]: 0x00, read w/o addr, none op[1]: 0x00, read w/o addr, none op[2]: 0x00, read w/o addr, none op[3]: 0x00, read w/o addr, none op[4]: 0x00, read w/o addr, none op[5]: 0x00, read w/o addr, none op[6]: 0x00, read w/o addr, none op[7]: 0x00, read w/o addr, none Pre-OP 0: 0x00, Pre-OP 1: 0x00 0x06: 0x0100 (HSFC) HSFC: FGO=0, HSFC=0, WET=0, FDBC=1, SME=0 0x08: 0x00a29d8e (FADDR) 0x0c: 0x00000000 (DLOCK) DLOCK: BMWAG_LOCKDN=0, BMRAG_LOCKDN=0, SBMWAG_LOCKDN=0, SBMRAG_LOCKDN=0, PR0_LOCKDN=0, PR1_LOCKDN=0, PR2_LOCKDN=0, PR3_LOCKDN=0, PR4_LOCKDN=0, SSEQ_LOCKDN=0 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. 0x58: 0x0fff0a00 FREG1: BIOS region (0x00a00000-0x00ffffff) is read-write. 0x5C: 0x09ff0003 FREG2: Management Engine region (0x00003000-0x009fffff) is read-write. 0x60: 0x00020001 FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write. 0x64: 0x1fff1000 FREG4: Platform Data region (0x01000000-0x01ffffff) is read-write. 0x68: 0x00007fff FREG5: unknown region is unused. 0x6C: 0x00007fff FREG6: unknown region is unused. 0x70: 0x00007fff FREG7: unknown region is unused. 0x74: 0x00007fff FREG8: unknown region is unused. 0x78: 0x00007fff FREG9: unknown region is unused. 0x84: 0x00000000 (PR0 is unused) 0x88: 0x00000000 (PR1 is unused) 0x8C: 0x00000000 (PR2 is unused) 0x90: 0x00000000 (PR3 is unused) 0x94: 0x00000000 (PR4 is unused) 0x98: 0x00000000 (GPR0 is unused) 0xa0: 0x90 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=1 0xa1: 0xfe0000 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=6 0xa4: 0x0000 (PREOP) 0xa6: 0x0000 (OPTYPE) 0xa8: 0x00000000 (OPMENU) 0xac: 0x00000000 (OPMENU+4) Reading flash descriptors mapped by the chipset via FDOC/FDOD... done. === Content Section === FLVALSIG 0x0ff0a55a FLMAP0 0x00040103 FLMAP1 0x58100208 FLMAP2 0x00310330 --- Details --- NR (Number of Regions): 10 FRBA (Flash Region Base Address): 0x040 NC (Number of Components): 2 FCBA (Flash Component Base Address): 0x030 ISL (ICH/PCH Strap Length): 88 FISBA/FPSBA (Flash ICH/PCH Strap Base Address): 0x100 NM (Number of Masters): 3 FMBA (Flash Master Base Address): 0x080 MSL/PSL (MCH/PROC Strap Length): 3 FMSBA (Flash MCH/PROC Strap Base Address): 0x300 === Component Section === FLCOMP 0x325c0055 FLILL 0xad604221 FLILL1 0xc7c4b9b7 --- Details --- Component 1 density: 16 MB Component 2 density: 16 MB Read Clock Frequency: 17 MHz Read ID and Status Clock Freq.: 17 MHz Write and Erase Clock Freq.: 48 MHz Fast Read is supported. Fast Read Clock Frequency: 48 MHz Dual Output Fast Read Support: enabled Invalid instruction 0: 0x21 Invalid instruction 1: 0x42 Invalid instruction 2: 0x60 Invalid instruction 3: 0xad Invalid instruction 4: 0xb7 Invalid instruction 5: 0xb9 Invalid instruction 6: 0xc4 Invalid instruction 7: 0xc7 === Region Section === FLREG0 0x00000000 FLREG1 0x0fff0a00 FLREG2 0x09ff0003 FLREG3 0x00020001 FLREG4 0x1fff1000 FLREG5 0x00007fff FLREG6 0x00007fff FLREG7 0x00007fff FLREG8 0x00007fff FLREG9 0x00007fff --- Details --- Region 0 (Descr. ) 0x00000000 - 0x00000fff Region 1 (BIOS ) 0x00a00000 - 0x00ffffff Region 2 (ME ) 0x00003000 - 0x009fffff Region 3 (GbE ) 0x00001000 - 0x00002fff Region 4 (Platf. ) 0x01000000 - 0x01ffffff Region 5 (unknown) is unused. Region 6 (BIOS2 ) is unused. Region 7 (unknown) is unused. Region 8 (EC/BMC ) is unused. Region 9 (unknown) is unused. === Master Section === FLMSTR1 0xffffff00 FLMSTR2 0xffffff00 FLMSTR3 0xffffff00 --- Details --- FD BIOS ME GbE Pltf Reg5 Reg6 Reg7 EC Reg9 BIOS rw rw rw rw rw rw rw rw rw rw ME rw rw rw rw rw rw rw rw rw rw GbE rw rw rw rw rw rw rw rw rw rw Enabling hardware sequencing due to multiple flash chips detected. OK. The following protocols are supported: Parallel, LPC, FWH, Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Hardware sequencing reports 2 attached SPI flash chips with a combined density of 32768 kB. There is only one partition containing the whole address space (0x000000 - 0x1ffffff). There are 8192 erase blocks with 4096 B each. Found Programmer flash chip "Opaque flash chip" (32768 kB, Programmer-specific) mapped at physical address 0x00000000. 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0x01, id2 0x00, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F080, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F080T, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, 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 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for ESMT F49B002UA, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV040(A), 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0xffff, id2 0x00ff Probing for Eon EN29GL064(A)B, 8192 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 Eon EN29GL064(A)T, 8192 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 Eon EN29GL064H/L, 8192 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 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 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_jedec_common: id1 0x4c, id2 0x04, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400TC, 512 kB: probe_jedec_common: id1 0x4c, id2 0x04, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29LV160BE, 2048 kB: probe_jedec_common: id1 0x01, id2 0x00, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29LV160TE, 2048 kB: probe_jedec_common: id1 0x01, id2 0x00, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0x4c, id2 0x04, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0x4c, id2 0x04, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ISSI IS29GL064B, 8192 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 ISSI IS29GL064T, 8192 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 ISSI IS29GL064H/L, 8192 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 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F022(N)B, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F022(N)T, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29GL320EB, 4096 kB: probe_jedec_29gl: man_id 0x35, dev_id 0x7bb072, 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 0x35, dev_id 0x7bb072, 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 0x35, dev_id 0x7bb072, 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 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 MX29GL640ET, 8192 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 MX29GL640EH/L, 8192 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 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 0x4c, id2 0x24, 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 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, 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 0x00, id2 0x00, id1 parity violation, 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 0x00, id2 0x00, id1 parity violation, 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 0x00, id2 0x00, id1 parity violation, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF080, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x5d, id2 0xf4, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x01, id2 0x00, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, 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 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0x01, id2 0x00, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_jedec_common: id1 0x4c, id2 0x04, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BT, 512 kB: probe_jedec_common: id1 0x4c, id2 0x04, 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 0x4c, id2 0x24, 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 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x01, id2 0x00, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW080, 1024 kB: probe_82802ab: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0x01, id2 0x00, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29GL032CB, 4096 kB: probe_jedec_29gl: man_id 0x35, dev_id 0x7bb072, 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 0x35, dev_id 0x7bb072, 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 0x35, dev_id 0x7bb072, 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 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 W29GL064CT, 8192 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 W29GL064CH/L, 8192 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 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x8b, id2 0x44, 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 0x4c, id2 0x24, id1 is normal flash content, id2 is normal flash content Found Programmer flash chip "Opaque flash chip" (32768 kB, Programmer-specific). Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Error accessing Opaque flash chip, 0x2000000 bytes at 0xfe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip Opaque flash chip at 0xfe000000. Restoring PCI config space for 00:1f:5 reg 0xdc ######################################################## Simon Furlong Senior Staff Engineer/Technologist Abaco Systems Telephone: +44 (0) 1327 359444 Fax: +44 (0) 1327 322817 Direct Dial: +44 (0) 1327 322861 E-mail: simon.furlong(a)abaco.com Web: www.abaco.com Abaco Systems Ltd, registered in England and Wales (02151516 ) at Tove Valley Business Park, Old Tiffield Road, Towcester, Northamptonshire, NN12 6PF, VAT Reg No GB 927 559 189

1 0

Re: [flashrom] GPG signature on flashrom release
by Archange 19 Jan '18

19 Jan '18

Hi David, Thanks, I was able to retrieve the key and verify the signature. Maybe you add the information on the key used to sign on this page: https://www.flashrom.org/Downloads (which by the way is outdated as it refers to 0.9.9)? Also, note that the section regarding ArchLinux on this page should be updated to. I, Bruno Pagani, am the new maintainer of this package following retirement of Giovanni. Also the link should rather point to https://www.archlinux.org/people/trusted-users/#Archange than the maintainer package list. ;) Finally, please change “i686” to “x86_64” in the “package overview” link, since we dropped support for i686 distro-wide. Regards, Bruno On Thu, Jan 18, 2018 at 8:35 AM, David Hendricks <david.hendricks(a)gmail.com> wrote: > Hi Bruno, > Try again, it should be posted now (I used keys.gnupg.net > <http://keys.gnupg.net>). > > On Thu, Jan 11, 2018 at 9:44 AM, Archange <archange(a)archlinux.org > <mailto:archange@archlinux.org>> wrote: > > Hi, > > It seems that flashrom provides GPG sigs for the tarball, e.g. > http://download.flashrom.org/releases/flashrom-1.0.tar.bz2.asc > <http://download.flashrom.org/releases/flashrom-1.0.tar.bz2.asc>, > which is > nice. > > However, I seems I can’t find the key use to sign this on usual > keyservers. Could you tell me where it is available? > > Regards, > Bruno > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> > https://mail.coreboot.org/mailman/listinfo/flashrom > <https://mail.coreboot.org/mailman/listinfo/flashrom> > >

1 0

GPG signature on flashrom release
by Archange 18 Jan '18

18 Jan '18

Hi, It seems that flashrom provides GPG sigs for the tarball, e.g. http://download.flashrom.org/releases/flashrom-1.0.tar.bz2.asc, which is nice. However, I seems I can’t find the key use to sign this on usual keyservers. Could you tell me where it is available? Regards, Bruno

2 1

[Lenovo G505S] KB9012 EC controller patches for the latest flashrom
by Mike Banon 15 Jan '18

15 Jan '18

Hi Nico and Paul, and Lenovo G505S owners/developers, I have ported the patches by Paul Kocialkowski to the latest flashrom sources of master branch (earlier there were incompatibilities) -- making it possible to flash KB9012 EC controller [found in Lenovo G505S AMD coreboot-supported laptop (no AMD PSP backdoor!)] with the latest flashrom. Probed/read/erased/flashed/verified a few times, looks like its working perfectly :) Also, thanks to [v4,5/6] patch, now KB9012 is "hidden" and will never be probed for, unless explicitly specified by its chip name: -c "KB9012 (EDI)" or --chip "KB9012 (EDI)" . That should help to avoid the problems with other chips [v4,5/6] Add the hidden-from-probing chips category and make KB9012 hidden There are some chips like ENE KB9012, probing for which could cause the other chips to misbehave. Therefore, such chips should be "hidden" - not probed for unless the user wants This commit introduces a new field to the "flashchip" structure: int hidden; Now it is possible to "hide" any chip by adding this line .hidden = 1, to the "struct flashchip flashchips[]" structure of a chip, like .write = edi_chip_write, .read = edi_chip_read, .voltage = {2700, 3600}, .hidden = 1, }, flashrom will probe for a chip only if one of these conditions is true: 1) no chip has been specified AND this chip is not "hidden" 2) this chip has been specified by -c | --chip <chipname> All the patches could be reviewed by these links below, and it is possible to merge them sequentially: [v4,1/6] --> [v4,2/6] --> [v4,3/6] --> [v4,4/6] --> [v4,5/6] --> [v4,6/6] https://review.coreboot.org/#/c/flashrom/+/23258 [v4,1/6] Add support for selecting the erased bit value with a flag https://review.coreboot.org/#/c/flashrom/+/23259 [v4,2/6] ENE Embedded Debug Interface EDI and ENE KB9012 EC flashing support https://review.coreboot.org/#/c/flashrom/+/23260 [v4,3/6] ENE EDI - add dummy read to ensure proper detection of ENE chips https://review.coreboot.org/#/c/flashrom/+/23261 [v4,4/6] ENE EDI - print debug info like others while probing for ENE chips https://review.coreboot.org/#/c/flashrom/+/23262 [v4,5/6] Add the hidden-from-probing chips category and make KB9012 hidden https://review.coreboot.org/#/c/flashrom/+/23263 [v4,6/6] Add support for reading the current flash contents from a file Cheers, Mike On Wed, Jan 3, 2018 at 5:18 PM, Paul Kocialkowski <contact(a)paulk.fr> wrote: > Hi, > > Le mercredi 03 janvier 2018 à 15:34 +0300, Ivan Ivanov a écrit : >> Please tell - are there any real reasons why the Paul Kocialkowski's >> KB9012 support patches >> still cannot be merged? It is very discouraging - after 2 years of >> waiting to not see them at 1.0 >> Is there any way to get these patches merged, and maybe re-tag the >> flashrom 1.0 release ? > > We have been discussing about the future of these patches and they > cannot be accepted as-is today. Mostly, Nico was worried that issuing > SPI commands for the EDI protocol might cause some chips to misbehave if > these commands have another signification. I think this is a valid > concern. > > We agreed that one way to solve this would be to create groups for > probing, e.g. one with jedec-compliant chips (default) and one for ene > chips, so that only one group is probbed at the same time. > > I did not have the time to implement this idea yet, so it will block > kb9012 inclusion for now. If you'd like to go ahead and implement this > feature, I'd be happy to review your patches! > > Cheers, > > Paul > >> 2017-12-30 23:49 GMT+03:00 Ivan Ivanov <qmastery16(a)gmail.com>: >> > Hi Nico, please could you also merge the KB9012 patches by Paul >> > Kocialkowski : >> > >> > https://patchwork.coreboot.org/patch/4412/ >> > https://patchwork.coreboot.org/patch/4413/ >> > https://patchwork.coreboot.org/patch/4414/ >> > >> > It is ridiculous how these patches are still not merged , after >> > almost >> > 2 years... :P >> > These patches are adding the support for KB9012 reading / writing, >> > the only open source flashing solution for these embedded >> > controllers >> > >> > Merging these patches could accelerate the development of Origami EC >> > libre firmware, >> > please do it >> > >> > Best regards, >> > Ivan Ivanov > -- > Paul Kocialkowski, developer of free digital technology and hardware > support > > Website: https://www.paulk.fr/ > Coding blog: https://code.paulk.fr/ > Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/ > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom > >

1 0

LE25FU406C Chip tested -> OK
by The_Raven Raven 12 Jan '18

12 Jan '18

Hi I have tested Chip "LE25FU406C" (found on a HDD). Chip works fine. Test Steps: - Chip Erased - Written Data1 - Written Data2 Data generated with "dd" from "/dev/urandom". Greets

1 0

FAILED: GF8200A
by Steve Sanbeg 12 Jan '18

12 Jan '18

I tried just upgrading the bios on my GF8200A with one downloaded from http://www.ecs.com.tw/ECSWebSite/Product/Product_DOWNLOAD.aspx?DetailID=873… And got the following error: ---- steve@ultra ~/Downloads/bios $ sudo flashrom -p internal -w 78NA113.ROM flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-38-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "NVIDIA MCP78S". Enabling flash write... OK. Found Winbond flash chip "W25X80" (1024 kB, SPI) mapped at physical address 0x00000000fff00000. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00003f00! Expected=0xa1, Found=0xff, failed byte count from 0x00000000-0x000fffff: 0x5ec Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! --- I got a similar error trying to reload a backup I'd just made with flashrom -r. I then found another thread that mentioned to retry both the update & restore with the -VVV and -o options, so I retried twice, then retried the backup, but both also failed.

1 0

Misleading successful message if you do not specify option --image
by R. Diez 11 Jan '18

11 Jan '18

Hi all: The behaviour of option --image has changed between versions 0.9.9 and 1.0.0. In the past, I wasn't specifying any --image, and flashrom just flashed the one and only that I had defined in my layout file. Now, flashrom just states that the chip content is identical, which is not the case. This is the output: --------8<--------8<--------8<-------- flashrom v1.0 on Windows 6.1 (x86) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on ft2232_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Warning: Chip content is identical to the requested image. Erase/write done. --------8<--------8<--------8<-------- That is misleading. If the newer flashrom does not default to any image (or maybe to all images?), and the user specifies a layout file but not --image arguments, it should then fail with "no layout image specified" or a similar error message. Best regards, rdiez

2 3

Re: [flashrom] how to install
by Nico Huber 10 Jan '18

10 Jan '18

Hi, On 09.01.2018 17:19, Kenzho anandiya yudistiro wrote: > hi > > how to install flashrom on openwrt/lede? the packages its already on > openwrt/lede but it not working when I install it. you have to be much more specific. What command did you try? What error message did it return? Also, what does your setup look like, do you want to use a SPI interface of the board that runs LEDE or an external, e.g. USB, programmer? Nico

1 0

how to install
by Kenzho anandiya yudistiro 09 Jan '18

09 Jan '18

hi how to install flashrom on openwrt/lede? the packages its already on openwrt/lede but it not working when I install it. thank you for help

1 0

Re: [flashrom] Can you help me?
by Nico Huber 05 Jan '18

05 Jan '18

Hi, On 01.01.2018 22:42, Kārlis Magone wrote: > ... > 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. > ipj-System-Product-Name ~ # > > > The reason, why i am traying to update BIOS is that Linux before > installing said that i have pnpBios Fault. So i also cant to install > other OSes like Windows. So I have a problem. you should first try to find and use flashing tools provided by your mainboard vendor. The error you've seen from flashrom is most common when there is some kind of write protection implemented on your board (sometimes it's a physical jumper or switch, sometimes it's controlled by a GPIO of the southbridge or super-i/o chip). If you can't use your board vendor's tools, please tell what board you have exactly and send a full log taken with: flashrom -p internal -o logfile.txt Nico

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom