- flashrom - mail.coreboot.org

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

09 Jan '25

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

2 1

FAILED: Swanky Baytrail
by Chris Andrew 09 Jan '25

09 Jan '25

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

2 1

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

07 Jan '25

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

2 2

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

07 Jan '25

Had to boot kernel w/ iomem=relaxed for a read to work $ sudo builddir/flashrom -p nicintel_spi:pci=81:00.0 -r W25X40-81-00-0.bin --progress flashrom v1.6.0-devel (git:v1.5.0-10-g2e6b0510) on Linux 6.1.0-29-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === Found Winbond flash chip "W25X40" (512 kB, SPI) on nicintel_spi. === This flash part has status UNTESTED for operations: WP The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. You can also try to follow the instructions here: https://www.flashrom.org/contrib_howtos/how_to_mark_chip_tested.html Thanks for your help! Reading flash... [READ: 100%]...done. 81:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) Subsystem: Super Micro Computer Inc AOC-STGN-i2S Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 30 NUMA node: 1 IOMMU group: 13 Region 0: Memory at faf80000 (64-bit, prefetchable) [size=512K] Region 2: I/O ports at f020 [size=32] Region 4: Memory at fb404000 (64-bit, prefetchable) [size=16K] Expansion ROM at fbe80000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: ixgbe Kernel modules: ixgbe 81:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) Subsystem: Super Micro Computer Inc AOC-STGN-i2S Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin B routed to IRQ 340 NUMA node: 1 IOMMU group: 14 Region 0: Memory at faf00000 (64-bit, prefetchable) [size=512K] Region 2: I/O ports at f000 [size=32] Region 4: Memory at fb400000 (64-bit, prefetchable) [size=16K] Expansion ROM at fbe00000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: ixgbe Kernel modules: ixgbe -- Jared Mauch | pgp key available via finger from jared(a)puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.

1 0

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

04 Jan '25

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

1 0

flashrom
by rik Hendrickx 30 Dec '24

30 Dec '24

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

1 0

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

22 Dec '24

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

1 0

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

16 Dec '24

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

4 5

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

13 Dec '24

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

3 12

Winbond25q128jvsm2120
by Mohammed Hazim 12 Dec '24

12 Dec '24

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

1 0

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

07 Dec '24

Hello, attached are two text documents: output from --wp-disable and output from erase/write - let me know if any other information is needed. Chip in question is "W25Q64JW...M" Thanks, Tim

2 4

Splitting flashchips.c
by Anastasia Klimchuk 06 Dec '24

06 Dec '24

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

1 1

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

05 Dec '24

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

1 0

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

29 Nov '24

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

2 4

(no subject)
by Djkds Jsjks 21 Nov '24

21 Nov '24

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

2 1

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

15 Nov '24

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

1 0

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

12 Nov '24

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

1 0

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

11 Nov '24

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

1 0

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

01 Nov '24

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

3 11

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

31 Oct '24

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

1 0

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

29 Oct '24

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

1 0

linux_spi
by reza adinepour 28 Oct '24

28 Oct '24

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

1 0

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

25 Oct '24

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

2 5

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

22 Oct '24

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

2 1

Error Report
by Ben Muller 18 Oct '24

18 Oct '24

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

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom