flashrom

flashrom@flashrom.org

5 participants
9161 discussions

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom