July 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 28, 2025

July 28, 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

flashrom release v1.6.0 is out
by Anastasia Klimchuk July 24, 2025

July 24, 2025

Good day everyone, flashrom release v1.6.0 is out! Tarball: https://download.flashrom.org/releases/flashrom-v1.6.0.tar.xz Signature: https://download.flashrom.org/releases/flashrom-v1.6.0.tar.xz.asc Fingerprint: 6E6E F9A0 BA47 8006 E277 6E4C C037 BB41 3134 D111 Checkout from git repository at https://review.coreboot.org/flashrom.git (tag v1.6.0) Release notes published: https://flashrom.org/release_notes/v_1_6.html This is the work done during the 6 months since the previous release, and we had 50+ commits made by 18 authors. Thank you everyone so much for your contributions to flashrom, it is so cool to work with you all! <3 List of commits with full details/authors/reviewers can be inspected in git repo or in our mirror here: https://github.com/flashrom/flashrom/commits/main/?since=2024-12-06&until=2… -- Anastasia.

1 0

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