February 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

Feature Request : Software SPI using gpio lines from sysfs or libgpiod (Issue #339)
by Pierre Colombier March 24, 2025

March 24, 2025

Hello, I am proposing the introduction of a new programmer type based on Bit-banging SPI using generic GPIO lines that are available on most SoCs. While there is existing support for linux_spi, creating a software-based SPI device using GPIOs currently involves complex configurations with the device-tree or sysfs, which can be quite cumbersome and technical. I noticed there is a file named bitbang_spi.c within the source that performs similar functionality. It might only be necessary to map the lower layer to the appropriate functions from libgpiod to achieve this and the most complicated may be the parsing of cmdline parameters. I initially considered writing a patch directly and contributing it to this project. However, given my limited familiarity with the current codebase structure, I am not very confident in my ability to implement this feature without guidance. Thank you for considering this Request. Best regards,

3 3

unusual behaviour and message
by Frans Peens March 7, 2025

March 7, 2025

. Hi Flashrom, I have a Winbond W25Q16 that i can read and write ok on raspberry pi 2b I've now tried the same process using a pi-400 and since now flashrom returns with unusual response(s) - writing and reading seems to work though..? (identical contents on rewrite) - btw : i am using WiringPi sysfs from bash to control the spi pins using a std 'bus pirate' ribbon to header cable here the flashrom response... Programming the SPI-Flash... flashrom unknown on Linux 6.6.51+rpt-rpi-v8 (aarch64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). === SFDP has autodetected a flash chip which is not natively supported by flashrom yet. All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually. You can help us by mailing us the output of the following command to flashrom(a)flashrom.org: 'flashrom -VV [plus the -p/--programmer parameter]' Thanks for your help! === Found Unknown flash chip "SFDP-capable chip" (2048 kB, SPI) on linux_spi. === This flash part has status UNTESTED for operations: WP 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! Reading old flash chip contents... done. Erasing and writing flash chip... Warning: Chip content is identical to the requested image. Erase/write done. Programming the SPI-Flash done. i tried 1/4 speed but no change then i performed (as suggested) flashrom -VV --programmer dummy - please see the attached file - and advise... Best Regards & Wishes frans .

4 4

S2430 or S24H30 Please help me
by Luca Bernardi March 6, 2025

March 6, 2025

Dear All, I'm new. I write in this list because I hope someone can help me. I need to read a S2430 or S24H30 EEprom from a car radio, but I'm trouble and so I ask if someone can help me. At the moment I have XGequ pro and T48 programmer but I have also a CoRight SkyPro Program suppose with EZ2019. I can buy also s new programmer, but I need to read the above chip. Someone can help me with my programmer or give me right information for a new programmer? regards Luca

2 1

Flashing Eon EN25Q32(A/B) with CH341A – Findings & Inquiry
by Jonathan Kendall March 6, 2025

March 6, 2025

Dear Flashrom Team, I wanted to share my experience and findings while working with flashrom to flash an Eon EN25Q32(A/B) SPI flash chip using a CH341A programmer with a SOIC clip. My goal was to flash SeaBIOS onto the chip as part of an experiment for a Lenovo ThinkPad T430u. Summary of My Process: 1. Successfully dumped and verified the original firmware using `flashrom -r`. 2. Encountered inconsistencies in chip detection, where it was sometimes identified as EN25Q64 (8MB) instead of EN25Q32 (4MB). 3. Managed to successfully erase and flash the chip by forcing the write process despite WP (Write Protection) warnings. 4. Verified the flashed BIOS integrity through multiple MD5 checksum comparisons. 5. Confirmed that the flashing was successful but experienced occasional inconsistencies with readback verification. Key Observations & Questions: - The CH341A programme sometimes fails to detect the chip or identifies it incorrectly. Could this be due to power delivery issues or specific quirks of the CH341A? - Write Protection messages were displayed, but forcing the flash succeeded. Does flashrom support unlocking this chip, or is WP handling dependent on external hardware? - Are there any recommended workarounds to improve stability and ensure more consistent reads/writes on this chip? - I would be happy to contribute testing logs if that would be useful for adding better support for this flash chip in future versions of flashrom. Thank you for your work on flashrom! Please let me know if any additional details would be helpful. Best regards, Jonathan Kendall

2 1

FAILED: Notebook NV4XMB,ME,MZ
by Master One Feb. 19, 2025

Feb. 19, 2025

Hello, I have been trying to convert my good old NovaCustom NV41MZ (11th Gen Intel) laptop to Dasharo (coreboot+UEFI) and although it has worked out at first, I now seem to be unable to flash an older firmware version or the backup that I made from the Original-Firmware. Please see the flashrom output here: https://paste.flashrom.org/view.php?id=3759 Now I'm afraid to turn the laptop off and don't know what to do next. Any idea what the problem may be? P.S. I'm using the flashrom version that the latest Dasharo Tools Suite comes with. Best wishes, -- Michael [PRIVACY] Digital signature and encryption of emails and files by OpenPGP is supported. [IMPORTANT INFORMATION] The content of this email and any attachments is confidential, potentially legally protected, and meant for the intended addressee exclusively. Should you not be the designated recipient, please delete this email and any attachments immediately, and notify the sender. Saving, forwarding or use of a misdirected email and any attachments is hereby prohibited explicitly, and may be unlawful. We assume no liability whatsoever for any possible disadvantage due to the data transmission over the Internet.

1 0

FAILED: PUJJOTEEN
by Antonio Hernandez Vega Feb. 10, 2025

Feb. 10, 2025

Hi, I was a problem in flash rom process. Can you help me, please?

1 0

Support for ASM1166
by Master Feb. 7, 2025

Feb. 7, 2025

Hello everyone, I hope you're doing fine ; - ) I am in the need to be able read and write the flash, under linux, of boards containing this component : ASM166 : https://www.asmedia.com.tw/product/45aYq54sP8Qh7WH8/58dYQ8bxZ4UR9wG5 through the PCIe bus. I have read a lot of stuff, but I may not be enough knowledgeable to sort out by myself where to start from to be able to add the support of this ASM1166 through the PCIe bus by myself. If someone is willing to help, I am willing to provide back what is necessary. Thanks in advance, Have a nice day Mickaël.

1 0

tested mainboard ASUS M2N-XE
by Mladen Milinkovic Feb. 1, 2025

Feb. 1, 2025

Hi I have tested reading and writing bios to mainboard ASUS M2N-XE. I have attached the relative logs. This were the command I've executed: flashrom --programmer internal --output backup.log -r backup.bin flashrom --programmer internal --output write-0211.log -w 0211.ROM Cheers -- Mladen Milinkovic GPG/PGP: EF9D9B26

1 0