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.
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
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
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
Hello, I'm trying to restore the bios of my Chromebook with a backup copy and the flashrom gives me an error, ERASE FAILED!, I would like to know if there is a solution.
The chip is a Winbond flash chip W25Q128.JW.DTR.
Thank you.
Dear sir/madam,
After reading the changelog for version 1.3 I saw that the XM25QH64C and XM25QH128C are supported. However I am trying to use flashrom with a ch341 (pro) to read and write qh64ahig/qh128ahig eeproms. It fails saying no eeprom/flash device found which comes down to lack of support I guess.
Are there any plans in the nearby feature for implementing these models of IC's?
Kind regards,
MJ
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