flashrom

flashrom@flashrom.org

5 participants
9161 discussions

Re: LA-894 Parrot
by Mike Banon 09 May '19

09 May '19

When you run the "apt-get install flashrom" command, you get the flashrom version that was build by the package maintainers of your Linux. If they cloned and built this flashrom version quite long ago, you get the old version with this apt-get. The easiest way to get the latest version is to clone the latest flashrom source code - git clone https://review.coreboot.org/flashrom , and then build it from source by running " make " command. Maybe you need some dependencies installed before you could successfully compile this. Please check this page - https://www.flashrom.org/Downloads#Installation_from_source - it contains some package names that you might have to install before running "make" . On Thu, May 9, 2019 at 9:35 AM fugee ohu <fugee279(a)gmail.com> wrote: > > I see sorry about that I might have checked what version I was running > The message made me think my version was too new and I was actually > even trying to install older versions starting with 9.0 and FTDI > support wasn't found so make failed Installing FTDI support requires > file operations and symlinks and there's no easy way to install > otherwise that I know of I assume you built FTDI support into later > versions Whatever version I was running, that's what I got when I ran > apt-get install flashrom on raspbian Will I have to compile the latest > release from source? > > On Thu, May 9, 2019 at 2:29 AM Mike Banon <mikebdp2(a)gmail.com> wrote: > > > > Could you please test with the latest flashrom version? Yours is a bit > > outdated, maybe git clone https://review.coreboot.org/flashrom and > > make? Also, what is a chip that you are trying to access, please tell > > the markings written on it. And check that your connectivity is > > correct, that the wires aren't too long, etc. > > > > On Wed, May 8, 2019 at 7:47 PM fugee ohu <fugee279(a)gmail.com> wrote: > > > > > > I get the long error message shown below but I can't find the log file > > > to show you I don't know where it is, it's not in /var/log I assume > > > there's only one Winbond chip on the board I found the Winbond chip > > > and assume it's the bios chip > > > > > > 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 at 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. > > > [florin at stick flashrom]$ sudo ./flashrom -p ch341a_spi -r ~/Desktop/bios.bin > > > flashrom v0.9.9-r1954 on Linux 4.10.11-1-ARCH (x86_64) > > > flashrom is free software, get the source code at https://flashrom.org > > > > > > Calibrating delay loop... ^[[AOK. > > > > > > Found Generic flash chip "unknown SPI chip (RDID)" (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 at 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. > > > _______________________________________________ > > > flashrom mailing list -- flashrom(a)flashrom.org > > > To unsubscribe send an email to flashrom-leave(a)flashrom.org

1 0

LA-894 Parrot
by fugee ohu 09 May '19

09 May '19

I get the long error message shown below but I can't find the log file to show you I don't know where it is, it's not in /var/log I assume there's only one Winbond chip on the board I found the Winbond chip and assume it's the bios chip 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 at 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. [florin at stick flashrom]$ sudo ./flashrom -p ch341a_spi -r ~/Desktop/bios.bin flashrom v0.9.9-r1954 on Linux 4.10.11-1-ARCH (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... ^[[AOK. Found Generic flash chip "unknown SPI chip (RDID)" (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 at 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.

2 1

Read is not working on this chip Aboring!
by fugee ohu 08 May '19

08 May '19

Here's what I'm reading from my stretch-lite console on a Raspberry Pi Zero W Found generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi. The test status of this chip may have been update in the latest development version, please email a report ... I'm trying to flash bios on an Acer C710 chromebook

1 0

Chip size
by EvilGremlin 07 May '19

07 May '19

Hello! Can you change chip size verification? At least for SPI EEPROMs, that i flash almost every day, chip size doesn't really matter. I find it really annoying, that i cannot flash 32Mb image to 64Mb chip and there is no option to force it. So i have to boot Windows or edit image just for that. Almost any other software can do that just fine. So, can you add force key or warning message with (yes/no) option. Default "yes", of course.

2 1

Intel Atom E3845
by karthikm618＠gmail.com 07 May '19

07 May '19

Hello, I'm working on Opencellular (https://code.fb.com/connectivity/introducing-opencellular-an-open-source-wi…) which is based on Intel Atom E3845. I have built the coreboot image and would like to flash onto the Opencellular board. Could you tell how to flash only onto the BIOS region using Flashrom? Thank you, in advance.

2 1

Intel Atom E3845
by karthikm618＠gmail.com 07 May '19

07 May '19

1 0

Green CH341A didn't work, turned out it's a badly soldered CS leg. Fixed now ;-)
by Mike Banon 04 May '19

04 May '19

My spare green CH341A almost always was unable to find a chip. Luckily I have another working CH341A, so started comparing them with a multimeter : When a "healthy" CH341A is simply plugged into a USB port, without any chips connected, there is a 3.15V - 3.3V voltage between GND hole and other 7 holes at 25xx socket. But a "glitchy" CH341A, when put to the same situation, did not have a ~3V voltage difference between GND and CS pin. Then I checked a resistance between CS leg of CH341A chip ( found it using this document - https://www.onetransistor.eu/2017/08/ch341a-mini-programmer-schematic.html ) and CS pin at the bottom of programmer (instead of CS hole for convenience) - it was almost always "infinite", but sometimes - when I pushed CS leg with a multimeter pin - there was a close to 0 Ohm resistance, almost zero. So I did a small soldering of CH341A CS leg, see a picture https://i.redd.it/mfrgs45beuv21.jpg - luckily this CS leg is at the corner of chip so was quite convenient to solder - and now this CH341A is happy and working perfectly! ;-) Will flash many BIOSes :3

1 0

Success in writing to AT29C010A via 3Com 905B
by Quinn Plattel 03 May '19

03 May '19

Hi, Just want to report that I have now had many successes in reading and writing to the following roms via the 3Com 905B network card: ATMEL AT29C010A 120ns ATMEL AT29C512 120ns The ATMEL AT29C010A 70ns do fail probably because of the speed. I have tested with both the iPXE and XTIDE open source projects. -- Best regards/Ystävällisin terveisin/Med venlig hilsen, Quinn Plattel

1 2

Outdated command-line stability warning
by Charles Daffern 01 May '19

01 May '19

Hello flashrom people, I just wanted to bring a small triviality to your attention: currently, `flashrom --help' warns the user that the command line interface is due to change before v1.0, but we have already passed that version. It is a very trivial change, but for convenience's sake I will attach a patch for `git apply'.

1 0

Bug Report
by Paulo Zorzan 30 Apr '19

30 Apr '19

./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -r romread_v1.rom ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mb_ukqwerty_txtmode.rom flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi. Error: WIP bit after WRSR never cleared spi_write_status_register failed. Reading old flash chip contents... Calibrating delay loop... OK. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi. Error: WIP bit after WRSR never cleared spi_write_status_register failed. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x5a, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x1d1 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 -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi. Error: WIP bit after WRSR never cleared spi_write_status_register failed. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x5a, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x2d1 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 -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi. Error: WIP bit after WRSR never cleared spi_write_status_register failed. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000100! Expected=0xff, Found=0x89, failed byte count from 0x00000000-0x00000fff: 0x2d ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x5a, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x1d1 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 -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x00000fff: 0x66 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x5a, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x3d1 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 -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mb_ukqwerty_vesafb.rom flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi. Error: WIP bit after WRSR never cleared spi_write_status_register failed. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00001000-0x00001fff: 0x62 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x0000ffff: 0x6829 ERASE FAILED! ading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0xf84ce ERASE FAILED! ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0xf83cf ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. 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. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks!

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom