flashrom January 2023

flashrom@flashrom.org

23 participants
27 discussions

Intel Gemini Lake help pls
by Alice Venet 13 Jan '23

13 Jan '23

pls help i have this error what i can do? Warning: unexpected second chipset match: "Intel Gemini Lake" ignoring, please report lspci and board URL to flashrom(a)flashrom.org with 'CHIPSET: your board name' in the subject line. Found GigaDevice flash chip "GD25LQ128C/GD25LQ128D" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.

1 0

Unable to flash AT25SF641 on PC Engine APU2
by Jon Brabender 12 Jan '23

12 Jan '23

Hi, I've got a APU2.e PCB with a AT25SF641 for the serial flash (flash PN based on looking at the PCB). Trying to run flashrom (via a Debian live usb stick...I'm having no issues with APU2 booting accessing serial console) as follows yields a lot of output, but nothing useful...is this expected with a AT25SF641? Other people commenting on the interweb with the APUs seem to be seeing Winbond (and no issues) Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000 Any thoughts are greatly appreciated Jon flashrom -w apu2_v4.17.0.2.rom -p internal:boardmismatch=force flashrom v1.2 on Linux 5.10.0-20-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). coreboot table found at 0xcfec5000. Found chipset "AMD FCH". Enabling flash write... OK. Error accessing GD25Q256D, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip GD25Q256D at 0x00000000fe000000. Error accessing IS25LP256, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip IS25LP256 at 0x00000000fe000000. Error accessing IS25WP256, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip IS25WP256 at 0x00000000fe000000. Error accessing MX25L25635F/MX25L25645G, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MX25L25635F/MX25L25645G at 0x00000000fe000000. Error accessing MX25U25635F, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MX25U25635F at 0x00000000fe000000. Error accessing MX25U51245G, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MX25U51245G at 0x00000000fc000000. Error accessing MX66L51235F/MX25L51245G, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MX66L51235F/MX25L51245G at 0x00000000fc000000. Error accessing N25Q00A..1G, 0x8000000 bytes at 0x00000000f8000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q00A..1G at 0x00000000f8000000. Error accessing N25Q00A..3G, 0x8000000 bytes at 0x00000000f8000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q00A..3G at 0x00000000f8000000. Error accessing N25Q256..1E, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q256..1E at 0x00000000fe000000. Error accessing N25Q256..3E, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q256..3E at 0x00000000fe000000. Error accessing N25Q512..1G, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q512..1G at 0x00000000fc000000. Error accessing N25Q512..3G, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip N25Q512..3G at 0x00000000fc000000. Error accessing MT25QL01G, 0x8000000 bytes at 0x00000000f8000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QL01G at 0x00000000f8000000. Error accessing MT25QU01G, 0x8000000 bytes at 0x00000000f8000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QU01G at 0x00000000f8000000. Error accessing MT25QL02G, 0x10000000 bytes at 0x00000000f0000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QL02G at 0x00000000f0000000. Error accessing MT25QU02G, 0x10000000 bytes at 0x00000000f0000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QU02G at 0x00000000f0000000. Error accessing MT25QL256, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QL256 at 0x00000000fe000000. Error accessing MT25QU256, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QU256 at 0x00000000fe000000. Error accessing MT25QL512, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QL512 at 0x00000000fc000000. Error accessing MT25QU512, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip MT25QU512 at 0x00000000fc000000. Error accessing S25FL256S......0, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip S25FL256S......0 at 0x00000000fe000000. Error accessing S25FL512S, 0x4000000 bytes at 0x00000000fc000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip S25FL512S at 0x00000000fc000000. Error accessing W25Q256.V, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip W25Q256.V at 0x00000000fe000000. Error accessing W25Q256JV_M, 0x2000000 bytes at 0x00000000fe000000 /dev/mem mmap failed: Operation not permitted Could not map flash chip W25Q256JV_M at 0x00000000fe000000. Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) mapped at physical address 0x0000000000000000. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Error: Image size (8388608 B) doesn't match the flash chip's size (0 B)!

1 0

Comet Lake U, "-p internal" not available?
by Rafael Send 09 Jan '23

09 Jan '23

Hi, I'm trying to flash laptop that has an i7-10710u on it. From what I've been told, it's not officially supported yet but works if I build from source. I did so, but when I try running it I'm told "-p internal" is not a valid programmer. How can I use that method of programming on the latest master? I've used the internal programmer on previous versions / different boards so I aware of the risks and have methods of recovery, but I'd prefer to start with flashrom for ease of use. Thanks, Rafael

1 0

Error on W25Q80
by Bernd Van Praet 09 Jan '23

09 Jan '23

Hi, I’m getting following report: Calibrating delay loop... OK. Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00007000! Expected=0x76, Found=0xff, failed byte count from 0x00000000-0x000fffff: 0x2451 Your flash chip is in an unknown state. Please report this to the mailing list at flashrom(a)flashrom.org or on IRC (see https://www.flashrom.org/Contact for details), thanks! Kind regards, Bernd Van Praet

1 0

Reporting flash error
by Steve F Dembiske 06 Jan '23

06 Jan '23

Hi: As requested at the bottom of the bios flash, the following error was reported. Appreciate any help you can provide. Thank you, S. *Error*: $ sudo flashrom -p ch341a_spi -c MX25L3273E -w bios1_wl.img flashrom v1.2 on Linux 5.4.0-136-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Macronix flash chip "MX25L3273E" (4096 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00000200! Expected=0xde, Found=0xff, failed byte count from 0x00000000-0x003fffff: 0x20c290 Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks!

1 0

[announce] flashrom point releases v1.2.1, v1.1.1 and v1.0.2
by Nico Huber 05 Jan '23

05 Jan '23

Hi folks, I'm happy to announce that we finally got new point releases ready. The most important being v1.2.1 which updates the almost three-year- old v1.2. It's still in use by current OS distributions and some rot has already become visible: It has trouble to identify PCI devices when paired with an up-to-date libpci. Another quite important change is present in all three point releases: For reliable operation on the newer Intel platforms, increased timeouts in the `ich_spi` driver became necessary. Please refer to the full release notes [1-3] for more details. Tarballs and signatures [4] are available as usual on https://download.flashrom.org/releases/ One more, old hint for package maintainers: If you don't use Git and don't override flashrom's version string anyway, avoid the tarballs offered by tools like Cgit or Github. They don't contain any version information. Best regards, Nico [1] https://www.flashrom.org/Flashrom/1.2.1 [2] https://www.flashrom.org/Flashrom/1.1.1 [3] https://www.flashrom.org/Flashrom/1.0.2 [4] Signed with key 2853079C9C66AB7E82C64966A5C163B7E557CAEB

1 0

HP laptop
by A Smith 01 Jan '23

01 Jan '23

Hello. Program does not work with hp laptop. Thanks. -- *streetmack*

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom January 2023