August 2024 - flashrom - mail.coreboot.org

Verification after write vs erase operations
by Anastasia Klimchuk Aug. 10, 2025

Aug. 10, 2025

Hello everyone, I want to bring into discussion a topic of verification of chip content which is performed after write or erase operations. Also for context prior discussion in this ticket: https://ticket.coreboot.org/issues/520 Currently we have a flag `-n` or `dont_verify_it` which is false by default. What the flag is doing is deciding whether verification needs to be performed after writing. The flag is false by default, so by default verification is happening after writing (which makes sense). Now the flag is only controlling write operation, and has no effect on erase operation. So for erase, the flag is ignored and verification is performed always. Just for context, it has always been like this. So for write operation we have a power option to say "ignore verification", and since it's false by default, the idea is, if you set it true then you know what you are doing. There is no such option for erase which seems a bit unfair. The two potential options to introduce equivalent option for erase are: 1) Add new flag `dont_verify_erase` (or some similar name) As a support for this option, it does not affect any existing use cases/scripts, and can be added any time. 2) Add coverage for erase operation under existing flag `-n` or `dont_verify_it` As a support for this option, erase operation can be seen as a variant of writing, since it does modify content of the chip, and so the fact it's not covered by the existing flag can be treated as a bug. What do people think about it? -- Anastasia.

2 2

Re: Support for GD25LR512ME flash chip.
by Anastasia Klimchuk Nov. 1, 2024

Nov. 1, 2024

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

Need help - Segmentation fault 11 when trying to write
by Flaviu Ciobanu Oct. 1, 2024

Oct. 1, 2024

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

Untested chipset Intel C236
by Mainville Aug. 29, 2024

Aug. 29, 2024

I'm happy to report that flashrom had no problems with my Intel C236 chipset, on my SuperMicro X11SSH-TF. I apologise for forgetting to use the -V verbose flag, thank you Flashrom team! I flashed from Coreboot 4.20.1 back to factory. You will need an external programmer to bypass the factory lock. root@holodeck:~# flashrom --programmer internal --write X11SSHTF-v3.bin flashrom unknown on Linux 6.8.8-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). coreboot table found at 0x7f2cc000. Found chipset "Intel C236". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed. New value is 0x8b. SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. FREG1: BIOS region (0x00500000-0x00ffffff) is read-write. FREG2: Management Engine region (0x00001000-0x004fffff) is read-write. OK. Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) on internal. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.

1 0

I'm a newb to this, I changed UMA Frame Buffer to 4G & it corrupted my BIOS, it won't erase now help?
by Chris Brooks Aug. 27, 2024

Aug. 27, 2024

I'm a newb to this, I changed UMA Frame Buffer to 4G & it corrupted my BIOS, it won't erase now help? What's the exact driver to use and how to install it to fix this issue on win11. [cid:74a8f1e9-06c4-488c-ab53-5efe7c5a413d]

1 0

Request to add new chip
by eswarit＠setsindia.net Aug. 26, 2024

Aug. 26, 2024

Dear team, Kindly help in adding the chip type "W25N01GVxxIG/IT" in Flashrom. Looking forward to hearing from you. -- Regards, Eswari T, Project Associate, Hardware Security Research Group, Society for Electronic Transactions and Security (SETS), Taramani Chennai-600113

1 0

report
by Rafael Aug. 17, 2024

Aug. 17, 2024

I received a message to report if it worked with this chip... And it worked correctly. Asus X451CA notebook: flashrom --programmer ch341a_spi --erase flashrom unknown on Linux 6.9.10-amd64 (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 Eon flash chip "EN25Q32(A/B)" (4096 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! Erasing and writing flash chip... Erase/write done.

1 0

Support for sub-1KByte EEPROM-s
by Miklós Márton Aug. 15, 2024

Aug. 15, 2024

Hello all, I tried to add support for some Microchip serial EEPROMs to being able to program them with an STLinkV3. I ran into problems with the smaller EEPROMs for e.g. 25LC040 which is only a 4Kbit device. The total_size in the flashchip structure is an unsigned int so I could only enter 0 as total size. In this case the flashrom shows the following message to me: ERROR: Flash chip 25C040 erase function 0 region walking resulted in 0x000200 bytes total, expected 0x000000 bytes. Please report a bug at flashrom(a)flashrom.org ERROR: Flash chip 25C040 erase function 0 is not in order. Please report a bug at flashrom(a)flashrom.org Is there any recommendations how to overcome on this? Is supporting smaller EEPROMs considered a feature what could be merged at some point, or the flashrom is going to focus purely on flash memories? -- Miklos

2 3

Found Unknown flash chip (MX25R3235FM1IL0)
by Leif Abbott Aug. 9, 2024

Aug. 9, 2024

Datasheet: https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2306061117_MXIC-Macronix… Output: Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). flashrom was built with GCC 12.2.0, 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: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L016, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L020, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L032, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L05PT, 64 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L05PU, 64 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L080, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L10PT, 128 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L10PU, 128 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L16PT, 2048 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L16PU, 2048 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L20PT, 256 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L20PU, 256 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L40PT, 512 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L40PU, 512 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25L512, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L80P, 1024 kB: compare_id: id1 0xc2, id2 0x2816 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25LQ16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25LQ64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF021, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF021A, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF041A, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF081, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF081A, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF321, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF321A, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF641(A), 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DL081, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DL161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DQ161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff 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: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25FS010, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25FS040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF041, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF081, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF128A, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF321, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SL128A, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26DF041, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26DF081A, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26DF161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26DF161A, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26F004, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45CS1282, 16896 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB011D, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB021D, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB041D, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB081D, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB161D, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB321C, 4224 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB321D, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB321E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB642D, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Boya/BoHong Microelectronics B.25D16A, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Boya/BoHong Microelectronics B.25Q128AS, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESI ES25P16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESI ES25P40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESI ES25P80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESMT F25L008A, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESMT F25L32PA, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B05, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B05T, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B10T, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B16T, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B20T, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B32T, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B40T, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B64T, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B80T, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F05, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P05, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q32(A/B), 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q80(A), 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25QH128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25QH16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25QH32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25QH64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25F005, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25F01, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25F02(A), 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25F04(A), 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25Q08, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25Q16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25Q32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25B128B/GD25Q128B, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ128C/GD25LQ128D/GD25LQ128E, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ64(B), 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q127C/GD25Q128C, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q16(B), 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q20(B), 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q256D/GD25Q256E, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q32(B), 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q40(B), 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q512, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q64(B), 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q80(B), 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25T80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ16C, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ21B, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ40C, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ41B, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ80C, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25WQ80E, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25LP064, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25LP128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25LP256, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25WP032, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25WP064, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25WP128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25WP256, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F160S33B8, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F160S33T8, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F320S33B8, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F320S33T8, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F640S33B8, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F640S33T8, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX23L12854, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX23L1654, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX23L3254, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX23L6454, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L12805D, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1635D, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1635E, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L25635F/MX25L25645G, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3205(A), 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3235D, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3233F/MX25L3273E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L5121E, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6405, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6405D, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6495F, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25R3235F, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25R6435F, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U12835F, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U1635E, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U25635F, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U3235E/F, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U51245G, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U6435E/F, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U8032E, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX66L51235F/MX25L51245G, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX66L1G45G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P05-A, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PX16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PX32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PX64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PX80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q00A..1G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q00A..3G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q016, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q256..1E, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q256..3E, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q512..1G, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q512..3G, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL01G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU01G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL02G, 262144 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU02G, 262144 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL256, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU256, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL512, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU512, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD010(C), 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD020(C), 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD040(C), 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD256C, 32 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD512(C), 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ016, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ020, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ032C, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ080, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for PMC Pm25LV010A, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV016B, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV020, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV080B, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25LF020A, 256 kB: compare_id: id1 0xc2, id2 0x16 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25VF010(A), 128 kB: compare_id: id1 0xc2, id2 0x16 Probing for SST SST25VF016B, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF020, 256 kB: compare_id: id1 0xc2, id2 0x16 Probing for SST SST25VF020B, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF032B, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF040, 512 kB: compare_id: id1 0xc2, id2 0x16 Probing for SST SST25VF040B, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF040B.REMS, 512 kB: compare_id: id1 0xc2, id2 0x16 Probing for SST SST25VF064C, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF080B, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF512(A), 64 kB: compare_id: id1 0xc2, id2 0x16 Probing for SST SST25WF010, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF020, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF020A, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF040B, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF080, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF080B, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF512, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST26VF016B(A), 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST26VF032B(A), 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST26VF064B(A), 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ST M95M02, 256 kB: probe_spi_st95: id1 0xff, id2 0xffff Probing for Sanyo LE25FU106B, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU206, 256 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU206A, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW203A, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo LE25FW403A, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Spansion S25FL004A, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL008A, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL016A, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL032A/P, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL064A/P, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL116K/S25FL216K, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL127S-256kB, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL127S-64kB, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128L, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128P......0, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128P......1, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128S......0, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128S......1, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128S_UL Uniform 128 kB Sectors, 16384 kB: Read id bytes: 0xc2 0x28 0x16 0xc2 0x28 0x16. Probing for Spansion S25FL128S_US Uniform 64 kB Sectors, 16384 kB: Read id bytes: 0xc2 0x28 0x16 0xc2 0x28 0x16. Probing for Spansion S25FL129P......0, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL129P......1, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL132K, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL164K, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL204K, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL208K, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL256L, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL256S Large Sectors, 16384 kB: Read id bytes: 0xc2 0x28 0x16 0xc2 0x28 0x16. Probing for Spansion S25FL256S Small Sectors, 16384 kB: Read id bytes: 0xc2 0x28 0x16 0xc2 0x28 0x16. Probing for Spansion S25FL256S......0, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL512S, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FS128S Large Sectors, 16384 kB: Read id bytes: 0xc2 0x28 0x16 0xc2 0x28 0x16. Probing for Spansion S25FS128S Small Sectors, 16384 kB: Read id bytes: 0xc2 0x28 0x16 0xc2 0x28 0x16. Probing for Winbond W25P16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25P32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25P80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q128.V, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q128.V..M, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q128.W, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q128.JW.DTR, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q16.V, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q16.W, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q20.W, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256FV, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256JV_Q, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256JV_M, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256JW, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256JW_DTR, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q32.V, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q32.W, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q32JW...M, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q40.V, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q40BW, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q40EW, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q512JV, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q512NW-IM, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64BV/W25Q64CV/W25Q64FV, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64JV-.Q, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64JV-.M, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64JW...M, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q80.V, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q80BW, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q80EW, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X05, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QH64C, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QU64C, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QH128C, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QU128C, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QH256C, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QU256C, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Zetta Device ZD25D20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Zetta Device ZD25D40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.6 SFDP number of parameter headers is 3 (NPH = 2). SFDP parameter table header 0/2: 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 4096 kB. Block eraser 0: 1024 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 1024 x 4096 B with opcode 0x20. Block eraser 1: 128 x 32768 B with opcode 0x52 Block eraser 2: 64 x 65536 B with opcode 0xd8 done. SFDP parameter table header 1/2: ID 0xc2, version 1.0 Length 16 B, Parameter Table Pointer 0x000110 SFDP parameter table header 2/2: ID 0x84, version 1.0 Length 8 B, Parameter Table Pointer 0x0000c0 === SFDP has autodetected a flash chip which is not natively supported by flashrom yet. All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually. You can help us by mailing us the output of the following command to flashrom(a)flashrom.org: 'flashrom -VV [plus the -p/--programmer parameter]' Thanks for your help! === Added layout entry 00000000 - 003fffff named complete flash Found Unknown flash chip "SFDP-capable chip" (4096 kB, SPI) on ch341a_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: compare_id: id1 0xc2, id2 0x2816 Probing for Atmel unknown Atmel SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon unknown Eon SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix unknown Macronix SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC unknown PMC SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST unknown SST SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ST unknown ST SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo unknown Sanyo SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: id1 0xc2, id2 0x16 Found Unknown flash chip "SFDP-capable chip" (4096 kB, SPI). === This flash part has status UNTESTED for operations: WP The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! No operations were specified.

1 0

Found Unknown flash chip (ZB25VQ64ASIG)
by Leif Abbott Aug. 9, 2024

Aug. 9, 2024

datasheet: https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2401101705_Zbit-Semi-ZB2… output: Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). flashrom was built with GCC 12.2.0, 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: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L016, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L020, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L032, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L05PT, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L05PU, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L080, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L10PT, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L10PU, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L16PT, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L16PU, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L20PT, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L20PU, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L40PT, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L40PU, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L512, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25L80P, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25LQ16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for AMIC A25LQ64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF021, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF021A, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF041A, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF081, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF081A, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF321, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF321A, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DF641(A), 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DL081, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DL161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25DQ161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff 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: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25FS010, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25FS040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF041, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF081, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF128A, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SF321, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT25SL128A, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26DF041, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26DF081A, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26DF161, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26DF161A, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT26F004, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45CS1282, 16896 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB011D, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB021D, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB041D, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB081D, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB161D, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB321C, 4224 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB321D, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB321E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel AT45DB642D, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Boya/BoHong Microelectronics B.25D16A, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Boya/BoHong Microelectronics B.25Q128AS, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESI ES25P16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESI ES25P40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESI ES25P80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESMT F25L008A, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ESMT F25L32PA, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B05, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B05T, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B10T, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B16T, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B20T, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B32T, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B40T, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B64T, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25B80T, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F05, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25F80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P05, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25P80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q32(A/B), 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25Q80(A), 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25QH128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25QH16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25QH32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25QH64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon EN25S80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25F005, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25F01, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25F02(A), 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25F04(A), 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25Q08, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25Q16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Fudan FM25Q32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25B128B/GD25Q128B, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ128C/GD25LQ128D/GD25LQ128E, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ64(B), 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25LQ80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q127C/GD25Q128C, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q16(B), 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q20(B), 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q256D/GD25Q256E, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q32(B), 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q40(B), 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q512, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q64(B), 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q80(B), 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25T80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ16C, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ21B, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ40C, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ41B, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25VQ80C, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for GigaDevice GD25WQ80E, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25LP064, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25LP128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25LP256, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25WP032, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25WP064, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25WP128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ISSI IS25WP256, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F160S33B8, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F160S33T8, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F320S33B8, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F320S33T8, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F640S33B8, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Intel 25F640S33T8, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX23L12854, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX23L1654, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX23L3254, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX23L6454, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L12805D, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1635D, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L1635E, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L25635F/MX25L25645G, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3205(A), 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3235D, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L3233F/MX25L3273E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L5121E, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6405, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6405D, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L6495F, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25R3235F, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25R6435F, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U12835F, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U1635E, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U25635F, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U3235E/F, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U51245G, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U6435E/F, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX25U8032E, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX66L51235F/MX25L51245G, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix MX66L1G45G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P05, 64 kB: probe_spi_res1: id 0xff Probing for Micron/Numonyx/ST M25P05-A, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25P80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PE80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PX16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PX32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PX64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M25PX80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST M45PE80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q00A..1G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q00A..3G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q016, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q256..1E, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q256..3E, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q512..1G, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q512..3G, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL01G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU01G, 131072 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL02G, 262144 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU02G, 262144 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL128, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL256, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU256, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QL512, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Micron MT25QU512, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Nantronics N25S80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD010(C), 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD020(C), 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD040(C), 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD256C, 32 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LD512(C), 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ016, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ020, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ032C, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LQ080, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for PMC Pm25LV010A, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV016B, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV020, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV080B, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25LF020A, 256 kB: compare_id: id1 0x5e, id2 0x16 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25VF010(A), 128 kB: compare_id: id1 0x5e, id2 0x16 Probing for SST SST25VF016B, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF020, 256 kB: compare_id: id1 0x5e, id2 0x16 Probing for SST SST25VF020B, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF032B, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF040, 512 kB: compare_id: id1 0x5e, id2 0x16 Probing for SST SST25VF040B, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF040B.REMS, 512 kB: compare_id: id1 0x5e, id2 0x16 Probing for SST SST25VF064C, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF080B, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25VF512(A), 64 kB: compare_id: id1 0x5e, id2 0x16 Probing for SST SST25WF010, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF020, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF020A, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF040, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF040B, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF080, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF080B, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST25WF512, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST26VF016B(A), 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST26VF032B(A), 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST SST26VF064B(A), 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ST M95M02, 256 kB: probe_spi_st95: id1 0xff, id2 0xffff Probing for Sanyo LE25FU106B, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU206, 256 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU206A, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW203A, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo LE25FW403A, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Spansion S25FL004A, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL008A, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL016A, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL032A/P, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL064A/P, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL116K/S25FL216K, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL127S-256kB, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL127S-64kB, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128L, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128P......0, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128P......1, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128S......0, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128S......1, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL128S_UL Uniform 128 kB Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x17 0x5e 0x40 0x17. Probing for Spansion S25FL128S_US Uniform 64 kB Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x17 0x5e 0x40 0x17. Probing for Spansion S25FL129P......0, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL129P......1, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL132K, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL164K, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL204K, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL208K, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL256L, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL256S Large Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x17 0x5e 0x40 0x17. Probing for Spansion S25FL256S Small Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x17 0x5e 0x40 0x17. Probing for Spansion S25FL256S......0, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FL512S, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Spansion S25FS128S Large Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x17 0x5e 0x40 0x17. Probing for Spansion S25FS128S Small Sectors, 16384 kB: Read id bytes: 0x5e 0x40 0x17 0x5e 0x40 0x17. Probing for Winbond W25P16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25P32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25P80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q128.V, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q128.V..M, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q128.W, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q128.JW.DTR, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q16.V, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q16.W, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q20.W, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256FV, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256JV_Q, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256JV_M, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256JW, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q256JW_DTR, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q32.V, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q32.W, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q32JW...M, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q40.V, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q40BW, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q40EW, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q512JV, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q512NW-IM, 65536 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64BV/W25Q64CV/W25Q64FV, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64JV-.Q, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64JV-.M, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q64JW...M, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q80.V, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q80BW, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25Q80EW, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X05, 64 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X10, 128 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X16, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X32, 4096 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X64, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond W25X80, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QH64C, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QU64C, 8192 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QH128C, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QU128C, 16384 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QH256C, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for XMC XM25QU256C, 32768 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Zetta Device ZD25D20, 256 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Zetta Device ZD25D40, 512 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff 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 8192 kB. Block eraser 0: 2048 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 2048 x 4096 B with opcode 0x20. Block eraser 1: 256 x 32768 B with opcode 0x52 Block eraser 2: 128 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 - 007fffff named complete flash Found Unknown flash chip "SFDP-capable chip" (8192 kB, SPI) on ch341a_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Atmel unknown Atmel SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Eon unknown Eon SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Macronix unknown Macronix SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for PMC unknown PMC SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for SST unknown SST SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for ST unknown ST SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Sanyo unknown Sanyo SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity violation. compare_id: id1 0xff, id2 0xffff Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: id1 0x5e, id2 0x16 Found Unknown flash chip "SFDP-capable chip" (8192 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. Thanks for your help! No operations were specified.

1 0

Tested Winbond W25Q32FV using serprog
by Larry Sellens Aug. 9, 2024

Aug. 9, 2024

tested with https://codeberg.org/libreboot/pico-serprog

1 0

flashrom 1.4.0 not support to flash MX25L5121E
by johanes hutapea Aug. 6, 2024

Aug. 6, 2024

flashrom 1.4.0 not support to flash MX25L5121E the chip, should be 512K or 1M. but flashrom detects only 64K. and flashrom said wp is untested. please add full support for this chip. thank you.

1 0

Flashrom - Error report
by Christopher Martin Aug. 5, 2024

Aug. 5, 2024

Hello, I tried to run flashrom on a Gigabyte B550M K 1.1 and it told me to send this: Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x51 does not match known values. sudo lspci -nnvx [sudo] password for ladmin: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630] Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630] Flags: fast devsel 00: 22 10 30 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 30 16 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631] Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631] Flags: bus master, fast devsel, latency 0, IRQ 255 Capabilities: [40] Secure device <?> Capabilities: [64] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00: 22 10 31 16 04 00 10 00 00 00 06 08 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 31 16 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Flags: fast devsel, IOMMU group 0 00: 22 10 32 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Flags: fast devsel, IOMMU group 1 00: 22 10 32 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453] Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 2 Bus: primary=00, secondary=01, subordinate=03, sec-latency=0 I/O behind bridge: f000-ffff [size=4K] [16-bit] Memory behind bridge: fcd00000-fcefffff [size=2M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), IntMsgNum 0 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [3c4] Designated Vendor-Specific: Vendor=1022 ID=0001 Rev=1 Len=44 <?> Kernel driver in use: pcieport 00: 22 10 34 16 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 01 03 00 f1 f1 00 00 20: d0 fc e0 fc f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453] Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 3 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: fcf00000-fcffffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), IntMsgNum 0 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [3c4] Designated Vendor-Specific: Vendor=1022 ID=0001 Rev=1 Len=44 <?> Kernel driver in use: pcieport 00: 22 10 34 16 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 04 04 00 f1 01 00 00 20: f0 fc f0 fc f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Flags: fast devsel, IOMMU group 4 00: 22 10 32 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] Flags: bus master, fast devsel, latency 0, IRQ 30, IOMMU group 5 Bus: primary=00, secondary=05, subordinate=05, sec-latency=0 I/O behind bridge: e000-efff [size=4K] [16-bit] Memory behind bridge: fc900000-fccfffff [size=4M] [32-bit] Prefetchable memory behind bridge: d0000000-e01fffff [size=258M] [32-bit] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), IntMsgNum 0 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver Kernel driver in use: pcieport 00: 22 10 35 16 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 05 05 00 e1 e1 00 00 20: 90 fc c0 fc 01 d0 11 e0 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 1a 00 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] Flags: 66MHz, medium devsel, IOMMU group 6 Kernel modules: i2c_piix4, sp5100_tco 00: 22 10 0b 79 03 04 20 02 51 00 05 0c 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 01 50 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 6 00: 22 10 0e 79 0f 00 20 02 51 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 01 50 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 [1022:166a] Flags: fast devsel, IOMMU group 7 00: 22 10 6a 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 [1022:166b] Flags: fast devsel, IOMMU group 7 00: 22 10 6b 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 [1022:166c] Flags: fast devsel, IOMMU group 7 00: 22 10 6c 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 [1022:166d] Flags: fast devsel, IOMMU group 7 Kernel driver in use: k10temp Kernel modules: k10temp 00: 22 10 6d 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 [1022:166e] Flags: fast devsel, IOMMU group 7 00: 22 10 6e 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 [1022:166f] Flags: fast devsel, IOMMU group 7 00: 22 10 6f 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 [1022:1670] Flags: fast devsel, IOMMU group 7 00: 22 10 70 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 [1022:1671] Flags: fast devsel, IOMMU group 7 00: 22 10 71 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller [1022:43ee] (prog-if 30 [XHCI]) Subsystem: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller [1b21:1142] Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 8 Memory at fcea0000 (64-bit, non-prefetchable) [size=32K] Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [68] MSI-X: Enable+ Count=8 Masked- Capabilities: [78] Power Management version 3 Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0 Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Capabilities: [300] Latency Tolerance Reporting Kernel driver in use: xhci_hcd 00: 22 10 ee 43 06 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 ea fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 21 1b 42 11 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00 01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller [1022:43eb] (prog-if 01 [AHCI 1.0]) Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:1062] Flags: bus master, fast devsel, latency 0, IRQ 35, IOMMU group 8 Memory at fce80000 (32-bit, non-prefetchable) [size=128K] Expansion ROM at fce00000 [disabled] [size=512K] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0 Capabilities: [100] Advanced Error Reporting Kernel driver in use: ahci 00: 22 10 eb 43 06 04 10 00 00 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 e8 fc 00 00 00 00 21 1b 62 10 30: 00 00 e0 fc 50 00 00 00 00 00 00 00 0a 02 00 00 01:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Upstream Port [1022:43e9] (prog-if 00 [Normal decode]) Subsystem: ASMedia Technology Inc. Device [1b21:0201] Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 8 Bus: primary=01, secondary=02, subordinate=03, sec-latency=0 I/O behind bridge: f000-ffff [size=4K] [16-bit] Memory behind bridge: fcd00000-fcdfffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Upstream Port, IntMsgNum 0 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:0201] Capabilities: [100] Advanced Error Reporting Kernel driver in use: pcieport 00: 22 10 e9 43 07 00 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 01 02 03 00 f1 f1 00 00 20: d0 fc d0 fc f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 03 12 00 02:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea] (prog-if 00 [Normal decode]) Subsystem: ASMedia Technology Inc. Device [1b21:3308] Flags: bus master, fast devsel, latency 0, IRQ 33, IOMMU group 8 Bus: primary=02, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: f000-ffff [size=4K] [16-bit] Memory behind bridge: fcd00000-fcdfffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), IntMsgNum 0 Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device [1b21:3308] Capabilities: [100] Advanced Error Reporting Capabilities: [200] Secondary PCI Express Kernel driver in use: pcieport 00: 22 10 ea 43 07 04 10 00 00 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 02 03 03 00 f1 f1 00 00 20: d0 fc d0 fc f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 04 01 12 00 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000] Flags: bus master, fast devsel, latency 0, IRQ 32, IOMMU group 8 I/O ports at f000 [size=256] Memory at fcd04000 (64-bit, non-prefetchable) [size=4K] Memory at fcd00000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, IntMsgNum 1 Capabilities: [b0] MSI-X: Enable+ Count=4 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8169 Kernel modules: r8169 00: ec 10 68 81 07 04 10 00 15 00 00 02 10 00 00 00 10: 01 f0 00 00 00 00 00 00 04 40 d0 fc 00 00 00 00 20: 04 00 d0 fc 00 00 00 00 00 00 00 00 58 14 00 e0 30: 00 00 00 00 40 00 00 00 00 00 00 00 04 01 00 00 04:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P2 [Nick P2] / P3 / P3 Plus NVMe PCIe SSD (DRAM-less) [c0a9:540a] (rev 01) (prog-if 02 [NVM Express]) Subsystem: Micron/Crucial Technology Device [c0a9:5021] Flags: bus master, fast devsel, latency 0, IRQ 63, IOMMU group 9 Memory at fcf00000 (64-bit, non-prefetchable) [size=16K] Capabilities: [80] Express Endpoint, IntMsgNum 0 Capabilities: [d0] MSI-X: Enable+ Count=9 Masked- Capabilities: [e0] MSI: Enable- Count=1/8 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [128] Alternative Routing-ID Interpretation (ARI) Capabilities: [1e0] Data Link Feature <?> Capabilities: [200] Advanced Error Reporting Capabilities: [300] Secondary PCI Express Kernel driver in use: nvme Kernel modules: nvme 00: a9 c0 0a 54 06 04 10 00 01 02 08 01 10 00 00 00 10: 04 00 f0 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 a9 c0 21 50 30: 00 00 00 00 80 00 00 00 00 00 00 00 0b 01 00 00 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 10 Memory at d0000000 (64-bit, prefetchable) [size=256M] Memory at e0000000 (64-bit, prefetchable) [size=2M] I/O ports at e000 [size=256] Memory at fcc00000 (32-bit, non-prefetchable) [size=512K] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, IntMsgNum 0 Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=4 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [2a0] Access Control Services Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver Kernel driver in use: amdgpu Kernel modules: amdgpu 00: 02 10 38 16 07 04 10 08 c9 00 00 03 10 00 80 00 10: 0c 00 00 d0 00 00 00 00 0c 00 00 e0 00 00 00 00 20: 01 e0 00 00 00 00 c0 fc 00 00 00 00 58 14 00 d0 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 01 00 00 05:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637] Flags: bus master, fast devsel, latency 0, IRQ 75, IOMMU group 11 Memory at fcc88000 (32-bit, non-prefetchable) [size=16K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, IntMsgNum 0 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [2a0] Access Control Services Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 02 10 37 16 07 04 10 00 00 00 03 04 10 00 80 00 10: 00 80 c8 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 37 16 30: 00 00 00 00 48 00 00 00 00 00 00 00 04 02 00 00 05:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df] Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 12 Memory at fcb00000 (32-bit, non-prefetchable) [size=1M] Memory at fcc8c000 (32-bit, non-prefetchable) [size=8K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, IntMsgNum 0 Capabilities: [a0] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=2 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [2a0] Access Control Services Kernel driver in use: ccp Kernel modules: ccp 00: 22 10 df 15 07 04 10 08 00 00 80 10 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 b0 fc 00 00 00 00 20: 00 00 00 00 00 c0 c8 fc 00 00 00 00 22 10 df 15 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 03 00 00 05:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639] (prog-if 30 [XHCI]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007] Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 13 Memory at fca00000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, IntMsgNum 0 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [2a0] Access Control Services Kernel driver in use: xhci_hcd 00: 22 10 39 16 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 a0 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 07 50 30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 04 00 00 05:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639] (prog-if 30 [XHCI]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007] Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 14 Memory at fc900000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, IntMsgNum 0 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [2a0] Access Control Services Kernel driver in use: xhci_hcd 00: 22 10 39 16 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 90 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 07 50 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 01 00 00 05:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3] DeviceName: Realtek ALC1220 Subsystem: Gigabyte Technology Co., Ltd Device [1458:a194] Flags: bus master, fast devsel, latency 0, IRQ 76, IOMMU group 15 Memory at fcc80000 (32-bit, non-prefetchable) [size=32K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, IntMsgNum 0 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [2a0] Access Control Services Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 22 10 e3 15 07 04 10 00 00 00 03 04 10 00 80 00 10: 00 00 c8 fc 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 94 a1 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 03 00 00

1 0

Past, Present, and Future of the Bus Pirate
by David Reguera Garcia Aug. 3, 2024

Aug. 3, 2024

I'm excited to announce that I am taking over as the maintainer of the Bus Pirate. Having been closely involved with the Bus Pirate through conducting training, developing modified PCBs, addons, and crafting custom firmware... Currently, I am collaborating with Ian (Bus Pirate creator) to determine the best way to support the upcoming Bus Pirate v5 in Flashrom. We are exploring various options, including the potential use of DirtyJTAG or perhaps devising a new, more modern binary protocol. These are exciting times, and I am eager to lead our community through them. I would like to take a moment to extend my heartfelt thanks to Anastasia for her kindness and support. Please note, for the Bus Pirate v3 and v4, there will be no major updates as the hardware is quite dated. However, I am here for any support or queries you might have regarding any version of the Bus Pirate. If anyone has questions, needs assistance, or wants to contribute ideas, please feel free to reach out. Your input and collaboration are what make our community thrive. Sincerely, Dreg

2 1