flashrom September 2024

flashrom@flashrom.org

11 participants
11 discussions

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

Request support for xmc qh64ahig, qh128ahig
by M. Jacobs 11 Oct '24

11 Oct '24

Dear sir/madam, After reading the changelog for version 1.3 I saw that the XM25QH64C and XM25QH128C are supported. However I am trying to use flashrom with a ch341 (pro) to read and write qh64ahig/qh128ahig eeproms. It fails saying no eeprom/flash device found which comes down to lack of support I guess. Are there any plans in the nearby feature for implementing these models of IC's? Kind regards, MJ

2 1

Need help - Segmentation fault 11 when trying to write
by Flaviu Ciobanu 02 Oct '24

02 Oct '24

Hi devs! I previously successfully used flashrom to read and patch a MX25L6406E BIOS chip in a late 2013 15" MacBook Pro with a Ch341a programmer, but I am now having issues trying to write to a 25Q064A BIOS chip in a mid 2014 15" MacBook Pro. I installed flashrom with homebrew. I connected the SOP8 clip to the chip, then the adapter, then the CH341A. I read the chip into an image.bin file 3 times and compared MD5 sums to make sure they were the same. I then patched the file with UEFI Patch to unlock undervolting ( https://github.com/IsmaelHG/UndervoltPatchMacBook). I then ran the write command in terminal. You can see the command and the output pasted below ending in "Segmentation fault: 11". Should I try erasing the chip first? I'm scared I will brick it if it still can't write afterward. What else can I try? Terminal output: sudo flashrom -V -p ch341a_spi -c N25Q064..3E -w /Users/Flyview/Downloads/UEFIPatch_0.28.0_mac/image.bin flashrom 1.4.0 on Darwin 23.6.0 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with LLVM Clang 15.0.0 (clang-1500.3.9.4), little endian Command line (7 args): flashrom -V -p ch341a_spi -c N25Q064..3E -w /Users/Flyview/Downloads/UEFIPatch_0.28.0_mac/image.bin Initializing ch341a_spi programmer libusb: info [darwin_detach_kernel_driver] no capture entitlements. may not be able to detach the kernel driver for this device Device revision is 3.0.4 The following protocols are supported: SPI. Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: compare_id: id1 0x20, id2 0xba17 Added layout entry 00000000 - 007fffff named complete flash Found Micron/Numonyx/ST flash chip "N25Q064..3E" (8192 kB, SPI) on ch341a_spi. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Top/Bottom (TB) is top Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set 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. You can also try to follow the instructions here: https://www.flashrom.org/contrib_howtos/how_to_mark_chip_tested.html Thanks for your help! Reading old flash chip contents... read_flash: region (00000000..0x7fffff) is readable, reading range (00000000..0x7fffff). done. Segmentation fault: 11 Thank you! Faviu

2 2

"FAILED: PLELT028JHR0CA"
by Dave Storer 25 Sep '24

25 Sep '24

Getting a "flash write failed" error when trying to change the serial number on a HP Chromebook G7. We don't usually have issues doing this. Any reason or possible fixes would be greatly appreciated. Thank you -- Dave Storer WMBOE Tech Dept. West Milford Board of Ed

1 0

output from "unknown flash chip" (Puya P25D32SH)
by Nickolas Zuliy 25 Sep '24

25 Sep '24

was probing this firmware chip (Puya P25D32SH) on a cheap unbranded mp3 player, flashrom said to send the output of 'flashrom -VV [-p ch341a_spi]' to this email, so here it is.

1 0

Thinpad flashing error - N25Q064..3E - Your flash chip is in an unknown state.
by Dennis Schneck 21 Sep '24

21 Sep '24

1 0

Subject: Seeking Assistance with W39V080FA Flash Chip and Flashrom
by LUIS ROBERTO ALVES DE MENDONÇA JOSÉ 20 Sep '24

20 Sep '24

Greetings, Flashrom Team! My name is Luisão, and I'm writing to ask for your guidance and expertise in interfacing a W39V080FA flash chip with Flashrom. I've encountered a lot challenges while attempting to interface this chip manually using an Arduino Mega, level shifters, and pull-down resistors. The main obstacles I've faced, regarding my scenario, are: - *Signal integrity issues:* Ensuring clean and reliable signals between the microcontroller and the flash chip has proven to be quite complex. - *Multiplexed address system:* The W39V080FA's multiplexed address system has required careful timing and control. - *Complex features:* The chip's various features and modes have made it difficult to understand and implement correctly. - *Hard-to-understand datasheet:* The datasheet for the W39V080FA has been somewhat unclear and challenging to interpret. I've noticed that the W39V080FA is listed as fully supported on the Flashrom wiki, which gives me hope that Flashrom can provide a more streamlined and reliable solution. I have some microcontrollers that could be used if there's firmware available for them, including Arduino Nano, Uno, Mega, ESP32-S3, Raspberry Pi Pico, and CH32 (In the case of Arduino Uno, I cannot make the custom FWH PCB easily, unfortunately :/) I would greatly appreciate any advice, instructions, or resources you can provide to help me program the W39V080FA because it's been a nightmare so far. Thank you for your time and assistance. Sincerely, Luisão

1 0

Backup bios Asus X5Din
by Ciro Cappiello 18 Sep '24

18 Sep '24

Good afternoon, I'm trying to do a bios backup for my laptop Asus X5Din (it's an old laptop.) -cpu intel core 2 duo t6500 2.10ghz -mobo K50IN. -O.S. Debian 12. (I'm not very expert on Debian os or linux distribution) After installation of flashrom 1.4.0, typing the command: sudo flashrom -r namefilebackup.bin -p internal, The error is: <Found chipset "nvidia MCP79". This chipset is marked as untested...> I try to add parameter -N --noverify, -p internal:laptop=force_I_want_a_brick (aware of the ricks), but always the same issue. I hope you can help me. Thaks a lot. Ciro Cappiello.

1 0

new SPI? - CH341 black
by Ace Ventura 08 Sep '24

08 Sep '24

[cid:image001.png@01DB01EC.DD9F0EE0] C:\Users\user\Documents\bins\flashrom-1.4>flashrom -VV --programmer ch341a_spi flashrom 1.4.0 on Windows 10.0 (x86_64) flashrom is free software, Dreg comp, code source https://flashrom.org flashrom was built with GCC 13.2.0, little endian Command line (3 args): flashrom -VV --programmer ch341a_spi Initializing ch341a_spi programmer Cannot detach the existing USB driver. Claiming the interface may fail. LIBUSB_ERROR_NOT_SUPPORTED Device revision is 3.0.4 The following protocols are supported: SPI. Probing for AMIC A25L010, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L016, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L020, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L032, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L040, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L05PT, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L05PU, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L080, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L10PT, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L10PU, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L16PT, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L16PU, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L20PT, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L20PU, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L40PT, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L40PU, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L512, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25L80P, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25LQ16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for AMIC A25LQ64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF011, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF021, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF021A, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF041A, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF081, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF081A, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF161, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF321, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF321A, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DF641(A), 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DL081, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DL161, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25DQ161, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25FS010, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25FS040, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25SF041, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25SF081, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25SF128A, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25SF161, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25SF321, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT25SL128A, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT26DF041, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT26DF081A, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT26DF161, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT26DF161A, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT26F004, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45CS1282, 16896 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB011D, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB021D, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB041D, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB081D, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB161D, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB321C, 4224 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB321D, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB321E, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel AT45DB642D, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Boya/BoHong Microelectronics B.25D16A, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Boya/BoHong Microelectronics B.25D80A, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Boya/BoHong Microelectronics B.25Q64AS, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Boya/BoHong Microelectronics B.25Q128AS, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ESI ES25P16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ESI ES25P40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ESI ES25P80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ESMT F25L008A, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ESMT F25L32PA, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B05, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B05T, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B10T, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B16T, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B20T, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B32T, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B40T, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B64T, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25B80T, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25F05, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25F10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25F16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25F20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25F32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25F40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25F64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25F80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25P05, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25P10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25P16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25P20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25P32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25P40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25P64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25P80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25Q128, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25Q16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25Q32(A/B), 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25Q40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25Q64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25Q80(A), 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25QH128, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25QH16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25QH32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25QH32B, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25QH64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25QH64A, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25S10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25S16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25S20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25S32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25S40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25S64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon EN25S80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Fudan FM25F005, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Fudan FM25F01, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Fudan FM25F02(A), 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Fudan FM25F04(A), 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Fudan FM25Q08, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Fudan FM25Q16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Fudan FM25Q32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25B128B/GD25Q128B, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LF128E, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LQ128E/GD25LB128E/GD25LR128E/GD25LQ128D/GD25LQ128C, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LQ255E, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LQ16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LQ32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LQ40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LQ64(B), 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LQ80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LB256E/GD25LR256E, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25LR512ME, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q127C/GD25Q128E, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q128C, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q16(B), 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q20(B), 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q256D/GD25Q256E, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q32(B), 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q40(B), 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q512, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q64(B), 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25Q80(B), 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25T80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25VQ16C, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25VQ21B, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25VQ40C, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25VQ41B, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25VQ80C, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for GigaDevice GD25WQ80E, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25LP016, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25LP064, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25LP128, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25LP256, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25LQ016, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WP016, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WP020, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WP032, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WP040, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WP064, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WP080, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WP128, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WP256, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ISSI IS25WQ040, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Intel 25F160S33B8, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Intel 25F160S33T8, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Intel 25F320S33B8, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Intel 25F320S33T8, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Intel 25F640S33B8, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Intel 25F640S33T8, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX23L12854, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX23L1654, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX23L3254, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX23L6454, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L12805D, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L12833F, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L12835F/MX25L12873F, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L12845E/MX25L12865E, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L12850F, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L1605, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25V16066, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L1635D, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L1633E, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L1635E/MX25L1636E, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L25635F/MX25L25645G, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L3205(A), 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L3273F, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L3239E, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L3235D, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L3233F/MX25L3273E, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L3255E, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L5121E, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L6405, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L6405D, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L6473E, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L6473F, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L6495F, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25R1635F, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25R2035F, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25R3235F, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25R4035F, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25R6435F, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25R8035F, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25V4035F, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25V8035F, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25V1635F, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25U12835F, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25U1635E, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25U25635F, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25U25643G, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25U3235E/F, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25U51245G, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25U6435E/F, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX25U8032E, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX66L51235F/MX25L51245G, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX66L1G45G, 131072 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix MX77L25650F, 32768 kB: compare_id: id1 0xc7, id2 0x4014 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 0xc7, id2 0x4014 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 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25P128, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25P16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25P20, 256 kB: compare_id: id1 0xc7, id2 0x4014 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 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25P40, 512 kB: compare_id: id1 0xc7, id2 0x4014 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 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25P80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PE10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PE20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PE40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M45PE10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M45PE20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M45PE40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q00A..1G, 131072 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q00A..3G, 131072 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q256..1E, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q256..3E, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q512..1G, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron/Numonyx/ST N25Q512..3G, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QL01G, 131072 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QU01G, 131072 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QL02G, 262144 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QU02G, 262144 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QU128, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QL128, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QL256, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QU256, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QL512, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Micron MT25QU512, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Nantronics N25S10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Nantronics N25S16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Nantronics N25S20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Nantronics N25S40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Nantronics N25S80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LD010(C), 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LD020(C), 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LD040(C), 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LD256C, 32 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LD512(C), 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LQ016, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LQ020, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LQ032C, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LQ040, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LQ080, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for PMC Pm25LV010A, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LV016B, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LV020, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LV040, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LV080B, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for PUYA P25Q06H, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PUYA P25Q11H, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PUYA P25Q21H, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25LF020A, 256 kB: compare_id: id1 0xc7, id2 0x13 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25VF010(A), 128 kB: compare_id: id1 0xc7, id2 0x13 Probing for SST SST25VF016B, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25VF020, 256 kB: compare_id: id1 0xc7, id2 0x13 Probing for SST SST25VF020B, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25VF032B, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25VF040, 512 kB: compare_id: id1 0xc7, id2 0x13 Probing for SST SST25VF040B, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25VF040B.REMS, 512 kB: compare_id: id1 0xc7, id2 0x13 Probing for SST SST25VF064C, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25VF080B, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25VF512(A), 64 kB: compare_id: id1 0xc7, id2 0x13 Probing for SST SST25WF010, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25WF020, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25WF020A, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25WF040, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25WF040B, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25WF080, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25WF080B, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST25WF512, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST26VF016B(A), 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST26VF032B(A), 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST SST26VF064B(A), 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ST M95M02, 256 kB: probe_spi_st95: id1 0xff, id2 0xffff Probing for Sanyo LE25FU106B, 128 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FU206, 256 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FU206A, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FW203A, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Sanyo LE25FW403A, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Spansion S25FL004A, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL008A, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL016A, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL032A/P, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL064A/P, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL127S-256kB, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL127S-64kB, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL128L, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL128P......0, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL128P......1, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL128S......0, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL128S......1, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL128S_UL Uniform 128 kB Sectors, 16384 kB: Read id bytes: 0xc7 0x40 0x14 0xc7 0x40 0x14. Probing for Spansion S25FL128S_US Uniform 64 kB Sectors, 16384 kB: Read id bytes: 0xc7 0x40 0x14 0xc7 0x40 0x14. Probing for Spansion S25FL129P......0, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL129P......1, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL132K, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL164K, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL204K, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL208K, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL256L, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL256S Large Sectors, 16384 kB: Read id bytes: 0xc7 0x40 0x14 0xc7 0x40 0x14. Probing for Spansion S25FL256S Small Sectors, 16384 kB: Read id bytes: 0xc7 0x40 0x14 0xc7 0x40 0x14. Probing for Spansion S25FL256S......0, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FL512S, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Spansion S25FS128S Large Sectors, 16384 kB: Read id bytes: 0xc7 0x40 0x14 0xc7 0x40 0x14. Probing for Spansion S25FS128S Small Sectors, 16384 kB: Read id bytes: 0xc7 0x40 0x14 0xc7 0x40 0x14. Probing for Winbond W25P16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25P32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25P80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q128.V, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q128.V..M, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q128.W, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q128.JW.DTR, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q16JV_M, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q16.V, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q16.W, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q20.W, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q256FV, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q256JV_Q, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q256JV_M, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q256JW, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q256JW_DTR, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q32BV/W25Q32CV/W25Q32DV, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q32FV, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q32JV, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q32BW/W25Q32CW/W25Q32DW, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q32FW, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q32JW...Q, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q32JW...M, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q40.V, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q40BW, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q40EW, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q512JV, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q512NW-IM, 65536 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q64BV/W25Q64CV/W25Q64FV, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q64JV-.Q, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q64JV-.M, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q64.W, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q64JW...M, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q80.V, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q80BW, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25Q80EW, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25X05, 64 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25X10, 128 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25X16, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25X20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25X32, 4096 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25X40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25X64, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond W25X80, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QH80B, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QU80B, 1024 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QH16C/XM25QH16D, 2048 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QH64C, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QU64C, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QH128A, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QH128C, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QU128C, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QH256C, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25QU256C, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XMC XM25RU256C, 32768 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XTX Technology Limited XT25F02E, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XTX Technology Limited XT25F64B, 8192 kB: compare_id: id1 0xc7, id2 0x4014 Probing for XTX Technology Limited XT25F128B, 16384 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Zetta Device ZD25D20, 256 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Zetta Device ZD25D40, 512 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Zetta Device ZD25LQ128, 16384 kB: compare_id: id1 0xc7, id2 0x13 Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.0 SFDP number of parameter headers is 2 (NPH = 1). SFDP parameter table header 0/1: ID 0x00, version 1.0 Length 36 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 1024 kB. Block eraser 0: 256 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 256 x 4096 B with opcode 0x20. Block eraser 1: 32 x 32768 B with opcode 0x52 Block eraser 2: 16 x 65536 B with opcode 0xd8 done. SFDP parameter table header 1/1: ID 0xc7, version 1.0 Length 12 B, Parameter Table Pointer 0x000090 === 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 - 000fffff named complete flash Found Unknown flash chip "SFDP-capable chip" (1024 kB, SPI) on ch341a_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Atmel unknown Atmel SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Eon unknown Eon SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Macronix unknown Macronix SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for PMC unknown PMC SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for SST unknown SST SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for ST unknown ST SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Generic unknown SPI chip (RDID), 0 kB: compare_id: id1 0xc7, id2 0x4014 Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: id1 0xc7, id2 0x13 Found Unknown flash chip "SFDP-capable chip" (1024 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. C:\Users\user\Documents\bins\flashrom-1.4>flashrom --programmer ch341a_spi -r flash_dump.bin flashrom 1.4.0 on Windows 10.0 (x86_64) flashrom is free software, Dreg comp, code source https://flashrom.org Cannot detach the existing USB driver. Claiming the interface may fail. LIBUSB_ERROR_NOT_SUPPORTED === 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" (1024 kB, SPI) on ch341a_spi. === This flash part has status UNTESTED for operations: WP The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. You can also try to follow the instructions here: https://www.flashrom.org/contrib_howtos/how_to_mark_chip_tested.html Thanks for your help! Reading flash... done.

1 0

flashrom1.4 segfault in init_eraseblock
by Grant Pannell 07 Sep '24

07 Sep '24

Hi, Trying to report a bug in flashrom 1.4. I'm not subject matter expert, but I've done my best to try and debug and fix the issue. Seeking guidance from the experts on whether this is the solution :-) I found that in 1.4, it looks like the erase and write logic was refactored. Since then, I get segfaults when trying to flash my coreboot image. The chip is a Macronix MX25U6435E in a Protectli FW4B. I'm running on OpenBSD 7.5. The segfault occurs in erasure_layout.c: init_eraseblock line 55. I am no expert on the internals of flashrom, or what's going on here...but I've narrowed it down to segfaulting at the last iteration of this while loop. Code in question looks like: edata->first_sub_block_index = *sub_block_index; struct eraseblock_data *subedata = &layout[idx - 1].layout_list[*sub_block_index]; while (subedata->start_addr >= start_addr && subedata->end_addr <= end_addr && *sub_block_index < layout[idx-1].block_count) { (*sub_block_index)++; subedata++; } In my case, it seems that the last iteration looks like: layout[idx-1].block_count == 2048 *sub_block_index == 2047 subedata->end_addr == end_addr What then happens is, the variable "subedata" is incremented and the while condition is checked, but subedata is now out of bounds and the application segfaults. I'm pretty sure the while loop shouldn't iterate again because the next iteration would fail the *sub_block_index < layout[idx-1].block_count check (2048 < 2028). I solved this by short circuiting the while condition and checking that condition first, so that subedata is not accessed and flashrom successfully flashes my coreboot image. Patch included below. Is this an appropriate fix? Thank you, Grant --- erasure_layout.c.orig +++ erasure_layout.c @@ -52,8 +52,8 @@ edata->first_sub_block_index = *sub_block_index; struct eraseblock_data *subedata = &layout[idx - 1].layout_list[*sub_block_index]; - while (subedata->start_addr >= start_addr && subedata->end_addr <= end_addr && - *sub_block_index < layout[idx-1].block_count) { + while (*sub_block_index < layout[idx-1].block_count && + subedata->start_addr >= start_addr && subedata->end_addr <= end_addr) { (*sub_block_index)++; subedata++; }

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom September 2024