December 2025 - flashrom - mail.coreboot.org

ROM offset and Layout
by Xavier Jiang Dec. 13, 2025

Dec. 13, 2025

The board is AsRock B85M-ITX. The chip "died", whatever. I am trying to flash it. When I tried to flash the images, I get "Error: Image size (8392704 B) doesn't match the expected size (8388608 B)!" I went and found the use of uefiextract to "extract" images. What I found is that the Full size: 801000h (8392704)Header size: 1000h (4096)Image size: 300000h (3145728)Flags: 00010001h Which, if you do the math, 8392704 is exactly 4096 more than the 8388608. How would I flash this?

2 1

Unable to dump Macronix MX35LF1GE4AB
by pc_magas Dec. 13, 2025

Dec. 13, 2025

Hello I am trying to add Macronix `MX35LF1GE4AB` support upon flashrom. I am using a raspberrypi Zero W and its SPi driver to dump it. So far upon `flashchips/macronix.c` I placed: ``` { .vendor = "Macronix", .name = "MX35LF1GE4AB", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = MACRONIX_MX35LF1GE4AB, .total_size = 1024, .page_size = 256, .tested = {.probe = NT, .read = NT, .erase = NA, .write = NA, .wp = NA}, .probe = PROBE_SPI_RDID, .probe_timing = TIMING_ZERO, .write = 0, /* MX35LF1GE4AB is a flash chip but I could test only the reading */ .read = SPI_CHIP_READ, /* Fast read (0x0B) supported */ .voltage = {3000, 3600}, }, ``` Whilst on `include/flashchips.h` I set: ``` #define MACRONIX_MX35LF1GE4AB 0xC212 ``` And I compile it as: ``` meson setup builddir --wipe meson compile -C builddir meson test -C builddir meson install -C builddir ``` But `meson test -C builddir` throws error: ``` meson test -C builddir ninja: Entering directory `/home/pcmagas/flashrom/builddir' ninja: no work to do. 1/2 cmocka test flashrom FAIL 7.01s (exit status 255 or signal 127 SIGinvalid) >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 MALLOC_PERTURB_=86 MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MESON_TEST_ITERATION=1 /home/pcmagas/flashrom/builddir/tests/flashrom_unit_tests 2/2 flashrom client tests OK 0.67s Ok: 1 Expected Fail: 0 Fail: 1 Unexpected Pass: 0 Skipped: 0 Timeout: 0 Full log written to /home/pcmagas/flashrom/builddir/meson-logs/testlog.txt ``` How I can see what's wrong with the test? Also if I ingore the error of the test and proceed with the installation it is installed normaly. But once I try to dump the flash I get: ``` sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 flashrom v1.7.0-devel (git:v1.6.0-49-gf5bcb6d1) on Linux 6.12.47+rpt-rpi-v6 (armv6l) flashrom is free software, get the source code at https://flashrom.org No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. ``` The chip datasheet is upon: https://www.mxic.com.tw/Lists/Datasheet/Attachments/9075/MX35LF1GE4AB,%203V… Can you guide me what I am doing wrong?

2 1

Failed coreboot flash reran
by d.sunde＠tex-sun.net Dec. 11, 2025

Dec. 11, 2025

In a follow-up to my last email, I ran the flash again and got this message. flashrom v1.6.0 on FreeBSD 14.3-RELEASE-p5 (amd64) flashrom is free software, get the source code at https://flashrom.org coreboot table found at 0x76a14000. Found chipset "Intel Alder Lake-P". Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed. New value is 0x8b. SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. FREG1: BIOS region (0x00580000-0x00ffffff) is read-write. FREG2: Management Engine region (0x00001000-0x003aefff) is read-write. PR0: Warning: 0x00b00000-0x00ffffff is read-only. At least some flash regions are write protected. For write operations, you should use a flash layout and include only writable regions. See manpage for more details. OK. Found Macronix flash chip "MX25L12805D" (16384 kB, Programmer-specific) on internal. === 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... done. Updating flash chip contents... Transaction error between offset 0x00b04000 and 0x00b04000 (= 0x00b04000 + 0)! Erase/write done from 0 to ffffff Write Failed!Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Good, writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this to the mailing list at flashrom(a)flashrom.org or on chat channels (see https://flashrom.org/contact.html for details), thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. Should I reboot? Dave ------- Forwarded Message ------- From: d.sunde(a)tex-sun.net <d.sunde(a)tex-sun.net> Date: On Thursday, December 11th, 2025 at 4:28 PM Subject: Failed coreboot flash To: flashrom(a)flashrom.org <flashrom(a)flashrom.org> > I was attempting to update my protectli VP6650 while running opnsense with the command flashrom -p internal -w protectli_vp6600_v0.9.2.rom. The current coreboot is 0.9.0 and I tried updating to 0.9.2 but it gave me an error and says do not reboot. See below: > > flashrom v1.6.0 on FreeBSD 14.3-RELEASE-p5 (amd64) > flashrom is free software, get the source code at https://flashrom.org > > coreboot table found at 0x76a14000. > Found chipset "Intel Alder Lake-P". > Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed. > New value is 0x8b. > SPI Configuration is locked down. > FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. > FREG1: BIOS region (0x00580000-0x00ffffff) is read-write. > FREG2: Management Engine region (0x00001000-0x003aefff) is read-write. > PR0: Warning: 0x00b00000-0x00ffffff is read-only. > At least some flash regions are write protected. For write operations, > you should use a flash layout and include only writable regions. See > manpage for more details. > OK. > Found Macronix flash chip "MX25L12805D" (16384 kB, Programmer-specific) on internal. > === > 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... done. > Updating flash chip contents... Transaction error between offset 0x00b04000 and 0x00b04000 (= 0x00b04000 + 0)! > Erase/write done from 0 to ffffff > Write Failed!Uh oh. Erase/write failed. Checking if anything has changed. > Reading current flash chip contents... done. > Apparently at least some data has changed. > Your flash chip is in an unknown state. > Get help on chat (see https://flashrom.org/contact.html) or mail > flashrom(a)flashrom.org with the subject "FAILED: <your board name>"!--------------------------------------------------------- > ---------------------- > DO NOT REBOOT OR POWEROFF! > > What should i do at this point? This is my router. > > Thanks, > > Dave

1 0

Failed coreboot flash
by d.sunde＠tex-sun.net Dec. 11, 2025

Dec. 11, 2025

I was attempting to update my protectli VP6650 while running opnsense with the command flashrom -p internal -w protectli_vp6600_v0.9.2.rom. The current coreboot is 0.9.0 and I tried updating to 0.9.2 but it gave me an error and says do not reboot. See below: flashrom v1.6.0 on FreeBSD 14.3-RELEASE-p5 (amd64) flashrom is free software, get the source code at https://flashrom.org coreboot table found at 0x76a14000. Found chipset "Intel Alder Lake-P". Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed. New value is 0x8b. SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. FREG1: BIOS region (0x00580000-0x00ffffff) is read-write. FREG2: Management Engine region (0x00001000-0x003aefff) is read-write. PR0: Warning: 0x00b00000-0x00ffffff is read-only. At least some flash regions are write protected. For write operations, you should use a flash layout and include only writable regions. See manpage for more details. OK. Found Macronix flash chip "MX25L12805D" (16384 kB, Programmer-specific) on internal. === 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... done. Updating flash chip contents... Transaction error between offset 0x00b04000 and 0x00b04000 (= 0x00b04000 + 0)! Erase/write done from 0 to ffffff Write Failed!Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has changed. Your flash chip is in an unknown state. Get help on chat (see https://flashrom.org/contact.html) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"!--------------------------------------------------------- ---------------------- DO NOT REBOOT OR POWEROFF! What should i do at this point? This is my router. Thanks, Dave

1 0