flashrom March 2020

flashrom@flashrom.org

17 participants
18 discussions

by Greg Troxel

I have a PC Engines apu2d4 running NetBSD 8 (amd64), and would like to update coreboot/etc. on it. I searched the list (perhaps not well) and didn't find any reports of success, although I realize things are generally expected to work so success might well go unreported. I am using flashrom 1.1 as built from pkgsrc. I was able to read the existing bios without issues as: flashrom --programmer internal -r 20200301-readflash.rom Before I try to write, I am wondering if anyone has successfully done an apu2 bios update with flashrom under NetBSD 8 amd64? (I have a debricking adaptor (spi1a) and will prepare a Linux flashing image on USB before trying myself, whether I not a get a report of success.) Thanks, Greg

5 months, 3 weeks

ST 95XXX chips

by Николай Николаев

Hello My pull request has already been created that had occurred *several months* previously. I added support for ST 95XXX chips . The following chipsets have been successfully tested for read, erase and write operations: ST [ 95080, 95160, 95320, 95640, 95128, 95256 ]. I would like to discuss a new features. Maybe someone in the community will spent a bit of time and review my pull request. Don't worry about the conflicting files. The part of the code has already been merged into effect. *I'm open-minded and ready. *

1 year, 4 months

Gigabyte A320-S2H AMD FP4

by Balázs Vinarz

Hi! This board seem to be failing with the internal programmer. F23 BIOS on board. Regards

1 year, 6 months

Re: Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D)

by Angel Pons

Hi Ocean On Tue, Mar 24, 2020 at 2:41 AM Ocean Huang <hahuan(a)celestica.com> wrote: > > Hi Angel: > > "0xa1c8" seems is the "QS/PRQ" SKU, but it does not mark it as "QS/PRQ" SKU in the eds spec "568202-d-2100-eds-rev2-1-review.pdf", the detail you can see the below image. > > > However, I think the device id 0xa1c8 whether QS/PRQ SKU or Super SKU will not affect for flashrom tool. Right, looks like the Xeon D-2100 integrates a Lewisburg PCH inside. That explains why I couldn't find that ID anywhere: there is no publicly available datasheet for these Xeons. > Anyway, thank you very much for the support. > > Thanks, > Best Regards, > Ocean > > On Mon, Mar 23, 2020 at 11:08 PM Angel Pons <th3fanbus(a)gmail.com> wrote: >> >> Hi Ocean, >> >> On Mon, Mar 23, 2020 at 2:00 PM Ocean Huang via flashrom >> <flashrom(a)flashrom.org> wrote: >> > >> > Hi David: >> > >> > For flashrom could update BIOS successfully on the Intel Bakerville platform(CPU:SKY-D), we need to add device id to chipset_enables table in the file of"chipset_enables.c", or it will cause below error: >> > WARNING: No chipset found. Flash detection will most likely fail. >> > No EEPROM/flash device found. >> > Note: flashrom can never write if the flash chip isn't found automatically. >> > >> > So could you please help to add these three device ids to the chipset_enable table and upload to the Github? >> > Attached the changed file. >> >> I see that you have added these three new device IDs: >> >> {0x8086, 0xa1c8, NT, "Intel", "C620 Series Chipset Supersku", >> enable_flash_c620}, >> {0x8086, 0xa248, NT, "Intel", "C620 Series Chipset Supersku", >> enable_flash_c620}, >> {0x8086, 0xa249, NT, "Intel", "C620 Series Chipset Supersku", >> enable_flash_c620}, >> >> I can confirm that the last two IDs are for Super SKUs, but "0xa1c8" >> (the first one) seems to be a "QS/PRQ" SKU. Could you please confirm >> it? I have created a change to add these IDs: >> >> https://review.coreboot.org/39780 >> >> In addition, since flashrom can successfully update the BIOS on these >> chipsets, knowing the Device IDs that have been tested would be much >> appreciated. That way, we can mark the chipsets as tested. >> >> > Thanks, >> > Best Regards, >> > Ocean >> > >> > -- >> > Thanks, >> > Best Regards, >> > Ocean Huang >> > BIOS Engineer >> > Celestica(Shanghai) R&D Center, China >> > email: hahuan(a)celestica.com >> > www.celestica.com >> > _______________________________________________ >> > flashrom mailing list -- flashrom(a)flashrom.org >> > To unsubscribe send an email to flashrom-leave(a)flashrom.org >> >> Thanks in advance, >> >> Angel Pons > > > > -- > Thanks, > Best Regards, > Ocean Huang > BIOS Engineer > Celestica(Shanghai) R&D Center, China > email: hahuan(a)celestica.com > www.celestica.com Best regards, Angel Pons

1 year, 6 months

Re: Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D)

by David Hendricks

(Resending to the mailing list) ________________________________ From: David Hendricks <dhendrix(a)fb.com> Sent: Monday, March 2, 2020 2:50:24 PM To: flashrom(a)flashrom.org <flashrom(a)flashrom.org>; Ocean Huang <hahuan(a)celestica.com> Subject: Re: [flashrom] Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D) Hello Ocean, At the moment we do not support updating the Intel ME region. You may target other regions described by the flash descriptor using the --ifd option, for example `flashrom -p internal --ifd -i bios --noverify-all -w CBR.1.00.01.bin`. Depending on your use case, another option is to modify the flash descriptor to allow the host to write to the ME region. However Intel recommends locking the ME region so that reads and writes to the ME region from the host are not allowed. Please also see https://flashrom.org/ME#Suggested_workarounds for additional guidance. ________________________________ From: Ocean Huang via flashrom <flashrom(a)flashrom.org> Sent: Wednesday, February 26, 2020 5:20 AM To: flashrom(a)flashrom.org <flashrom(a)flashrom.org> Subject: [flashrom] Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D) Hi Vendor: We have some issue when using flashrom tool update BIOS & ME firmware on the Intel Bakeville platform, you can refer to the below error log, could you please help give some comments or suggestions about this issue? [root@localhost flashrom-v1.1]# ./flashrom -p internal -w CBR.1.00.01.bin flashrom v1.1 on Linux 3.10.0-957.el7.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org&d=DwMFaQ&…> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel C620 Series Chipset Supersku". 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<mailto:flashrom@flashrom.org> including a verbose (-V) log. Thank you! Enabling flash write... SPI Configuration is locked down. FREG2: Management Engine region (0x00003000-0x00a15fff) is locked. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME<https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org_ME&d=DwMF…> for details. At least some flash regions are read protected. You have to use a flash layout and include only accessible regions. For write operations, you'll additionally need the --noverify-all switch. See manpage for more details. Enabling hardware sequencing because some important opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" (32768 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Reading old flash chip contents... Transaction error between offset 0x00003000 and 0x0000303f (= 0x00003000 + 63)! FAILED. [root@localhost flashrom-v1.1]# ./flashrom -p internal -r 111.bin --ifd -i bios flashrom v1.1 on Linux 3.10.0-957.el7.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org&d=DwMFaQ&…> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel C620 Series Chipset Supersku". 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<mailto:flashrom@flashrom.org> including a verbose (-V) log. Thank you! Enabling flash write... SPI Configuration is locked down. FREG2: Management Engine region (0x00003000-0x00a15fff) is locked. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME<https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org_ME&d=DwMF…> for details. At least some flash regions are read protected. You have to use a flash layout and include only accessible regions. For write operations, you'll additionally need the --noverify-all switch. See manpage for more details. Enabling hardware sequencing because some important opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" (32768 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Reading ich descriptor... done. Using region: "bios". Reading flash... done. -- Thanks, Best Regards, Ocean Huang BIOS Engineer Celestica(Shanghai) R&D Center, China email: hahuan(a)celestica.com<mailto:hahuan@celestica.com> www.celestica.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.celestica.com_&d=Dw…>

1 year, 6 months

25x10cln1g erase and write failed!

by The real bruno mars

Hello all. It seems that I am having issues with my Arduino based flasher. I installed Frser-duino on my Arduino UNO and tried flashing a winbond 25x10cln1g. However I am running into errors. My log is here: https://pastebin.com/eLJNu43T I would greatly appreciate any help.

1 year, 6 months

Supporting GD25LB64CVIG

by Renato Kristić

Hello, I'd like to flash *GD25LB64CVIG* but I cannot see that it is shown in the list of supported chips. Would it be possible to add support for this chip? If not, is there any guide that can help me to manually add support for this chip. Best Regards, -- *Renato Kristić*, Electronic system engineer +387 63 77 48 45 | kristic.renato(a)nsoft.com | nsoft.com

1 year, 6 months

Failed flashing

by Ryan Campbell

I’m attempting to flash an MSI MS-7680 Ver. 5.1 (H61M-P25 (B3)) Here is what is shown after running flashrom: Found Winbond flash chip “W25Q32.V” (4096 kB, SPI) on ch341a_spiReading old flash chip contents...done.Erasing and writing flash chip...Erase/write done.Verifying flash...FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x003fffff: 0x1f3d61Your flash chip is in an unknown state I did successfully create a backup, but when I opened it with a hex editor, it is mostly FF. Is the chip toast? Or is there something else I can try? Sent from Yahoo Mail for iPhone

1 year, 6 months

CH341 verifying fail under Linux

by Vincenzo Nesticò

As suggested in your website I am reporting a problem when trying to flash a W25Q128FV using CH341 mini programmer (black version) with a dedicated PC running Linux/Ubuntu. I have this message displaying. ------------------------------------------------------------------------------------------------------------- Calibrating delay loop... delay loop is unreliable, trying to continue OK. Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00b555d9! Expected=0xae, Found=0x8e, failed byte count from 0x00000000-0x00ffffff: 0x3 Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! ---------------------------------------------------------------------------------------------------------------- If possible I have the opportunity to use different programmer as TL866II plus, EZP2019. I am new to Ubuntu and I am writing from Italy. Looking forward to your reply.

1 year, 6 months

Trying to fix my Chromebook

by Johnny Doeskigoog

firmware update said to file a bug report trying to map non-existent mapping, etc. Let me know how to fix pls...tried a lot of things already :s Thanks Allan Nott allanwnott(a)gmail.com 2049605003

1 year, 6 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom March 2020