On Fri, 11 Dec 2015 10:52:38 +0100
Ruben Van de Put <rubenvandeput(a)gmail.com> wrote:
> I'm having some problems flashing a SPI chip with the BusPirate V3. Writing
> the image is successful but verification is not successful.
> First try with chip on breadboard and long leads (20-25cm):
> Then I shortened the signal leads and soldered them directly on the
> Then I soldered all leads directly on the chip (with an adapter) instead of
> using a breadboard:
> I also tried lowering the SPI speed to 1 MHz:
> Current set-up
> [image: Inline afbeelding 1]
> [image: Inline afbeelding 2]
> Chip datasheet: http://www.farnell.com/datasheets/1674442.pdf
> Flash connected in this way: http://flashrom.org/Bus_Pirate
> Is there anything else I can try or should I try replacing the flash chip?
if you did not give up yet: looks like your changes constantly improved
the situation and you would probably succeed if you just continued to
write the same image a few more times.
One thing that could further improve the communication between the BP
and the flash chip: adding line termination resistors or capacitors as
well as a decoupling capacitor between VCC and GND as near as possible
to the flash chip.
See also https://www.flashrom.org/ISP with some more details even
though the site is directed at other use cases.
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
On Thu, 2015-12-17 at 13:08 +0300, Антон Кочков wrote:
> Mainstream flashrom currently not yet merged patches, adding support
> of reading layout. Because ME region usually not readable not from ME
> it should be skipped, so using layout file, in your case:
> # flashrom layout v2
> 0x00000000:0x00000fff descr
> 0x00500000:0x00ffffff BIOS
> 0x00003000:0x004fffff ME
> 0x00001000:0x00002fff GbE
> And using flashrom with my patches should help:
> Some of the patches are still 'dirty' but should work - I've checked
> them on a bunch of hardware.
> you need to run it like:
> flashrom -V -p internal -l this_file.layout -i BIOS -r bios_dump.bin
Layout files are currently supported for write operations only.
I thought you mean the read operation would work.
On Wed, 16 Dec 2015 01:00:15 +0100
Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> wrote:
> No other changes are required to build flashrom (excluding programmers
> with NEED_PCI) on Android.
> Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at>
> os.h | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
> diff --git a/os.h b/os.h
> index 2e6dbaa..e5f72e4 100644
> --- a/os.h
> +++ b/os.h
> @@ -58,6 +58,11 @@
> #define __FLASHROM_OS__ "libpayload"
> // Linux
> #elif defined(__linux__)
> -#define __FLASHROM_OS__ "Linux"
> + // There are various flags in use on Android apparently. __ANDROID__ seems to be the most trustworthy.
> + #if defined(__ANDROID__)
> + #define __FLASHROM_OS__ "Android"
> + #else
> + #define __FLASHROM_OS__ "Linux"
> + #endif
I'll add this change to my tested stuff branch to be committed within
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
I'm playing with a Spansion S25FL128SAGMF1000 and running flashrom on a
I started with a new chip and was successful writing and reading back a
image. It fails when I try to erase the part.
Probing this part gives several possible chip names and I picked
I'm assuming that the 0 vs. 1 suffix is selecting 64k vs. 256k sector size.
I may put some effort into chasing the erase problem. Is there anyone
currently working on this?
I have successfully flashed a Dell D830 notebook (with discrete NVIDIA
VGA) using flashrom from A14 BIOS revision to A17.
This means two things: the notebook itself is supported, and the
S25FL016A could be marked as verified for probe, read, erase, write.
For the later one I have created a patch. I have forgotten to run lspci
-vvvv, but I will do that and create a board enable patch soon.
I have successfully flashed a N25Q128..1E SPI flash using flashrom with
a 16MB image.
The programmer was an external one: NI USB-8452. This is not supported
in the mainline yet, but patch is coming soon.
/Flashing output (I have forgotten to //run with -V//)://
//flashrom v0.9.7-unknown on Linux 3.13.0-70-generic (x86_64)//
//flashrom is free software, get the source code at
//Calibrating delay loop... OK.//
//Found USB device (3923:7514).//
//USB-8452 IO voltage set to: 1.8 V//
//USB-8452 SCK frequency set to: 50.00 MHz//
//Found Micron/Numonyx/ST flash chip "N25Q128..1E" (16384 kB, SPI) on
//This flash part has status UNTESTED for operations: PROBE READ ERASE
//The test status of this chip may have been updated in the latest
//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
//work correctly for you with this flash part. Please include the flashrom//
//output with the additional -V option for all operations you tested
//-VE, -Vw), and mention which mainboard or programmer you tested.//
//Please mention your board in the subject line. Thanks for your help!//
//Reading old flash chip contents... done.//
//Erasing and writing flash chip... //
//Verifying flash... VERIFIED.
flashrom v0.9.7-r1852 on Linux 4.2.0-22-generic (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org
flashrom was built with libpci 3.2.1, GCC 4.9.1, little endian
Command line (3 args): flashrom -V -p internal
Calibrating delay loop... OS timer resolution is 1 usecs, 2684M loops
per second, 10 myus = 10 us, 100 myus = 124 us, 1000 myus = 1021 us,
10000 myus = 10128 us, 4 myus = 4 us, OK.
Initializing internal programmer
No coreboot table found.
Using Internal DMI decoder.
DMI string chassis-type: "Notebook"
Laptop detected via DMI.
DMI string system-manufacturer: "LENOVO"
DMI string system-product-name: "80EU"
DMI string system-version: "Lenovo B50-70"
DMI string baseboard-manufacturer: "LENOVO"
DMI string baseboard-product-name: "Lenovo B50-70"
DMI string baseboard-version: "00000000NO DPK"
W836xx enter config mode worked or we were already in config mode.
W836xx leave config mode had no effect.
Active config mode, unknown reg 0x20 ID: fc.
Please send the output of "flashrom -V -p internal" to
flashrom(a)flashrom.org with W836xx: your board name: flashrom -V
as the subject to help us finish support for your Super I/O. Thanks.
Did you tried to do clear CMOS to see if it fixes your issue to boot on the
Anyway, if you want to upgrade your BIOS, you will first need a valid BIOS
image of your computer/motherboard. Do you have it ?
2015-12-19 5:27 GMT+01:00 Alan Bruce <alandbruce(a)gmail.com>:
> I did go to the FAQ on your website and clicked on "How Do I Use
> Flashrom". The attached screenshot is what I got. So, how do I use this
> program. I would not mind paying someone a few bucks to remotely re
> configure my BIOS. I think that it has been hacked and modified.
> On Fri, Dec 18, 2015 at 6:32 PM, Alan Bruce <alandbruce(a)gmail.com> wrote:
>> Name is Alan. I am running an older Compaq Presario Desktop PC the model
>> number is SR2264WM. it is an AMD 64 Athlion model. The operating system
>> is Ubuntu 10.04. I just loved this OS and failed to upgrade before it was
>> too late as it is now unsupported. So I downloaded Ubuntu 15.04 and was
>> preparing to install it. All of a sudden my BIOS will not go to the boot
>> menu when I press the ESC key upon startup, like it used to do. Although I
>> downloaded flashrom from the Ubuntu Software Center, I am unable to find it
>> on my PC and access the program to reset my BIOS. So how do I access this
>> program? Your suggestions and advise will be greatly appreciated.
> flashrom mailing list