June 2025 - flashrom - mail.coreboot.org

HP 11MK G9EE - M44236-001 - "W25Q64JW...M"
by Tim Tech Oct. 20, 2025

Oct. 20, 2025

Hello, attached are two text documents: output from --wp-disable and output from erase/write - let me know if any other information is needed. Chip in question is "W25Q64JW...M" Thanks, Tim

2 5

Verification after write vs erase operations
by Anastasia Klimchuk Aug. 10, 2025

Aug. 10, 2025

Hello everyone, I want to bring into discussion a topic of verification of chip content which is performed after write or erase operations. Also for context prior discussion in this ticket: https://ticket.coreboot.org/issues/520 Currently we have a flag `-n` or `dont_verify_it` which is false by default. What the flag is doing is deciding whether verification needs to be performed after writing. The flag is false by default, so by default verification is happening after writing (which makes sense). Now the flag is only controlling write operation, and has no effect on erase operation. So for erase, the flag is ignored and verification is performed always. Just for context, it has always been like this. So for write operation we have a power option to say "ignore verification", and since it's false by default, the idea is, if you set it true then you know what you are doing. There is no such option for erase which seems a bit unfair. The two potential options to introduce equivalent option for erase are: 1) Add new flag `dont_verify_erase` (or some similar name) As a support for this option, it does not affect any existing use cases/scripts, and can be added any time. 2) Add coverage for erase operation under existing flag `-n` or `dont_verify_it` As a support for this option, erase operation can be seen as a variant of writing, since it does modify content of the chip, and so the fact it's not covered by the existing flag can be treated as a bug. What do people think about it? -- Anastasia.

2 2

Erase fails with flashrom using mtd
by Sakthipriya M July 29, 2025

July 29, 2025

Hi, We are using customised Elkhart lake board, when we tried to update BIOS using flashrom, following error is reported, "linux_mtd_erase: MEMERASE ioctl call returned -1, error: Input/output error". But sometimes we could update BIOS successfully. Chip size is 16MB, Flashrom erases successfully till 6MB and fails then Flashchip: Macronix MX25L12835F OS: GNU/LINUX Kernel: Tried in 6.12.5 and 6.14.2. Ensured that MTD kernel configurations are enabled. Flash chip is detected as "BIOS" in /dev/mtd0. Thanks, Sakthipriya M

2 4

release v1.6.0 and timeline
by Anastasia Klimchuk July 18, 2025

July 18, 2025

Good day everyone, We are planning to release v1.6.0 by the end of July. Planned dates are: 4th July: tagging v1.6.0-rc1 25th July: tagging the release v1.6.0 In between 4th and 25th we will be mostly testing, and only bugfixes will be merged. It's still fine to send any other (not a bugfix) patch and it can be reviewed, but it will be merged after the 25th (after release tagged). For more details, release process is described here: https://flashrom.org/dev_guide/release_process.html The patches which are already approved (4 of those currently) will be merged before the rc1. Any help with building/testing/bugfixing is very much appreciated! https://flashrom.org/how_to_support_flashrom.html#building-and-testing Most of the major updates on what's included in v1.6.0 are here https://flashrom.org/release_notes/devel.html however some of the updates are missing on that page. I will post later when full release notes are ready. -- Anastasia.

1 2

Problems detecting Winbond Flash with Flashrom
by KAISER Stefan (HELLA) July 14, 2025

July 14, 2025

INTERNAL & PARTNERS Hello, I tried to use Flashrom with a Winbond W25Q32JVSSSM, but it is not detecting it. "Found Unknown flash chip "SFDP-capable chip" (4096 kB, SPI) on linux_spi." Reading and Flashing works, but I need to have full support. I am running Flashrom on a raspberry. Is my above-mentioned device supported? Do you know why it is not detected? I have added the output of the -VV command. My version of flashrom is fresh compiled by a colleague from github mainline. Thank you!! Best regards Stefan KAISER Hardware Design Engineer Hardware Project Manager Stefan.Kaiser(a)forvia.com<mailto:Stefan.Kaiser@forvia.com> Hella GmbH & Co. KGaA Beckumer Str. 130 59552 - Lippstadt - Germany HELLA GmbH & Co. KGaA, Rixbecker Str. 75, 59552 Lippstadt, Germany, Handelsregister Amtsgericht / Commercial Register District Court Paderborn HRB 6857 Komplement?rin / General Partner: Hella Gesch?ftsf?hrungsgesellschaft mbH, Lippstadt (Amtsgericht / District Court Paderborn, HRB 5650) Gesch?ftsf?hrer der / Managing Directors of the Hella Gesch?ftsf?hrungsgesellschaft mbH: Bernard Sch?ferbarthold (Vorsitzender / CEO), Yves Andres, Stefan van Dalen, Stefanie Rheker, Philippe Vienney, J?rg Weisgerber Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Andreas Renschler 5acXjzUk

2 2

libflashrom updates
by Anastasia Klimchuk June 30, 2025

June 30, 2025

Good day everyone, There have been a few threads this year about libflashrom, this post gives a summary of what has been done - for people who are interested in using libflashrom or maybe already using it. # New API for progress callback `flashrom_set_progress_callback_v2` -> new API, supported from now on `flashrom_set_progress_callback` -> old and deprecated API. Still works for now, but will eventually be removed in future # New API for probing flashchips `flashrom_flash_probe_v2` -> new API, supported from now on `flashrom_flash_probe` -> old and deprecated API. Still works for now, but will eventually be removed in future # New API to get the list of supported programmers `flashrom_supported_programmers` -> brand new API # New API for logging `flashrom_set_log_callback_v2` -> new API, supported from now on `flashrom_set_log_callback` -> existing API which continues working and being supported. # New API to set log level `flashrom_set_log_level` -> brand new API, works with both versions of log callback There are more details and reasons for deprecation on the "Recent development" page https://flashrom.org/release_notes/devel.html#libflashrom-api-updates (this info will eventually go to release notes). Many thanks to people who contributed and reviewed this recent work on libflashrom: Dmitry Zhadinets, Peter Marheine, Sergii Dmytruk, and me (Anastasia Klimchuk). All of the updates will be included in the upcoming end of July v1.6.0 release. -- Anastasia.

1 0

Support for winbond 25Q128JV50?
by Andreas Schildbach June 13, 2025

June 13, 2025

Will flashrom be able to read/write a winbond 25Q128JV50, using a CH341A programmer? I notice the support list (flashchips/winbond.c) contains a couple of very similar names but not this exact name. If not, can it be made to read/write that chip just by adding another entry? Or is it possible that the CH341A can't do it? The chip is in a Lenovo X280 which I bricked just by enrolling my own secure boot key. Cheers, Andreas

3 3

[PATCH] flashchips: Add EN25QX128A
by Andranux June 10, 2025

June 10, 2025

I tested with an "ch341a" usb adapter. I was able to read, erase and write successfully. Change-Id: I89bcad8dee520bcab0df18fa094faba1b0ff3a1d Signed-off-by: Andranux <andreas_coding(a)gmx.de> --- flashchips/eon.c | 41 +++++++++++++++++++++++++++++++++++++++++ include/flashchips.h | 1 + 2 files changed, 42 insertions(+) diff --git a/flashchips/eon.c b/flashchips/eon.c index 921eb564..a167328a 100644 --- a/flashchips/eon.c +++ b/flashchips/eon.c @@ -1578,6 +1578,47 @@ .voltage = {2700, 3600}, }, + { + .vendor = "Eon", + .name = "EN25QX128A", + .bustype = BUS_SPI, + .manufacture_id = EON_ID_NOPREFIX, + .model_id = EON_EN25QX128A, + .total_size = 16384, + .page_size = 256, + /* supports SFDP */ + /* OTP: 512B total; enter 0x?? */ + /* QPI enable 0x38, disable 0xFF */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP | FEATURE_QPI, + .tested = TEST_OK_PREW, + .probe = PROBE_SPI_RDID, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 4096} }, + .block_erase = SPI_BLOCK_ERASE_20, + }, { + .eraseblocks = { {32 * 1024, 512} }, + .block_erase = SPI_BLOCK_ERASE_52, + }, { + .eraseblocks = { {64 * 1024, 256} }, + .block_erase = SPI_BLOCK_ERASE_D8, + }, { + .eraseblocks = { {16 * 1024 * 1024, 1} }, + .block_erase = SPI_BLOCK_ERASE_60, + }, { + .eraseblocks = { {16 * 1024 * 1024, 1} }, + .block_erase = SPI_BLOCK_ERASE_C7, + } + }, + .printlock = SPI_PRETTYPRINT_STATUS_REGISTER_BP3_SRWD, /* bit6 is quad enable */ + .unlock = SPI_DISABLE_BLOCKPROTECT_BP3_SRWD, + .write = SPI_CHIP_WRITE256, + .read = SPI_CHIP_READ, + .voltage = {2700, 3600}, + }, + { .vendor = "Eon", .name = "EN25S10", diff --git a/include/flashchips.h b/include/flashchips.h index 49ef8c7f..fb1be827 100644 --- a/include/flashchips.h +++ b/include/flashchips.h @@ -298,6 +298,7 @@ #define EON_EN25QH64 0x7017 #define EON_EN25QH128 0x7018 #define EON_EN25QH256 0x7019 +#define EON_EN25QX128A 0x7118 #define EON_EN25S10 0x3811 #define EON_EN25S20 0x3812 #define EON_EN25S40 0x3813 -- 2.49.0

2 1