On 17.10.2017 01:14, David Hendricks wrote:
> On Sat, Oct 14, 2017 at 7:20 AM, Stefan Tauner <stefan.tauner(a)gmx.at> wrote:
>> While there was a bunch of patches that have been piled up back then it
>> was less of a problem then the increasing divergence between the
>> chromiumos fork and upstream. Thus we have discussed ways to converge
>> that (by pulling changes mainly from upstream into chromium but also
>> vice versa) and also increase the pace of merging stuff into upstream
>> later. This was still with no intention to switch to git because of
>> Carl-Daniel's concerns.
> I'm surprised that you think that chromiumos's divergence is a *worse*
> problem than the huge backlog of upstream patches. The chromiumos fork is
> self-contained, has its own review system, its own testing, and is targeted
> at a narrow set of devices. I don't understand how it could have been a
> problem for upstream and would be interested if you can elaborate on this
I think there are at least two views on this:
What might happen in such a case: People loose interest in upstream and
less patches get send there. (This might even have a positive effect on
the patch queue.)
What I think happened (and maybe Stefan had something like this in
mind): Progress on upstream stalled on more invasive topics because
people tried to find a solution fitting both branches, first. FWIW,
this was the case for better layout support in upstream. Maybe there
were more topics stalled, I don't know the cros fork well enough.
On 17.10.2017 22:18, Benedikt Broich via flashrom wrote:
> I am trying to flash the MX25L6405D in my Lenovo X200, but i get the
> following Error:
> Do you have any Idea what i am doing wrong?
Flashing this chip in an X200 is rather finicky. You either need a
very good programmer and connection or a patch for flashrom (e.g.
https://paste.flashrom.org/view.php?id=3042) that doesn't solve but
reduces the problem. Though, I have no idea if the libreboot? flashrom
you are using already has that patch.
If it doesn't work with the patch applied, it's likely a connection
(e.g. wire length) problem.
> Verifying flash... FAILED at 0x000e9000! Expected=0xac, Found=0x4f, failed
> byte count from 0x00000000-0x007fffff: 0x1f1a
It looks like you already succeeded in flashing most of the chip. Iff
the "failed byte count" decreases with every try. You can probably
just try again and again until it's finished.
Hope that helps,
Can you post a verbose log (flashrom -V ...)? The chip should be supported,
though there might be some limitation with your programmer that prevents it
from being flashed, especially if you're using an Intel platform.
On Sun, Oct 15, 2017 at 3:48 PM, Abran DeCarlo Hernandez <
> Flashrom cannot PROBE/READ/ERASE/WRITE to my BIOS chip (Winbond 25064BVAIG)
> How do I go about fixing this? It detects the chip but it is unsupported
> flashrom mailing list
my flash is w39v040cpz. it is write-protected. afudos.exe give me "bios
does not support afu...", amf895.exe give me "flash module is
write-protected", flashrom give
root@debian:/home/q# flashrom --programmer internal -c W39V040C -w 0702.ROM
flashrom v0.9.9-r1955 on Linux 4.9.0-3-amd64 (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
Found chipset "NVIDIA MCP51".
Enabling flash write... OK.
Enabling full flash access for board "ASUS M2NBP-VM CSM"... OK.
Found Winbond flash chip "W39V040C" (512 kB, LPC) mapped at physical
Reading old flash chip contents... done.
Erasing and writing flash chip... FAILED at 0x00000008! Expected=0xff,
Found=0xa4, failed byte count from 0x00000000-0x0000ffff: 0xfef3
Reading current flash chip contents... done. Looking for another erase
FAILED at 0x00000008! Expected=0xff, Found=0xa4, failed byte count from
Looking for another erase function.
No usable erase functions left.
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Good, writing to the flash chip apparently didn't do anything.
This means we have to add special support for your board, programmer or
chip. Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom(a)flashrom.org, thanks!
You may now reboot or simply leave the machine running.