April 2026 - flashrom - mail.coreboot.org

ZB25VQ128ASIG on Orange pi zero 3 v1.3.1
by Igor Ivascu April 26, 2026

April 26, 2026

Hi. log of ZB25VQ128ASIG on Orange pi zero 3 v1.3.1 : flashrom -p linux_spi:dev=/dev/spidev0.0

1 0

x99 motherboad && Fedora
by Augusto Silva April 17, 2026

April 17, 2026

Hi, i have tried do a bkp file from motherboard bios but this message occurs: root@fedora:/home/augusto/Downloads# sudo flashrom -p internal -r backup_bios.bin flashrom 1.4.0 on Linux 6.19.10-200.fc43.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Found chipset "Intel C610/X99 (Wellsburg)". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000 /dev/mem mmap failed: Operation not permitted FAILED! FATAL ERROR! Error: Programmer initialization failed. abr 17 19:17:48 fedora audit[20929]: AUDIT1101 pid=20929 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix acct="root" exe="/usr/bin/sudo" hostname=fedora addr=? terminal=/dev/pts/0 res=success' abr 17 19:17:48 fedora audit[20929]: AUDIT1123 pid=20929 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/augusto/Downloads" cmd=666C617368726F6D202D7020696E7465726E616C202D72206261636B75705F62696F732E62696E exe="/usr/bin/sudo" terminal=pts/0 res=success' abr 17 19:17:48 fedora sudo[20929]: root : TTY=pts/0 ; PWD=/home/augusto/Downloads ; USER=root ; COMMAND=/usr/sbin/flashrom -p internal -r backup_bios.bin abr 17 19:17:48 fedora audit[20929]: AUDIT1110 pid=20929 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname=fedora addr=? terminal=/dev/pts/0 res=success' abr 17 19:17:48 fedora sudo[20929]: pam_unix(sudo:session): session opened for user root(uid=0) by augusto(uid=0) abr 17 19:17:48 fedora audit[20929]: AUDIT1105 pid=20929 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=fedora addr=? terminal=/dev/pts/0 res=success' abr 17 19:17:48 fedora sudo[20929]: pam_unix(sudo:session): session closed for user root abr 17 19:17:48 fedora audit[20929]: AUDIT1106 pid=20929 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=fedora addr=? terminal=/dev/pts/0 res=success' abr 17 19:17:48 fedora audit[20929]: AUDIT1104 pid=20929 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname=fedora addr=? terminal=/dev/pts/0 res=success'

1 1

UNTESTED Chip successfully tested: "S25FL128P......0"
by Daniel (iPhone) April 11, 2026

April 11, 2026

Hello, I’m sharing a successful chip writing operation, that is marked as UNTESTED: Environment: Machine: MacBook Pro M1 2020 OS: macOS v15.7.5 Flashrom: "v1.7.0 on Darwin 24.6.0 (arm64)" (via homebrew) Programmer: "ch341a_spi" (v1.7) Chip: "S25FL128P……0” (Spansion FL128PIF 3.3v SOP16) Test summary : Successfully recognized the chip type. Successfully read. Successfully erase. Successfully write. Successfully compared flash file with post-writing reading file. Terminal details: April 11th 2026 … erasing chip. ... ds@Ds-MacBook-Pro flash % flashrom -p ch341a_spi -c “S25FL128P......0" -w flash.bin --progress flashrom v1.7.0 on Darwin 24.6.0 (arm64) flashrom is free software, get the source code at https://flashrom.org libusb: info [darwin_detach_kernel_driver] no capture entitlements. may not be able to detach the kernel driver for this device libusb: warning [darwin_detach_kernel_driver] USB device capture requires either an entitlement (com.apple.vm.device-access) or root privilege Cannot detach the existing USB driver. Claiming the interface may fail. LIBUSB_ERROR_ACCESS Found Spansion flash chip "S25FL128P......0" (16384 kB, SPI) on ch341a_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. You can also try to follow the instructions here: https://www.flashrom.org/contrib_howtos/how_to_mark_chip_tested.html Thanks for your help! Reading old flash chip contents... [READ: 100%]...done. Updating flash chip contents... [WRITE: 100%]...Erase/write done from 0 to ffffff Verifying flash... [READ: 100%]…VERIFIED. ds@Ds-MacBook-Pro flash % flashrom -p ch341a_spi -c "S25FL128P......0" -r read_post_write.bin --progress ds@Ds-MacBook-Pro flash % cmp flash.bin read_post_write.bin ds@Ds-MacBook-Pro flash % (identical files) —————————————————— Thanks! Best, Daniel

1 0

[RFC] cli: Auto-select programmer when only one non-default is compiled in
by Abdelkader Boudih April 11, 2026

April 11, 2026

Hi again, This need email since look like "behaviour change" , but we just entered 1.8.0. Here is the context: flashrom supports default_programmer_name for users who always use the same programmer. (it also a compile time default, not available in distro). That's not my workflow. I rotate between multiple USB programmers depending on signal quality or sockets i have handy. When flashrom is invoked without --programmer and no default is configured, it exits and lists all compiled programmers. That is correct when there is ambiguity. However, in many practical cases there isn't: • Exactly one supported USB programmer is physically connected. • Its VID/PID is known. • flashrom already has the identification logic inside each programmer driver. Yet the user must still specify -p. The proposal , and i already have the patch ready. When invoked without --programmer, flashrom should: 1. Enumerate connected USB devices. 2. Match them against the known programmer VID/PID entries. 3. If exactly one supported programmer is detected: • Auto-select it. • Print a clear informational message. • Proceed normally. This will ignore the internal programmer (we don't want read the bios of the host machine).. it will also not work for programmers like serprog or programmers that are compatible with others protocol (example hydrabus). Flashrom will become frictionless in that part: ``` $ flashrom -r dump.bin Detected programmer "ch341a_spi" ``` Manual override still works (to apply speed and other settings). Overall this approach could be wrong, because i did not try it with every programmer in the list + i could be missing some important details. Looking forward to get feed back so i open or no a gerrit patch. Regards Abdelkader

2 2

SFDP has autodetected a flash chip which is not natively supported by flashrom yet.
by Adam Wilber April 2, 2026

April 2, 2026

As requested, here is the verbose output from reading the flash on a D1 Mini ESP8266 board provided to me at CypherCon 9 as part of a CTF. SFDP parameter table header 0/1: ID 0x00, version 1.7 Length 64 B, Parameter Table Pointer 0x000030 Parsing JEDEC flash parameter table... 3-Byte only addressing. Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR. Write chunk size is at least 64 B. Flash chip size is 4096 kB. Block eraser 0: 1024 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 1024 x 4096 B with opcode 0x20. Block eraser 1: 128 x 32768 B with opcode 0x52 Block eraser 2: 64 x 65536 B with opcode 0xd8 done. SFDP parameter table header 1/1: ID 0x5e, version 1.0 Length 12 B, Parameter Table Pointer 0x000070 === 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! === Added layout entry 00000000 - 003fffff named complete flash Found Unknown flash chip "SFDP-capable chip" (4096 kB, SPI) on ch341a_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for Atmel unknown Atmel SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for Eon unknown Eon SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for Macronix unknown Macronix SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for PMC unknown PMC SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for SST unknown SST SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for ST unknown ST SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for Generic unknown SPI chip (RDID), 0 kB: compare_id: id1 0x5e, id2 0x4016 Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: id1 0x5e, id2 0x15 Found Unknown flash chip "SFDP-capable chip" (4096 kB, 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. You can also try to follow the instructions here: https://www.flashrom.org/contrib_howtos/how_to_mark_chip_tested.html Thanks for your help! Block protection is disabled. Reading flash... read_flash: region (00000000..0x3fffff) is readable, reading range (00000000..0x3fffff). done.

1 0