- flashrom - mail.coreboot.org

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

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

14 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

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

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

01 Apr '25

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

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

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

06 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 27 Jan '25

27 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 23 Jan '25

23 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

Bugreport: ASUS PRIME X370-A "internal" programmer, Flash not detected
by Markus Rudolf 09 Jan '25

09 Jan '25

Hi, I have an ASUS PRIME X370-A and wanted to make a raw flash image of the BIOS chip, to no avail: root@ubuntu:~# flashrom -p internal flashrom unknown on Linux 6.8.0-41-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 chipset "AMD FP4". Enabling flash write... Disabling read write protection of flash addresses from 0xfc000000 to 0xfc05ffff failed. Disabling read write protection of flash addresses from 0xfd000000 to 0xfd05ffff failed. Disabling read write protection of flash addresses from 0xfe000000 to 0xfe05ffff failed. Disabling read write protection of flash addresses from 0xff000000 to 0xff05ffff failed. FCH device found but SMBus revision 0x61 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. See attached lspci dump! Seems to be a bug, hope it can be fixed, or is there something I overlooked? Markus

2 1

FAILED: Swanky Baytrail
by Chris Andrew 09 Jan '25

09 Jan '25

Hi, guys. I'm trying to update the firmware for my Toshiba Swanky. I've done this several times before, without issue, but have got an error, this time. Can you tell me what you may need, to help troubleshoot this? *My machine:* System: Host: swanky Kernel: 6.12.4-arch1-1 arch: x86_64 bits: 64 Desktop: Xfce v: 4.18.1 Distro: EndeavourOS Machine: Type: Laptop System: GOOGLE product: Swanky v: 1.0 serial: 5F239563C Mobo: GOOGLE model: Swanky v: 1.0 serial: N/A UEFI: coreboot v: MrChromebox-4.22.4 date: 04/16/2024 Battery: ID-1: BAT0 charge: 33.1 Wh (97.6%) condition: 33.9/44.2 Wh (76.7%) CPU: Info: dual core model: Intel Celeron N2840 bits: 64 type: MCP cache: L2: 1024 KiB *The command I used, today:* [chris@swanky ~]$ cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh *Some of the output:* 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). Skipping writeprotect-based unlocking for read/verify operations. Block protection is disabled. Reading ich descriptor... read_flash: region (00000000..0x7fffff) is readable, reading range (00000000..0x000fff). done. Assuming chipset 'Baytrail'. Added layout entry 00000000 - 00000fff named fd Added layout entry 00200000 - 007fffff named bios Added layout entry 00001000 - 001fffff named me Using region: "bios". coreboot last image size (not ROM size) is 8388608 bytes. Manufacturer: Google Mainboard ID: Swanky This coreboot image matches this mainboard. spi_read_register: read from register 2 not supported by programmer I hope this helps, Chris (chris_debian)

2 1

Re: BIOS update fails on a Minix Z100-0db device
by Robert 07 Jan '25

07 Jan '25

Thank you Alex, this is very useful info. So if I am on 0161 now, do I have to go 0171 then 0181 then 0191? One more question: how do I back up the product key exactly? I already tried to update to 0181 with flashrom, but that failed, then reverte to 0161 with flashrom that succeeded. I hope I did not erase the product key? regards, Robert On Mon, 2025-01-06 at 11:25 +0800, Alex Lui wrote: > Dear Robert, > > Many thanks for contacting us. > > What is the currently BIOS version (project version) on NEO Z100-0dB? > When booting, press the "DEL" key repeatedly to enter the BIOS > homepage. See attached pic. > > AD0J0151 or AD0J0161 cannot be directly updated to AD0J0181 or > AD0J0.191 in UEFI. It must be updated to AD0J0.171 first. > > AD0J0171 BIOS for Z100-0dB can be downloaded from link below: > https://mega.nz/file/fvRkSIgJ#riNMb_bjsuTePo_l0Co1aWsCLTZTVAbNAw1j3vQC5WQ > > File name: Z100-0dB-BIOS-171_UEFI.zip > File size: 18.4 MB > > AD0J0181 BIOS update under UEFI for Z100-0dB can be downloaded from > link below: > https://mega.nz/file/T64FwaDR#Ic4a69ntKaoF2RrXLDcMM94x1Gt1YYkezWPediBWXtY > > Please note: Please back up the product key when updating BIOS under > UEFI, as this will erase the product key stored in the BIOS. > > Look forward to hearing from you soon. > > Best Regards, > Alex Lui > > Minix Group Company Limited > Minix Forum: https://theminixforum.com > > > > -----Original Message----- > From: Robert [mailto:openbsd@openbsd.hu] > Sent: Sunday, January 5, 2025 2:44 AM > To: support(a)minix.com.hk; flashrom(a)flashrom.org > Cc: openbsd(a)openbsd.hu > Subject: BIOS update fails on a Minix Z100-0db device > > > Hi guys, > > I tried to update the BIOS on my Minix Z100-0db device so that I can > boot a Linux UEFI from the NVME disk. Pls. see below: > > 1. As per > https://theminixforum.com/index.php?threads/guide-updating-bios-uefi-using-… > I downloaded the newest image for Minix:AD0J0181.bin > (well download zip, decompress) > 2. I booted the device from an archlinux install USB and copied the > new image there so I can access it > 3. I installed flashrom to the arch install OS (pacman -S flashrom), > the version is 1.5.1-1, compiled Dec 20 2024 4. I made a backup of > the current version: flashrom -p internal -c > "Opaque flash chip" -r my_backup_bios_AD0J0161.bin ... so far so > good .. > 5. I attempted to upload the new binary: flashrom -p internal -c > "Opaque flash chip" -w my_backup_bios_AD0J0161.bin > > issue follows: > > Opened /dev/mtd0 successfully > Found programmer flash chip "Opaque flash chip" > linux_mtd_wp_read_cfg: ioctl Operation not supported Failed to unlock > flash status reg with wp support. > Reading old flash chip contents... done. > Updating flash chip contents... linux_mtd_erase: MEMERASE ioctl call > returned -, 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... done. > Apparently at least some data has changed. > Your flash chip is in an unknown state. > Get help ... > > Retried with -f, which in turn again changed something, but same > outcome. > I did not try to put back the original image so far, it would > probably give me the same > > The device is still on sitting in the arch install shell, I increased > the install disk size and added a few packages to help with the > possible fix, since I believe if I would try to reboot, the device > would be lost, and I would likely have to replace it. > > I am a long time linux user, can try any workaround or optionally > even allow ssh access to the device. > Can someone please give me some hints about where to go from here. > > Appeciate your time, > Robert

2 2

Intel Corporation 82599ES - read success
by Jared Mauch 07 Jan '25

07 Jan '25

Had to boot kernel w/ iomem=relaxed for a read to work $ sudo builddir/flashrom -p nicintel_spi:pci=81:00.0 -r W25X40-81-00-0.bin --progress flashrom v1.6.0-devel (git:v1.5.0-10-g2e6b0510) on Linux 6.1.0-29-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === Found Winbond flash chip "W25X40" (512 kB, SPI) on nicintel_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 flash... [READ: 100%]...done. 81:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) Subsystem: Super Micro Computer Inc AOC-STGN-i2S Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 30 NUMA node: 1 IOMMU group: 13 Region 0: Memory at faf80000 (64-bit, prefetchable) [size=512K] Region 2: I/O ports at f020 [size=32] Region 4: Memory at fb404000 (64-bit, prefetchable) [size=16K] Expansion ROM at fbe80000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: ixgbe Kernel modules: ixgbe 81:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) Subsystem: Super Micro Computer Inc AOC-STGN-i2S Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin B routed to IRQ 340 NUMA node: 1 IOMMU group: 14 Region 0: Memory at faf00000 (64-bit, prefetchable) [size=512K] Region 2: I/O ports at f000 [size=32] Region 4: Memory at fb400000 (64-bit, prefetchable) [size=16K] Expansion ROM at fbe00000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: ixgbe Kernel modules: ixgbe -- Jared Mauch | pgp key available via finger from jared(a)puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.

1 0

BIOS update fails on a Minix Z100-0db device
by Robert 04 Jan '25

04 Jan '25

Hi guys, I tried to update the BIOS on my Minix Z100-0db device so that I can boot a Linux UEFI from the NVME disk. Pls. see below: 1. As per https://theminixforum.com/index.php?threads/guide-updating-bios-uefi-using-… I downloaded the newest image for Minix:AD0J0181.bin (well download zip, decompress) 2. I booted the device from an archlinux install USB and copied the new image there so I can access it 3. I installed flashrom to the arch install OS (pacman -S flashrom), the version is 1.5.1-1, compiled Dec 20 2024 4. I made a backup of the current version: flashrom -p internal -c "Opaque flash chip" -r my_backup_bios_AD0J0161.bin ... so far so good .. 5. I attempted to upload the new binary: flashrom -p internal -c "Opaque flash chip" -w my_backup_bios_AD0J0161.bin issue follows: Opened /dev/mtd0 successfully Found programmer flash chip "Opaque flash chip" linux_mtd_wp_read_cfg: ioctl Operation not supported Failed to unlock flash status reg with wp support. Reading old flash chip contents... done. Updating flash chip contents... linux_mtd_erase: MEMERASE ioctl call returned -, 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... done. Apparently at least some data has changed. Your flash chip is in an unknown state. Get help ... Retried with -f, which in turn again changed something, but same outcome. I did not try to put back the original image so far, it would probably give me the same The device is still on sitting in the arch install shell, I increased the install disk size and added a few packages to help with the possible fix, since I believe if I would try to reboot, the device would be lost, and I would likely have to replace it. I am a long time linux user, can try any workaround or optionally even allow ssh access to the device. Can someone please give me some hints about where to go from here. Appeciate your time, Robert

1 0

flashrom
by rik Hendrickx 30 Dec '24

30 Dec '24

hi, i work together for a school in Gambia, now we got some older chrome laptops and i installed other OS on it but with only one i need some other flash program to succeed , meaby Flasrom can do it ? laptop specs HP Chromebook 14 Nyan blaze 32 bit ARM where can i download flashrom ? Or can you give me advice or links ? Best Regards Rik

1 0

flashrom point release v1.5.1 is out
by Anastasia Klimchuk 22 Dec '24

22 Dec '24

Good day everyone, We have one more release this year (this is the last one of this year, for sure :)). It contains one bug fix for the bug which was introduced in v1.5.0. Bug fix is also merged into the main branch, so building from the latest source works too. Details: Users with older Intel-based platforms (Broadwell/Braswell and earlier) flashing using the internal programmer option might encounter an ‘Invalid OPCODE’ error when erasing/writing which would lead to an incomplete flash and potentially a bricked device. External flashing was not affected at all. Ticket: https://ticket.coreboot.org/issues/573 Patch: https://review.coreboot.org/c/flashrom/+/85612 Release notes: https://flashrom.org/release_notes/v_1_5.html#version-v1-5-1 Git tag: v1.5.1 (in branch 1.5.x) Tarball: https://download.flashrom.org/releases/flashrom-v1.5.1.tar.xz Signature: https://download.flashrom.org/releases/flashrom-v1.5.1.tar.xz.asc Fingerprint: 6E6E F9A0 BA47 8006 E277 6E4C C037 BB41 3134 D111 Thanks heaps to people who helped to do v1.5.1 to get it ready before holidays break! <3 I wish everyone a nice and happy holidays time. -- Anastasia.

1 0

Reg:libmtd: error!: MEMERASE64 ioctl failed for eraseblocks (mtd0)
by Arvind GP 16 Dec '24

16 Dec '24

Hi All, We are trying to implement the flashrom tool utility on the x86 Elkhart Lake(LEC-EL) platform. In this case, we are facing an issue when trying to erase the BIOS device MTD0. There are 4096 erase blocks available in the mtd0 device, but only 1791 erase blocks we can erase; the remaining blocks are throwing errors, and it shows MEMERASE64 IOCTL FAILED. Please see the below error message and MTD0 device info for your reference. NOTE: Sometimes it works; we can erase the MTD0 device without any error, and we can upgrade/downgrade the BIOS. ERROR MESSAGAE: #sudo flash_erase /dev/mtd0 0 0 Erasing 16384 Kibyte @ 0 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 0 (mtd0) error 524 (Unknown error 524) flash_erase: error!: Entering into mtd_erase_multi flash_erase: error!: /dev/mtd0: MTD Erase entire chip failureTrying one by one each sector. error 524 (Unknown error 524) Erasing 4 Kibyte @ 700000 -- 43 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 1792 (mtd0) error 5 (Input/output error) flash_erase: error!: /dev/mtd0: MTD Erase failure error 5 (Input/output error) Erasing 4 Kibyte @ 700000 -- 43 % complete cnt 4096 MTD0 INFO:(sudo mtdinfo /dev/mtd0) Name: BIOS Туре: nor Eraseblock size: 4096 bytes, 4.0 KiB Amount of eraseblocks: 4096 (16777216 bytes, 16.0 MB) Minimum input/output unit size: 1 byte Sub-page size: 1 byte Character device major/minor: 90:0 Bad blocks are allowed: false Device is writable: true Please share your inputs on this. Thanks & Regards, Arvind G P.

4 5

request for support programmer with ch341b
by S. 13 Dec '24

13 Dec '24

flashrom supports only programmers with ch341a, but many programmers sold now have ch341b onboard, pid:vid is then 1a86:5523 tnx in advance Stephan

3 12

Winbond25q128jvsm2120
by Mohammed Hazim 12 Dec '24

12 Dec '24

Hi can you help me please? I have hp chrome book c1030 elite it have bios Winbond25q128jvsm2120 i need to install windows on it and it’s just taking chrome os .how can I install windows on it?

1 0

HP 11MK G9EE - M44236-001 - "W25Q64JW...M"
by Tim Tech 07 Dec '24

07 Dec '24

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 4

Splitting flashchips.c
by Anastasia Klimchuk 06 Dec '24

06 Dec '24

Good day, I wanted to confirm that we are splitting flashchips.c file into separate files per vendor. flashchips.c will still stay in the source code but it will be much smaller and will only contain "generic" chip entries. The patch is here: https://review.coreboot.org/c/flashrom/+/83307 , it will be submitted after v1.5.0 tag is done. The patch will not be included in v1.5.0 release. There will be no changes to the usage, and everything that's supported stays the same. If you are a flashrom user who does not look into source code: this does not affect you at all. If you are working on adding support for a chip model: when the patch is submitted (I will post again) you will need to copy your code from flashchips.c into a vendor-specific file. Thank you! -- Anastasia.

1 1

flashrom release v1.5.0 is out
by Anastasia Klimchuk 05 Dec '24

05 Dec '24

Good day everyone, flashrom release v1.5.0 is out! Tarball: https://download.flashrom.org/releases/flashrom-v1.5.0.tar.xz Signature: https://download.flashrom.org/releases/flashrom-v1.5.0.tar.xz.asc Fingerprint: 6E6E F9A0 BA47 8006 E277 6E4C C037 BB41 3134 D111 Checkout from git repository at https://review.coreboot.org/flashrom.git (tag v1.5.0) Release notes published: https://flashrom.org/release_notes/v_1_5.html It has been only 4 months since previous v1.4.0, and yet we have 91 commits made by 24 authors! Release notes explain the details of what was done, and thanks heaps to all the people who did it, reviewed it, and helped in any way <3 All the patches that have been ready and waiting, will be submitted very soon. -- Anastasia.

1 0

release v1.5.0 plan and timeline
by Anastasia Klimchuk 28 Nov '24

28 Nov '24

Good day everyone, We are doing one more release this year! It's a smaller scope than the previous one, but will contain some important things. We now have a document describing release process in details: https://flashrom.org/dev_guide/release_process.html so I will just tell the dates: 15 November: tagging v1.5.0-rc1 6 December: tagging the release v1.5.0 Between 15 November and 6 December we are focused on testing and bugfixing, so no new features will be submitted during that time. The patches can still be pushed and reviewed, but submit will need to wait for after we tag v1.5.0 (ETA 6 December). Bugfixes will be submitted as usual. Any help with buildind/testing/bugfixing is very much appreciated! https://flashrom.org/how_to_support_flashrom.html#building-and-testing-1 What's included in the next release? We now have a document which accumulates info about recent development (for any next release): https://flashrom.org/release_notes/devel.html It's not full final release notes, some things might be missing: for example I will soon add the "Bugs fixed" section there. Lastly, we plan to split flashchips.c into separate smaller files per vendor. The file grew huge, and it's time to split. To minimise the disruption for contributors who are adding support for new chip models, we plan to do this between 15 November and 6 December, when there are less contributions. This work will be submitted only after v1.5.0 tag. -- Anastasia.

2 4

(no subject)
by Djkds Jsjks 20 Nov '24

20 Nov '24

sudo flashrom -VV [plus the -p/--programmer parameter] flashrom 1.4.0 on Linux 6.6.54-current-sunxi64 (aarch64) flashrom is free software, get the source code at https://flashrom.org Error: Unknown programmer "/--programmer". Valid choices are: internal, dummy, gfxnvidia, raiden_debug_spi, drkaiser, satasii, asm106x, atavia, it8212, ft2232_spi, serprog, buspirate_spi, dediprog, developerbox, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, linux_mtd, linux_spi, usbblaster_spi, pickit2_spi, ch341a_spi, ch347_spi, digilent_spi, jlink_spi, stlinkv3_spi, dirtyjtag_spi. Please run "flashrom --help" for usage info.

2 1

FAILED: Lenovo 300e G4
by John Trimble 15 Nov '24

15 Nov '24

Hello, I can not disable write protect with flashrom on these devices. It keeps saying, "unknown WP error" or "Your flash chip is in an unknown state". Any information would be helpful. Thank you, John

1 0

Subject: Issue with flashrom on AMD FP4 chipset and unrecognized SMBus revision
by DAVID GOMEZ CRUZ 12 Nov '24

12 Nov '24

Dear flashrom team, I am encountering an issue when trying to use flashrom on a system with an AMD FP4 chipset. Upon attempting to access the flash memory, I receive the following error messages: flashrom v1.2 on Linux 6.4.0-150600.23.25-default (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 chipset "AMD FP4". Enabling flash write... Disabling read write protection of flash addresses from 0xfffff800 to 0x0007f7ff failed. Disabling read write protection of flash addresses from 0xfffff800 to 0x0007f7ff failed. Disabling read write protection of flash addresses from 0xfffff800 to 0x0007f7ff failed. Disabling read write protection of flash addresses from 0xfffff800 to 0x0007f7ff failed. FCH device found but SMBus revision 0x71 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation. PROBLEMS, continuing anyway No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. I have attached the lspci_output.txt file with the full output from the lspci -nnvx command, as suggested by the error message. I am seeking a solution to access the flash memory for reading or writing, but it appears that my chipset and SMBus revision may not be fully supported or recognized by flashrom. I would greatly appreciate any guidance or solutions you can provide. Thank you for your attention and for the excellent work on flashrom. I look forward to your response. Best regards, David

1 0

RPMC feature addition for v1.5
by Matti Finder 11 Nov '24

11 Nov '24

Hello, Over the last few weeks I have been adding support for the Replay protected monotonic counter commands to flashrom. Their functionality is defined in the JESD260 specification [1]. Currently they only work by manually setting the flash chip to use SFDP-capable chip. This is done with `-c "SFDP-capable chip"`. This enables automatic feature detection by parsing the corresponding SFDP-table. If you want to enable this new feature on supporting flashchips, this is done by setting the FEATURE_FLASH_HARDENING bit and then setting the correct values within the rpmc_ctx struct. Usage of the commands is explained here [2]. They just made the cutoff and so this new feature will be a part of flashrom v1.5. Best Regards, Matti. [1] https://www.jedec.org/standards-documents/docs/jesd260 [2] https://www.flashrom.org/classic_cli_manpage.html#rpmc-commands

1 0

Re: Support for GD25LR512ME flash chip.
by Anastasia Klimchuk 01 Nov '24

01 Nov '24

Victor, Thank you so much for the datasheets! I did a review of the pending patch, and now it will be possible to finally finish the patch from 2021 and get the chips submitted. Also thank you for attaching the log. Not sure if the log is complete? It ends at the start of the reading operation, but there is no final message of SUCCESS or FAIL. However, importantly, I could see in the beginning of the log which platform was detected, and it is Promontory. Which means... Avinash, Most likely you are hitting a known issue, you can read more details here: https://ticket.coreboot.org/issues/370 The issue is for Promontory, and also for chips larger than 16Mbyte: which is exactly what you have. I was actually trying to get help from AMD with this issue, so it's really good to have you here on the mailing list! Maybe you can help? Someone from AMD would be in the best position to fix Promontory, you have all the datasheets available, and all the hardware. Thank you! On Sat, May 11, 2024 at 9:40 PM Vlim <vlim(a)gigadevice.com> wrote: > > Hi, Anastasia, > > Please find the attached datasheet for GD25LR256E and GD25LR512ME. > > There are actually two issues. > > the released flashrom does not support GD25LR256E and GD25LR512ME. > With my patch, the dediprog programmer works for GD25LR512ME. But the AMD internal programmer for Birman Plus Board does not work. Output file attached. > > > This is the comment about Birman Plus Board > > Now, Flashrom can detect the flash chip. > Using dediprog programmer I can read/write the flash chip successfully. > Whereas with using the internal programmer i.e. "-p internal" the read/write is failing. I am attaching the log here. > Please give your input on this. > > > Regards, > > Victor > > > ________________________________ > From: Anastasia Klimchuk <aklm(a)chromium.org> > Sent: Saturday, May 11, 2024 17:59 > To: Vlim <vlim(a)gigadevice.com>; Munduru, Avinash <avinash.munduru(a)amd.com> > Cc: flashrom(a)flashrom.org <flashrom(a)flashrom.org> > Subject: Re: [flashrom] Re: Support for GD25LR512ME flash chip. > > 此为外部邮件，谨防钓鱼邮件，请注意邮件是否涉及敏感信息 > This is an external email, beware of phishing emails. Please pay close attention to whether the email contains sensitive information > > There is another thing, in addition to my previous message. > > I looked into the patch which adds chip definitions (this one > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.co…) and the reason it is > pending is there are no links to datasheets (old links are not working > anymore). > It is unfortunate that the patch is pending since 2021, but I want to > try to fix the situation now, in the year 2024. > > Victor, maybe you know, is it possible to find datasheets for > GD25LR256E and GD251R512ME? I could finish the old patch and get chips > into the tree. > > This is a separate question to Avinash's issue with internal > programmer, but for this we need the very verbose log (which is log > with -VVV option on command line). > > Thank you! > > On Thu, May 9, 2024 at 11:03 PM Anastasia Klimchuk <aklm(a)chromium.org> wrote: > > > > Avinash, I read the thread and I see you are saying "I am attaching > > the log here" but I don't see the log? maybe you can re-send it again, > > now with the mailing list? (perhaps you sent it to Victor only?) > > Yes it is also important to know your board, since you are saying the > > chip worked successfully with dediprog, but not with the internal > > programmer. > > > > Victor, thank you so much for helping! > > > > > > On Mon, May 6, 2024 at 6:42 PM Vlim <vlim(a)gigadevice.com> wrote: > > > > > > Thanks, Avinash, > > > > > > Can you advise which board are you using? > > > I have tested this patch with the USB programmer only since I do not have access to the motherboard. > > > > > > Hi, Flashrom team, > > > Can you also help on this? > > > > > > > > > Regards, > > > > > > Victor Lim > > > FAE Director > > > GigaDevice Semiconductor > > > 4088833856 > > > vlim(a)gigadevice.com > > > > > > ________________________________ > > > From: Munduru, Avinash <Avinash.Munduru(a)amd.com> > > > Sent: Monday, May 6, 2024 16:24 > > > To: Vlim <vlim(a)gigadevice.com>; flashrom(a)flashrom.org <flashrom(a)flashrom.org> > > > Subject: Re: Support for GD25LR512ME flash chip. > > > > > > You don't often get email from avinash.munduru(a)amd.com. Learn why this is important > > > 此为外部邮件，谨防钓鱼邮件，请注意邮件是否涉及敏感信息 > > > This is an external email, beware of phishing emails. Please pay close attention to whether the email contains sensitive information > > > > > > [AMD Official Use Only - General] > > > > > > > > > Hi Victor, > > > > > > Thanks for sharing the patch. Here is an update after trying the shared patch. > > > > > > Now, Flashrom can detect the flash chip. > > > Using dediprog programmer I can read/write the flash chip successfully. > > > Whereas with using the internal programmer i.e. "-p internal" the read/write is failing. I am attaching the log here. > > > Please give your input on this. > > > > > > Once again! Thanks for your help! > > > > > > > > > ________________________________ > > > From: Vlim <vlim(a)gigadevice.com> > > > Sent: Sunday, May 5, 2024 1:54 PM > > > To: flashrom(a)flashrom.org <flashrom(a)flashrom.org>; Munduru, Avinash <Avinash.Munduru(a)amd.com> > > > Subject: Re: Support for GD25LR512ME flash chip. > > > > > > Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding. > > > > > > Hi, Avinash, > > > > > > Sorry that I am working on adding this part to Flashrom, but has not completed the entire process. > > > > > > Can you please use the attached flashchips.c and flashshchips.h and replace that in flashrom distribution? > > > > > > This is the process. > > > > > > git clone "https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.co…" > > > > > > meson setup builddir > > > meson compile -C builddir > > > meson test -C builddir > > > meson install -C builddir > > > > > > > > > Please also refer to the following link for compilation of the code. > > > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fflashrom.… > > > > > > I have a compiled version for Ubuntu Linux, if that will help, I can share with you. > > > > > > Regards, > > > > > > Victor Lim > > > GigaDevice Semiconductors Inc. > > > 4088833856 > > > vlim(a)gigadevice.com > > > > > > > > > ________________________________ > > > From: Munduru, Avinash via flashrom <flashrom(a)flashrom.org> > > > Sent: Tuesday, April 30, 2024 16:54 > > > To: flashrom(a)flashrom.org <flashrom(a)flashrom.org> > > > Subject: [flashrom] Re: Support for GD25LR512ME flash chip. > > > > > > 此为外部邮件，谨防钓鱼邮件，请注意邮件是否涉及敏感信息 > > > This is an external email, beware of phishing emails. Please pay close attention to whether the email contains sensitive information > > > > > > [AMD Official Use Only - General] > > > > > > > > > + attaching the output log > > > > > > ________________________________ > > > From: Munduru, Avinash > > > Sent: Tuesday, April 30, 2024 2:04 PM > > > To: flashrom(a)flashrom.org <flashrom(a)flashrom.org> > > > Subject: Support for GD25LR512ME flash chip. > > > > > > Hi, > > > > > > Currently, flash chip support for GD25LR512ME is not supported in flashrom utility. > > > Please share a patch if it is already available. If not let me know how I can modify it. > > > > > > _______________________________________________ > > > flashrom mailing list -- flashrom(a)flashrom.org > > > To unsubscribe send an email to flashrom-leave(a)flashrom.org > > > > > > > > -- > > Anastasia. > > > > -- > Anastasia. -- Anastasia.

3 11

orange pi zero 2 W 15 M flash device as requested by flashrom
by Andi Allen 31 Oct '24

31 Oct '24

ic package is 8 pin25VQ128ASIG by the logo on it i believe it to be a zetta device Link included so you can see the logo at the top of the document as it matches the physical device http://www.zettadevice.com/upload/file/20150821/DS_Zetta_25LQ128_RevA_20180… # flashrom -VV --programmer ch341a_spi flashrom 1.4.0 (git:v1.4.0) on Linux 6.11.5-zen1-1-zen (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with GCC 14.1.1 20240720, little endian Command line (3 args): flashrom -VV --programmer ch341a_spi 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 0x5e, id2 0x4018 Probing for AMIC A25L016, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L020, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L032, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L040, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L05PT, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L05PU, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L080, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L10PT, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L10PU, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L16PT, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L16PU, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L20PT, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L20PU, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L40PT, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L40PU, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L512, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25L80P, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25LQ16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for AMIC A25LQ64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF011, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF021, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF021A, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF041A, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF081, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF081A, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF161, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF321, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF321A, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DF641(A), 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DL081, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DL161, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25DQ161, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512B, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25FS010, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25FS040, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25SF041, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25SF081, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25SF128A, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25SF161, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25SF321, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT25SL128A, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT26DF041, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT26DF081A, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT26DF161, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT26DF161A, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT26F004, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45CS1282, 16896 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB011D, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB021D, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB041D, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB081D, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB161D, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB321C, 4224 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB321D, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB321E, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel AT45DB642D, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Boya/BoHong Microelectronics B.25D16A, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Boya/BoHong Microelectronics B.25D80A, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Boya/BoHong Microelectronics B.25Q64AS, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Boya/BoHong Microelectronics B.25Q128AS, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ESI ES25P16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ESI ES25P40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ESI ES25P80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ESMT F25L008A, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ESMT F25L32PA, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B05, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B05T, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B10T, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B16T, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B20T, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B32T, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B40T, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B64T, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25B80T, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25F05, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25F10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25F16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25F20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25F32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25F40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25F64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25F80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25P05, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25P10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25P16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25P20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25P32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25P40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25P64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25P80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25Q128, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25Q16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25Q32(A/B), 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25Q40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25Q64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25Q80(A), 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25QH128, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25QH16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25QH32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25QH32B, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25QH64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25QH64A, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25S10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25S16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25S20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25S32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25S40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25S64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon EN25S80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Fudan FM25F005, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Fudan FM25F01, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Fudan FM25F02(A), 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Fudan FM25F04(A), 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Fudan FM25Q08, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Fudan FM25Q16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Fudan FM25Q32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25B128B/GD25Q128B, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LF128E, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LQ128E/GD25LB128E/GD25LR128E/GD25LQ128D/GD25LQ128C, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LQ255E, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LQ16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LQ32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LQ40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LQ64(B), 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LQ80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LB256E/GD25LR256E, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25LR512ME, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q127C/GD25Q128E, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q128C, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q16(B), 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q20(B), 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q256D/GD25Q256E, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q32(B), 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q40(B), 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q512, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q64(B), 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25Q80(B), 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25T80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25VQ16C, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25VQ21B, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25VQ40C, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25VQ41B, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25VQ80C, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for GigaDevice GD25WQ80E, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25LP016, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25LP064, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25LP128, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25LP256, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25LQ016, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WP016, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WP020, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WP032, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WP040, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WP064, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WP080, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WP128, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WP256, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ISSI IS25WQ040, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Intel 25F160S33B8, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Intel 25F160S33T8, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Intel 25F320S33B8, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Intel 25F320S33T8, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Intel 25F640S33B8, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Intel 25F640S33T8, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX23L12854, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX23L1654, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX23L3254, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX23L6454, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L12805D, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L12833F, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L12835F/MX25L12873F, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L12845E/MX25L12865E, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L12850F, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L1605, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25V16066, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L1635D, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L1633E, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L1635E/MX25L1636E, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L25635F/MX25L25645G, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L3205(A), 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L3273F, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L3239E, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L3235D, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L3233F/MX25L3273E, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L3255E, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L5121E, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L6405, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L6405D, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L6473E, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L6473F, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L6495F, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25R1635F, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25R2035F, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25R3235F, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25R4035F, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25R6435F, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25R8035F, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25V4035F, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25V8035F, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25V1635F, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25U12835F, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25U1635E, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25U25635F, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25U25643G, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25U3235E/F, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25U51245G, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25U6435E/F, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX25U8032E, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX66L51235F/MX25L51245G, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX66L1G45G, 131072 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix MX77L25650F, 32768 kB: compare_id: id1 0x5e, 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 0x5e, 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 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25P128, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25P16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25P20, 256 kB: compare_id: id1 0x5e, 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 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25P40, 512 kB: compare_id: id1 0x5e, 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 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25P80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PE10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PE20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PE40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M45PE10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M45PE20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M45PE40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q00A..1G, 131072 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q00A..3G, 131072 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q256..1E, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q256..3E, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q512..1G, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron/Numonyx/ST N25Q512..3G, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QL01G, 131072 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QU01G, 131072 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QL02G, 262144 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QU02G, 262144 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QU128, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QL128, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QL256, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QU256, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QL512, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Micron MT25QU512, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Nantronics N25S10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Nantronics N25S16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Nantronics N25S20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Nantronics N25S40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Nantronics N25S80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LD010(C), 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LD020(C), 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LD040(C), 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LD256C, 32 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LD512(C), 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LQ016, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LQ020, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LQ032C, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LQ040, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LQ080, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for PMC Pm25LV010A, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LV016B, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LV020, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LV040, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LV080B, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for PUYA P25Q06H, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PUYA P25Q11H, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PUYA P25Q21H, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25LF020A, 256 kB: compare_id: id1 0x5e, 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 0x5e, id2 0x17 Probing for SST SST25VF016B, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25VF020, 256 kB: compare_id: id1 0x5e, id2 0x17 Probing for SST SST25VF020B, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25VF032B, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25VF040, 512 kB: compare_id: id1 0x5e, id2 0x17 Probing for SST SST25VF040B, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25VF040B.REMS, 512 kB: compare_id: id1 0x5e, id2 0x17 Probing for SST SST25VF064C, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25VF080B, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25VF512(A), 64 kB: compare_id: id1 0x5e, id2 0x17 Probing for SST SST25WF010, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25WF020, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25WF020A, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25WF040, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25WF040B, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25WF080, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25WF080B, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST25WF512, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST26VF016B(A), 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST26VF032B(A), 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST SST26VF064B(A), 8192 kB: compare_id: id1 0x5e, 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 0x5e, 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 0x5e, id2 0x4018 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW203A, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Sanyo LE25FW403A, 512 kB: compare_id: id1 0x5e, 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 0x5e, id2 0x4018 Probing for Spansion S25FL008A, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL016A, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL032A/P, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL064A/P, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL127S-256kB, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL127S-64kB, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL128L, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL128P......0, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL128P......1, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL128S......0, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL128S......1, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL128S_UL Uniform 128 kB Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x18 0x5e 0x40 0x18. Probing for Spansion S25FL128S_US Uniform 64 kB Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x18 0x5e 0x40 0x18. Probing for Spansion S25FL129P......0, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL129P......1, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL132K, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL164K, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL204K, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL208K, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL256L, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL256S Large Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x18 0x5e 0x40 0x18. Probing for Spansion S25FL256S Small Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x18 0x5e 0x40 0x18. Probing for Spansion S25FL256S......0, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FL512S, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Spansion S25FS128S Large Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x18 0x5e 0x40 0x18. Probing for Spansion S25FS128S Small Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x18 0x5e 0x40 0x18. Probing for Winbond W25P16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25P32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25P80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q128.V, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q128.V..M, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q128.W, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q128.JW.DTR, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q16JV_M, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q16.V, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q16.W, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q20.W, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q256FV, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q256JV_Q, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q256JV_M, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q256JW, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q256JW_DTR, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q32BV/W25Q32CV/W25Q32DV, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q32FV, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q32JV, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q32BW/W25Q32CW/W25Q32DW, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q32FW, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q32JW...Q, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q32JW...M, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q40.V, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q40BW, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q40EW, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q512JV, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q512NW-IM, 65536 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q64BV/W25Q64CV/W25Q64FV, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q64JV-.Q, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q64JV-.M, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q64.W, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q64JW...M, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q80.V, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q80BW, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25Q80EW, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25X05, 64 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25X10, 128 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25X16, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25X20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25X32, 4096 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25X40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25X64, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond W25X80, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QH80B, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QU80B, 1024 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QH16C/XM25QH16D, 2048 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QH64C, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QU64C, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QH128A, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QH128C, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QU128C, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QH256C, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25QU256C, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XMC XM25RU256C, 32768 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XTX Technology Limited XT25F02E, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XTX Technology Limited XT25F64B, 8192 kB: compare_id: id1 0x5e, id2 0x4018 Probing for XTX Technology Limited XT25F128B, 16384 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Zetta Device ZD25D20, 256 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Zetta Device ZD25D40, 512 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Zetta Device ZD25LQ128, 16384 kB: compare_id: id1 0x5e, id2 0x17 Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.6 SFDP number of parameter headers is 1 (NPH = 0). SFDP parameter table header 0/0: ID 0x00, version 1.6 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 16384 kB. Block eraser 0: 4096 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 4096 x 4096 B with opcode 0x20. Block eraser 1: 512 x 32768 B with opcode 0x52 Block eraser 2: 256 x 65536 B with opcode 0xd8 done. === 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 - 00ffffff named complete flash Found Unknown flash chip "SFDP-capable chip" (16384 kB, SPI) on ch341a_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Atmel unknown Atmel SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Eon unknown Eon SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Macronix unknown Macronix SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for PMC unknown PMC SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for SST unknown SST SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for ST unknown ST SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Generic unknown SPI chip (RDID), 0 kB: compare_id: id1 0x5e, id2 0x4018 Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: id1 0x5e, id2 0x17 Found Unknown flash chip "SFDP-capable chip" (16384 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! No operations were specified.

1 0

Firmware recovery pixel book go
by Vladislav Sergeev 29 Oct '24

29 Oct '24

Good day! Help me understand the issue, MrChromebook sent to you, details here https://github.com/MrChromebox/scripts/issues/431

1 0

linux_spi
by reza adinepour 28 Oct '24

28 Oct '24

Dear Flashrom Support Team, I am reaching out to seek assistance with an issue I encountered while attempting to program a flash chip (XM25QU256C) using flashrom V1.5.0. I am using an external setup with a Raspberry Pi 4 and its SPI interface. Additionally, I have connected the /WP and /Hold pins of the flash chip to the VCC. I attached (error_output.txt) details of the command and the error message. *Best Regards,* *Reza*

1 0

v1.4 not available on https://download.flashrom.org/releases/
by Patrick Rudolph 24 Oct '24

24 Oct '24

Hi, I cannot download v1.4 as it's not on https://download.flashrom.org/releases/. There's only 1.4 available for download (missing the *v* prefix), though that's not matching the tag. Please fix to not break existing CIs relying on the correct tag. Regards, Patrick Rudolph

2 5

Gigabyte B450 GAMING X successful write with ch341a_spi and W25Q128.W
by Matthias Küch 22 Oct '24

22 Oct '24

Hey, I have successfully flashed my Bios with the Gigabyte B450 GAMING X, ch341a_spi and W25Q128.W. WP operation was marked as untested. Logs: https://paste.flashrom.org/view.php?id=3741 Thank you for your effort. It was fun! Please give me some feedback if my contribution was helpful. Matthias

2 1

Error Report
by Ben Muller 18 Oct '24

18 Oct '24

This happened while trying to dump the UEFI BIOS off of a T2SEEP rev2 Motherboard with an EPYC GENOA 9654QS on proxmox. Original Shell output: flashrom -p internal -r /root/output.rom flashrom unknown on Linux 6.8.12-2-pve (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 chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x71 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. Due to the high number of cores of the associated CPU, please find the output of the lspci -nnvx attached as a .txt file Kind Regards and thank you for developing FOSS software Ben Muller

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom