flashrom

flashrom@flashrom.org

5 participants
9161 discussions

[PATCH] linux_spi: add handling of suffices M and K in spispeed value
by Joerg Albert 14 Jun '18

14 Jun '18

This patch adds correct handling of the suffices M,m,K,k for the spispeed value (K,k don't change anything). Drop an error for any other suffix. Change-Id: Ideb2295df8e82ccb2bbe2d58a6ee035b2ea602d0 Signed-Off-By: Joerg Albert <jal2(a)gmx.de> --- flashrom.8.tmpl | 4 ++++ linux_spi.c | 19 +++++++++++++++++++ 2 files changed, 23 insertions(+) diff --git a/flashrom.8.tmpl b/flashrom.8.tmpl index a3528f1..642a697 100644 --- a/flashrom.8.tmpl +++ b/flashrom.8.tmpl @@ -1032,6 +1032,10 @@ Example that sets the frequency to 8 MHz: .sp .B " flashrom \-p linux_spi:dev=/dev/spidevX.Y,spispeed=8000" .sp +or +.sp +.B " flashrom \-p linux_spi:dev=/dev/spidevX.Y,spispeed=8M" +.sp Please note that the linux_spi driver only works on Linux. .SS .BR "mstarddc_spi " programmer diff --git a/linux_spi.c b/linux_spi.c index 3e60492..1f3632b 100644 --- a/linux_spi.c +++ b/linux_spi.c @@ -80,6 +80,25 @@ int linux_spi_init(void) free(p); return 1; } + if (strlen(endp) == 1) { + if (toupper(*endp) == 'M') { + speed_hz *= 1000; + } else { + if (toupper(*endp) == 'K') { + ; + } else { + msg_perr("Error: Garbage following 'spispeed' value: %s\n", p); + free(p); + return 1; + } + } + } else { + if (strlen(endp) > 1) { + msg_perr("Error: Garbage following 'spispeed' value: %s\n", p); + free(p); + return 1; + } + } } free(p); -- 2.11.0

1 0

Fwd: Re: Request to mailing list flashrom rejected
by Nico Huber 08 Jun '18

08 Jun '18

------- Forwarded Message -------- Subject: Re: Request to mailing list flashrom rejected Date: Fri, 8 Jun 2018 12:29:43 +0600 From: Константин Z <konstantin.z100(a)gmail.com> To: flashrom-owner(a)flashrom.org Hello, Nico! I am correcting past mistakes: I've reduced the level of verbose. First I erased the flash, then I read the contents of the memory, and then wrote down the necessary dump. After erasing on the chip, all memory is filled with zeros. After writing the required dump, the necessary data was in the memory of the chip. So everything works correctly! Thank you for developing the flashrom! If there's anything else I can help, write to me. Logs attached. 2018-05-31 17:55 GMT+06:00 <flashrom-owner(a)flashrom.org>: > Your request to the flashrom mailing list > > Posting of your message titled "Testing Atmel AT25DF161" > > has been rejected by the list moderator. The moderator gave the > following reason for rejecting your request: > > "Hi Konstantin, > > thanks for your report. Your message got filtered, though. Your > attachment exceeds our size limit (256KiB). Please reduce the > verbosity of your logs; nobody is going to read half a million lines > of hexdumps here ;) > > Also, a note on your write log: You missed to test anything but > reading because flashrom detected that no data would change and didn't > write anything: > >> Warning: Chip content is identical to the requested image. > > Please, if you have the time, test writing again with an image that > differs from the flash contents. > > Nico " > > Any questions or comments should be directed to the list administrator > at: > > flashrom-owner(a)flashrom.org -- Best regards, Konstantin

1 0

Re: [flashrom] Patch for LE25FU106B
by The_Raven Raven 07 Jun '18

07 Jun '18

Sorry, forgot the patch... *palmface*

1 0

Patch for LE25FU106B
by The_Raven Raven 07 Jun '18

07 Jun '18

Hi This patch add support for LE25FU106B chip. Tested and works: - Probe - Read - Write - All erase functions Greets

1 0

Re: [flashrom] PATCH: Adding support for Sanyo "LE25FU206"
by The_Raven Raven 07 Jun '18

07 Jun '18

Hi again In the mean time i found a LE25FU206A chip and modified the patch to support both chips. So with this patch LE25FU206 and LE25FU206A are supported. Unfortunately i have not found any datasheet for 206A. So it's only guessing that the 206A is the same as 206. I tested the 206A and it works. Maybe someone has a datasheet and can verify the patch? I have both chips and can test it. Greets

1 0

[RFC PATCH 0/2] Experimental Developerbox/CP2102 bitbang programmer
by Daniel Thompson 04 Jun '18

04 Jun '18

This patchset contains a couple of experimental patches to allow me to recover the ROM of a 96Boards Developerbox. Basically I've hacked something together that appears to work and am interested in thoughts and opinions before I invest time to clean it up or optimize it any further. The two patches are entirely separable; the only commonality is that both are needed for Developerbox tool-free recovery to work (and that both currently contain questions in the patch description). Daniel Thompson (2): programmer: Add Developerbox/CP2104 bit bang driver flashchips: Add Macronix MX25U51245G Makefile | 24 +++- developerbox_spi.c | 296 +++++++++++++++++++++++++++++++++++++++++++++ flashchips.c | 40 ++++++ flashchips.h | 1 + flashrom.c | 12 ++ programmer.h | 12 ++ 6 files changed, 383 insertions(+), 2 deletions(-) create mode 100644 developerbox_spi.c -- 2.17.0

1 2

Re: [flashrom] Fail to flash W25X40
by David Hendricks 31 May '18

31 May '18

On Wed, May 30, 2018 at 9:03 AM, Yang Hu <yh2948(a)columbia.edu> wrote: > Hi, > > I'm trying to rewrite a W24X40AL flash on a Seagate hard drive motherboard. > I can successfully read the data, although some weird things happened. > (First dumped code is nonsense, second time works fine, third or the rest > are just partial corrupted code). > > Then I want to flash the code back but get the following error, > > parallels@ubuntu:~/Desktop$ sudo flashrom -p > buspirate_spi:dev=/dev/ttyUSB0,spispeed=2M -E > flashrom on Linux 4.4.0-59-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 "W25X40" (512 kB, SPI) on buspirate_spi. > Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, > Found=0x7f, failed byte count from 0x00001000-0x00001fff: 0x1 > ERASE FAILED! > Looking for another erase function. > FAILED at 0x00001800! Expected=0xff, Found=0x00, failed byte count from > 0x00000000-0x0000ffff: 0x42b > ERASE FAILED! > Looking for another erase function. > FAILED at 0x00002000! Expected=0xff, Found=0x00, failed byte count from > 0x00000000-0x0007ffff: 0x6596 > 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! > > My connection right now is: the motherboard is not powered, using bus pirate > 3.3v directly connects to VCC, /WP and /HOLD. I've tried to add 10k, 20k > resistor between 3.3v and /WP, /HOLD pin but the chip won't be recognized > then. > > I don't have much experience in electronics. Is this do with write > protection? Is there anything I can do with this? Hi Yang, It sounds like your Bus Pirate is backpowering other electronics on the board (e.g. an embedded controller), which in turn try to access the SPI flash and interfere. This happens when the vendor does not isolate the SPI flash circuitry. Determine what other electronics might be powered by the Bus Pirate and see if you can hold them in reset so that they don't try to access the SPI flash.

1 0

how to have a log from the program
by nicola scattolin 30 May '18

30 May '18

Hi, i'm using a ch341a programmer to flash my motherboard bios with your program, but i have the followin error: flashrom v0.9.9-97-g29333a0 on Windows 6.2 (x86) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Error: Image size (6815744 B) doesn't match the flash chip's size (8388608 B)! C:\Users\Marco\DOWNLO~1\FLASHR~1\FLASHR~1>flashrom.exe -w E7917IMS.1D0.bin flashrom v0.9.9-97-g29333a0 on Windows 6.2 (x86) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi. Reading old flash chip contents... done in 4 min and 37 sec. Erasing and writing flash chip... Erase/write done in 19 min and 7 sec. Verifying flash... FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x66847a 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! How can i extract some more logs? could it be a bad clip positioning? Thanks for your time and for your useful program Regards Nicola

1 0

Fail to flash W25X40
by Yang Hu 30 May '18

30 May '18

Hi, I'm trying to rewrite a W24X40AL flash on a Seagate hard drive motherboard. I can successfully read the data, although some weird things happened. (First dumped code is nonsense, second time works fine, third or the rest are just partial corrupted code). Then I want to flash the code back but get the following error, parallels@ubuntu:~/Desktop$ sudo flashrom -p buspirate_spi:dev=/dev/ttyUSB0,spispeed=2M -E flashrom on Linux 4.4.0-59-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 "W25X40" (512 kB, SPI) on buspirate_spi. Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x7f, failed byte count from 0x00001000-0x00001fff: 0x1 ERASE FAILED! Looking for another erase function. FAILED at 0x00001800! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0x42b ERASE FAILED! Looking for another erase function. FAILED at 0x00002000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0007ffff: 0x6596 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! My connection right now is: the motherboard is not powered, using bus pirate 3.3v directly connects to VCC, /WP and /HOLD. I've tried to add 10k, 20k resistor between 3.3v and /WP, /HOLD pin but the chip won't be recognized then. I don't have much experience in electronics. Is this do with write protection? Is there anything I can do with this? Thanks for your help. Yang Hu

1 0

Re: [flashrom] Update bios (not full flash) with flashrom
by Mike Banon 30 May '18

30 May '18

It could be that a manufacturer has released the same motherboards with two various sizes of a BIOS chip. You could try padding your 256 KB image with FF's to increase its' size up to 512 KB and then flash to the chip, after making a full backup ofcourse. Also you could look through your existing backup, to see how much of your 512 KB image is really occupied with anything thats not FF's, especially at the end. Could use some simple hex editor like Okteta to quickly check this On Tue, May 29, 2018 at 10:45 PM, Skoll RC <amisbievre(a)hotmail.fr> wrote: > I have an external programmer and a full backup of my current bios. nothing > writen, there was a label but it had to come off with time. > How can I concatenate images? The update is not a full bios, is it? > ________________________________ > De : David Hendricks <david.hendricks(a)gmail.com> > Envoyé : mardi 29 mai 2018 19:19 > À : Skoll RC > Cc : flashrom(a)flashrom.org > Objet : Re: [flashrom] Update bios (not full flash) with flashrom > > On Sun, May 27, 2018 at 11:44 AM, Skoll RC <amisbievre(a)hotmail.fr> wrote: >> Hi everyone, >> >> I would like to update my GA-8I915P-MF's bios with flashrom but Gigabyte >> only provide updates and no full bios so when I try to update with >> flashrom -p internal -w 8i9pmf.f2 I have an error message: Error: Image >> size >> (262144 B) doesn't match the flash chip's size (524288 B)! >> How can I fix it? > > That's unfortunate. Do you have an external programmer (something like > a buspirate) that can be used in case things go wrong? Can you tell if > there is anything written to the lower half of the chip? It could be > as simple as concatenating the 256KB image to itself to create a 512KB > image. But I wouldn't recommend trying that unless you have a good > means of recovering. > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom