On Mon, 9 May 2016 20:46:18 -0700
David Hendricks <dhendrix(a)google.com> wrote:
> Hi Victor,
> From Flashrom's software perspective all chips with the same ID are
> indistinguishable.
>
> Part number often includes characteristics such as package and thermal
> tolerance which do not affect software compatibility.
However, we will add the new names to the in-program (and hence
wiki) database so that this new information becomes public. Thanks for
the heads up, Victor.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Hi,
we're hitting the 80 column limit in our code in ways which actually
reduce readability for the code. Examples are various multiline messages
and complicated nested code where refactoring to a separate function
doesn't make sense.
Keeping the old 80 column limit is not really an option anymore.
Standard terminal sizes have one of 80, 100 or 132 columns.
Given the monitor resolutions many people have nowadays, I think it is
safe to say that you can fit two xterms with 100 columns horizonally
next to each other. 100 columns should also be sufficient for a msg_p*
of roughly 80 columns of text.
132 columns provide more leeway, but IMHO that would be too wide for
good readability (and my screen can't fit two xterms side-by-side anymore).
Of course some files have sections where any column limit is not
acceptable (board lists etc.), but the column limit violations should be
limited to the affected file sections, not whole files.
Comments?
I'd like to get this decided today or tomorrow so we know where we need
line breaks in Stefan Tauner's new struct flashchip patch.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
A Hardware Enablement devroom will be taking place at FOSDEM this year,
on Sunday 10 December 2017. This newly-created devroom is the result of
3 proposals that were merged together. It is co-organized by several
individuals.
The devroom covers all aspects related to hardware enablement and
support with free software, including aspects related to boot software,
firmwares, drivers and userspace tools and adaptation.
Proposals for talks related to these topics are welcome and can be
submitted until Sunday 26 November 2017 via the pentabarf interface.
Short talks are encouraged over longer ones in order to cover a wide
range of topics.
The announcement for the devroom, that contains all the useful
information, was published at:
https://lists.fosdem.org/pipermail/fosdem/2017-October/002649.html
Cheers and see you at FOSDEM!
--
Paul Kocialkowski, developer of free digital technology and hardware
support
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/https://git.code.paulk.fr/
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.
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
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
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
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.
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.
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?
thx
