- flashrom - mail.coreboot.org

Skylarks chipsets
by Jason La Mont 10 Aug '16

10 Aug '16

Hi, Is there, or are there plans to, support the Intel skylake CM236 PCH? Thanks, Lee Sent from my iPhone

1 0

Aspire One
by scrooyahoo＠riseup.net 06 Aug '16

06 Aug '16

Hi, In the Laptop table the Aspire one is listed as BAD But as there are so many different aspire one models i wonder if ALL Aspire one models are BAD In my case i have the ZG5 model also known as AOA110 (512MB) and AOA150 (1GB) These models have Winbond W25x80 EEPROMS (these are listed as supported, all OK I wonder what's the safest way to try? Also the link regarding the Aspire One in the Laptop table points to the coreboot mailing list, but in the entire post there is NO mention of the aspire one. Eventually i could de-solder the chip and try to flash it in an external programmer. I have 3 of these Acers that could use a fresh BIOS. (hopefully the latest one allows to boot from SD) Most Aspire One netbooks have BIOS issues and having a tool that doesn't require Microsoft would be very welcome. In software there is a mention of SST2400 and there is no mention of Winbond, but on the mainboard there is a Winbond 25x80 chip. Best, Wilfried

3 2

Re: [flashrom] Broadwell-DE SoC
by Wen Wang 05 Aug '16

05 Aug '16

I am able to update the BIOS region too using Nico's patches. Updating the entire flash is still an issue - timing out in ME region. Hopefully Intel could help address it. Many thanks to Nico and Ed! Wen -----Original Message----- From: Ed Swierk [mailto:eswierk@skyportsystems.com] Sent: Tuesday, August 2, 2016 7:22 PM To: Nico Huber <nico.h(a)gmx.de> Cc: Wen Wang <wen.wang(a)adiengineering.com>; flashrom(a)flashrom.org Subject: Re: [flashrom] Broadwell-DE SoC I flashed coreboot using an external programmer (RPi), and booted it. Now flashrom with Nico's patches works fine for reading, erasing and writing the BIOS region. Just need to specify the layout (-l) and image (-i), and verify only the region being updated (-A). When I switch back to the stock BIOS I'll grab more debug output to figure out the write protection issue. --Ed On Tue, Aug 2, 2016 at 2:10 PM, Nico Huber <nico.h(a)gmx.de> wrote: > Hi Ed, > > On 02.08.2016 21:34, Ed Swierk wrote: >> With Nico's patches, I am able to read the BIOS portion of the flash >> (0x08000000-0x10000000) on a Camelback Mountain board with the stock >> BIOS. > thanks for the report. > >> I haven't been able to write the BIOS portion of the flash, though, >> as it fails to erase the very first block. Despite the warning, the >> flash is left untouched. > Your log too seems incomplete (please send a full log with -o option), > I can't say if it's not just due to write protection. > >> [...] >> Warning: SPI Configuration Lockdown activated. > We are only allowed to use SPI commands specified below. > >> [...] >> 0x94: 0x5006 (PREOP) > Each byte in PREOP specfies an allowed pre command (0x06 prepares for > write). >> 0x96: 0x4ed0 (OPTYPE) >> 0x98: 0x0201009f (OPMENU) >> 0x9C: 0xc705d803 (OPMENU+4) > Each byte in OPMENU specifies an allowed SPI command. > >> [...] >> Erasing and writing flash chip... Trying erase function 0... >> 0x800000-0x800fff:EInvalid OPCODE 0x06, will not execute. >> spi_block_erase_20 failed during command execution at address >> 0x800000 > This is supposed to fail, as SPI command 0x20 is not allowed. > (It complains about 0x06 because that's always executed before 0x20). > >> Reading current flash chip contents... done. Looking for another erase function. >> Trying erase function 1... 0x800000-0x807fff:EInvalid OPCODE 0x06, >> will not execute. >> spi_block_erase_52 failed during command execution at address >> 0x800000 > 52 is not allowed too. > >> Reading current flash chip contents... done. Looking for another erase function. >> Trying erase function 2... 0x800000-0x80ffff:ETransaction error! >> SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 >> SSFC: SCGO=0, ACS=1, SPOP=0, COP=5, DBC=0, SME=0, SCF=4 Running >> OPCODE 0xd8 failed at address 0x800000 (payload length was 0). >> spi_block_erase_d8 failed during command execution at address >> 0x800000 > d8 is allowed but fails, might be due to a write protection. > >> Reading current flash chip contents... done. Looking for another erase function. >> Trying erase function 3... 0x000000-0xffffff:RTransaction error! >> SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 >> SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=63, SME=0, SCF=4 Running >> OPCODE 0x03 failed at address 0x023000 (payload length was 64). > Here it tried to fall back to erasing the whole chip, which again > tries to read the ME region and fails. > >> Can't read! Aborting. >> FAILED! >> Uh oh. Erase/write failed. >> Your flash chip is in an unknown state. > The warning is correct IMHO, as flashrom really doesn't know the state. > > In any case you can also try the hardware sequencing mode of flashrom > (see flashrom's manpage). It let's the hardware choose the opcodes > based on the flash descriptor. > > Nico

1 0

i found the supported laptop table
by scrooyahoo＠riseup.net 03 Aug '16

03 Aug '16

There is an aspire one listed as not suported, but it does not sat what exact type aspire one it is. I have the AOA110, also knowns as AOA150 with more RAM and ZG5. hwinfo told me that it uses an SST2400 chip. But that's as far as my skills get. I'll try FreeDOS route Best, Wilfried

1 0

How do i know if it is safe to try this tool to flash a Aspire One AOA 110?
by scrooyahoo＠riseup.net 03 Aug '16

03 Aug '16

Dear flashrom crew, I downloaded the latest BIOS for aspire one AOA 110 In case it helps here are the links https://acer--uk.custhelp.com/app/answers/detail/a_id/6054/~/updating-the-b… http://www.acer.com/ac/en/US/content/drivers http://global-download.acer.com/GDFiles/BIOS/BIOS/BIOS_Acer_3310_A_AOA110%2… Looks like the .fd file is the binary. But how do i know if this will work? Just trying to save some hardware from the scrapheap. So the risk is low, but it would be a shame if i brick this thing. Kind regards, Wilfried

1 0

Re: [flashrom] Broadwell-DE SoC
by Nico Huber 03 Aug '16

03 Aug '16

Hi Ed, On 02.08.2016 21:34, Ed Swierk wrote: > With Nico's patches, I am able to read the BIOS portion of the flash > (0x08000000-0x10000000) on a Camelback Mountain board with the stock > BIOS. thanks for the report. > I haven't been able to write the BIOS portion of the flash, though, as > it fails to erase the very first block. Despite the warning, the flash > is left untouched. Your log too seems incomplete (please send a full log with -o option), I can't say if it's not just due to write protection. > [...] > Warning: SPI Configuration Lockdown activated. We are only allowed to use SPI commands specified below. > [...] > 0x94: 0x5006 (PREOP) Each byte in PREOP specfies an allowed pre command (0x06 prepares for write). > 0x96: 0x4ed0 (OPTYPE) > 0x98: 0x0201009f (OPMENU) > 0x9C: 0xc705d803 (OPMENU+4) Each byte in OPMENU specifies an allowed SPI command. > [...] > Erasing and writing flash chip... Trying erase function 0... > 0x800000-0x800fff:EInvalid OPCODE 0x06, will not execute. > spi_block_erase_20 failed during command execution at address 0x800000 This is supposed to fail, as SPI command 0x20 is not allowed. (It complains about 0x06 because that's always executed before 0x20). > Reading current flash chip contents... done. Looking for another erase function. > Trying erase function 1... 0x800000-0x807fff:EInvalid OPCODE 0x06, > will not execute. > spi_block_erase_52 failed during command execution at address 0x800000 52 is not allowed too. > Reading current flash chip contents... done. Looking for another erase function. > Trying erase function 2... 0x800000-0x80ffff:ETransaction error! > SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 > SSFC: SCGO=0, ACS=1, SPOP=0, COP=5, DBC=0, SME=0, SCF=4 > Running OPCODE 0xd8 failed at address 0x800000 (payload length was 0). > spi_block_erase_d8 failed during command execution at address 0x800000 d8 is allowed but fails, might be due to a write protection. > Reading current flash chip contents... done. Looking for another erase function. > Trying erase function 3... 0x000000-0xffffff:RTransaction error! > SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 > SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=63, SME=0, SCF=4 > Running OPCODE 0x03 failed at address 0x023000 (payload length was 64). Here it tried to fall back to erasing the whole chip, which again tries to read the ME region and fails. > Can't read! Aborting. > FAILED! > Uh oh. Erase/write failed. > Your flash chip is in an unknown state. The warning is correct IMHO, as flashrom really doesn't know the state. In any case you can also try the hardware sequencing mode of flashrom (see flashrom's manpage). It let's the hardware choose the opcodes based on the flash descriptor. Nico

2 1

Broadwell-DE SoC
by Wen Wang 02 Aug '16

02 Aug '16

Hello, Has anybody tried flashrom on Broadwell-DE SoC? Intel has upstreamed coreboot support. But we are having trouble with flashrom. The ME region does not seem to be accessible. We cannot read the entire flash (fails when reading ME) even though we enabled all reads in Master Access Section in FITC. We also tried to set FDO, it did not help either. We would like to at least be able to update the BIOS region. However, flashrom performs a full read prior to doing partial write. Below is the log using flashrom trunk. Thanks! Wen ++++++++++++ flashrom log ++++++++++++++++ [root@localhost flashrom_trunk]# ./flashrom -p internal -r backup.bin -V flashrom v0.9.9-r1954 on Linux 4.2.8-200.fc22.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.3.0, GCC 5.3.1 20151207 (Red Hat 5.3.1-2), little endian Command line (5 args): ./flashrom -p internal -r backup.bin -V Calibrating delay loop... OS timer resolution is 1 usecs, 2474M loops per second, 10 myus = 10 us, 100 myus = 102 us, 1000 myus = 1011 us, 10000 myus = 10133 us, 4 myus = 4 us, OK. Initializing internal programmer Found candidate at: 00000500-00000510 Found coreboot table at 0x00000500. Error accessing high tables, 0x100000 bytes at 0x000000007efcf000 /dev/mem mmap failed: Resource temporarily unavailable Failed getting access to coreboot high tables. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "ADI Engineering" DMI string system-product-name: "BCC" DMI string system-version: "1.0" DMI string baseboard-manufacturer: "ADI Engineering" DMI string baseboard-product-name: "BCC" DMI string baseboard-version: "1.0" Found chipset "Intel C224" with PCI ID 8086:8c54. 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... Root Complex Register Block address = 0xfed1c000 GCS = 0xc21: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap: enabled (A16(+) inverted) 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x09: BIOS Lock Enable: disabled, BIOS Write Enable: enabled SPIBAR = 0x00007f7924698000 + 0x3800 0x04: 0xd009 (HSFS) HSFS: FDONE=1, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=0, FDV=1, FLOCKDN=1 Warning: SPI Configuration Lockdown activated. The Flash Descriptor Override Strap-Pin is set. Restrictions implied by the Master Section of the flash descriptor are NOT in effect. Please note that Protected Range (PR) restrictions still apply. Reading OPCODES... done 0x06: 0x3f00 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=63, SME=0 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. 0x58: 0x0fff0e00 FREG1: BIOS region (0x00e00000-0x00ffffff) is read-write. 0x5C: 0x0dff0001 FREG2: Management Engine region (0x00001000-0x00dfffff) is read-write. 0x90: 0x80 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 0x91: 0xf80000 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=0 0x94: 0x0000 (PREOP) 0x96: 0x0000 (OPTYPE) 0x98: 0x00000000 (OPMENU) 0x9C: 0x00000000 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x80800000 (LVSCC) LVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=1 0xC8: 0x00000000 (UVSCC) UVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0 0xD0: 0x50444653 (FPB) Enabling hardware sequencing because some important opcode is locked. OK. The following protocols are supported: FWH, Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Hardware sequencing reports 1 attached SPI flash chip with a density of 16384 kB. The first partition ranges from 0x000000 to 0x652fff. In that range are 1619 erase blocks with 4096 B each. The second partition ranges from 0x653000 to 0xffffff. In that range are 2477 erase blocks with 4096 B each. Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x75, id2 0xef, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x75, id2 0xef, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x13, id2 0x8c, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x75, id2 0xef, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x75, id2 0xef, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x4c, id2 0x41, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x75, id2 0xef, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x75, id2 0xef, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x4c, id2 0x41, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x75, id2 0xef, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x75, id2 0xef, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x02, id2 0x58, id1 is normal flash content, id2 is normal flash content Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific). Reading flash... Reading 16777216 bytes starting at 0x000000. Timeout error between offset 0x00014400 and 0x0001443f (= 0x00014400 + 63)! HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=1, FDOPSS=0, FDV=1, FLOCKDN=1 HSFC: FGO=0, FCYCLE=0, FDBC=63, SME=0 Read operation failed! FAILED. Restoring MMIO space at 0x7f792469b8a0 Restoring PCI config space for 00:1f:0 reg 0xdc [root@localhost flashrom_trunk]#

3 3

Re: [flashrom] Writing to a specific Flash region with Layout approach
by Pradeep Ch 02 Aug '16

02 Aug '16

Hello David, Thanks for commands usage . For the command: dd if=test2.bin of=test.bin bs=1 seek=$((0x1a1e0)) conv=notrunc It is subtle when you are mentioning bs=1, If we donot specify bs, it will take a default value of 512 I suppose, then seek will be (0x1a1e0)*512 which will skip lot of bytes from the beginning of the file. So, we cannot use a layout file to write to a specific region. Rgds, On Tue, Aug 2, 2016 at 1:31 AM, David Hendricks <dhendrix(a)chromium.org> wrote: > > > On Mon, Aug 1, 2016 at 9:59 AM, Pradeep Ch <shanmugp(a)sysargus.com> wrote: > >> How do I pad the bootloader. img to 8MBytes ? But, still it occupies the >> first 106976 Bytes right ? Remaining space is empty I suppose. >> > To create a 8MB file full of 0xff bytes: > dd if=/dev/zero bs=1k count=8192 2>/dev/null | tr "\000" "\377" > test.bin > > From there, you can use dd with skip=, seek=, and conv=notrunc to place > your content wherever you need to in the image. For example, > dd if=test1.bin of=test.bin bs=1 conv=notrunc > dd if=test2.bin of=test.bin bs=1 seek=$((0x1a1e0)) conv=notrunc > > Thanks. >> On Aug 1, 2016 9:08 PM, "Urja Rannikko" <urjaman(a)gmail.com> wrote: >> >>> Hi, >>> >>> On Mon, Aug 1, 2016 at 10:33 AM, Pradeep Ch <shanmugp(a)sysargus.com> >>> wrote: >>> > >>> > I am attempting to write to a flashrom using layout/region approach. >>> > The NOR flash size is 8MBytes. The file size I am writing is 106976 >>> Bytes. >>> > >>> > The rom.layout file contents are: >>> > 00000000:0001a1df test1 >>> > 0001a1e0:007fffff test2 >>> > >>> > The command I am using is: >>> > ./flashrom -p ft2232_spi:type=arm-usb-ocd --layout rom.layout --image >>> test1 >>> > -w bootloader.img >>> > >>> > The error I am getting is : >>> > Using region: "test1". >>> > Calibrating delay loop... OK. >>> > Found Eon flash chip "EN25Q64" (8192 kB, SPI) on ft2232_spi. >>> > Error: Image size (106976 B) doesn't match the flash chip's size >>> (8388608 >>> > B)! >>> > >>> > Please let me know about the error. >>> >>> The current layout system will only limit the actually written area, >>> not change the requirements of the flash file being the size of the >>> chip, so in this case you'd need to pad the bootloader.img to 8MB. >>> >> >> _______________________________________________ >> flashrom mailing list >> flashrom(a)flashrom.org >> https://www.flashrom.org/mailman/listinfo/flashrom >> > > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. >

1 0

Re: [flashrom] Writing to a specific Flash region with Layout approach
by David Hendricks 01 Aug '16

01 Aug '16

On Mon, Aug 1, 2016 at 9:59 AM, Pradeep Ch <shanmugp(a)sysargus.com> wrote: > How do I pad the bootloader. img to 8MBytes ? But, still it occupies the > first 106976 Bytes right ? Remaining space is empty I suppose. > To create a 8MB file full of 0xff bytes: dd if=/dev/zero bs=1k count=8192 2>/dev/null | tr "\000" "\377" > test.bin >From there, you can use dd with skip=, seek=, and conv=notrunc to place your content wherever you need to in the image. For example, dd if=test1.bin of=test.bin bs=1 conv=notrunc dd if=test2.bin of=test.bin bs=1 seek=$((0x1a1e0)) conv=notrunc Thanks. > On Aug 1, 2016 9:08 PM, "Urja Rannikko" <urjaman(a)gmail.com> wrote: > >> Hi, >> >> On Mon, Aug 1, 2016 at 10:33 AM, Pradeep Ch <shanmugp(a)sysargus.com> >> wrote: >> > >> > I am attempting to write to a flashrom using layout/region approach. >> > The NOR flash size is 8MBytes. The file size I am writing is 106976 >> Bytes. >> > >> > The rom.layout file contents are: >> > 00000000:0001a1df test1 >> > 0001a1e0:007fffff test2 >> > >> > The command I am using is: >> > ./flashrom -p ft2232_spi:type=arm-usb-ocd --layout rom.layout --image >> test1 >> > -w bootloader.img >> > >> > The error I am getting is : >> > Using region: "test1". >> > Calibrating delay loop... OK. >> > Found Eon flash chip "EN25Q64" (8192 kB, SPI) on ft2232_spi. >> > Error: Image size (106976 B) doesn't match the flash chip's size >> (8388608 >> > B)! >> > >> > Please let me know about the error. >> >> The current layout system will only limit the actually written area, >> not change the requirements of the flash file being the size of the >> chip, so in this case you'd need to pad the bootloader.img to 8MB. >> > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://www.flashrom.org/mailman/listinfo/flashrom > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] Writing to a specific Flash region with Layout approach
by Pradeep Ch 01 Aug '16

01 Aug '16

How do I pad the bootloader. img to 8MBytes ? But, still it occupies the first 106976 Bytes right ? Remaining space is empty I suppose. Thanks. On Aug 1, 2016 9:08 PM, "Urja Rannikko" <urjaman(a)gmail.com> wrote: > Hi, > > On Mon, Aug 1, 2016 at 10:33 AM, Pradeep Ch <shanmugp(a)sysargus.com> wrote: > > > > I am attempting to write to a flashrom using layout/region approach. > > The NOR flash size is 8MBytes. The file size I am writing is 106976 > Bytes. > > > > The rom.layout file contents are: > > 00000000:0001a1df test1 > > 0001a1e0:007fffff test2 > > > > The command I am using is: > > ./flashrom -p ft2232_spi:type=arm-usb-ocd --layout rom.layout --image > test1 > > -w bootloader.img > > > > The error I am getting is : > > Using region: "test1". > > Calibrating delay loop... OK. > > Found Eon flash chip "EN25Q64" (8192 kB, SPI) on ft2232_spi. > > Error: Image size (106976 B) doesn't match the flash chip's size (8388608 > > B)! > > > > Please let me know about the error. > > The current layout system will only limit the actually written area, > not change the requirements of the flash file being the size of the > chip, so in this case you'd need to pad the bootloader.img to 8MB. >

1 0

Re: [flashrom] Writing to a specific Flash region with Layout approach
by Urja Rannikko 01 Aug '16

01 Aug '16

Hi, On Mon, Aug 1, 2016 at 10:33 AM, Pradeep Ch <shanmugp(a)sysargus.com> wrote: > > I am attempting to write to a flashrom using layout/region approach. > The NOR flash size is 8MBytes. The file size I am writing is 106976 Bytes. > > The rom.layout file contents are: > 00000000:0001a1df test1 > 0001a1e0:007fffff test2 > > The command I am using is: > ./flashrom -p ft2232_spi:type=arm-usb-ocd --layout rom.layout --image test1 > -w bootloader.img > > The error I am getting is : > Using region: "test1". > Calibrating delay loop... OK. > Found Eon flash chip "EN25Q64" (8192 kB, SPI) on ft2232_spi. > Error: Image size (106976 B) doesn't match the flash chip's size (8388608 > B)! > > Please let me know about the error. The current layout system will only limit the actually written area, not change the requirements of the flash file being the size of the chip, so in this case you'd need to pad the bootloader.img to 8MB.

1 0

Writing to a specific Flash region with Layout approach
by Pradeep Ch 01 Aug '16

01 Aug '16

I am attempting to write to a flashrom using layout/region approach. The NOR flash size is 8MBytes. The file size I am writing is 106976 Bytes. The rom.layout file contents are: 00000000:0001a1df test1 0001a1e0:007fffff test2 The command I am using is: ./flashrom -p ft2232_spi:type=arm-usb-ocd --layout rom.layout --image test1 -w bootloader.img The error I am getting is : Using region: "test1". Calibrating delay loop... OK. Found Eon flash chip "EN25Q64" (8192 kB, SPI) on ft2232_spi. Error: Image size (106976 B) doesn't match the flash chip's size (8388608 B)! Please let me know about the error. Thanks, Pradeep Ch.

1 0

Re: [flashrom] Failed to write/read NOR flash EN25Q64 using ARM-USB-OCD Jtag.
by Stefan Tauner 01 Aug '16

01 Aug '16

On Sun, 31 Jul 2016 15:34:18 +0530 Pradeep Ch <pradeepsysargus(a)gmail.com> wrote: > favorite > <http://stackoverflow.com/questions/38674226/flashrom-tool-command-has-faile…> > > I am able to detect my flash chip when I use the command: > > ./flashrom -p ft2232_spi:type=arm-usb-ocd -c EN25Q64 > > If use the below command to write binary file to the flash memory using > JTAG - ARM-USB-OCD debugger for my target board RT5350F-OLinuXino-EVB, > > ./flashrom -p ft2232_spi:type=arm-usb-ocd -w > FlashImage_RT5350F_OLinuXino_EVB.bin > > I am getting an error, the error is: > > Found Eon flash chip "EN25Q64" (8192 kB, SPI) on ft2232_spi. > ftdi_write_data: -110, usb bulk write failed > send_buf failed before read: 1 > Reading old flash chip contents... ftdi_read_data: -110, usb bulk read failed > get_buf failed: 1 > FAILED. Do you power the whole setup via the OCD? That might be the culprit. I presume that it can not supply enough current in all operating modes. Apparently it is enough to probe for the chip though... -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Failed to write/read NOR flash EN25Q64 using ARM-USB-OCD Jtag.
by Pradeep Ch 31 Jul '16

31 Jul '16

favorite <http://stackoverflow.com/questions/38674226/flashrom-tool-command-has-faile…> I am able to detect my flash chip when I use the command: ./flashrom -p ft2232_spi:type=arm-usb-ocd -c EN25Q64 If use the below command to write binary file to the flash memory using JTAG - ARM-USB-OCD debugger for my target board RT5350F-OLinuXino-EVB, ./flashrom -p ft2232_spi:type=arm-usb-ocd -w FlashImage_RT5350F_OLinuXino_EVB.bin I am getting an error, the error is: Found Eon flash chip "EN25Q64" (8192 kB, SPI) on ft2232_spi. ftdi_write_data: -110, usb bulk write failed send_buf failed before read: 1 Reading old flash chip contents... ftdi_read_data: -110, usb bulk read failed get_buf failed: 1 FAILED. Please let me know, Thanks, Pradeep Ch.

1 0

[PATCH] Work around very broken timers.
by Stefan Tauner 30 Jul '16

30 Jul '16

Allow myusec_calibrate_delay() to indicate errors and abort in cli_classic if that happens. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> --- cli_classic.c | 6 +++++- programmer.h | 2 +- udelay.c | 22 ++++++++++++++-------- 3 files changed, 20 insertions(+), 10 deletions(-) Roxfan on IRC had major problems getting flashrom to even start because of some hardware-related timing problems. Without this patch his hardware would (almost?) endlessly loop during timer calibration. This patch aborts instead after a while and should not trigger any regressions. One can test it by overriding the gettimeofday results in measure_delay() by adding following assignments: start.tv_sec = 0; end.tv_sec = 0; start.tv_usec = 0; end.tv_usec = 0; diff --git a/cli_classic.c b/cli_classic.c index a2c2014..4a68f0b 100644 --- a/cli_classic.c +++ b/cli_classic.c @@ -414,7 +414,11 @@ int main(int argc, char *argv[]) } /* FIXME: Delay calibration should happen in programmer code. */ - myusec_calibrate_delay(); + if (myusec_calibrate_delay() != 0) { + msg_perr("Error: Custom timer calibration failed.\n"); + ret = 1; + goto out_shutdown; + } if (programmer_init(prog, pparam)) { msg_perr("Error: Programmer initialization failed.\n"); diff --git a/programmer.h b/programmer.h index bd8e98d..b39fba4 100644 --- a/programmer.h +++ b/programmer.h @@ -268,8 +268,8 @@ extern const struct board_info laptops_known[]; #endif /* udelay.c */ +int myusec_calibrate_delay(void); void myusec_delay(unsigned int usecs); -void myusec_calibrate_delay(void); void internal_sleep(unsigned int usecs); void internal_delay(unsigned int usecs); diff --git a/udelay.c b/udelay.c index 7c6961d..3562268 100644 --- a/udelay.c +++ b/udelay.c @@ -85,7 +85,7 @@ static unsigned long measure_delay(unsigned int usecs) return timeusec; } -void myusec_calibrate_delay(void) +int myusec_calibrate_delay(void) { unsigned long count = 1000; unsigned long timeusec, resolution; @@ -106,16 +106,21 @@ recalibrate: if (timeusec > 1000000 / 4) break; if (count >= ULONG_MAX / 2) { - msg_pinfo("timer loop overflow, reduced precision. "); + msg_pwarn("timer loop overflow (count=%lu, micro=%lu, timeusec=%lu), reduced precision.\n", + count, micro, timeusec); break; } count *= 2; } tries ++; - /* Avoid division by zero, but in that case the loop is shot anyway. */ - if (!timeusec) - timeusec = 1; + /* Something is completely wrong. Avoid a possible endless loop and fall back to internal_delay(). */ + if (timeusec == 0) { + micro = 0; + msg_pwarn("Timing measurement seems to be broken.\n" + "Falling back to possibly insufficient timing sources!\n"); + return 1; + } /* Compute rounded up number of loops per microsecond. */ micro = (count * micro) / timeusec + 1; @@ -168,6 +173,7 @@ recalibrate: msg_pdbg("%ld myus = %ld us, ", resolution * 4, timeusec); msg_pinfo("OK.\n"); + return 0; } /* Not very precise sleep. */ @@ -187,7 +193,7 @@ void internal_sleep(unsigned int usecs) void internal_delay(unsigned int usecs) { /* If the delay is >1 s, use internal_sleep because timing does not need to be so precise. */ - if (usecs > 1000000) { + if (micro == 0 || usecs > 1000000) { internal_sleep(usecs); } else { myusec_delay(usecs); @@ -197,9 +203,9 @@ void internal_delay(unsigned int usecs) #else #include <libpayload.h> -void myusec_calibrate_delay(void) +int myusec_calibrate_delay(void) { - get_cpu_speed(); + return get_cpu_speed() == 0; // Return 1 on errors, i.e. if get_cpu_speed() returns 0 } void internal_delay(unsigned int usecs) -- Kind regards, Stefan Tauner

1 0

[PATCH 0/6] Initial status register and access protection infrastructure
by Hatim Kanchwala 29 Jul '16

29 Jul '16

Hi, Following patches add new infrastructure for status register(s) and locking/unlocking of access protection. Detailed points for explaining each patch are included within them. Some general thoughts - - The code has a lot TODOs and FIXMEs (most of which I have addressed to myself). They are short-term targets and represent the work-in-progress nature of the patches. Future revisions will resolve them. - There are a lot of comments. Eventually much of that will be relocated to documentation and wiki, so comments in future revisions will shrink. - Some CLI code is borrowed from the ChromiumOS fork (https://chromium.googlesource.com/chromiumos/third_party/flashrom/). IMO, the exact words to use for the options is subjective. - The names for struct status_register and struct wp defines (in statusreg_layouts.c and writeprotect_layouts.c respectively) are not very creative and tend to be long. I couldn't come up with a generic scheme that captures most of the information regarding it. You are welcome to offer creative suggestions ;) Further work - - Read and write "configuration" registers (a lot of Spansion chips have those) - Add tested/untested status for new infrastructure similar to what we have for chips (like TEST_PREW, etc.) - write protection modes - protection ranges - Access protection for non-SPI chips (pointed to by Stefan over IRC) - Reuse layouts for locking/unlocking (pointed to by Stafan and David over IRC) - Handling WPS bit (a couple of GigaDevice chips have this) - Exotic chips (mostly Atmel, now Adesto, chips fall under this category) This is what I particularly seek - - Feedback on code - Feedback on CLI - Any other ideas that you'd like to add tu further work - Please add support for a few chips that you might have, and if possible also test them - would like to know how cumbersome it is Thank you for your time. I am looking forward to your feedback and having a discussion. I hope this contribution (and many more in the future) adds value to flashrom and its community. Bye, Hatim Hatim Kanchwala (6): Status register infrastructure Locking/unlocking access protection infrastructure WIP: Add support for status register infrastructure to existing chips WIP: Add support for access protection infrastructure to existing chips Integrate new infrastructure with existing codebase Add command-line interface to expose new infrastructure Makefile | 6 +- chipdrivers.h | 24 +++ cli_classic.c | 200 +++++++++++++++++++++++- flash.h | 46 +++++- flashchips.c | 176 +++++++++++++++++---- flashrom.8.tmpl | 56 ++++++- flashrom.c | 17 +- spi.h | 8 +- spi25.c | 164 +++++++++++++++---- spi25_statusreg.c | 416 +++++++++++++++++++++++++++++++++++++++++++++++++ spi25_statusreg.h | 115 ++++++++++++++ statusreg_layouts.c | 320 +++++++++++++++++++++++++++++++++++++ writeprotect.c | 405 +++++++++++++++++++++++++++++++++++++++++++++++ writeprotect.h | 40 +++++ writeprotect_layouts.c | 166 ++++++++++++++++++++ 15 files changed, 2083 insertions(+), 76 deletions(-) create mode 100644 spi25_statusreg.h create mode 100644 statusreg_layouts.c create mode 100644 writeprotect.c create mode 100644 writeprotect.h create mode 100644 writeprotect_layouts.c -- 2.7.4

2 7

[PATCH] Add support for Micron N25Q016..3E
by Stefan Tauner 29 Jul '16

29 Jul '16

This kind of chip seems to be behind Altera's EPCQ16 that is used to store configuration of FPGAs on some boards. No official datasheet matching the chip is available. The chip definition bases on the datasheet of the EPCQ16 and other Micron chips of the same familiy. Its existence and functionality via SFDP was reported by Peter Ma. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> On Thu, 28 Jul 2016 19:59:59 +0000 "Ma, Peter" <peter.ma(a)intel.com> wrote: > I just received a new set of boards with the Altera EPCQ16 that we discussed before. Something odd happened: I would use flashrom and it would do the usual "SFDP-capable chip" (2048 kB, SPI). > > But on subsequent tries (even after re-boots), flashrom is coming back with: > Found ST flash chip "unknown ST SPI chip" (0 kB, SPI) > > Have any idea as to what could be going wrong? Not exactly, no. Apparently something you did changed the chip's reaction to the SFDP query opcode or something similar. You could try lowering the SPI frequency and look for a changed behavior while probing for SFDP. If that fails you could also try the attached patch that adds a chip definition that should work for your variation as well. --- flashchips.c | 39 ++++++++++++++++++++++++++++++++++++++- flashchips.h | 2 ++ 2 files changed, 40 insertions(+), 1 deletion(-) diff --git a/flashchips.c b/flashchips.c index 40b6b8e..30c50ca 100644 --- a/flashchips.c +++ b/flashchips.c @@ -9505,7 +9505,7 @@ const struct flashchip flashchips[] = { { .vendor = "Micron/Numonyx/ST", - .name = "N25Q016", + .name = "N25Q016..1E", .bustype = BUS_SPI, .manufacture_id = ST_ID, .model_id = ST_N25Q016__1E, @@ -9542,6 +9542,43 @@ const struct flashchip flashchips[] = { { .vendor = "Micron/Numonyx/ST", + .name = "N25Q016..3E", + .bustype = BUS_SPI, + .manufacture_id = ST_ID, + .model_id = ST_N25Q016__3E, + .total_size = 2048, + .page_size = 256, + /* supports SFDP */ + /* OTP: 64B total; read 0x4B, write 0x42 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_OK_PREW, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 512} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 64} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 32} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_n25q, /* TODO: config, lock, flag regs */ + .unlock = spi_disable_blockprotect_n25q, /* TODO: per 64kB sector lock registers */ + .write = spi_chip_write_256, /* Multi I/O supported */ + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {2700, 3600}, + }, + + { + .vendor = "Micron/Numonyx/ST", .name = "N25Q032..1E", .bustype = BUS_SPI, .manufacture_id = ST_ID, diff --git a/flashchips.h b/flashchips.h index 9ffb30f..7dfe985 100644 --- a/flashchips.h +++ b/flashchips.h @@ -839,6 +839,8 @@ #define ST_MT28GU256___2 0x8904 #define ST_MT28GU512___1 0x887E #define ST_MT28GU512___2 0x8881 +/* The N25Q family is also used by Altera in its EPCQ series. */ +#define ST_N25Q016__3E 0xBA15 /* N25Q016, 3.0V, (uniform sectors expected) */ #define ST_N25Q016__1E 0xBB15 /* N25Q016, 1.8V, (uniform sectors expected) */ #define ST_N25Q032__3E 0xBA16 /* N25Q032, 3.0V, (uniform sectors expected) */ #define ST_N25Q032__1E 0xBB16 /* N25Q032, 1.8V, (uniform sectors expected) */ -- Kind regards, Stefan Tauner

2 1

Re: [flashrom] FYI: flashrom output for Altera EPCQ16
by 冰 29 Jul '16

29 Jul '16

this is a not surport spi flash，you can add it！！！！！！！ reference:https://www.flashrom.org/Development_Guidelines#Adding.2Freviewin… or this link in chinese: http://bbs.ickey.cn/community/forum.php?mod=viewthread&tid=64498 发自网易邮箱大师 On 07/29/2016 03:59, Ma, Peter wrote: Hi, Stefan... I just received a new set of boards with the Altera EPCQ16 that we discussed before. Something odd happened: I would use flashrom and it would do the usual "SFDP-capable chip" (2048 kB, SPI). But on subsequent tries (even after re-boots), flashrom is coming back with: Found ST flash chip "unknown ST SPI chip" (0 kB, SPI) Have any idea as to what could be going wrong? Here is the -VV output: # flashrom -VV -p linux_spi:dev=/dev/spidev0.0 flashrom v0.9.8-r1888 on Linux 4.7.0 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.5.1, GCC 6.1.0, little endian Command line (3 args): flashrom -VV -p linux_spi:dev=/dev/spidev0.0 Calibrating delay loop... OS timer resolution is 1 usecs, 444M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus = 10012 us, 4 myus = 4 us, OK. Initializing linux_spi programmer Using device /dev/spidev0.0 The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 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 0xba15 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 0xba15 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 0xba15 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 0xba15 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Unknown SFDP-capable chip, 0 kB: Signature = 0x45f434f5 (should be 0x50444653) No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Found ST flash chip "unknown ST SPI chip" (0 kB, SPI) on linux_spi. Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xff, id2 0xff Found ST flash chip "unknown ST SPI chip" (0 kB, 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. Regards, --------------------------------------------------------- Peter Ma | email: peter.ma(a)intel.com Senior Design Engineer | tel: +1 (604) 742 5778 Intel of Canada, Ltd. | fax: +1 (604) 639 1185 #688 – 1333 West Broadway, Vancouver, BC, Canada, V6H 4C1 _______________________________________________ flashrom mailing list flashrom(a)flashrom.org https://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] FYI: flashrom output for Altera EPCQ16
by Stefan Tauner 28 Jul '16

28 Jul '16

On Thu, 30 Jun 2016 17:21:54 +0000 "Ma, Peter" <peter.ma(a)intel.com> wrote: > I understand the not wanting to allow casual users to not accidentally mis-program their BIOS. But it does make flashrom not very useful for non-BIOS uses -- like programming FPGA bitstreams, etc. One more thing regarding that: the way to go in that case at least for now is to pad the payload data with 0xFF to reach the flash chip size (either in front or back of the payload depending on the application's need). Cf. https://www.flashrom.org/pipermail/flashrom/2013-October/011828.html -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

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

28 Jul '16

Hello Andrius, Could you please send a verbose log to the mailing list? If you run flashrom with additional argument "-o logfile.txt", that should do. Please have a look at the man page. :) You could also check out common problems (https://www.flashrom.org/Common_problems). Perhaps a write protection mode is in effect, which cannot be disabled on a software level? Is the WP# pin low? We could help you better with that log file. ;) Thank you :) Hatim On Tuesday 26 July 2016 10:05 PM, Andrius Montvydas wrote: > > hello, > > I had a bad bios flash, so i wanted to flash original bios using > flashrom but it failed. > I was using Raspberry Pi 3, bios chip is winbond W25Q64FW > > flashrom v0.9.9-r1954 on Linux 4.4.13-v7+ (armv7l) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on linux_spi. > Reading old flash chip contents... done. > Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, > Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000 > ERASE FAILED! > Reading current flash chip contents... done. Looking for another erase > function. > FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from > 0x00000000-0x00007fff: 0x8000 > ERASE FAILED! > Reading current flash chip contents... done. Looking for another erase > function. > FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from > 0x00000000-0x0000ffff: 0x10000 > ERASE FAILED! > Reading current flash chip contents... done. Looking for another erase > function. > FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from > 0x00000000-0x007fffff: 0x800000 > ERASE FAILED! > Reading current flash chip contents... done. Looking for another erase > function. > FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from > 0x00000000-0x007fffff: 0x800000 > ERASE FAILED! > Looking for another erase function. > No usable erase functions left. > FAILED! > Uh oh. Erase/write failed. Checking if anything has changed. > Reading current flash chip contents... done. > Apparently at least some data has changed. > Your flash chip is in an unknown state. > Please report this on IRC at chat.freenode.net > <http://chat.freenode.net> (channel #flashrom) or > mail flashrom(a)flashrom.org <mailto:flashrom@flashrom.org>, thanks! > pi@raspberrypi:~ $ > > Thank you for any information. > > -- > Andrius M. > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://www.flashrom.org/mailman/listinfo/flashrom >

1 0

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

28 Jul '16

Hello, This set of patches should be applied on top of the previous patches (https://www.flashrom.org/pipermail/flashrom/2016-July/014717.html). Continuing with the major points from the previous mail (linked above), this patch should bring support for new infrastructure to quite a few more chips. OTP models for Eon, GigaDevice and Winbond are supported now. AMIC, Macronix and Spansion OTP models are scheduled for the next revision. I admit that the CLI may not be worded in the most optimum way, but that was a conscious decision so that it could be sorted out while review. Thank you for your time. I am looking forward to your feedback and having a discussion. Hatim Kanchwala (4): WIP: Add support for status register and access protection infrastructure to more existing chips OTP/Security Register infrastructure WIP: Add support for OTP/Security Register infrastructure to existing chips Integrate OTP infrastructure and add CLI Makefile | 5 +- chipdrivers.h | 23 +++ cli_classic.c | 263 ++++++++++++++++++++++++++++++++-- cli_common.c | 54 +++---- flash.h | 25 +++- flashchips.c | 296 ++++++++++++++++++++++++-------------- flashrom.8.tmpl | 52 ++++++- otp.c | 381 +++++++++++++++++++++++++++++++++++++++++++++++++ otp.h | 39 +++++ otp_layouts.c | 229 +++++++++++++++++++++++++++++ spi.h | 20 +++ spi25.c | 73 ++++++++++ spi25_statusreg.h | 6 + statusreg_layouts.c | 58 +++++++- writeprotect.h | 13 +- writeprotect_layouts.c | 269 +++++++++++++++++++++++++++++++++- 16 files changed, 1645 insertions(+), 161 deletions(-) create mode 100644 otp.c create mode 100644 otp.h create mode 100644 otp_layouts.c -- 2.7.4

1 4

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

27 Jul '16

make sure that PIN WP and HOLD must pull up to vcc or use other spi flash test your circuit connect ok！！发自网易邮箱大师 On 07/27/2016 00:35, Andrius Montvydas wrote: hello, I had a bad bios flash, so i wanted to flash original bios using flashrom but it failed. I was using Raspberry Pi 3, bios chip is winbond W25Q64FW flashrom v0.9.9-r1954 on Linux 4.4.13-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x8000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0x10000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x800000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x800000 ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has changed. Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! pi@raspberrypi:~ $ Thank you for any information. -- Andrius M.

1 0

failed flash
by Andrius Montvydas 26 Jul '16

26 Jul '16

hello, I had a bad bios flash, so i wanted to flash original bios using flashrom but it failed. I was using Raspberry Pi 3, bios chip is winbond W25Q64FW flashrom v0.9.9-r1954 on Linux 4.4.13-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x8000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0x10000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x800000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x800000 ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has changed. Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! pi@raspberrypi:~ $ Thank you for any information. -- Andrius M.

1 0

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

24 Jul '16

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

1 0

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

24 Jul '16

Dear Flashrom Team, As the title suggest, I flashed my old Asus M2V with coreboot but now it doesn't boot anymore. I'm guessing it has more to do with the coreboot rom than with the flashing procedure but I'd like to know if you had an idea to what could have caused this failure ? To flash the MB I used the following command : $ sudo flashrom -p internal -w <mycorebootrom> It successfully flashed a chip (ST something) which is a removable chip on the motherboard. So with this success I decided to reboot the computer but then nothing, screen stays black, no beeping, no keyboard light, only the hard drive led stays on permanently What I tested : I unplugged everything, FDD, HDD, cdrom drive, usb internal connectors, I only let inside the graphic card (a PCI-E Nvidia GF 6600GT) and a stick of RAM I tested with another PCI-E Nvidia card (I don't have any other brand to test with) and with multiple combination of RAM sticks (1, 2 sticks, dual channel slots or not, 512 MB and 2 GB) Now the only thing I could try I guess is remove the ST chip and flash it with an external programmer ? I backed up the original MB rom before flashing. I hope you'll have an idea on what went wrong, if not my next stop will be the coreboot team :) Anyway thanks a lot for your great work ! Best regards, Pierre

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom