- flashrom - mail.coreboot.org

Succesfully flashed GigaDevice GD25Q80(B) with ch341a_spi on AMD Radeon Pro W5700 (in situ with clip)
by Axel Drogoin 26 Apr '25

26 Apr '25

2 1

W25Q256JV_Q is checked
by works＠veghelyiattila.hu 26 Apr '25

26 Apr '25

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

Erase fails with flashrom using mtd
by Sakthipriya M 25 Apr '25

25 Apr '25

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

1 1

FAILED: HP Chromebook 11 G8 EE
by James Accuosti 24 Apr '25

24 Apr '25

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.

1 0

Reg: MEMERASE ioctl call returned -1, error: Input/output error
by Arvind GP 01 Apr '25

01 Apr '25

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

libflashrom questions
by Dmitry Zhadinets 29 Mar '25

29 Mar '25

Hi I'm writing some UI application based on libflashrom https://gitlab.com/dzhadinets/gflashrom I have some questions/suggestions: - how to obtain the list of programmers , as far as I see there is no any way to do it for now. Maybe using the log routine but it is definitely not the best way - could you add userdata to the callbacks you are calling . just a void* without any obligations - probing: in case of multiple chips it returns just an error about it. but there is no option to enumerate what was found. BTW relating to some previous thread. It would be great that libflasrom probe works like cli version (to probe everything but not only first 2) I will be happy to receive any advice. Looking forward to having progress api everywhere. Best regards Dmitry

3 6

Flashrom question regarding XMC25QH6A chip
by Eric Park 25 Mar '25

25 Mar '25

Hello! I have a device with a XMC25QH6A chip I'm trying to get a full image of. I came across this GitHub issue[1] and associated pull requests here[2] and here[3], but both pull requests were closed with a comment linking to a Gerrit patchset[4] that seems to no longer exist (or I do not have sufficient permissions to view). I commented on the original issue to ask the rationale behind closing the PRs and to perhaps seek some clarification on what the Gerrit patchset was about last year, but did not receive a response. I was under the impression that perhaps GitHub is not as closely monitored and I'd have better luck emailing the mailing list. If anyone would please comment on the status of this particular chip and what is blocking Flashrom from supporting it that would be greatly appreciated! - Eric [1]: https://github.com/flashrom/flashrom/issues/148 [2]: https://github.com/flashrom/flashrom/pull/150 [3]: https://github.com/flashrom/flashrom/pull/239 [4]: https://review.coreboot.org/c/flashrom/+/63900

2 2

Feature Request : Software SPI using gpio lines from sysfs or libgpiod (Issue #339)
by Pierre Colombier 24 Mar '25

24 Mar '25

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

linux_spi - spispeed not affecting erase/write speed - MT25QU01G
by Mathijs Van de Poel 17 Mar '25

17 Mar '25

Hello, We are using the driver to write to a MT25QU01G memory over SPI. I tried various speeds using the spispeed parameter but the erase/write times stayed the same. Any idea how I could improve this speed? time sudo flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=100000 -c "MT25QU01G" -E time sudo flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=100000 -w MT_file.bin -V -c MT25QU01G Spispeed Delete [min] Write [min] 16000 14 17 20000 13.5 15.43 25000 13.41 18.5 100000 14.4 17 Thank you in advance, Mathijs -- This email is private and confidential. If you are not the intended recipient, do not copy or disclose its content, but please contact the sender immediately. Open Cosmos Ltd is a company registered in England & Wales. Registration number: 09704443. Registered office: Electron Building, Fermi Avenue, Harwell, OX11 0QR.

1 0

ch341_spi - winbond 25Q128JVSQ - HUANANHI F8 MotherBoard
by Rogerio de Avila 16 Mar '25

16 Mar '25

Hi, I want to inform you that I successfully read/wrote a 25Q128JVSQ BIOS chip with Flashrom. Sorry, but I didn't write a log file. Here are the messages from the console. Thank you!!! --- sudo flashrom -p ch341a_spi -r backup_bios.bin flashrom unknown on Linux 6.8.0-55-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q128.V" (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. Thanks for your help! Reading flash... done. --- --- sudo flashrom -p ch341a_spi -w CX99DE45-F8-5567.ROM flashrom unknown on Linux 6.8.0-55-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q128.V" (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. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. --- Here are the messages with the verbose option: --- sudo flashrom -p ch341a_spi -v backup_bios.bin -V flashrom unknown on Linux 6.8.0-55-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). flashrom was built with GCC 13.2.0, little endian Command line (5 args): flashrom -p ch341a_spi -v backup_bios.bin -V Initializing ch341a_spi programmer Device revision is 3.0.4 The following protocols are supported: SPI. Probing for AMIC A25L010, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L016, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L020, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L032, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L040, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L05PT, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L05PU, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L080, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L10PT, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L10PU, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L16PT, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L16PU, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L20PT, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L20PU, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L40PT, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L40PU, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L512, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25L80P, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25LQ16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for AMIC A25LQ64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF021, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF021A, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF041A, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF081, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF081A, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF161, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF321, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF321A, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DF641(A), 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DL081, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DL161, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25DQ161, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x60, id2 0x60 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x60, id2 0x60 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x60, id2 0x60 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x60, id2 0x60 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x60, id2 0x60 Probing for Atmel AT25F512B, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25FS010, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25FS040, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25SF041, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25SF081, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25SF128A, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25SF161, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25SF321, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT25SL128A, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT26DF041, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT26DF081A, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT26DF161, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT26DF161A, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT26F004, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45CS1282, 16896 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB011D, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB021D, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB041D, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB081D, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB161D, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB321C, 4224 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB321D, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB321E, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel AT45DB642D, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Boya/BoHong Microelectronics B.25D16A, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Boya/BoHong Microelectronics B.25Q128AS, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for ESI ES25P16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for ESI ES25P40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for ESI ES25P80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for ESMT F25L008A, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for ESMT F25L32PA, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B05, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B05T, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B10T, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B16T, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B20T, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B32T, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B40T, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B64T, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25B80T, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25F05, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25F10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25F16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25F20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25F32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25F40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25F64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25F80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25P05, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25P10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25P16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25P20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25P32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25P40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25P64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25P80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25Q128, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25Q16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25Q32(A/B), 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25Q40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25Q64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25Q80(A), 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25QH128, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25QH16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25QH32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25QH64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25S10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25S16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25S20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25S32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25S40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25S64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon EN25S80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Fudan FM25F005, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Fudan FM25F01, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Fudan FM25F02(A), 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Fudan FM25F04(A), 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Fudan FM25Q08, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Fudan FM25Q16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Fudan FM25Q32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25B128B/GD25Q128B, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25LQ128C/GD25LQ128D/GD25LQ128E, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25LQ16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25LQ32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25LQ40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25LQ64(B), 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25LQ80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q127C/GD25Q128C, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q16(B), 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q20(B), 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q256D/GD25Q256E, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q32(B), 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q40(B), 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q512, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q64(B), 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25Q80(B), 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25T80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25VQ16C, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25VQ21B, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25VQ40C, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25VQ41B, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25VQ80C, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for GigaDevice GD25WQ80E, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for ISSI IS25LP064, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for ISSI IS25LP128, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for ISSI IS25LP256, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for ISSI IS25WP032, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for ISSI IS25WP064, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for ISSI IS25WP128, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for ISSI IS25WP256, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Intel 25F160S33B8, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Intel 25F160S33T8, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Intel 25F320S33B8, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Intel 25F320S33T8, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Intel 25F640S33B8, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Intel 25F640S33T8, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX23L12854, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX23L1654, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX23L3254, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX23L6454, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L12805D, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L1605, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L1635D, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L1635E, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L25635F/MX25L25645G, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L3205(A), 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L3235D, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L3233F/MX25L3273E, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L5121E, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L6405, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L6405D, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L6495F, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25R3235F, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25R6435F, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25U12835F, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25U1635E, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25U25635F, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25U3235E/F, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25U51245G, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25U6435E/F, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX25U8032E, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX66L51235F/MX25L51245G, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix MX66L1G45G, 131072 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P05-A, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P128, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25P80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PE10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PE20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PE40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M45PE10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M45PE20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M45PE40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q00A..1G, 131072 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q00A..3G, 131072 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q256..1E, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q256..3E, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q512..1G, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron/Numonyx/ST N25Q512..3G, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QL01G, 131072 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QU01G, 131072 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QL02G, 262144 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QU02G, 262144 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QU128, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QL128, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QL256, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QU256, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QL512, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Micron MT25QU512, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Nantronics N25S10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Nantronics N25S16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Nantronics N25S20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Nantronics N25S40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Nantronics N25S80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LD010(C), 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LD020(C), 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LD040(C), 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LD256C, 32 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LD512(C), 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LQ016, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LQ020, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LQ032C, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LQ040, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LQ080, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for PMC Pm25LV010A, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LV016B, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LV020, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LV040, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LV080B, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for SST SST25LF020A, 256 kB: compare_id: id1 0xef, id2 0x17 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for SST SST25VF010(A), 128 kB: compare_id: id1 0xef, id2 0x17 Probing for SST SST25VF016B, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25VF020, 256 kB: compare_id: id1 0xef, id2 0x17 Probing for SST SST25VF020B, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25VF032B, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25VF040, 512 kB: compare_id: id1 0xef, id2 0x17 Probing for SST SST25VF040B, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25VF040B.REMS, 512 kB: compare_id: id1 0xef, id2 0x17 Probing for SST SST25VF064C, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25VF080B, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25VF512(A), 64 kB: compare_id: id1 0xef, id2 0x17 Probing for SST SST25WF010, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25WF020, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25WF020A, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25WF040, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25WF040B, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25WF080, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25WF080B, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST25WF512, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST26VF016B(A), 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST26VF032B(A), 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST SST26VF064B(A), 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for ST M95M02, 256 kB: probe_spi_st95: id1 0xff, id2 0xffff Probing for Sanyo LE25FU106B, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FU206, 256 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FU206A, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW203A, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Sanyo LE25FW403A, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Spansion S25FL004A, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL008A, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL016A, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL032A/P, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL064A/P, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL127S-256kB, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL127S-64kB, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL128L, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL128P......0, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL128P......1, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL128S......0, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL128S......1, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL128S_UL Uniform 128 kB Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x18 0x00 0x00 0x00. Probing for Spansion S25FL128S_US Uniform 64 kB Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x18 0x00 0x00 0x00. Probing for Spansion S25FL129P......0, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL129P......1, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL132K, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL164K, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL204K, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL208K, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL256L, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL256S Large Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x18 0x00 0x00 0x00. Probing for Spansion S25FL256S Small Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x18 0x00 0x00 0x00. Probing for Spansion S25FL256S......0, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FL512S, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Spansion S25FS128S Large Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x18 0x00 0x00 0x00. Probing for Spansion S25FS128S Small Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x18 0x00 0x00 0x00. Probing for Winbond W25P16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25P32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25P80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q128.V, 16384 kB: compare_id: id1 0xef, id2 0x4018 Added layout entry 00000000 - 00ffffff named complete flash Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on ch341a_spi. Chip status register is 0x00. Probing for Winbond W25Q128.V..M, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q128.W, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q128.JW.DTR, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q16.V, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q16.W, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q20.W, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q256FV, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q256JV_Q, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q256JV_M, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q256JW, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q256JW_DTR, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q32.V, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q32.W, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q32JW...M, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q40.V, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q40BW, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q40EW, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q512JV, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q512NW-IM, 65536 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q64BV/W25Q64CV/W25Q64FV, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q64JV-.Q, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q64JV-.M, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q64.W, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q64JW...M, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q80.V, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q80BW, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25Q80EW, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25X05, 64 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25X10, 128 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25X16, 2048 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25X20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25X32, 4096 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25X40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25X64, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond W25X80, 1024 kB: compare_id: id1 0xef, id2 0x4018 Probing for XMC XM25QH64C, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for XMC XM25QU64C, 8192 kB: compare_id: id1 0xef, id2 0x4018 Probing for XMC XM25QH128C, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for XMC XM25QU128C, 16384 kB: compare_id: id1 0xef, id2 0x4018 Probing for XMC XM25QH256C, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for XMC XM25QU256C, 32768 kB: compare_id: id1 0xef, id2 0x4018 Probing for Zetta Device ZD25D20, 256 kB: compare_id: id1 0xef, id2 0x4018 Probing for Zetta Device ZD25D40, 512 kB: compare_id: id1 0xef, id2 0x4018 Probing for Unknown SFDP-capable chip, 0 kB: Parsing JEDEC flash parameter table... done. Probing for AMIC unknown AMIC SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for Atmel unknown Atmel SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for Eon unknown Eon SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for Macronix unknown Macronix SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for PMC unknown PMC SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for SST unknown SST SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for ST unknown ST SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for Generic unknown SPI chip (RDID), 0 kB: compare_id: id1 0xef, id2 0x4018 Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: id1 0xef, id2 0x17 Found Winbond flash chip "W25Q128.V" (16384 kB, SPI). This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). === 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! Verifying flash... VERIFIED. --- Best Regards, Rogério de Ávila

1 0

FAILED: Winbond flash chip "W25Q256JW_DTR"
by reza adinepour 10 Mar '25

10 Mar '25

Hi all, when i programm internally, chip doesn't programm and bellow message show: I try to disable WP using "--wp-disable" feature but it doesn't have effect on programm flash. thanks to help me. flashrom v1.6.0-devel (git:v1.5.0-19-g971ea27d) on Linux 6.9.3-76060903-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Cannot open file stream for /dev/mtd0 coreboot table found at 0x659fb000. Found chipset "Intel Meteor Lake-P/M". 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-0x00003fff) is read-write. FREG1: BIOS region (0x01000000-0x01ffffff) is read-write. FREG2: Management Engine region (0x00006000-0x00a69fff) is read-write. FREG3: Gigabit Ethernet region (0x00004000-0x00005fff) is read-write. FREG9: Device Expansion 2 region (0x00a6a000-0x00ffffff) is read-write. PR0: Warning: 0x01050000-0x01ffffff is read-only. PR1: Warning: 0x01000000-0x0100ffff 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 Winbond flash chip "W25Q256JW_DTR" (32768 kB, Programmer-specific) on internal. Disabled hardware protection Reading old flash chip contents... done. Updating flash chip contents... Transaction error between offset 0x01000000 and 0x01000000 (= 0x01000000 + 0)! Erase/write done from 0 to 1ffffff 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 IRC (see https://www.flashrom.org/Contact) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"!------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF!

2 1

old wiki website goes away in a month
by Anastasia Klimchuk 08 Mar '25

08 Mar '25

Hello people, This is the news: old wiki website wiki.flashrom.org goes away in one month. It still stays around for one month, in case someone needs to do something - migrate a doc to the new website, or download a doc, etc. Official website is flashrom.org It has been almost two years that wiki has that red deprecation banner on the top and was locked for editing. Now the time has come for the next step. For stats, during these two years we had: 47 documentation pages migrated to the new website, and their urls are already redirected to new website, and 63 pages were decided to be outdated and they will go away, If you disagree with the decision made on any of these 63 pages, it would be super helpful if you help to migrate that doc (wiki is still available for a month). You will need to commit to be the reviewer of the doc content. You can create the patch yourself (see https://flashrom.org/how_to_add_docs.html) or ask me, or post here on the list. But in any case, you will need to review the content. After one month, wiki will be gone, however it will stay on the web.archive.org (in fact, it's already there). So if you suddenly remember about some good old doc later, it can be pulled from the web archive and migrated (but see above). Important thing to say: these 47 pages did not migrate themselves. And while I did create most of the patches, each patch needs to be reviewed by someone who is not the owner of the patch. I want to say thank you so much to all the reviewers who put their effort in this, and reviewed old docs! <3 Also special thank you to Patrick Georgi and Stefan Reinauer who are our amazing infra admins and supported this two years long effort! <3 -- Anastasia.

1 0

unusual behaviour and message
by Frans Peens 07 Mar '25

07 Mar '25

. 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 07 Mar '25

07 Mar '25

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 06 Mar '25

06 Mar '25

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

Flashrom Write Verification Failure on Conga-TC570 (Intel Tiger Lake)
by ליאור סלמונה 06 Mar '25

06 Mar '25

*Dear Flashrom Developers,* I am experiencing an issue with *flashrom v1.1* on *Linux 5.15.86 (x86_64)* while attempting to flash a *Macronix MX25L25635E* SPI NOR flash chip on my *Conga-TC570* board, which features an *Intel® Core™ i5-1145GRE (Tiger Lake)* processor. *Issue Details:* - When the flash is *clean* (filled with 0xFF), I can *erase* and *write* successfully. - However, *verification fails*, reporting mismatched data. - The failure occurs *at address 0x00000000*, with the following error: FAILED at 0x00000000! Expected=0x11, found=0x00 Failed byte count from 0x000000 - 0x01FFFFF: 0x8DD2A6 *Steps Taken So Far:* 1. *Checked Write Protection* using flashrom -p internal --wp-status → No active protection. 2. *Attempted manual erase* before writing: flash_erase /dev/mtd0 0 0 flashrom -p internal -w bios.bin 3. *Loaded Intel SPI modules*: modprobe intel_spi_pci modprobe intel_spi_platform 4. *Verified SPI device detection*: ls /sys/bus/spi/devices/ The SPI device appears correctly. 5. *Tested alternative flashing methods*: - Using dd: dd if=bios.bin of=/dev/mtd0 bs=4096 Result: *Write completes, but verification still fails.* - Using flashrom -p internal -V for verbose output (logs available on request). *Questions:* 1. Is this a known issue with flashrom on *Tiger Lake* platforms? 2. Could the *Intel SPI controller* be interfering with writes? 3. Are there any debugging steps or patches I should try? Any guidance would be greatly appreciated. Thank you for your support! Best regards, *Lior Salmona*

2 1

This flash part has status UNTESTED for operations: WP
by Martin Gabriel Fleck 06 Mar '25

06 Mar '25

Hi, after using flashrom to flash coreboot to a Yanling device from Aliexpress, I came accross your message: ``` 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! ``` I was following the instructions of https://www.flashrom.org/contrib_howtos/how_to_mark_chip_tested.html You write "To see the examples of such patches, have a look at commit history of flashchips.c." Two confusions on my side, regarding this: #1 Looking at such commits, I see that flashchips.c is eddited in a line number much higher than the total line number of this file in my copy of the repo. (The version in my repo (latest main) contains 305 lines.) I'm confused by this. #2 My case seems to me: That I'm not marking an existing chip as tested. It seems to me I should be adding a completely new chip. Is there documentation for this as well? It seems to me my confusion #2 is because of confusion #1. In any case, I'd be happy to add the provided info in a patch / commit to your repo. I attached the logs of the operations I did (one log file per command). I hope you can clear up #1 above. Let me know how to continue from here. Kind regards, Martin Gabriel Fleck / Martin

2 1

flashrom's Hall of Fame
by Anastasia Klimchuk 02 Mar '25

02 Mar '25

Good day, We have created flashrom's Hall of Fame! We want to give credits to all the people who made contributions to flashrom over the years, and decades. The page pulls the info from the git history (which starts from January 2002!), and it is presented in two sections: Authors and Reviewers. Information is updated regularly (and by the script, no human needed). Everyone is very welcome to have a look and read! https://flashrom.org/about_flashrom/hall_of_fame.html I got this idea of pulling info from git history, and checked that git history goes back to Jan 2002 (perfect). But the idea might still be only in my head, if not Peter Marheine who actually implemented everything and made it work. Thank you! The main challenge was to make it work automatically, without humans needing to update the page. If anyone curious, here is the patch how it works: https://review.coreboot.org/c/flashrom/+/86350 We have these words at the entrance of the Hall, but I want to put it here in this post, too: flashrom is alive and running because of you all, the people who during all these years (and decades!) give their time, energy, knowledge, and a piece of their heart to flashrom. The project is what we all are creating together. *Thank you everyone so much!* -- Anastasia.

1 0

FAILED: Notebook NV4XMB,ME,MZ
by Master One 19 Feb '25

19 Feb '25

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 10 Feb '25

10 Feb '25

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

1 0

Support for ASM1166
by Master 07 Feb '25

07 Feb '25

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 01 Feb '25

01 Feb '25

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

probing logic in command line vs libflashrom
by Anastasia Klimchuk 28 Jan '25

28 Jan '25

Hello everyone, It turns out, flashrom has two different code paths for probing from command line vs probing with libflashrom. I think the logic should be the same, so as a goal I want to understand which approach is correct and use the same in both places. Have one piece of code and call it in two places. What is the difference: Command line keeps probing until the end of flashchips array, and as a result all matches will be found (no matter how many of them are). Currently code is on these lines: https://github.com/flashrom/flashrom/blob/main/cli_classic.c#L1211 Libflashrom only does probing twice, so at most two matches will be found. Currently code is on these lines: https://github.com/flashrom/flashrom/blob/main/libflashrom.c#L250 These two paths were initially introduced like this (>14 and >7yr ago). To me, command line's approach makes sense - because why stop at two matches? What if there are three matching chip definitions, and #3 is actually what the user has? So I am interested in what people think. A context how did this come up: I started working towards giving SFDP-detection more priority and this involves updating the probing logic, and that's how I came to this. -- Anastasia.

2 1

HP Compaq 8300 Elite - NVMe BIOS Update Error
by Manuel del Rey Carral 24 Jan '25

24 Jan '25

Dear flashroom.org friends. I am the owner of a HP Compact 8300 Elite Microtower and I tryed to follow the instructions of Paul Murana below, to modify the BIOS of my PC so that it allows the Start from a NVMe SSD. https://tachytelic.net/2022/01/hp-compaq-8300-nvme/ [https://tachytelic.net/wp-content/uploads/HP-Compaq-8300-Elite-NVMe.png]<https://tachytelic.net/2022/01/hp-compaq-8300-nvme/> Install and boot from an NVMe SSD on a HP Compaq Elite 8300 SFF - Tachytelic.net<https://tachytelic.net/2022/01/hp-compaq-8300-nvme/> Hola, intento implementar esto en un HP Z230 SFF, de momento no lo he probado, solo he encontrado las guías para poder hacerlo. Os adjunto 3 enlaces sobre como instalar NVMe M.2 pcie, reprogramando la bios por software (1 y 2) o, alternativamente, mediante un simple arranque alternativo del bios (3). tachytelic.net All good, but I've got an error in the very last step: flashing the corrected bin file (nvme.bin) . The error is: Error: Unknown chip 'MT25Q128' specified. The computer remainis ok, but the corrected BIOS could not be flashed. Any ideas of what migh have gone wrong? I previosly updated the BIOS to the version K01 v03 08 and installed a jumper cap into the FDO. You can find attached the outpot of the terminal log and below the Specs of my PC. I want to take the chance to give a big thanks to Pauli for his work and sharing his knowledge, and to you for yor kind sppport. Best Regards, Manuel dRC [cid:af5e4dfd-b870-4d4d-b9e7-c1a682be500f]

2 1

fbsd 14.1, flashrom 1.3.0_3 (fbsd pkg)
by Kurt Jaeger 22 Jan '25

22 Jan '25

Hi! flashrom-1.3.0_3 on FreeBSD 14.1 for pcengines APU1 seems to work with this command: flashrom -w apu1_v4.17.0.3.rom -c MX25L1605 -p internal:boardmismatch=force output: flashrom v1.3.0 on FreeBSD 14.1-RELEASE-p5 (amd64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 4, resolution: 70ns). coreboot table found at 0xdffdf000. Found chipset "AMD SB7x0/SB8x0/SB9x0". Enabling flash write... OK. Found Macronix flash chip "MX25L1605" (2048 kB, SPI) mapped at physical address 0x00000000ffe00000. === 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! This coreboot image (PC Engines:apu1) does not appear to be correct for the detected mainboard (PC Engines:APU). Proceeding anyway because user forced us to. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xe6f4 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Erase/write done. Verifying flash... VERIFIED. But it needs a power-cycle 8-( -- MfG/Best regards, Kurt Jaeger Now what ? Dr.-Ing. Nepustil & Co. GmbH fon +49 7123 93006-0 pi(a)nepustil.net Rathausstr. 3 mob +49 171 3101372 72658 Bempflingen

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom