flashrom

flashrom@flashrom.org

5 participants
9161 discussions

PS: FAILED: x60s
by msuzuqi＠posteo.net 02 Aug '19

02 Aug '19

Dear people, Hello. I am Masaru Suzuqi who sent a email to you about a few hours ago. The problem seems to be solved. So you don't have to spare your time to reply to me. Thank you very much. Sincerely, Masaru Suzuqi -------- Original Message -------- Subject: FAILED: x60s Date: 02.08.2019 17:36 From: msuzuqi(a)posteo.net To: flashrom(a)flashrom.org Dear people, Hello. My name is Masaru Suzuqi. I have been trying to libreboot the x60s. This is the first time for me to try to libreboot. Finally I have just succeeded to proceed to the step "./flash". Then I got below message. There was your email address. So I am writing this message. Would you mind teaching me what I should do? This message binds me. > Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! I cannot do anything. I am afraid but I have no language skills to chat and I have not used IRC. I am looking forward to your reply. Thank you very much for reading this message. Sincerely, Masaru Suzuqi -- softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ sudo ./flash i945lenovo_firstflash /home/softwdensky/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S/x60_usqwerty_txtmode.rom Mode selected: i945lenovo_firstflash bucts utility version 'withoutgit' Using LPC bridge 8086:27b9 at 0000:1f.00 Current BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is untranslated Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000 are swapped flashrom v0.9.9-unknown on Linux 4.4.0-119-generic (i686) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH7M". Enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. Found SST flash chip "SST25VF016B" (2048 kB, SPI) mapped at physical address 0xffe00000. Reading old flash chip contents... done. Erasing and writing flash chip... spi_block_erase_20 failed during command execution at address 0x0 Reading current flash chip contents... done. Looking for another erase function. spi_block_erase_52 failed during command execution at address 0x0 Reading current flash chip contents... done. Looking for another erase function. Transaction error! spi_block_erase_d8 failed during command execution at address 0x1f0000 Reading current flash chip contents... done. Looking for another erase function. spi_chip_erase_60 failed during command execution Reading current flash chip contents... done. Looking for another erase function. spi_chip_erase_c7 failed during command execution 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. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! flashrom v0.9.9-unknown on Linux 4.4.0-119-generic (i686) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH7M". Enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ -- The below log is a log of my stumble right before the success. For your reference. softwdensky@softwdensky:~$ cd twdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S bash: cd: twdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S: そのようなファイルやディレクトリはありません softwdensky@softwdensky:~$ cd softwdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S bash: cd: softwdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S: そのようなファイルやディレクトリはありません softwdensky@softwdensky:~$ cd /home/softwdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S bash: cd: /home/softwdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S: そのようなファイルやディレクトリはありません softwdensky@softwdensky:~$ cd /home/softwdensky/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ sudo ./flash i945lenovo_firstflash home/softwdensky/ドキュメント/libreboot_r20160907_src/coreboot/d83b0e9ac4174cca92ac2c3b83a7e8491a9a1ff4/d83b0e9ac4174cca92ac2c3b83a7e8491a9a1ff4/src/northbridge/intel/i945/x60/x60_usqwerty_text.rom [sudo] softwdensky のパスワード: すみません、もう一度試してください。 [sudo] softwdensky のパスワード: Mode selected: i945lenovo_firstflash File not found! softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ sudo ./flash i945lenovo_firstflash home/softwdensky/ドキュメント/libreboot_r20160907_src/coreboot/d83b0e9ac4174cca92ac2c3b83a7e8491a9a1ff4/d83b0e9ac4174cca92ac2c3b83a7e8491a9a1ff4/src/northbridge/intel/i945/x60/x60_usqwerty_text.rom Mode selected: i945lenovo_firstflash File not found! softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ ./flash i945lenovo_firstflash /home/softwdensky/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S/x60_usqwerty_textmode.rom This script must be run as root softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ sudo ./flash i945lenovo_firstflash /home/softwdensky/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S/x60_usqwerty_textmode.rom Mode selected: i945lenovo_firstflash File not found!

1 0

FAILED: x60s
by msuzuqi＠posteo.net 02 Aug '19

02 Aug '19

Dear people, Hello. My name is Masaru Suzuqi. I have been trying to libreboot the x60s. This is the first time for me to try to libreboot. Finally I have just succeeded to proceed to the step "./flash". Then I got below message. There was your email address. So I am writing this message. Would you mind teaching me what I should do? This message binds me. > Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! I cannot do anything. I am afraid but I have no language skills to chat and I have not used IRC. I am looking forward to your reply. Thank you very much for reading this message. Sincerely, Masaru Suzuqi -- softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ sudo ./flash i945lenovo_firstflash /home/softwdensky/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S/x60_usqwerty_txtmode.rom Mode selected: i945lenovo_firstflash bucts utility version 'withoutgit' Using LPC bridge 8086:27b9 at 0000:1f.00 Current BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is untranslated Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000 are swapped flashrom v0.9.9-unknown on Linux 4.4.0-119-generic (i686) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH7M". Enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. Found SST flash chip "SST25VF016B" (2048 kB, SPI) mapped at physical address 0xffe00000. Reading old flash chip contents... done. Erasing and writing flash chip... spi_block_erase_20 failed during command execution at address 0x0 Reading current flash chip contents... done. Looking for another erase function. spi_block_erase_52 failed during command execution at address 0x0 Reading current flash chip contents... done. Looking for another erase function. Transaction error! spi_block_erase_d8 failed during command execution at address 0x1f0000 Reading current flash chip contents... done. Looking for another erase function. spi_chip_erase_60 failed during command execution Reading current flash chip contents... done. Looking for another erase function. spi_chip_erase_c7 failed during command execution 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. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! flashrom v0.9.9-unknown on Linux 4.4.0-119-generic (i686) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH7M". Enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ -- The below log is a log of my stumble right before the success. For your reference. softwdensky@softwdensky:~$ cd twdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S bash: cd: twdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S: そのようなファイルやディレクトリはありません softwdensky@softwdensky:~$ cd softwdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S bash: cd: softwdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S: そのようなファイルやディレクトリはありません softwdensky@softwdensky:~$ cd /home/softwdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S bash: cd: /home/softwdensky/ドキュメント/LibreBoot_2/home/sof0160907_for_Lenovo_X60S: そのようなファイルやディレクトリはありません softwdensky@softwdensky:~$ cd /home/softwdensky/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ sudo ./flash i945lenovo_firstflash home/softwdensky/ドキュメント/libreboot_r20160907_src/coreboot/d83b0e9ac4174cca92ac2c3b83a7e8491a9a1ff4/d83b0e9ac4174cca92ac2c3b83a7e8491a9a1ff4/src/northbridge/intel/i945/x60/x60_usqwerty_text.rom [sudo] softwdensky のパスワード: すみません、もう一度試してください。 [sudo] softwdensky のパスワード: Mode selected: i945lenovo_firstflash File not found! softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ sudo ./flash i945lenovo_firstflash home/softwdensky/ドキュメント/libreboot_r20160907_src/coreboot/d83b0e9ac4174cca92ac2c3b83a7e8491a9a1ff4/d83b0e9ac4174cca92ac2c3b83a7e8491a9a1ff4/src/northbridge/intel/i945/x60/x60_usqwerty_text.rom Mode selected: i945lenovo_firstflash File not found! softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ ./flash i945lenovo_firstflash /home/softwdensky/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S/x60_usqwerty_textmode.rom This script must be run as root softwdensky@softwdensky:~/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S$ sudo ./flash i945lenovo_firstflash /home/softwdensky/ドキュメント/LibreBoot_20160907_for_Lenovo_X60S/x60_usqwerty_textmode.rom Mode selected: i945lenovo_firstflash File not found!

2 2

"sh: dmidecode: not found" on recovery_logs - ChromeBook
by Song An 01 Aug '19

01 Aug '19

Hello, I'm trying to install the ChromeBook Recovery image, build# 12371.6.0/77.0.3865.7 -Cyan. And, there is the following message on the Recovery.log file. Please check message on the log file. : sh: dmidecode: not found dmidecode execution unsuccessful - continuing without DMI info Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Reading flash... SUCCESS Thanks, Song

1 0

Error writing flash on x230
by dokuja 01 Aug '19

01 Aug '19

Hello, I get this error message that says to contact this address: Verifying flash...FAILED at 0x00000000! Expected=0xff, Found 0x00, failed byte count from 0x00000000-0x003fffff: 0x3f66e5 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!

1 0

Re: Support using FTD2XX driver for FT2232H device
by Buhrow, Simon 30 Jul '19

30 Jul '19

Hi Steffen, if that agrees with the free and open source software idea is to discuss by the flashrom owners (I think you deserve an answer by the owners...) Nevertheless I´d like to try it to look if it performs better than libftdi (at least for debugging where time could be saved). Would be nice if you could make it available in any way! (via Mail/git/etc.) Regards, Simon

1 0

Re: Programming Speed FTDI 2232H to N25Q128
by Buhrow, Simon 30 Jul '19

30 Jul '19

I found that libusb calls are mainly responsible for long idle times. For some improvement/workaround look at E-Mail with topic: ftdi_write_chunksize, block_erasers and spi_read_status_register proposals https://mail.coreboot.org/hyperkitty/list/flashrom@flashrom.org/thread/W2HU… But still looking for further improvement. Regards, Simon

1 0

Flashrom patches that haven't been touched in 18 months or more
by Martin Roth 29 Jul '19

29 Jul '19

Here's a list of patches in the flashrom project that haven't been touched in a while. Someone might want to consider abandoning or reviving them. I'm abandoning the coreboot patches next week, but I'll let the flashrom community decide how to take care of these. https://review.coreboot.org/q/status:open+before:2018-02-1+project:flashrom Martin

1 0

Copying and writing a flashrom
by Revive Car Audio 28 Jul '19

28 Jul '19

1 0

Support for NANO USB Programmer
by bostjan.ign.k＠t-2.si 28 Jul '19

28 Jul '19

Greetings everyone, I'm a new member of flashrom mailing list, searching for info pertaining certain external programmer and corresponding 'flashrom' support. I noticed that the official list of supported programmers has not been updated for quite a while (January 2018), so I'd be interested to know if anyone succeeded to make it work - running 'flashrom' on Linux machine, in combination with this tiny programmer: Product designation: "NANO USB Programmer" Mfg: HS-TECH R.O.K, Korea MPN: NANOUSB001 Site: http://shop3.nanobios.cafe24.com/article/download/7/8/?page=1 Programmer's core silicon: Name: Cypress enCoRe II Short description: Low Speed USB Peripheral Controller, with 8-bit M8C core. Chip designation: CY7C63813-PXC Ref.: https://www.cypress.com/products/encore-ii USB ID: 04b4:3813 Name: NANO BIOS Programmer Link: https://usb-ids.gowdy.us/read/UD/04b4/3813 WIN driver: cyusb3.inf (in case it's relevant); ---------------------------------------------------------------------------- I already contacted the guy, who runs the website mentioned above (shop3.nanobios.cafe24.com), and who also sells these programmers on eBay. He responded that in-the-house software, currently "NANO BIOS Programmer v1.1", is the only software that works with their Nano USB Programmer, but he promised to look into possibility, to "run an open platform software" for this programmer, as he elaborated in his response. Since I have doubts that Windows based programming SW will be ported to Linux, at least not in a foreseeable time window, I would appreciate any useful information, as in - whether this programmer is supported by 'flashrom' project, what needs to be done to make it happen, which Linux distro you're using (in case it matters), etc. Thank you in advance ! Kind regards, Bostjan

1 2

ftdi_write_chunksize, block_erasers and spi_read_status_register proposals
by Buhrow, Simon 26 Jul '19

26 Jul '19

Hi, I´m using flashrom to program a N25Q128E flash with a FT2232H chip (via linux in a virtual machine, I hope the virtual machine does not alter the results too much). As I found the programming time is quite long, I made some research. Here are some suggestions about which I think it´s worth to discuss (I started with a programming time of 05:15 min and got down to 1:44 min): 1) Proposal: in ft2332_spi.c change ftdi-chunksize to 269 ###### CODE Start ##### //Simon Buhrow: changed from 256 to 269 (1 Byte Flash CMD + 3 Byte Address + 256 Byte Flash-Data + 9 Byte FTDI-CMD) if (ftdi_write_data_set_chunksize(ftdic, 269)) { msg_perr("Unable to set chunk size (%s).\n", ftdi_get_error_string(ftdic)); } ###### CODE End ##### Background: Measurements with the oszilloscope let me see, that the transmission of a 256-Byte-page-write-paket takes about 4 ms. Please check spi_rpd_flashrom_bad_page_write_01.png for that (blue = SCK, green = nCS). Above is the whole measurement and below a zoom. First there is the zoomed 2000 bit = 250 Byte burst, followed by a 10 Byte burst (= 260 Byte => 1 Byte Flash Cmd + 3 Byte Address + 256 Byte Flash data). The ftdi_write_data_chunksize refers to all bytes send to the ftdi-chip and not only the raw-flash-data. So the first 256 Bytes of the actually 269 Bytes (6 Byte FTDI-Start-CMD + 1 Byte Flash CMD + 3 Byte Address + 256 Byte Flash-Data + 3 Byte FTDI-CMD) are send to ftdi-chip in a first paket. That´s why it sends only 250 Bytes in a first spi burst (as there are 6 Bytes of ftdi-cmds first followed by the flash cmd, address and raw data) and 10 Bytes in a second spi burst. Changing the value as proposed above the transmission of a 256-Byte-page-write-paket takes just about 80µs. Please check spi_rpd_flashrom_good_page_write.png for validation. I did not check the USB-Communication (for efficiency of paket sizes). But as you can see at spi-level it looks much better. And the total programming time was (in my case) about 30 seconds faster. 2) Proposal: add a flashrom cli parameter to select the block_erasers num May be there is already a similar functionality. But as I can see, the differen block_erasers given in flashchips.c are always used in the manner, that if the first entry works, the first entry is used and that´s it. In my case the second erase-function is the fastest (as I do not write the whole flash). Of course the work around is to change the order in flashchips.c, but may be there could be realized a more comfortable solution? 3) Wish: accelerate spi_read_status_register() after program data Please check spi_rpd_flashrom_bad_page_write_01.png again to see that reading status-register takes quite a long time as well (at the beginning there is 1 Byte send to flash and 2 Byte read from flash and then just idle time). As it is called quite a lot of times it really matters to timing. Looking some deeper I found that libusb_bulk_transfer() which is called from ftdi_read_data() is the bottle_neck (simple measured with prints). I did not get deeper. So I can´t say if the ftdi-chip is bad configured or is too slow or if libusb is not that efficient. To get a good solution for that would be fine. As a simple workaround for shorter programming time I propose - in case of program operation - to not call spi_read_status_register() but just wait a short time (1ms) (may be configurable with a cli parameter or via data at flashchips.c). Why? - I think spi_read_status_register() or better the calling spi25.c:spi_poll_wip() does not has any benefit in my case. It does only check for wip. But as you can see on the scope image it is done several ms after page-program. At least my flash does take much less than 1ms for a page program. Replacing the spi_poll_wip call for all program operations (not erase operations, as they last longer) by a 1ms programmer_delay speed up my programming time much more than 1 minute!! Here is what I did: I added a parameter to spr_write_cmd to indicate if spi_poll_wip() shall be done or not: ###### CODE Start ##### static int spi_write_cmd(..., const unsigned int ignore_spi_poll_wip) { ... if (ignore_spi_poll_wip == 0){ status = spi_poll_wip(flash, poll_delay); } else{ programmer_delay(1000); } } ... spi_nbyte_program(struct flashctx *flash, unsigned int addr, const uint8_t *bytes, unsigned int len) { ... return spi_write_cmd(..., 1); // Simon Buhrow: added ,1 to indicate to not call read_status_register } ###### CODE End ##### May be there are any ideas about making this more general and cleaner? What do you think? Regards, Simon Signed-off-by: Simon Buhrow <simon.buhrow(a)sieb-meyer.de>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom