flashrom July 2016

flashrom@flashrom.org

18 participants
26 discussions

Re: [flashrom] failed flash
by Hatim Kanchwala 28 Jul '16

28 Jul '16

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 >

1 0

[PATCH 0/4] Initial OTP/Security Register infrastructure
by Hatim Kanchwala 28 Jul '16

28 Jul '16

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

1 4

Re: [flashrom] failed flash
by 冰 27 Jul '16

27 Jul '16

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.

1 0

failed flash
by Andrius Montvydas 26 Jul '16

26 Jul '16

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.

1 0

Error at flashing motherboard BIOS
by Szőgyényi Gábor 24 Jul '16

24 Jul '16

Hi flashrom! I attached a screenshot about the BIOS writing problem. The model of my motherboard: SOYO-SY-P4i845peisa Thanks, Gabor

1 0

Flash went all well but MB doesn't boot anymore :)
by Pierre P 24 Jul '16

24 Jul '16

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

2 1

Re: [flashrom] About flashrom chips support plan?
by Yulong Chang 21 Jul '16

21 Jul '16

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

1 0

About flashrom chips support plan?
by Yulong Chang 20 Jul '16

20 Jul '16

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

2 1

Tested: SST29EE010
by Urja Rannikko 16 Jul '16

16 Jul '16

Just found a random chip :P -- Urja Rannikko

1 0

[PATCH] Print lock register configuration for N25Q128
by Hatim Kanchwala 15 Jul '16

15 Jul '16

Hi, As discussed over IRC, please apply this patch over the latest stable branch of flashrom from https://github.com/flashrom/flashrom. This is a "hacked" solution and is certainly not merge-worthy in its current state. Patch description - When prettyprinting status register byte 1 of N25Q128 chip, also print least two significant bits of lock register for each 64 kB sector. Thanks, Hatim Signed-off-by: Hatim Kanchwala <hatim(a)hatimak.me> --- spi25_statusreg.c | 31 +++++++++++++++++++------------ 1 file changed, 19 insertions(+), 12 deletions(-) diff --git a/spi25_statusreg.c b/spi25_statusreg.c index 266e7a9..b050ae1 100644 --- a/spi25_statusreg.c +++ b/spi25_statusreg.c @@ -454,58 +454,65 @@ static void spi_prettyprint_status_register_atmel_at25_swp(uint8_t status) } int spi_prettyprint_status_register_at25df(struct flashctx *flash) { uint8_t status = spi_read_status_register(flash); spi_prettyprint_status_register_hex(status); spi_prettyprint_status_register_atmel_at25_srpl(status); spi_prettyprint_status_register_bit(status, 6); spi_prettyprint_status_register_atmel_at25_epewpp(status); spi_prettyprint_status_register_atmel_at25_swp(status); spi_prettyprint_status_register_welwip(status); - if (flash->chip->model_id == ATMEL_AT25DF161) + if (flash->chip->model_id == ST_N25Q128__3E) { int address, i, count, result; - unsigned char read_result, lockdown_status_sector[32], cmd[5]; - cmd[0] = (unsigned char)0x35; - cmd[4] = (unsigned char)0x00; + uint8_t read_result, lockdown_status_sector[flash->chip->total_size / 64], cmd[4]; + cmd[0] = (uint8_t)0xE8; - for (address = 0x000000, i = 0, count = 0; address < 0x200000; address += 0x010000, i++) + msg_cdbg("Additional information regarding block locks for %s\n", flash->chip->name); + for (address = 0x000000, i = 0, count = 0; + address < flash->chip->total_size * 1024; + address += 0x010000, i++) { cmd[1] = (unsigned char)(address >> 16) & 0xff; cmd[2] = (unsigned char)(address >> 8) & 0xff; cmd[3] = (unsigned char)address & 0xff; - result = spi_send_command(flash, sizeof(cmd), sizeof(unsigned char), cmd, &read_result); + result = spi_send_command(flash, sizeof(cmd), sizeof(uint8_t), cmd, &read_result); if (result) { - msg_cerr("%s failed during command execution (ATMEL_AT25DF161)\n", __func__); + msg_cerr("%s failed during command execution (ST_N25Q128__3E)\n", __func__); return result; } if (i % 8 == 0) msg_cdbg("0x%02x:", i); - msg_cdbg(" %02x%s", read_result, (i + 1) % 8 == 0 ? "\n": ""); - lockdown_status_sector[address / 0x010000] = read_result; - if (read_result) + msg_cdbg(" [%s,%s]%s", + (read_result & 0x02) ? "1" : "0", + (read_result & 0x01) ? "1" : "0", + (i + 1) % 8 == 0 ? "\n": ""); + lockdown_status_sector[address / 0x010000] = read_result & 0x03; + if (read_result & 0x01) count++; } - msg_cdbg("%d sector%s locked down permanently%s", count, (count == 1) ? "" : "s", (count == 0) ? "." : " :"); + msg_cdbg("%d sector%s locked down%s", count, (count == 1) ? "" : "s", + (count == 0) ? "." : " :"); if (count) - for (i = 0; i < 32; i++) + for (i = 0; i < ARRAY_SIZE(lockdown_status_sector); i++) if (lockdown_status_sector[i]) msg_cdbg(" %2d", i); msg_cdbg("\n"); + msg_cdbg("You _may_ be able to unlock the sector%s\n", (count == 1) ? "" : "s"); } return 0; } int spi_prettyprint_status_register_at25df_sec(struct flashctx *flash) { /* FIXME: We should check the security lockdown. */ msg_cdbg("Ignoring security lockdown (if present)\n"); msg_cdbg("Ignoring status register byte 2\n"); return spi_prettyprint_status_register_at25df(flash); } -- 2.7.4

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom July 2016