- flashrom - mail.coreboot.org

error message
by Aidan Coward 27 Aug '19

27 Aug '19

log: flashrom v1.1 on Linux 5.2.9-arch1-1-ARCH (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x59 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. lspci -nnvx: output is in attached text file

1 0

Kaby Lake R - not detecting chip & size correctly
by Rafael Send 27 Aug '19

27 Aug '19

Hi there- I'm running a custom Thinkpad X210 motherboard, which has a Kaby Lake R on it. The default flash chip is 8MB, and is detected as "Opaque Flash Chip" with the correct size, and it flashes correctly. It's an MX25L64 When I replace it with a larger chip (32MB in this case), the detected chip is still the same as before (Opaque flash chip, size 8MB) but the new chip is a MX25L256. This actually works out great for using the same old images and swapping between chips, but I can't flash anything bigger if the size isn't detected correctly so it defeats the purpose of what I'm working on. What can I try to get the chips to be detected correctly? Alternatively, are there any logs or messages I can collect that would help folks on this list add chips or debug this? Thanks, Rafael

3 3

SFDP with Winbond chip
by ro_beri 22 Aug '19

22 Aug '19

Hi to all team members. chip: Winbond 25Q128BFVS0 programmer: ch341a device: Intel NUC5PPYH os: Debian Stretch kernel: 4.9.168-1+deb9u5 (2019-08-11) Flashrom builded with procedure: # apt install pciutils pciutils-dev libpci-dev zlib1g-dev libpci3 libftdi-dev libusb-dev # git clone https://github.com/flashrom/flashrom.git flashrom_git # cd flashrom_git; make; cp flashrom ../ Some parts of build log: # Replacing all version templates with v1.1-rc1-69-g188127e. # Checking for a C compiler... found. # Target arch is x86 # Target OS is Linux # Checking for libpci headers... found. # Checking version of pci_get_dev... new version (including PCI domain parameter). # Checking if libpci is present and sufficient... yes. # Checking for libusb-1.0 headers... found. # Checking if libusb-1.0 is usable... yes. # Checking for FTDI support... found. # Checking for FT232H support in libftdi... found. # Checking if Linux MTD headers are present... yes. # Checking if Linux SPI headers are present... yes. # Checking for utsname support... found. # Checking for clock_gettime support... found. log from "flashrom -p ch341a_spi -VV" in attachment. Regards Bercik

2 1

Unsupported spi flash: XMC qh128ahig
by Oleksij Rempel 17 Aug '19

17 Aug '19

Hi, I was reading out an unsupported chip located on this device: https://wikidevi.com/wiki/Hi-Flying_Eport_Pro-EP20 By pulling nRST down I disabled the SoC and was able to dump the spi flash (XMC qh128ahig) flashrom log is in attachment. -- Regards, Oleksij

1 0

Patch for W25Q64JVSM
by Nick Sayer 16 Aug '19

16 Aug '19

This is just a copy of the W25Q128 with the sizes all cut in half and a different chip ID. It works fine for me. --- ./flashchips.c 2018-11-01 09:37:32.000000000 -0700 +++ ../flashrom-v1.1/flashchips.c 2019-08-07 18:48:54.000000000 -0700 @@ -15671,6 +15671,42 @@ { .vendor = "Winbond", + .name = "W25Q64.V.M", + .bustype = BUS_SPI, + .manufacture_id = WINBOND_NEX_ID, + .model_id = WINBOND_NEX_W25Q64_V_M, + .total_size = 8192, + .page_size = 256, + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP | FEATURE_QPI, + .tested = TEST_OK_PREW, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {2 * 1024, 4096} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {16 * 1024, 512} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {32 * 1024, 256} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {8 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {8 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .unlock = spi_disable_blockprotect, + .write = spi_chip_write_256, + .read = spi_chip_read, + .voltage = {2700, 3600}, + }, + { + .vendor = "Winbond", .name = "W25Q128.V..M", .bustype = BUS_SPI, .manufacture_id = WINBOND_NEX_ID, --- ./flashchips.h 2018-11-01 09:37:32.000000000 -0700 +++ ../flashrom-v1.1/flashchips.h 2019-08-07 18:48:54.000000000 -0700 @@ -931,6 +931,7 @@ #define WINBOND_NEX_W25Q32_W 0x6016 /* W25Q32DW; W25Q32FV in QPI mode */ #define WINBOND_NEX_W25Q64_W 0x6017 /* W25Q64DW; W25Q64FV in QPI mode */ #define WINBOND_NEX_W25Q128_W 0x6018 /* W25Q128FW; W25Q128FV in QPI mode */ +#define WINBOND_NEX_W25Q64_V_M 0x7017 /* W25Q64JVSM */ #define WINBOND_NEX_W25Q128_V_M 0x7018 /* W25Q128JVSM */ #define WINBOND_NEX_W25Q256JV_M 0x7019 /* W25Q256JV_M (QE=0) */

1 0

BIOS Update
by Shaver,Zachary J 16 Aug '19

16 Aug '19

Hey, I'm considering using flashrom to upgrade the bios on a MSI B450M Pro-M2 Motherboard. It's BIOS ROM appears to be a MX25U12873F but I only see MX25U12835F in the supported chips for flashrom. I did a cursory comparison of the datasheets for the two and they look very similar. Is there a chance I could flash the 73 with the 35 profile in flashrom? I am aware that they are 1.8V and will need a 1.8V supply and 1.8V gpio from the programmer (in my case raspberry pi). Thanks

3 3

Copy / backup ENTIRE flash chip; does "-r" already do this?
by Rafael Send 15 Aug '19

15 Aug '19

Hi there- I'm looking at swapping out the physical flash chip on my machine for a larger capacity one, so I wanted to get a quick sanity check: Does a flashrom -r pick up all the various regions in the chip, or does it only go after the BIOS region if I don't specify a layout file? I.e if I do a flashrom -r on the old chip then flashrom -w on the new one, will I get an identical copy of the entire thing? Thanks and apologies if this can be found in the documentation, please feel free to point me there instead. Rafael

2 2

Re: [flashrom] New SPI NOR Flash product Support
by Stefan Tauner 15 Aug '19

15 Aug '19

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

4 4

Re: lenovo c540
by Mike Banon 15 Aug '19

15 Aug '19

You need to extract a clean BIOS ROM ( "clean" = without any system-specific settings ) from a BIOS update utility. Try to open this utility (called something like "winflash_3.00.exe") as an archive with 7zip, and extract the contents of this .exe file using 7zip. If successful, it would give you a set of files, one of which might contain this clean BIOS ROM. Could be called something like WinVALGC300.bin ( you could guess it by looking at the file sizes ). Then open this file using a hexedit, search for $_IFLASH_BIOSIMG header. Not directly after but slightly further after this header, at the closest address ending by 0 (rounded by 0x10) there is a start of BIOS section, the size of which should be equal to a size of your BIOS chip. Copy-paste it into a new binary file, then you could try using it (but only after making a backup of your current chip contents!). You could also compare the contents of your original ROM image vs this "clean" image, to get an idea where a password might be stored (could be encoded instead of a plain text). On Thu, Aug 15, 2019 at 4:27 PM Darko Svilkovic <darko.svilkovic2(a)gmail.com> wrote: > > Hi, > > Yes flashed with a windows update tool,which automaticly updates,has no download ... > > Any help which program tu use to download the bios ... > > Read somthing like there are 2 chips for bios (one for bios and the other for password and settings) ... > > thx > > On Thu, Aug 15, 2019 at 2:28 PM Mike Banon <mikebdp2(a)gmail.com> wrote: >> >> "I have flashed the bios to a new version" - how you did that, using a >> windows tool provided by a laptop manufacturer? If yes, then it >> preserves the originally set password and maybe the other settings. >> Try to extract a "clean" BIOS image from the BIOS update utility >> provided by a laptop manufacturer. Then, using a flashrom-supported >> programmer like USB CH341A with a test clip (SOIC8 ?) together with >> our flashrom opensource tool, you might be able to flash a clean BIOS >> image (without any passwords/settings) into your BIOS chip. Of course >> please make a backup before flashing a new image, in the case it's >> incorrect or you'd need to borrow some Intel ME-related regions or to >> have a MAC address specified in your ROM in order for onboard Ethernet >> working. >> >> On Wed, Aug 7, 2019 at 12:01 PM Darko Svilkovic >> <darko.svilkovic2(a)gmail.com> wrote: >> > >> > hi, >> > >> > Hawe a problem with lenovo c540 AIO,bought this from a second hand,and didn't see,and he didn,t mention that there is a bios admin pass ... >> > >> > I have flashed the bios to a new wersion,taked out the cmos battery,jumpered the cmos jumper but with no success ... >> > >> > Now i heard that the password is in eeprom ... >> > >> > How to remowe it ??? >> > >> > thx >> > >> > Darko/Croatia >> > _______________________________________________ >> > flashrom mailing list -- flashrom(a)flashrom.org >> > To unsubscribe send an email to flashrom-leave(a)flashrom.org

1 0

Flashrom & bus pirate v4 - supported?
by Nick Sayer 15 Aug '19

15 Aug '19

I’ve got flashrom v1.1 (via brew on MacOS X) and a Buspirate v4 running the v7.0 community firmware. I’ve hooked it up to a Winbond W25Q64FV. I’m fairly confident that it’s hooked up correctly, because if I use a terminal program to talk to the BP, I can set it into SPI mode, turn on the power and manually perform a 0x90 command and I get back 0xEF 0x16, which is what the manual tells me is supposed to be a W25Q64FV’s ID. I’ve also manually written a few bytes into the chip and erased them, so I generally have an expectation that the chip is wired up properly and operating correctly. But there are a couple of issues with flashrom. First, every time I use flashrom, if I then do not reset the buspirate, subsequent runs of flashrom just hang. So flashrom isn’t putting the BP back into a mode where it can be recognized, apparently. Secondly, the probe always results in % flashrom --programmer buspirate_spi:dev=/dev/tty.usbmodem000000011,spispeed=30k flashrom v1.1 on Darwin 18.7.0 (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Warning: given baudrate 2000000 rounded down to 230400. Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on buspirate_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! No operations were specified. Adding -V -V gives one interesting extra line: Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x7017 Now, the manual says that there’s supposed to be a 0xef 0x6017 result for 0x9f, but the bus pirate gets back 0x7017, even when I perform a 0x9f manually. So in short, does flashrom 1.1 work properly with the buspirate v4 with firmware v7?

3 5

Problem with BIOS flashin.
by Michał Rączka-Dudek 15 Aug '19

15 Aug '19

Hi. Recently i have experienced problems with flashi bios in broken NAS server. Flahrom was able to detect the chip but couldn't do anything with it. Below is the output from the tool. Can you help me somehow or direct me the way to find solutuon myself? Thanks! Found Winbond flash chip "W25Q64.W" (8192 kB, SPI). 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). Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:EFAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Looking for another erase function. Trying erase function 1... 0x000000-0x007fff:EFAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x8000 ERASE FAILED! Looking for another erase function. Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0x10000 ERASE FAILED! Looking for another erase function. Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x800000 ERASE FAILED! Looking for another erase function. Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x800000 ERASE FAILED! Looking for another erase function. Trying erase function 5... not defined. 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! Pozdrawiam mrd

2 1

lenovo c540
by Darko Svilkovic 15 Aug '19

15 Aug '19

hi, Hawe a problem with lenovo c540 AIO,bought this from a second hand,and didn't see,and he didn,t mention that there is a bios admin pass ... I have flashed the bios to a new wersion,taked out the cmos battery,jumpered the cmos jumper but with no success ... Now i heard that the password is in eeprom ... How to remowe it ??? thx Darko/Croatia

2 1

Timeout in reading whit ch341a programmer
by Marino.Gregorio＠libero.it 15 Aug '19

15 Aug '19

Hi flashrom developers, first af all thankyou for your awesome work. I recently migrated from linux mint 13 (ubuntu 12.04 based) to Linux Mint lmde (Debian stretch based) and i'm aving some problems in using flashrom with a ch341a based programmer. When trying to read an spi flash i got this error : cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT cb_in: error: LIBUSB_TRANSFER_TIMED_OUT ch341a_spi_spi_send_command: Failed to read 4100 bytes Read operation failed! FAILED. Sometimes, but very rarely, i can achieve a complete read. Everything work fine if i reboot in the old OS, so, i think, it's not an hardware problem. Have you got any advice for me? Or is there any way i can help you to figure out the trouble? Thankyou in advance.

2 1

XMC 0H64AH1G
by Tony Lipford 14 Aug '19

14 Aug '19

Thanks for the awesome program! Here is the output for the XMC 0H64AH1G SPI flash chip ----------------------------------------------------------------------------------------------------------------------------- # flashrom -VV -p linux_spi:dev=/dev/spidev0.0,spispeed=8000 flashrom p1.0-78-g7590d1a on Linux 4.9.59-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.5.2, GCC 6.3.0 20170516, little endian Command line (3 args): flashrom -VV -p linux_spi:dev=/dev/spidev0.0,spispeed=8000 Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing linux_spi programmer Using device /dev/spidev0.0 Using 8000 kHz clock linux_spi_init: Using value from /sys/module/spidev/parameters/bufsiz as max buffer size. linux_spi_init: max_kernel_buf_size: 4096 The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25SF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT25SF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESI ES25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESI ES25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ESI ES25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ64(B), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25LQ128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25Q128C, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ21B, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ40C, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ41B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ80C, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for GigaDevice GD25VQ16C, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25LP128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ISSI IS25WP128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L25635F, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX66L51235F, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron N25Q256..3E/MT25QL256, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Micron N25Q512..3E/MT25QL512, 65536 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LQ032C, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x20, id2 0x16 Probing for SST SST25WF020A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST26VF016B(A), 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST26VF032B(A), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST26VF064B(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q256.V, 32768 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q40BW, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q80BW, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q40EW, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q80EW, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25Q128.W, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond W25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Zetta Device ZD25D20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Zetta Device ZD25D40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.0 SFDP number of parameter headers is 2 (NPH = 1). SFDP parameter table header 0/1: ID 0x00, version 1.0 Length 36 B, Parameter Table Pointer 0x000030 Parsing JEDEC flash parameter table... 3-Byte only addressing. Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR. Write chunk size is at least 64 B. Flash chip size is 8192 kB. Block eraser 0: 2048 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 2048 x 4096 B with opcode 0x20. Block eraser 1: 256 x 32768 B with opcode 0x52 Block eraser 2: 128 x 65536 B with opcode 0xd8 done. SFDP parameter table header 1/1: ID 0x20, version 1.0 Length 16 B, Parameter Table Pointer 0x000060 === SFDP has autodetected a flash chip which is not natively supported by flashrom yet. All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually. You can help us by mailing us the output of the following command to flashrom(a)flashrom.org: 'flashrom -VV [plus the -p/--programmer parameter]' Thanks for your help! === Found Unknown flash chip "SFDP-capable chip" (8192 kB, SPI) on linux_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x20, id2 0x16 Found Unknown flash chip "SFDP-capable chip" (8192 kB, SPI). No operations were specified.

1 0

MX25U12873F
by Antonio Ortega 13 Aug '19

13 Aug '19

Hi, Im just trying with this chip MX25U12873F but it doesn´t work, can you help me please.

1 0

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 02 Aug '19

02 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

SMBus revision 0x61 does not match known values
by Ahmad Wahyudin 23 Jul '19

23 Jul '19

$ sudo flashrom --programmer internal [sudo] password for wahyudin: flashrom on Linux 5.0.0-20-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x61 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.

2 2

use the code in github
by sara Azizi 22 Jul '19

22 Jul '19

hello i have a problem in use of thid library which has been put in Github. i dont know how to introduce my chip (for programming). i am afraid of breaking my laptop with my wrongs. please help me! Sara

2 2

Is MX25L6433F supported by flashrom?
by bang corrupt 13 Jul '19

13 Jul '19

Hello, I need to re-flash MX25L6433F, it is not listed as supported by flashrom. This application note <https://www.macronix.com/Lists/ApplicationNote/Attachments/1989/AN0336V3-Co…> lists it in the same column as MX25L6473F, which is supported. The datasheet <https://www.macronix.com/Lists/Datasheet/Attachments/7408/MX25L6433F,%203V,…> says the chip supports SFDP. I can't try it until next week when the ISP clip arrives. I'm wondering if it's worth me adding a definition to flaschips.c. Is MX25L6433F implicitly supported by flashrom? Kind regards, BC.

1 0

Adding a chip
by Krystian Kotkowski 12 Jul '19

12 Jul '19

Could you add a chip to the supported list? MX25L12872F - from a laptop 840 G1 -- Pozdrawiam / Best regards Krystian Kotkowski Serwisant Tel: +48 71 308 98 97 krystian.kotkowski(a)cebitgroup.pl CebITgroup <https://cebitgroup.pl/> | CebITserwis <https://cebitserwis.pl/> | WIPERAPP® <https://wiperapp.eu/> | CebITrecykling <http://www.cebitrecykling.pl/> | firebit.pl <https://www.firebit.pl/> | fajnykomputer.pl <https://www.fajnykomputer.pl/> | LetLease <https://letlease.me/> CebITgroup EP sp. z o.o. sp.j. ul. Kominiarska 42B, 51-180 Wrocław, POLAND VAT EU:PL8943042312 | REGON: 021995311 | KRS:0000476246 | BDO: 000015587

1 1

Flash XMC QH64AHIG
by Dawid Rybacki 11 Jul '19

11 Jul '19

Hello I've de-soldered chip XMC QH64AHIG (XM25QH64AHIG) In attachment you can find dump from flashrom Also I've found that, this chip is equals to : XM25QH64AHIG GD25Q64CSIG MX25L6406EN2I-12G EN25QH64A-104HIP W25Q64JVSSIQ Under link you can find photo of that chip https://ibb.co/Rbjjj62

1 0

This flash part has status UNTESTED: sucsessfull write to W25Q128.W
by prokudin 10 Jul '19

10 Jul '19

Write in Asus P5B SE, xubuntu 19.04 flashrom -p internal -r PRX370A_orig.bin flashrom on Linux 5.0.0-16-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel ICH8/ICH8R". Enabling flash write... OK. Found Winbond flash chip "W25Q128.W" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading flash... done. root@prokudin-System-Product-Name:~# flashrom -p internal -v PRX370A_orig.bin flashrom on Linux 5.0.0-16-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel ICH8/ICH8R". Enabling flash write... OK. Found Winbond flash chip "W25Q128.W" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Verifying flash... VERIFIED. root@prokudin-System-Product-Name:~# ls -la PRX370A_orig.bin -rw-r--r-- 1 root root 16777216 июл 9 13:32 PRX370A_orig.bin root@prokudin-System-Product-Name:~# flashrom -p internal -w /home/prokudin/PRX370A.bin flashrom on Linux 5.0.0-16-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel ICH8/ICH8R". Enabling flash write... OK. Found Winbond flash chip "W25Q128.W" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. root@prokudin-System-Product-Name:~# flashrom -p internal -v /home/prokudin/PRX370A.bin flashrom on Linux 5.0.0-16-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel ICH8/ICH8R". Enabling flash write... OK. Found Winbond flash chip "W25Q128.W" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Verifying flash... VERIFIED. root@prokudin-System-Product-Name:~# flashrom -p internal -r PRX370A_test.bin flashrom on Linux 5.0.0-16-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel ICH8/ICH8R". Enabling flash write... OK. Found Winbond flash chip "W25Q128.W" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading flash... done. root@prokudin-System-Product-Name:~# md5sum PRX370A_test.bin bf7eb9e93467f204c37814177f389044 PRX370A_test.bin root@prokudin-System-Product-Name:~# md5sum /home/prokudin/PRX370A.bin bf7eb9e93467f204c37814177f389044 /home/prokudin/PRX370A.bin

3 3

Eeprom SPI MX25L1636E
by tormenta 08 Jul '19

08 Jul '19

Eeprom SPI MX25L1636E memory does not work to read, write or erase. It would be nice to add the eeprom spi memories that Canon printers have.

1 0

ASRock X370-AM4 BIOS Support
by Furkan Mustafa 07 Jul '19

07 Jul '19

Hello, Thanks for your work on flashrom. I'm sending this email for reporting a system that is not yet supported. Report is attached. Please let me know if I can help in any other way. Thanks, Furkan Mustafa https://rainlab.co.jp

1 0

new SPI FLASH definitions: PN25Fxx(B)
by Thomas Shaddack 05 Jul '19

05 Jul '19

Attached are chip definitions for the PN25Fxx chips. The PN25F08B is now frequently found in IoT devices, usually together with ESP8266, e.g. in Sonoff devices or the newer ESP-01 modules. Chip seems to be functionally identical with many of the more common Winbond W25 ones. Datasheet here: http://www.xtxtech.com/upfile/2016082517095182.pdf The datasheet for the B variant is not easily available, it is assumed it is the "plain" version with a different manufacturer. (Vendor code 0x5E for B version vs 0xE0 for the "plain" one.) However, test on the B variant (in hand) with config based on the "plain" variant datasheet seem to give functional results. PN24F08B is tested on a ch341a_spi programmer hardware (with a SOIC-8 clip and ESP-01 module). Identifies, reads, erases, writes. (Read chip. Check visually, looks like stock ESP-01 firmware. Erase chip. Read chip, get all 0xFF. Write in the firmware read in the first step. Read chip. Get identical file as the first one. Should pass as a successful test.) PN24F04..64 and PN24F04B..128B are untested (not at hand). They are believed to differ only in memory sizes. Due to my current lack of deep familiarity with differences between individual chip flavors, some ".feature_bits" may be missing. Someone more skilled and familiar with the FlashROM project may like to take over here.

1 0

Support For GigaDevice GD25Q64C 8M/64M
by Chawit Wattanakanjana 30 Jun '19

30 Jun '19

Hello, I would like to ask for a support of the chip GigaDevice GD25Q64C. The latest flashrom is able to read the data on the chip but cannot erase nor write. Is this possible to do for the flashrom future updates? P.S. Here is the data sheet for GD25Q64C >> http://www.elm-tech.com/en/products/spi-flash-memory/gd25q64/gd25q64.pdf Regards, Ohm. Sent from my iPhone

1 0

How to program sst49lf020a chip with raspberry pi?
by Craig Taylor 28 Jun '19

28 Jun '19

I am having trouble figuring out the correct pinout for the plcc32 chip to program with the raspberry pi. Here is the Data sheet https://datasheetspdf.com/mobile-pdf/574977/SST/SST49LF020A.html I know that I need to solder to pins VCC, HOLD, WP, GND, SCLK, SO, SI and CS however I have no idea what pins these are on the datasheet. If you have any input on this that would be awesome. I am looking to reprogram a bios on one of these chips Serious thanks in advanced.

1 0

Support using FTD2XX driver for FT2232H device
by Steffen Mauch 27 Jun '19

27 Jun '19

Hello, right now, I am working on a windows version of Flashrom based on the FTD2XX driver from FTDI instead of libFTDI. Thus, I would like to know if I should submit a patch such that the ‚ft2232_spi.c‘ can cope with libFTDI and FTD2XX via defines or crate a new driver. Best regards Steffen

1 0

Not found
by Shamus Hammons 27 Jun '19

27 Jun '19

This is on a Gigabyte AB350M-Gaming 3 motherboard. Let me know if I can provide any other useful information.

1 0

[announce] flashrom v1.1
by Nico Huber 23 Jun '19

23 Jun '19

Dear flashrom followers, I'm pleased to announce that we released flashrom v1.1 after fixing a few minor compilation issues in v1.1-rc2. This is a feature release with a handful of new programmers and lots of new flash chips including, finally, 4-byte-address SPI flashes. You can find the complete release notes here: https://flashrom.org/Flashrom/1.1 The official tarball and signature here: https://download.flashrom.org/releases/flashrom-v1.1.tar.bz2 https://download.flashrom.org/releases/flashrom-v1.1.tar.bz2.asc Again, the hint for package maintainers: If you don't use Git or don't override flashrom's version string anyway, avoid the tarballs offered by tools like Cgit or Github. They don't contain any version information. Best regards, Nico

1 0

Programming Speed FTDI 2232H to N25Q128
by Buhrow, Simon 19 Jun '19

19 Jun '19

Hi, I´m using a N25Q128..3E to store a bitstream configuration for an FPGA. To program the flash I´m using an ftdi2232H chip. I have two ways how to program the flash (with the same ftdi chip!): Via the JTAG and the FPGA (which first loads a JTAG to SPI converter core to do so) or directly via SPI. I prefer the last way as it is with less possible error points and I suppose that it should be faster. My problem: Programming the flash directly via SPI is much slower than the indirect way through JTAG and the FPGA. I think that it does not has to do with the SPI clock frequency as it is even slower in indirect case. But I can observe a significant difference in the Idle time between two SPI sequences/packages. You can see that at attached screenshots. The idle time (red arrows) is 2 - 4 times longer in direct case (below) than in the indirect (above) (as there are about 16000 SPI sequences it really does matter). 1. I couldn't find any flashrom parameters to change idle time. Is there any? 2. When looking at the source code I found the function call 'ftdi_set_latency_timer' but can´t find the function definition. Does it has to do with the idle time? 3. Which function should I touch to change idle time if there is any to do so? 4. Any other advice about how to change the idle time? Regards, Simon

1 0

Print timestamps
by Buhrow, Simon 18 Jun '19

18 Jun '19

Hi, sometimes I like to know how long an operation took or when I started programming. That´s why I added some timestamp printouts. May be you want to add it to the sources or do it in a more elegant way? What´s about adding the timestamp printout to msg_cinfo ? Just a proposal... Regards, Simon

1 0

Flashrom and GD25Q32C
by flashrom＠gnuproject.org 11 Jun '19

11 Jun '19

Hello List, i have a bricked TP-Link router with GD25Q32C DIP8-chip, but flashrom supports only the GD25Q32(B). I can read this ROM with --force option, but no write :( What can i do? Whitch other options exitst for me to write to the DIP8-chip? Thanks, Christioph -- Mit freundlichen Grüßen Christoph Machon -----BEGIN PGP PUBLIC KEY BLOCK----- EMail : christoph(a)mach0n.de GPG Public Key : 0x74D2 5E2E 3D30 9485 Key fingerprint : C33C 5F2F A3C4 3D9E 9319 35D0 74D2 5E2E 3D30 9485 -----END PGP PUBLIC KEY BLOCK-----

2 1

Flash chip in unknown state!
by Max Bell 08 Jun '19

08 Jun '19

Hello, Ijust discovered this project and thought I would try it out on a spare Gigabye GA-N3050-D3P board that I had in storage. Unfortunately, flashing the modified image back to the board fails during the verify step. The same thing happens when I attempt to write the original BIOS back to the board, so I'm stuck with a presumably bricked board. Below is (I hope) all the relevant information you need. I've also attached the original and modified BIOS images. Board: Gigabye GA-N3050-D3P Chip: MX25U6435F (8192 kB) Flashrom ver: 1.0.1 Using Raspberry Pi and Pomona 5252 for SPI interface Verifying flash... FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0xc0d48 Your flash chip is in an unknown state. Thanks, Max Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Re: N25Q128A
by Buhrow, Simon 06 Jun '19

06 Jun '19

I found the error: I had a signal integrity problem. The chip now is detected correctly as N25Q128..3E . All commands execute correctly. So please forget my las mail/post as the chip is already in the flashrom database and working fine!! (as my N25Q128A is a N25Q128..3E ) Sorry! Simon

1 0

about ASUS H110M-E M.2 board with GD25B128CPIG 16MB bios chip
by Pavel Sayekat 06 Jun '19

06 Jun '19

Dear FlashromTeam, if it helps any, (ASUS-H110M-E M.2 board with GD25B128CPIG 16MB bios chip) flashrom -p internal flashrom v1.1-rc1-6-g7eb38aa on Linux 5.1.6-gnu-1 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel H110". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed. New value is 0xaa. SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only. FREG2: Management Engine region (0x00001000-0x0027ffff) is read-only. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME for details. At least some flash regions are write protected. For write operations, you should use a flash layout and include only writable regions. See manpage for more details. Enabling hardware sequencing because some important opcode is locked. PROBLEMS, continuing anyway Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000. No operations were specified.

1 1

Erase/write fail, could you help me?
by William Schmitt 04 Jun '19

04 Jun '19

I believe the chip is proprerly connected, i guess its a code problem, but if isnt, then its the chip... Could you guys help me? This is the log from terminal: sudo flashrom -p serprog:dev=/dev/ttyACM0:115200,spispeed=100k -w BIOS.FI [sudo] senha para wizogales: flashrom v0.9.9-r1954 on Linux 4.9.0-9-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. serprog: Programmer name is "frser-duino" serprog: requested mapping AT45CS1282 is incompatible: 0x1080000 bytes at 0x00000000fef80000. Found Macronix flash chip "MX25L4005(A/C)/MX25L4006E" (512 kB, SPI) on serprog. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x0000fffd! Expected=0xff, Found=0xfc, failed byte count from 0x0000f000-0x0000ffff: 0x3 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: 0x5c0c ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x0000fff4! Expected=0xff, Found=0xfe, failed byte count from 0x00000000-0x0000ffff: 0xc ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0xa0, failed byte count from 0x00000000-0x0007ffff: 0x7659a 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-0x0007ffff: 0x765b5 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!

1 0

Supprot new St95XXx series
by evrinoma＠gmail.com 04 Jun '19

04 Jun '19

Hi Tell me, please, how to post a patch? I added support ST95XXX chips. I've done tested, all chip-sets reads , erases, writes and verifies successfully. Only st95xxxA125 series chipsets respond to RDID request, what why force key logic was improve. chip-set STM95080 STM95160 STM95320 STM95640 STM95128 STM95256

2 2

N25Q128A
by Buhrow, Simon 04 Jun '19

04 Jun '19

Hi, see attached files for success in probe, read and erase for the N25Q128A Flash from Micron. Write-cmd fails. See write_flash.log for details. I will investigate it the next weeks. Any suggestions are welcome. Regards, Simon PS: @Nico Huber: Thanks for your mail. I got the aforementioned error solved: I had a bad formatted hyphen at the '-w' parameter. (As I copied the command from a notepad on my windows system) -----Ursprüngliche Nachricht----- Von: Nico Huber <nico.h(a)gmx.de> Gesendet: Montag, 3. Juni 2019 17:27 An: Buhrow, Simon <simon.buhrow(a)sieb-meyer.de> Betreff: Re: N25Q128A Hello Simon, your mail got filtered because of its size, we have a limit of 256KiB. If you could send your modification as a `diff`, that would be nice. Have a look here, for more instructions: https://flashrom.org/Development_Guidelines Regarding your error: > Error: Extra parameter found. > Please run "flashrom --help" for usage info. I've no idea what could have caused it. You can add `-o logfile.txt` to your flashrom command and attach the resulting log file to your mail. Maybe it can tell us more. Regards, Nico

1 0

[announce] flashrom 1.1-rc2
by Nico Huber 03 Jun '19

03 Jun '19

Hello flashrom friends, after an unannounced rc1, we now have a `v1.1-rc2` in Git. During the 1.5 years since v1.0, we have merged SPI 4-byte address support, about half a dozen new programmers and a lot of flash chips. Preliminary release notes can be found at [1], and the full list of supported hardware at [2]. Happy testing! If you don't use Git, you can find a tarball at [3]. Best regards, Nico [1] https://flashrom.org/Flashrom/1.1 [2] https://flashrom.org/Flashrom/1.1/Supported_Hardware [3] https://review.coreboot.org/cgit/flashrom.git/snapshot/flashrom-1.1-rc2.tar…

1 0

Intel QS77 report
by Evgeny Zinoviev 28 May '19

28 May '19

Internal flashing works, see attached log.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom