April 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

FAILED: HP Chromebook 11 G8 EE
by James Accuosti April 28, 2025

April 28, 2025

Greetings! I encountered an error updating the serial number for a chromebook. Per the error instructions, I am sending this message and it is telling me to not reboot or power off. Please let me know if you need more information. Thank you! -- CONFIDENTIALITY(NOTICE):This is a staff email account managed by Weston Public Schools. This e-mail message from the Weston Public Schools, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive information for the recipient, you are hereby notified that any review, use, disclosure, distribution, copying, printing, or action taken in reliance on the contents of this email is strictly prohibited. If you receive this communication in error, please, immediately contact the sender and destroy the material in its entirety. Please note that messages to or from the Weston Public Schools domain may be subject to the Freedom of Information Act (Conn. Gen. Stat. sections 1-200 et seq.) and/or the Federal Educational Rights and Privacy Act (20 U.S.C. § 1232g; 34 CFR Part 99). Thank you.

2 1

Succesfully flashed GigaDevice GD25Q80(B) with ch341a_spi on AMD Radeon Pro W5700 (in situ with clip)
by Axel Drogoin April 26, 2025

April 26, 2025

2 1

W25Q256JV_Q is checked
by works＠veghelyiattila.hu April 26, 2025

April 26, 2025

hi, I checked the PROBE - READ - ERASE - WRITE operations of the W25Q256JV_Q flash with J-Link and CH341 spi writers. the flashrom version was the newest development release at 2025-04-14 (#4d4688ccf132c580107b013d2d929a0816aa89c1) I made a little modification in the 'jlink_spi.c' source, because I use the power supply from the J-Link device pin 19. this power is 5V, I put a 3.3V LDO (HT7333) after it, and this LDO (and decoupling capacitors) need more time to fix output voltage. I attached the patch file. [ I tried to ask merge request via Jenkins, but it was too complicated for modify one char in the source ;-) ] my flash type was Winbond 25Q256JVEQ, which recognized by flashrom to W25Q256JV_Q or W25Q256FV, both type probed, read, wrote, erased, both modality worked fine. regards, Attila

2 1

Reg: MEMERASE ioctl call returned -1, error: Input/output error
by Arvind GP April 1, 2025

April 1, 2025

Hi All, We are trying to update the BIOS using the flashrom utility on the Elkhart Lake (LEC-EL) x86 platform, but we are facing the issue: "linux_mtd_erase: MEMERASE ioctl call returned -1, error: Input/output error" when running the flashrom tool. Please see below the attached error log for your reference. System Configuration: * Ubuntu 24.04 * Kernel Version: 6.13.7 NOTE: We have previously used this tool to upgrade and downgrade the BIOS without issues, but we are currently encountering this error. ERROR MESSAGE: $ sudo flashrom -p linux_mtd:dev=0 -w /home/adlink/Documents/LEC-EL_10710_FullImage/LEC-EL_10710.BIN -V flashrom v1.5.1 on Linux 6.13.7 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with GCC 13.3.0, little endian Command line (5 args): flashrom -p linux_mtd:dev=0 -w /home/adlink/Documents/LEC-EL_10710_FullImage/LEC-EL_10710.BIN -V Initializing linux_mtd programmer get_mtd_info: device_name: "BIOS", is_writeable: 1, numeraseregions: 0, total_size: 16777216, erasesize: 4096 Opened /dev/mtd0 successfully The following protocols are supported: Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Added layout entry 00000000 - 00ffffff named complete flash Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) on linux_mtd. Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific). Reading old flash chip contents... read_flash: region (00000000..0xffffff) is readable, reading range (00000000..0xffffff). done. Updating flash chip contents... erase_write: region (00000000..0xffffff) is writable, erasing range (00000000..0xffffff). linux_mtd_erase: MEMERASE ioctl call returned -1, error: Input/output error Erase/write done from 0 to ffffff Write Failed!Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... read_flash: region (00000000..0xffffff) is readable, reading range (00000000..0xffffff). done. Good, writing to the flash chip apparently didn't do anything. Please check the connections (especially those to write protection pins) between the programmer and the flash chip. If you think the error is caused by flashrom please report this to the mailing list at flashrom(a)flashrom.org or on IRC (see https://www.flashrom.org/Contact for details), thanks! Could you please suggest if any kernel configuration needs to be changed? We would appreciate your input. Thanks & Regards, Arvind G P.

1 0