flashrom February 2015

flashrom@flashrom.org

30 participants
77 discussions

Start a nNew thread

ARM-USB-OCD works!
by skrizi＠web.de 17 Feb '15

17 Feb '15

1 0

Re: [flashrom] flashrom support for Spansion S25FL128S
by Antonio Ospite 17 Feb '15

17 Feb '15

On Mon, 16 Feb 2015 20:50:39 -0600 <Lakesh_Sharma(a)DELL.com> wrote: > > Hi Idwer > > I had fixed the compilation issues and could generate the binary. > I tried to read the bios chip first, but it does not seem to recognize S25FL128S > > (1) It lists the chip as supported: > flashrom# ./flashrom --list-supported | grep S25FL128S > Spansion S25FL128S......0 16384 SPI > Spansion S25FL128S......1 16384 SPI > > > (2) However when it is specified with --chip options, it says not supported or unknown. > > flashrom# ./flashrom --chip S25FL128S flashrom# ./flashrom --chip "SS25FL128S......0" or the other one depending on your actual chip. The dots are placeholders for variable characters in the chip name for different chip variants. And remember to add the -c option also when you perform the other operations, flashrom still can't discriminate between the variants on its own. > flashrom v0.9.8-rc1-r1883 on Linux 3.14.0-rc8 (x86_64) > flashrom is free software, get the source code at http://www.flashrom.org > > Error: Unknown chip 'S25FL128S' specified. > Run flashrom -L to view the hardware supported in this flashrom version. > > > (3) Tried to read the chip first. It could not determine the chip type. > > > ./flashrom -p internal:laptop=this_is_not_a_laptop -r file_name.bin > flashrom v0.9.8-rc1-r1883 on Linux 3.14.0-rc8 (x86_64) > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > ======================================================================== > WARNING! You may be running flashrom on an unsupported laptop. We could > not detect this for sure because your vendor has not setup the SMBIOS > tables correctly. You can enforce execution by adding > '-p internal:laptop=this_is_not_a_laptop' to the command line, but > please read the following warning if you are not sure. > > Laptops, notebooks and netbooks are difficult to support and we > recommend to use the vendor flashing utility. The embedded controller > (EC) in these machines often interacts badly with flashing. > See the manpage and http://www.flashrom.org/Laptops for details. > > If flash is shared with the EC, erase is guaranteed to brick your laptop > and write may brick your laptop. > Read and probe may irritate your EC and cause fan failure, backlight > failure and sudden poweroff. > You have been warned. > ======================================================================== > Proceeding anyway because user forced us to. > Found chipset "Intel Avoton/Rangeley". > 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 including a verbose (-V) log. > Thank you! > Enabling flash write... Warning: SPI Configuration Lockdown activated. > OK. > Found Spansion flash chip "S25FL127S-64kB" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL127S-256kB" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL128P......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL128P......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL128S......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL128S......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL129P......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL129P......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Multiple flash chip definitions match the detected chip(s): "S25FL127S-64kB", "S25FL127S-256kB", "S25FL128P......0", "S25FL128P......1", "S25FL128S......0", "S25FL128S......1", "S25FL129P......0", "S25FL129P......1" > Please specify which chip definition to use with the -c <chipname> option. > IOT just do what flashrom is telling you here :) Ciao, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?

2 1

Re: [flashrom] flashrom support for Spansion S25FL128S
by Lakesh_Sharma＠DELL.com 17 Feb '15

17 Feb '15

Hi Idwer I had fixed the compilation issues and could generate the binary. I tried to read the bios chip first, but it does not seem to recognize S25FL128S (1) It lists the chip as supported: flashrom# ./flashrom --list-supported | grep S25FL128S Spansion S25FL128S......0 16384 SPI Spansion S25FL128S......1 16384 SPI (2) However when it is specified with --chip options, it says not supported or unknown. flashrom# ./flashrom --chip S25FL128S flashrom v0.9.8-rc1-r1883 on Linux 3.14.0-rc8 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Error: Unknown chip 'S25FL128S' specified. Run flashrom -L to view the hardware supported in this flashrom version. (3) Tried to read the chip first. It could not determine the chip type. ./flashrom -p internal:laptop=this_is_not_a_laptop -r file_name.bin flashrom v0.9.8-rc1-r1883 on Linux 3.14.0-rc8 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. ======================================================================== WARNING! You may be running flashrom on an unsupported laptop. We could not detect this for sure because your vendor has not setup the SMBIOS tables correctly. You can enforce execution by adding '-p internal:laptop=this_is_not_a_laptop' to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel Avoton/Rangeley". 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 including a verbose (-V) log. Thank you! Enabling flash write... Warning: SPI Configuration Lockdown activated. OK. Found Spansion flash chip "S25FL127S-64kB" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL127S-256kB" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL128P......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL128P......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL128S......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL128S......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL129P......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL129P......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Multiple flash chip definitions match the detected chip(s): "S25FL127S-64kB", "S25FL127S-256kB", "S25FL128P......0", "S25FL128P......1", "S25FL128S......0", "S25FL128S......1", "S25FL129P......0", "S25FL129P......1" Please specify which chip definition to use with the -c <chipname> option. regards lakesh ________________________________________ From: Sharma, Lakesh Sent: Monday, February 16, 2015 3:42 PM To: Idwer Vollering Cc: flashrom; Taylor, Ron; Natarajan, Kannan Subject: RE: [flashrom] flashrom support for Spansion S25FL128S Dell - Internal Use - Confidential Hi Idwer I could not access the svn based link. Also the changeset link is not accessible. So instead I have download it from https://github.com/jhcloos/flashrom as it stated that “Mirror of svn://flashrom.org/flashrom” Once I try to compile it, I see following error. Can you pls help. flashrom > make Replacing all version templates with 0.9.8-rc1-r1883. Package libftdi was not found in the pkg-config search path. Perhaps you should add the directory containing `libftdi.pc' to the PKG_CONFIG_PATH environment variable No package 'libftdi' found Package libusb was not found in the pkg-config search path. Perhaps you should add the directory containing `libusb.pc' to the PKG_CONFIG_PATH environment variable No package 'libusb' found Checking for a C compiler... found. Target arch is x86 Target OS is Linux Checking for libpci headers... found. Checking version of pci_get_dev... new version (including PCI domain parameter). Checking if libpci is present and sufficient... yes. Checking for libusb-0.1/libusb-compat headers... .test.c:5:17: fatal error: usb.h: No such file or directory #include <usb.h> ^ compilation terminated. not found. Please install libusb-0.1 headers or libusb-compat headers. See README for more information. make: *** [hwlibs] Error 1 -----Original Message----- From: Idwer Vollering [mailto:vidwer@gmail.com] Sent: Monday, February 16, 2015 3:09 PM To: Sharma, Lakesh Cc: flashrom; Taylor, Ron; Natarajan, Kannan Subject: Re: [flashrom] flashrom support for Spansion S25FL128S 2015-02-16 22:19 GMT+01:00 : > Dell - Internal Use - Confidential This disclaimer is useless on a public mailing list ;) > > Hello flashrom team. > > > > > > We are trying to access Spansion S25FL128S chip using flashrom (ver 0.9.7). > > It is connected to Rangeley cpu using SPI i/f. > > It seems that this chip is not supported in current version of flashrom ? Support for that particular chip is present in development code, see subversion revision r1858 ( http://tracker.coreboot.org/trac/flashrom/changeset/1858 ). You can obtain the development code through the steps mentioned here: http://flashrom.org/Downloads#Installation_from_source > > Pls see the errors seen during read and write in attachments. > > > > Do we need to import patch listed in url below for suppothing this chip: > > > > http://flashrom.flashrom.narkive.com/zDxnVzWn/s25fl128s-0-on-usbblaste > r-spi > > > > > > regards > > lakesh HTH, Idwer > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] flashrom support for Spansion S25FL128S
by Lakesh_Sharma＠DELL.com 16 Feb '15

16 Feb '15

Dell - Internal Use - Confidential Hi Idwer I could not access the svn based link. Also the changeset link is not accessible. So instead I have download it from https://github.com/jhcloos/flashrom as it stated that "Mirror of svn://flashrom.org/flashrom" Once I try to compile it, I see following error. Can you pls help. flashrom > make Replacing all version templates with 0.9.8-rc1-r1883. Package libftdi was not found in the pkg-config search path. Perhaps you should add the directory containing `libftdi.pc' to the PKG_CONFIG_PATH environment variable No package 'libftdi' found Package libusb was not found in the pkg-config search path. Perhaps you should add the directory containing `libusb.pc' to the PKG_CONFIG_PATH environment variable No package 'libusb' found Checking for a C compiler... found. Target arch is x86 Target OS is Linux Checking for libpci headers... found. Checking version of pci_get_dev... new version (including PCI domain parameter). Checking if libpci is present and sufficient... yes. Checking for libusb-0.1/libusb-compat headers... .test.c:5:17: fatal error: usb.h: No such file or directory #include <usb.h> ^ compilation terminated. not found. Please install libusb-0.1 headers or libusb-compat headers. See README for more information. make: *** [hwlibs] Error 1 -----Original Message----- From: Idwer Vollering [mailto:vidwer@gmail.com] Sent: Monday, February 16, 2015 3:09 PM To: Sharma, Lakesh Cc: flashrom; Taylor, Ron; Natarajan, Kannan Subject: Re: [flashrom] flashrom support for Spansion S25FL128S 2015-02-16 22:19 GMT+01:00 : > Dell - Internal Use - Confidential This disclaimer is useless on a public mailing list ;) > > Hello flashrom team. > > > > > > We are trying to access Spansion S25FL128S chip using flashrom (ver 0.9.7). > > It is connected to Rangeley cpu using SPI i/f. > > It seems that this chip is not supported in current version of flashrom ? Support for that particular chip is present in development code, see subversion revision r1858 ( http://tracker.coreboot.org/trac/flashrom/changeset/1858 ). You can obtain the development code through the steps mentioned here: http://flashrom.org/Downloads#Installation_from_source > > Pls see the errors seen during read and write in attachments. > > > > Do we need to import patch listed in url below for suppothing this chip: > > > > http://flashrom.flashrom.narkive.com/zDxnVzWn/s25fl128s-0-on-usbblaste > r-spi > > > > > > regards > > lakesh HTH, Idwer > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] flashrom support for Spansion S25FL128S
by Idwer Vollering 16 Feb '15

16 Feb '15

2015-02-16 22:19 GMT+01:00 <Lakesh_Sharma(a)dell.com>: > Dell - Internal Use - Confidential This disclaimer is useless on a public mailing list ;) > > Hello flashrom team. > > > > > > We are trying to access Spansion S25FL128S chip using flashrom (ver 0.9.7). > > It is connected to Rangeley cpu using SPI i/f. > > It seems that this chip is not supported in current version of flashrom ? Support for that particular chip is present in development code, see subversion revision r1858 ( http://tracker.coreboot.org/trac/flashrom/changeset/1858 ). You can obtain the development code through the steps mentioned here: http://flashrom.org/Downloads#Installation_from_source > > Pls see the errors seen during read and write in attachments. > > > > Do we need to import patch listed in url below for suppothing this chip: > > > > http://flashrom.flashrom.narkive.com/zDxnVzWn/s25fl128s-0-on-usbblaster-spi > > > > > > regards > > lakesh HTH, Idwer > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

flashrom support for Spansion S25FL128S
by Lakesh_Sharma＠DELL.com 16 Feb '15

16 Feb '15

Dell - Internal Use - Confidential Hello flashrom team. We are trying to access Spansion S25FL128S chip using flashrom (ver 0.9.7). It is connected to Rangeley cpu using SPI i/f. It seems that this chip is not supported in current version of flashrom ? Pls see the errors seen during read and write in attachments. Do we need to import patch listed in url below for suppothing this chip: http://flashrom.flashrom.narkive.com/zDxnVzWn/s25fl128s-0-on-usbblaster-spi regards lakesh

1 0

Re: [flashrom] [PATCH] Add programmer for the MSTAR I2C ISP protocol
by Stefan Tauner 16 Feb '15

16 Feb '15

On Mon, 9 Feb 2015 00:53:40 +0100 Idwer Vollering <vidwer(a)gmail.com> wrote: > 2014-05-04 18:20 GMT+02:00 Alexandre Boeglin <alex(a)boeglin.org>: > > Hi, > > > > Here is a patch, that provides support for the MSTAR ISP protocol. > > > > Basically, among other chips, MSTAR manufactures SoCs that equip TV sets > > and computer screens, and it seems that all of their products use the > > same in-system programming protocol. Basically, they use the DDC channel > > of VGA or DVI connectors, which is actually an I2C bus, to encapsulate > > SPI frames (the flash chip is connected to the SoC through an SPI bus). > > > > I wrote this patch since the screen I bought had a software bug, and the > > manufacturer only released a new firmware binary, but no tool or > > instructions on flashing it. > > > > More details can be found here: > > http://boeglin.org/blog/index.php?entry=Flashing-a-BenQ-Z-series-for-free(d… > > There seems to be a silicon (=SoC) bug as well. > > One can recover by rotating the original image (YOU DO HAVE BACKUPS, > RIGHT :) ) _back_wards - the example assumes the read file is 128 > kilobyte large: > tail -c 1 orig_read.bin > realimage.bin; head -c 131071 orig_read.bin > >> realimage.bin; flashrom -p mstar -w realimage.bin --noverify hm... I wonder if that is a bug in how we do it... but the write routine looks really trivial. Maybe it would be a good idea to start a list with monitors, SoC revisions... (whatever ID data is accessible) that require this hack. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Verbose Log
by Stefan Tauner 14 Feb '15

14 Feb '15

On Tue, 6 Jan 2015 22:24:31 +0100 Rainer Spillmann <rainerspillmann(a)googlemail.com> wrote: > Hello Stefan, > > yes. Hello Rainer, I have added your board to our list of supported hardware and will commit that later together with other small changes. > 2015-01-06 0:41 GMT+01:00 Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at>: > > > On Sun, 4 Jan 2015 23:35:09 +0100 > > Rainer Spillmann <rainerspillmann(a)googlemail.com> wrote: > > > > > Hello Flashrom, > > > > > > I could update a Fujitsu Esprimo E5625 (mainboard D2724-A1x) to a Esprimo > > > E5635 (mainboard D2904-A1x) to support AMD AM2/AM3 C3 revision > > processors. > > > I have used the official E5635 bios from the fujitsu website which > > normally > > > would say when trying to update that the bios does not match the system > > due > > > to it is a E5625. The only difference of the E5635 is a chassis lock on > > the > > > mainboard. It now works perfect. > > > > > > Normally the used Esprimo E5625 does only support due to missing > > microcode > > > and older AMD agesa rom up to AMD C2 prozessors witht the official E5625 > > > bios. > > > ( > > > > > http://en.wikipedia.org/wiki/List_of_AMD_Phenom_microprocessors#.22Rana.22_… > > > ) > > > > Hello Rainer, > > > > thank you for your report. The log file got mangled too much to be > > useful (you better should have used the -o option of flashrom I guess). > > Anyway, if I interpret your mail correctly apart from sharing your story > > you also want me to add the D2724-A1x to our list of tested boards. Is > > that correct? > > > > -- > > Kind regards/Mit freundlichen Grüßen, Stefan Tauner > > -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Add PICkit2 as an SPI programmer
by Justin Chevrier 14 Feb '15

14 Feb '15

The patch as committed works fine here (only tested read). In addition, I tried other voltage values (eg. 2.9V, 3.3V, 3.1V) beyond the 3 currently supported and the hardware happily sets those voltages as well. Thanks again, Justin On Sun, Feb 8, 2015 at 6:23 PM, Justin Chevrier <jchevrier(a)gmail.com> wrote: > Hey Stefan, > > Apologies for the late response. > > voltage=0V along with the 3 voltage levels was basically just a matter > of doing the same thing as the Dediprog code. The 3 voltage levels in > particular made sense as I assumed that covered all current SPI chips. > I'm not sure what the hardware will do if other values are chosen, > although you've piqued my interest. If someone else doesn't beat me to > it, I'll try out the committed (thanks btw) version of the patch and > attempt setting other voltages. > > Justin > > On Sat, Jan 31, 2015 at 9:56 PM, Stefan Tauner > <stefan.tauner(a)alumni.tuwien.ac.at> wrote: >> On Fri, 26 Dec 2014 20:53:47 -0500 >> Justin Chevrier <jchevrier(a)gmail.com> wrote: >> >>> Hi Stefan, >>> >>> It seems you're correct. Signed off is below. >>> >>> Signed-off-by: Justin Chevrier <jchevrier(a)gmail.com> >>> >> >> Does the option to set voltage=0V really make sense? But since this is >> even possible... I would rather set it to 0V at shutdown. If that turns >> off the drivers completely it might be very useful while doing >> in-circuit programming because the programmer could remain attached >> even when the target is running. >> >> Why do we restrict the levels to 3 values although the API seems to >> allow to transmit a much finer resolution? What does the hardware >> actually do with these values? >> >> -- >> Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Intel HM65
by roberto.russo＠x-akseli.fi 12 Feb '15

12 Feb '15

FAILED

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom February 2015