flashrom January 2021

flashrom@flashrom.org

26 participants
30 discussions

Start a nNew thread

GD25Q10 - Flash Log
by Sean Rhodes 15 Jan '21

15 Jan '21

Please see the attached flash log as chip reported as untested.

1 0

Opinions on it87spi.c hack to support IT8686E?
by Pete Smith 09 Jan '21

09 Jan '21

Hi, I have a a GIGABYTE GA-H270N-WIFI motherboard with DualBIOS feature. Flashrom 1.2 is unable to select between the two flash chips with dualbiosindex parameter, as the Super I/O chip (ITE IT8686E) is unsupported: "Super I/O ID 0x8686 is not on the list of flash-capable controllers." In a naive attempt, I just tried to add the chip ID to the list: --- a/it87spi.c +++ b/it87spi.c @@ -256,6 +256,7 @@ int init_superio_ite(void) case 0x8718: case 0x8720: … [View More]

2 1

chipset Intel C226 is marked as untested
by Philippe Lefèvre 07 Jan '21

07 Jan '21

Hello, just curious about my ROM, I used flashrom to see what is in and would like, why not, replace it by a coreboot version, and let you know. It seems that it wouldn't work as enable flash write seems not working. My box is a DELL Precision T1700 Here is what I get : flashrom v0.9.9-r1954 on Linux 4.9.0-14-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "Intel C226". This chipset is marked as untested. … [View More]

1 0

Re: acer aspire 7750g
by Mohammed Salhi 06 Jan '21

06 Jan '21

Von meinem iPhone gesendet

1 0

Successfully tested flashrom linux_spi with FM25F02(A)
by André Plümer 05 Jan '21

05 Jan '21

Hello, if someone likes to update the wiki for FM25F02(A) :) Managed to read corrupted GT730 GPU-BIOS and write back original rom via raspberry pi 3 with rasbian buster. I had to git clone source + make + make install. apt-Version of flashrom (1.0) didn't know the FM25F02(A) flash-chip, but flashrom v1.2-174-g32f4cb4 worked. GPU now working again! I had to pad the original rom to fit the flash chip size. The Size in the error-message of flashrom was helpful for truncate-command (which in … [View More]

1 0

Please report this to flashrom@flashrom.org
by Matt Rixman 04 Jan '21

04 Jan '21

Hi, I'm the asker of this question: https://superuser.com/questions/1613342/why-do-windows-updates-make-linux-r… I was hoping to use `flashrom` to gather before/after dumps, which I can (hopefully) compare to get to the bottom of my problem. When I run: `sudo flashrom --programmer internal` I get this: --- begin output --- flashrom on Linux 4.19.0-13-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, … [View More]

2 1

w25q16jv
by Luis Martinez 03 Jan '21

03 Jan '21

need some help with erasing and writing to a w25q16jv . its not in the supported list but i was able to read from it by forcing it with a similar chip i force read using w25q16.v but i cant erase or write this is what it reads it at. Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: compare_id: id1 0xef, id2 0x7015 Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on linux_spi. Probing for Generic Variable Size SPI chip, 64 kB: Probing for Generic … [View More]

1 0

ps:
by msuzuqi＠posteo.net 03 Jan '21

03 Jan '21

By the way, PSU has just broken, right after I sent the previous email. Masaru Suzuqi

1 0

please check logs
by msuzuqi＠posteo.net 03 Jan '21

03 Jan '21

Hello, I have been failing to flash libreboot rom on a X200 with a Beaglebone external flashing. Please check logs and tell me what the cause do you think. I succeeded just once between the two logs. But this is not the first time succeeded. I mean I have been using the laptop for around a year with libreboot. thanks. Masaru Suzuqi -- To run a command as administrator (user "root"), use "sudo <command>". To become root use "sudo -i". See "man sudo_root" for details. trisquel@trisquel:~$… [View More]

1 0

Unhandled programmer parameters: dualbiosindex?
by Pete Smith 02 Jan '21

02 Jan '21

I'm trying to use flashrom 1.2 on a GIGABYTE GA-H270N-WIFI motherboard with DualBIOS feature. According to manpage, one can check which of the two flash chips is currently selected like this: flashrom -p internal:dualbiosindex This error message is shown instead: Unhandled programmer parameters: dualbiosindex Aborting. Error: Programmer initialization failed. If I don't specify the dualbiosindex parameter this message is shown: Found Programmer flash chip "Opaque flash chip" (16384 kB, … [View More]Programmer-specific) mapped at physical address 0x0000000000000000. No operations were specified. I'm also able to dump a valid copy of the firmware without problems, but I'm unable to control which of the two flash chips are being read (or written). flashrom -V -p internal:dualbiosindex ======================================================================= flashrom 1.2 on Linux 4.19.164_1 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.7.0, GCC 9.3.0, little endian Command line (3 args): flashrom -V -p internal:dualbiosindex Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer /sys/class/mtd/mtd0 does not exist No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "Gigabyte Technology Co., Ltd." DMI string system-product-name: "H270N-WIFI" DMI string system-version: "Default string" DMI string baseboard-manufacturer: "Gigabyte Technology Co., Ltd." DMI string baseboard-product-name: "H270N-WIFI-CF" DMI string baseboard-version: "x.x" Found ITE Super I/O, ID 0x8686 on port 0x2e Found chipset "Intel H270" with PCI ID 8086:a2c4. 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 = 0x00007fbbfbbcb000 (phys = 0xfe010000) 0x04: 0xe004 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=1, SCIP=0, PRR34_LOCKDN=0, WRSDIS=0, FDOPSS=1, FDV=1, FLOCKDN=1 SPI Configuration is locked down. Reading OPCODES... done 0x06: 0x3f00 (HSFC) HSFC: FGO=0, HSFC=0, WET=0, FDBC=63, SME=0 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: 0x0fff0200 FREG1: BIOS region (0x00200000-0x00ffffff) is read-write. 0x5C: 0x01ff0003 FREG2: Management Engine region (0x00003000-0x001fffff) is read-write. 0x60: 0x00020001 FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write. 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) 0xc4: 0xf3d82005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xc8: 0x20452045 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20 Enabling hardware sequencing because some important opcode is locked. OK. Unhandled programmer parameters: dualbiosindex Aborting. Error: Programmer initialization failed. Restoring PCI config space for 00:1f:5 reg 0xdc ======================================================================= Any ideas why this happens? Thanks. Best regards, Pete Smith [View Less]

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom January 2021