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/
Hi,
I recently bought two VMAC V1 Mini PC's with Winbond W25Q64FWSIG EFI chips. Updating the EFI information on teh devices using the normal software route is extremely flakey and I managed to corrupt the EFI on both boards, making them unbootable.
I now have a Chinese CH341a ("Black Edition") usb programmer and a "piggy-back" 1.8v adapter and can connect to the Winbond chip using a test clip.
I installed flashrom from the debian package V0.99 and can do a:
Initially, I thought I had problems getting the clip properly seated, but no matter how much I clean the contacts and re-seat the clip, if I do a:
#flashrom -p ch341a_spi -V
I get (randomly):
Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on ch341a_spi.
Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ch341a_spi.
Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on ch341a_spi.
Finding the correct chip or not seems to have little or nothing to do with the physical contact to the chip.
If I then try to erase the chip. I get:
# flashrom -p ch341a_spi -c W25Q64.W -E
flashrom v0.9.9-r1954 on Linux 4.10.1-towo.1-siduction-amd64 (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on ch341a_spi.
Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x53cb
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x00000000! Expected=0xff, Found=0xd6, failed byte count from 0x00000000-0x0000ffff: 0x9264
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x5e1391
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x5ce187
ERASE FAILED!
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!
Again, the hex codes for the failures seem pretty random and are different each time I try the command.
I attach the log.
Can anyone say what's going on?
Best Regards
Marius
Hi Marius,
A few days ago Nico suggested for a similar issue the following:
/You probably didn't connect all pins of the flash chip. You have to pull
/HOLD and /WP high (connect them to 3V3, preferably through some
resistor) to succeed. /
Best regards,
Miklos Marton
2017-09-23 12:00 keltezéssel, flashrom-request(a)flashrom.org írta:
>
> Hi,
>
> ??I recently bought two VMAC V1 Mini PC's with Winbond W25Q64FWSIG EFI chips. Updating the EFI information on teh devices using the normal software route is extremely flakey and I managed to corrupt the EFI on both boards, making them unbootable.
>
> I now have a Chinese CH341a ("Black Edition") usb programmer and a "piggy-back" 1.8v adapter and can connect to the Winbond chip using a test clip.
>
> I installed flashrom from the debian package V0.99 and can do a:
>
>
>
> Initially, I thought I had problems getting?the?clip properly seated, but no matter?how much I clean the contacts and re-seat the clip, if I do a:
> ?#flashrom -p ch341a_spi -V
>
> I get (randomly):
> Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on ch341a_spi.
> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ch341a_spi.
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on ch341a_spi.
>
> Finding the correct chip or not seems to have little or nothing to do with the physical contact to the chip.
> If I then try to erase the chip. I get:
>
> ? # flashrom -p ch341a_spi -c W25Q64.W -E
> flashrom v0.9.9-r1954 on Linux 4.10.1-towo.1-siduction-amd64 (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> Calibrating delay loop... OK.
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on ch341a_spi.
> Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase function.
> FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x53cb
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase function.
> FAILED at 0x00000000! Expected=0xff, Found=0xd6, failed byte count from 0x00000000-0x0000ffff: 0x9264
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase function.
> FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x5e1391
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase function.
> FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x5ce187
> ERASE FAILED!
> 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!
>
>
> Again, the hex codes for the failures seem pretty random and are different each time I try the command.
>
> I attach the log.
>
> ??Can anyone say what's going on?
>
> ?Best Regards
>
> Marius
>
>
> End of flashrom Digest, Vol 100, Issue 15
> *****************************************
>
looking to upgrade my mix 5500 mph 7500, the BIOS is different as is the power supply. the rest is easy to upgrade CPU, memory, Cadmium card.
SAME motherboard X7DCU4 .
has anyone done this? https://youtu.be/OiBQXuw-vBw
Joe
On 17.09.2017 03:51, junkheap(a)tiscali.co.uk wrote:
> Thank you for the help Nico.
>
> Your advice was successful. After connecting /HOLD & /WP to 3.3V,
> Flashrom wrote & verified the W25Q64SIG without any error messages.
Nice!
>
> After previously checking the datasheet I thought that it was necessary
> to do that. But I have little experience of electronics and thought it
> wise to seek advice before trying, as all of the guides to programming
> EEPROMs with Raspberry Pi I found on the web had always left those pins
> unused.
Most guides probably assume that the chip is still soldered to a board.
In that case the circuit on the board pulls /HOLD and /WP already.
Nico
PS. Please always keep the mailing list in CC when you respond. Some
email clients have an extra button (e.g. "Reply all") for that.
>
>
> On 16/09/2017 13:57, Nico Huber wrote:
>> Hi,
>>
>> On 15.09.2017 18:56, junkheap--- via flashrom wrote:
>>> I am trying to write to a Winbond W25Q64FVSIG EEPROM (SOIC-8) using
>>> Flashrom and a Raspberry Pi 3 (running up to date Raspbian). But I
>>> receive the message "ERASE FAILED!".
>>>
>>> I am using the shortest wires which are practical to connect to the
>>> Raspberry Pi (~10CM) and I have checked many times that I have connected
>>> to the correct GPIO pins. To make sure that there is a good connection,
>>> I abandoned the clip I was using and have soldered the EEPROM to the
>>> pads on a daughterboard (designed for the purpose). The wires I am using
>>> have factory-fitted female terminals on both ends and connect tightly to
>>> the GPIO pins on the RPI and pin head on the daughterboard.
>>>
>>> From what I have found some people have flashed this model of EEPROM
>>> successfully using Flashrom, but others have encountered the same
>>> problem. I have not been able to find a solution. If anyone can offer
>>> assistance or advice I would me most grateful. Thank you.
>> I see two possible causes:
>>
>> 1. You probably didn't connect all pins of the flash chip. You have to
>> pull /HOLD and /WP high (connect them to 3V3, preferably through some
>> resistor) to succeed.
>>
>> 2. You run the SPI interface at a too high clock. As you didn't supply
>> a `spispeed` argument to the linux_spi programmer, it will at run
>> at some (to me unknown) default speed.
>>
>> Nico
>
I am trying to write to a Winbond W25Q64FVSIG EEPROM (SOIC-8) using
Flashrom and a Raspberry Pi 3 (running up to date Raspbian). But I
receive the message "ERASE FAILED!".
I am using the shortest wires which are practical to connect to the
Raspberry Pi (~10CM) and I have checked many times that I have connected
to the correct GPIO pins. To make sure that there is a good connection,
I abandoned the clip I was using and have soldered the EEPROM to the
pads on a daughterboard (designed for the purpose). The wires I am using
have factory-fitted female terminals on both ends and connect tightly to
the GPIO pins on the RPI and pin head on the daughterboard.
From what I have found some people have flashed this model of EEPROM
successfully using Flashrom, but others have encountered the same
problem. I have not been able to find a solution. If anyone can offer
assistance or advice I would me most grateful. Thank you.
The Flashrom log is as follows:
pi@raspberrypi:~ $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -c
"W25Q64.V" -V -w GMS_64M.bin
flashrom v0.9.9-r1954 on Linux 4.9.26v7-aufs (armv7l)
flashrom is free software, get the source code at https://flashrom.org
flashrom was built with libpci 3.2.1, GCC 4.9.2, little endian
Command line (7 args): flashrom -p linux_spi:dev=/dev/spidev0.0 -c
W25Q64.V -V -w GMS_64M.bin
Calibrating delay loop... OS timer resolution is 3 usecs, 595M loops per
second, 10 myus = 10 us, 100 myus = 101 us, 1000 myus = 1045 us, 10000
myus = 9999 us, 12 myus = 12 us, OK.
Initializing linux_spi programmer
Using device /dev/spidev0.0
The following protocols are supported: SPI.
Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xef,
id2 0x4017
Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on linux_spi.
Chip status register is 0x00.
This chip may contain one-time programmable memory. flashrom cannot read
and may never be able to write it, hence it may not be able to completely
clone the contents of this chip (see man page for details).
Reading old flash chip contents... done.
Erasing and writing flash chip... Trying erase function 0...
0x000000-0x000fff:E
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from
0x00000000-0x00000fff: 0x9b8
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase
function.
Trying erase function 1... 0x000000-0x007fff:EFAILED at 0x000001c1!
Expected=0xff, Found=0x80, failed byte count from 0x00000000-0x00007fff:
0x4a3f
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase
function.
Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00000000!
Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff:
0x976e
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase
function.
Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00000000!
Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff:
0x4b5b41
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase
function.
Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00000000!
Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff:
0x52483f
ERASE FAILED!
Looking for another erase function.
No usable erase functions left.
FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Apparently at least some data has changed.
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!
