flashrom

flashrom@flashrom.org

5 participants
9186 discussions

Start a nNew thread

Update FW on untested chipset
by Роман Ашаев 13 Jan '20

13 Jan '20

Hello. I successfully updated chipset "Intel Skylake" via flashrom utility. Log file in attachment. Thanks

1 0

CH341A & W25X41CLNIG
by Nick 11 Jan '20

11 Jan '20

I need a hand with a W25X41CLNIG chip. I can read it without issue but cant write a thing to it. I am able to write to a W25X40CLNIG I have. This is on Manjaro with a CH341A Thanks kindly, -- Nick Email - hypnogerm(a)gmail.com

1 0

Problem update bios from flashrom
by andreywlf＠protonmail.com 06 Jan '20

06 Jan '20

Hello. I wanted to update the BIOS on my Aser Aspire 3 A315-41 laptop using your flashrom utility, but I got this message: flashrom v1.1 on Linux 5.3.12-2-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). No DMI table found. Found chipset "AMD FP4". Enabling flash write ... Disabling read write protection of flash addresses from 0xffafa000 to 0xffb4cfff failed. FCH device found but SMBus revision 0x61 does not match known values. Please report this to [flashrom@flashrom.org](https://e.mail.ru/compose?To=flashrom@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. The output of the inxi and lspci commands in the attachment. С Уважением, Андрей Ефремов Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

MW0100R
by Anthony S 02 Jan '20

02 Jan '20

I am running into issues reading the SPI off of a MW0100R. This is a RTL8711AM SoC. I am not able to see the chip. However, flashrom is detecting it as a Atmel. According to the fcc documentation on the MW0100R the flash should be 1024kB. This is being read from a raspberry pi 3b+ via the SPI header pins. Any assistance would be appreciated... Thank you.

1 0

Acer Aspire 3 A315-41 cannot read BIOS
by Derk Shredinger 31 Dec '19

31 Dec '19

1 0

Re: In a bind
by Mike Banon 30 Dec '19

30 Dec '19

Try to shorten the wires between SOIC8 and CH341A and/or replace them with the copper ones, maybe that would help. On Sun, Dec 29, 2019 at 9:00 PM AL VAN DER LAAN <aelaan(a)rogers.com> wrote: > > I am trying to flash the HP Elitebook 850 G2 - as mentioned three went succesful but the one I forgot to erase first did not. I have read up a lot about this in the various forums. I tried with -f and it seems part of the bios chip is actually locked. The laptop still boots properly and I can install Windows on it but cannot change any of the bios settings as the TPM is preventing me to manipulate it. I mean it is not too bad these units are going into the resale channel but not the one with the locked bios. I will see if there are any samples, and if I am successful I will upload my process. > > > > On Dec 29, 2019, at 12:42 PM, Mike Banon <mikebdp2(a)gmail.com> wrote: > > > > You haven't described what device you are trying to flash. Usually > > there's nothing wrong with using SOIC8 test clip, for the laptops. > > However, some routers/hdmi recorders/other devices of this type, may > > try powering its' main CPU from a test clip and interfere with your > > programming through a test clip. In example, here's a flashrom mod I > > had to do for making it possible to read a firmware of one router > > through a test clip https://review.coreboot.org/c/flashrom/+/31830 > > (because a CPU tries to power itself from a test clip and access a > > flash chip, its' only available for 30% of each second to a programmer > > behind a test clip), however - despite a similar code for read and > > write - this router becomes software bricked if a write has been > > attempted, and then a chip is inaccessible at all without a > > desoldering. > > > > So a chip itself could be fine, and such problems could be caused by > > an imperfection in your device's hardware design. Other problems could > > be i.e. too long cables between a SOIC8 test clip and a programmer, or > > their poor quality (i.e. electrical resistance of aluminium wires is > > about 1.5x times higher than of the copper ones with the same > > properties). > > > > On Sun, Dec 29, 2019 at 8:32 PM AL VAN DER LAAN <aelaan(a)rogers.com> wrote: > >> > >> Hi Mike, thanks for responding. I tried with Linux as well and am using the SOIC8. I think I did mess up when I forgot to Erase and performed a write to it (it should still erase before the write but here we are). I performed the same tasks on three other units that came out of an auction and successfully reprogrammed them with a bios file obtained from HP. > >> > >> I am thinking of ordering a couple clean ones from eBay and desolder the defective one. > >> > >> And I know, everyone keeps telling me to stop using the SOIC8, but I simply have too much volume with a huge backlog. > >> > >> > >> > >>> On Dec 29, 2019, at 11:18 AM, Mike Banon <mikebdp2(a)gmail.com> wrote: > >>> > >>>> MX25L12835F/MX25L12845E/MX25L12865E > >>> This doesn't seem to be one-time-programmable. Have you tried flashing > >>> it on Linux instead of OS X ? Are you doing ISP (In system > >>> programming, i.e. with a test clip like SOIC8 or SOIC16) ? At the > >>> moment it's unclear to me why your erase operation is failing... > >>> > >>> On Fri, Dec 27, 2019 at 10:34 PM AL VAN DER LAAN <aelaan(a)rogers.com> wrote: > >>>> > >>>> Happy Holidays, > >>>> > >>>> > >>>> So this happened: I forgot to Erase the EEPROM, which clearly is my fault, but it was late and I was tired. > >>>> > >>>> Just trying to see if I can recover this EEprom at all or if I am better getting a couple of new ones from eBay? > >>>> > >>>> > >>>> > >>>> > >>>> flashrom -p ch341a_spi -E -c MX25L12835F/MX25L12845E/MX25L12865E -f > >>>> flashrom v1.1 on Darwin 19.2.0 (x86_64) > >>>> flashrom is free software, get the source code at https://flashrom.org > >>>> > >>>> Calibrating delay loop... OK. > >>>> Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, SPI) on ch341a_spi. > >>>> Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x00000fff: 0x1000 > >>>> ERASE FAILED! > >>>> Looking for another erase function. > >>>> FAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x00007fff: 0x8000 > >>>> ERASE FAILED! > >>>> Looking for another erase function. > >>>> FAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x0000ffff: 0x10000 > >>>> ERASE FAILED! > >>>> Looking for another erase function. > >>>> ^[[B^[[B^[[B^[[BFAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x00ffffff: 0x1000000 > >>>> ERASE FAILED! > >>>> Looking for another erase function. > >>>> FAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x00ffffff: 0x1000000 > >>>> ERASE FAILED! > >>>> Looking for another erase function. > >>>> Looking for another erase function. > >>>> Looking for another erase function. > >>>> No usable erase functions left. > >>>> FAILED! > >>>> 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! > >>>> _______________________________________________ > >>>> flashrom mailing list -- flashrom(a)flashrom.org > >>>> To unsubscribe send an email to flashrom-leave(a)flashrom.org > >> >

1 0

C232 chipset
by Kevin Cody 30 Dec '19

30 Dec '19

I've had success flashing internally on a C232 chipset, an ASUS P10S-I motherboard with a partially working in-progress coreboot port. flashrom picks it up as an opaque chip when flashing internally. It's a W25Q128.V according to the ch341a. Output attached. - Kevin

1 0

Thanking for the tool
by Omer Basri 29 Dec '19

29 Dec '19

Hi, I would like to thank you for development of the flashrom tool, as I was able to fix my bios via the tool. The chip I have is gigadevice GD25B128C and I was able to use the settings for GD25Q128C. The software informed me that reading or writing to this chip wasn't tested so I thought it would help to inform you that both functions worked for me. Sencirely, Omer basri

1 0

Re: In a bind
by Mike Banon 29 Dec '19

29 Dec '19

You haven't described what device you are trying to flash. Usually there's nothing wrong with using SOIC8 test clip, for the laptops. However, some routers/hdmi recorders/other devices of this type, may try powering its' main CPU from a test clip and interfere with your programming through a test clip. In example, here's a flashrom mod I had to do for making it possible to read a firmware of one router through a test clip https://review.coreboot.org/c/flashrom/+/31830 (because a CPU tries to power itself from a test clip and access a flash chip, its' only available for 30% of each second to a programmer behind a test clip), however - despite a similar code for read and write - this router becomes software bricked if a write has been attempted, and then a chip is inaccessible at all without a desoldering. So a chip itself could be fine, and such problems could be caused by an imperfection in your device's hardware design. Other problems could be i.e. too long cables between a SOIC8 test clip and a programmer, or their poor quality (i.e. electrical resistance of aluminium wires is about 1.5x times higher than of the copper ones with the same properties). On Sun, Dec 29, 2019 at 8:32 PM AL VAN DER LAAN <aelaan(a)rogers.com> wrote: > > Hi Mike, thanks for responding. I tried with Linux as well and am using the SOIC8. I think I did mess up when I forgot to Erase and performed a write to it (it should still erase before the write but here we are). I performed the same tasks on three other units that came out of an auction and successfully reprogrammed them with a bios file obtained from HP. > > I am thinking of ordering a couple clean ones from eBay and desolder the defective one. > > And I know, everyone keeps telling me to stop using the SOIC8, but I simply have too much volume with a huge backlog. > > > > > On Dec 29, 2019, at 11:18 AM, Mike Banon <mikebdp2(a)gmail.com> wrote: > > > >> MX25L12835F/MX25L12845E/MX25L12865E > > This doesn't seem to be one-time-programmable. Have you tried flashing > > it on Linux instead of OS X ? Are you doing ISP (In system > > programming, i.e. with a test clip like SOIC8 or SOIC16) ? At the > > moment it's unclear to me why your erase operation is failing... > > > > On Fri, Dec 27, 2019 at 10:34 PM AL VAN DER LAAN <aelaan(a)rogers.com> wrote: > >> > >> Happy Holidays, > >> > >> > >> So this happened: I forgot to Erase the EEPROM, which clearly is my fault, but it was late and I was tired. > >> > >> Just trying to see if I can recover this EEprom at all or if I am better getting a couple of new ones from eBay? > >> > >> > >> > >> > >> flashrom -p ch341a_spi -E -c MX25L12835F/MX25L12845E/MX25L12865E -f > >> flashrom v1.1 on Darwin 19.2.0 (x86_64) > >> flashrom is free software, get the source code at https://flashrom.org > >> > >> Calibrating delay loop... OK. > >> Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, SPI) on ch341a_spi. > >> Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x00000fff: 0x1000 > >> ERASE FAILED! > >> Looking for another erase function. > >> FAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x00007fff: 0x8000 > >> ERASE FAILED! > >> Looking for another erase function. > >> FAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x0000ffff: 0x10000 > >> ERASE FAILED! > >> Looking for another erase function. > >> ^[[B^[[B^[[B^[[BFAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x00ffffff: 0x1000000 > >> ERASE FAILED! > >> Looking for another erase function. > >> FAILED at 0x00000000! Expected=0xff, Found=0x40, failed byte count from 0x00000000-0x00ffffff: 0x1000000 > >> ERASE FAILED! > >> Looking for another erase function. > >> Looking for another erase function. > >> Looking for another erase function. > >> No usable erase functions left. > >> FAILED! > >> 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! > >> _______________________________________________ > >> flashrom mailing list -- flashrom(a)flashrom.org > >> To unsubscribe send an email to flashrom-leave(a)flashrom.org >

1 0

winbond w25128jvsm bios chip for asus chromebox cn65
by Eds Orioque 29 Dec '19

29 Dec '19

try to flash this bios chip and this is the log ubuntu@ubuntu:~$ sudo ./flashrom -p ch341a_spi flashrom p1.0-23-g34b0ff2f on Linux 5.0.0-23-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 Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on ch341a_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! No operations were specified. another one sudo ./flashrom -p ch341a_spi -r badflash.rom flashrom p1.0-23-g34b0ff2f on Linux 5.0.0-23-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 Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on ch341a_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Read is not working on this chip. Aborting. hoping for your help tnx so much in advance ---------- Forwarded message --------- From: *Eds Orioque* <conradoorioque(a)gmail.com> Date: Fri, Dec 27, 2019, 4:58 PM Subject: winbond w25128jvsm bios chip for asus chromebox cn65 To: <flashrom(a)flashrom.org> try to flash this bios chip and this is the log ubuntu@ubuntu:~$ sudo ./flashrom -p ch341a_spi flashrom p1.0-23-g34b0ff2f on Linux 5.0.0-23-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 Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on ch341a_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! No operations were specified. another one sudo ./flashrom -p ch341a_spi -r badflash.rom flashrom p1.0-23-g34b0ff2f on Linux 5.0.0-23-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 Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on ch341a_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Read is not working on this chip. Aborting. hoping for your help tnx so much in advance

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom