Hello Andrius,
Could you please send a verbose log to the mailing list? If you run
flashrom with additional argument "-o logfile.txt", that should do.
Please have a look at the man page. :)
You could also check out common problems
(https://www.flashrom.org/Common_problems). Perhaps a write protection
mode is in effect, which cannot be disabled on a software level? Is the
WP# pin low?
We could help you better with that log file. ;) Thank you :)
Hatim
On Tuesday 26 July 2016 10:05 PM, Andrius Montvydas wrote:
>
> hello,
>
> I had a bad bios flash, so i wanted to flash original bios using
> flashrom but it failed.
> I was using Raspberry Pi 3, bios chip is winbond W25Q64FW
>
> flashrom v0.9.9-r1954 on Linux 4.4.13-v7+ (armv7l)
> 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 linux_spi.
> Reading old flash chip contents... done.
> 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: 0x8000
> 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-0x0000ffff: 0x10000
> 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: 0x800000
> 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: 0x800000
> 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
> <http://chat.freenode.net> (channel #flashrom) or
> mail flashrom(a)flashrom.org <mailto:flashrom@flashrom.org>, thanks!
> pi@raspberrypi:~ $
>
> Thank you for any information.
>
> --
> Andrius M.
>
>
> _______________________________________________
> flashrom mailing list
> flashrom(a)flashrom.org
> https://www.flashrom.org/mailman/listinfo/flashrom
>
Hello,
This set of patches should be applied on top of the previous patches (https://www.flashrom.org/pipermail/flashrom/2016-July/014717.html).
Continuing with the major points from the previous mail (linked above), this patch should bring support for new infrastructure to quite a few more chips. OTP models for Eon, GigaDevice and Winbond are supported now. AMIC, Macronix and Spansion OTP models are scheduled for the next revision. I admit that the CLI may not be worded in the most optimum way, but that was a conscious decision so that it could be sorted out while review.
Thank you for your time. I am looking forward to your feedback and having a discussion.
Hatim Kanchwala (4):
WIP: Add support for status register and access protection
infrastructure to more existing chips
OTP/Security Register infrastructure
WIP: Add support for OTP/Security Register infrastructure to existing
chips
Integrate OTP infrastructure and add CLI
Makefile | 5 +-
chipdrivers.h | 23 +++
cli_classic.c | 263 ++++++++++++++++++++++++++++++++--
cli_common.c | 54 +++----
flash.h | 25 +++-
flashchips.c | 296 ++++++++++++++++++++++++--------------
flashrom.8.tmpl | 52 ++++++-
otp.c | 381 +++++++++++++++++++++++++++++++++++++++++++++++++
otp.h | 39 +++++
otp_layouts.c | 229 +++++++++++++++++++++++++++++
spi.h | 20 +++
spi25.c | 73 ++++++++++
spi25_statusreg.h | 6 +
statusreg_layouts.c | 58 +++++++-
writeprotect.h | 13 +-
writeprotect_layouts.c | 269 +++++++++++++++++++++++++++++++++-
16 files changed, 1645 insertions(+), 161 deletions(-)
create mode 100644 otp.c
create mode 100644 otp.h
create mode 100644 otp_layouts.c
--
2.7.4
make sure that PIN WP and HOLD must pull up to vcc
or use other spi flash test your circuit connect ok!!
发自 网易邮箱大师
On 07/27/2016 00:35, Andrius Montvydas wrote:
hello,
I had a bad bios flash, so i wanted to flash original bios using flashrom but it failed.
I was using Raspberry Pi 3, bios chip is winbond W25Q64FW
flashrom v0.9.9-r1954 on Linux 4.4.13-v7+ (armv7l)
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 linux_spi.
Reading old flash chip contents... done.
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: 0x8000
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-0x0000ffff: 0x10000
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: 0x800000
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: 0x800000
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!
pi@raspberrypi:~ $
Thank you for any information.
--
Andrius M.
hello,
I had a bad bios flash, so i wanted to flash original bios using flashrom
but it failed.
I was using Raspberry Pi 3, bios chip is winbond W25Q64FW
flashrom v0.9.9-r1954 on Linux 4.4.13-v7+ (armv7l)
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 linux_spi.
Reading old flash chip contents... done.
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: 0x8000
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-0x0000ffff: 0x10000
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: 0x800000
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: 0x800000
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!
pi@raspberrypi:~ $
Thank you for any information.
--
Andrius M.
Dear Flashrom Team,
As the title suggest, I flashed my old Asus M2V with coreboot but now it doesn't boot anymore.
I'm guessing it has more to do with the coreboot rom than with the flashing procedure but I'd like to know if you had an idea to what could have caused this failure ?
To flash the MB I used the following command :
$ sudo flashrom -p internal -w <mycorebootrom>
It successfully flashed a chip (ST something) which is a removable chip on the motherboard. So with this success I decided to reboot the computer but then nothing, screen stays black, no beeping, no keyboard light, only the hard drive led stays on permanently
What I tested :
I unplugged everything, FDD, HDD, cdrom drive, usb internal connectors, I only let inside the graphic card (a PCI-E Nvidia GF 6600GT) and a stick of RAM
I tested with another PCI-E Nvidia card (I don't have any other brand to test with) and with multiple combination of RAM sticks (1, 2 sticks, dual channel slots or not, 512 MB and 2 GB)
Now the only thing I could try I guess is remove the ST chip and flash it with an external programmer ? I backed up the original MB rom before flashing.
I hope you'll have an idea on what went wrong, if not my next stop will be the coreboot team :)
Anyway thanks a lot for your great work !
Best regards,
Pierre
Hello David,
Thanks for your response.
I am looking forward to hear it.
Yulong
David Hendricks 於 2016/7/21 上午 03:58 寫道:
> Hello Yulong,
> FYI - Apollo Lake support was recently added to the chromium.org
> <http://chromium.org> version of flashrom:
> https://chromium.googlesource.com/chromiumos/third_party/flashrom/+/4408875…
>
> I expect upstream will have support for APL soon as well.
>
>
> On Tue, Jul 19, 2016 at 7:02 PM, Yulong Chang <yulong.chang(a)insyde.com
> <mailto:yulong.chang@insyde.com>> wrote:
>
> Hi Gentleman and Lady,
>
> Let's me introduce myself first.
> I am an engineer manager in Insyde Corp.
>
> I am investigating to use flashrom binary to develop flash
> tool for Intel Apollo lake/Broxton chipset.
> The Intel Apollo lake/Broxton chipset is not on supported
> hardware of flashrom yet
>
> ***Will Intel Broxton/Apollo lake chipset to be supported flash
> chips for flashrom?*
>
>
> Sincerely.
>
> --
> Yulong Chang
> Insyde Software Corp.
> 13F, No.161, Sec. 2, MinSheng E. Rd., JhongShan District, Taipei, Taiwan.
> Tel: (886) 2-6608-3688 Ext.8572
>
>
> _______________________________________________
> flashrom mailing list
> flashrom(a)flashrom.org <mailto:flashrom@flashrom.org>
> https://www.flashrom.org/mailman/listinfo/flashrom
>
>
>
>
> --
> David Hendricks (dhendrix)
> Systems Software Engineer, Google Inc.
--
Yulong Chang
Insyde Software Corp.
13F, No.161, Sec. 2, MinSheng E. Rd., JhongShan District, Taipei, Taiwan.
Tel: (886) 2-6608-3688 Ext.8572
Hi Gentleman and Lady,
Let's me introduce myself first.
I am an engineer manager in Insyde Corp.
I am investigating to use flashrom binary to develop flash tool for
Intel Apollo lake/Broxton chipset.
The Intel Apollo lake/Broxton chipset is not on supported hardware
of flashrom yet
***Will Intel Broxton/Apollo lake chipset to be supported flash chips
for flashrom?*
Sincerely.
--
Yulong Chang
Insyde Software Corp.
13F, No.161, Sec. 2, MinSheng E. Rd., JhongShan District, Taipei, Taiwan.
Tel: (886) 2-6608-3688 Ext.8572