Hi Yves,
please keep the list in CC so they know what's going on. Thanks.
On 13.11.2008 18:51, Dupont Yves wrote:
here is the corresponding dump :
Calibrating delay loop... 326M loops per second, 100 myus = 193 us. OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000 GCS = 0x460: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1 (SPI) [...] SPI Read Configuration: prefetching disabled, caching enabled, OK. [...] Probing for Atmel AT25DF321, 4096 KB: Programming OPCODES... done RDID returned ff ff ff.
The flash chip doesn't support RDID.
RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff [...] Probing for ST M25P40-old, 512 KB: RDID returned ff ff ff. RES returned 13.
But the chip supports RES.
probe_spi_res: id 0x13 [....] No EEPROM/flash device found.
The big problem is that ~30 chips from different manufacturers with different sizes all have the same RES ID. I will try to cook up a patch checking REMS (which is more accurate).
It seems to bea SPI flash device but I don't want to open my laptop. Any idea?
I will create a patch to improve detection, but that may take a week or so. If you don't hear anything back from me in the next 7 days, please ask me for a status.
Regards, Carl-Daniel
Hi Carl-Daneil,
Thanks for your help, could you tell me what is REMS? regards,
Yves
2008/11/13 Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Hi Yves,
please keep the list in CC so they know what's going on. Thanks.
On 13.11.2008 18:51, Dupont Yves wrote:
here is the corresponding dump :
Calibrating delay loop... 326M loops per second, 100 myus = 193 us. OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000 GCS = 0x460: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1
(SPI)
[...] SPI Read Configuration: prefetching disabled, caching enabled, OK. [...] Probing for Atmel AT25DF321, 4096 KB: Programming OPCODES... done RDID returned ff ff ff.
The flash chip doesn't support RDID.
RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff [...] Probing for ST M25P40-old, 512 KB: RDID returned ff ff ff. RES returned 13.
But the chip supports RES.
probe_spi_res: id 0x13 [....] No EEPROM/flash device found.
The big problem is that ~30 chips from different manufacturers with different sizes all have the same RES ID. I will try to cook up a patch checking REMS (which is more accurate).
It seems to bea SPI flash device but I don't want to open my laptop. Any idea?
I will create a patch to improve detection, but that may take a week or so. If you don't hear anything back from me in the next 7 days, please ask me for a status.
Regards, Carl-Daniel
Hi Yves,
On 13.11.2008 20:14, Dupont Yves wrote:
Thanks for your help, could you tell me what is REMS?
Sure. There are three methods to get an ID from a SPI flash chip: - RDID: The standard JEDEC Read ID command, usually 3 bytes. - REMS: Read Electronic Manufacturer Signature, 2 bytes. - RES: Read Electronic Signature, 1 byte.
RDID and REMS tell you about the vendor, so it is rather easy to find out the real chip type. RES only gives you a one-byte identifier for the chip, but there is no way to find out the manufacturer.
Regards, Carl-Daniel
2008/11/13 Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net:
Hi Yves,
please keep the list in CC so they know what's going on. Thanks.
On 13.11.2008 18:51, Dupont Yves wrote:
here is the corresponding dump :
Calibrating delay loop... 326M loops per second, 100 myus = 193 us. OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000 GCS = 0x460: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1 (SPI) [...] SPI Read Configuration: prefetching disabled, caching enabled, OK. [...] Probing for Atmel AT25DF321, 4096 KB: Programming OPCODES... done RDID returned ff ff ff.
The flash chip doesn't support RDID.
RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff [...] Probing for ST M25P40-old, 512 KB: RDID returned ff ff ff. RES returned 13.
But the chip supports RES.
probe_spi_res: id 0x13 [....] No EEPROM/flash device found.
The big problem is that ~30 chips from different manufacturers with different sizes all have the same RES ID. I will try to cook up a patch checking REMS (which is more accurate).
It seems to bea SPI flash device but I don't want to open my laptop. Any idea?
I will create a patch to improve detection, but that may take a week or so. If you don't hear anything back from me in the next 7 days, please ask me for a status.
Regards, Carl-Daniel
Hi Carl-Daniel,
I still have troubles with the detection of my SPI flash. Here is the result of the dump:
Calibrating delay loop... 227M loops per second, 100 myus = 135 us. OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000 GCS = 0x460: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3020 0x00: 0x0004 (SPIS) 0x02: 0x4260 (SPIC) 0x04: 0x00000000 (SPIA) 0x08: 0xffffffff (SPID0) 0x0c: 0x00000000 (SPID0+4) 0x10: 0x00000000 (SPID1) 0x14: 0x00000000 (SPID1+4) 0x18: 0x00000000 (SPID2) 0x1c: 0x00000000 (SPID2+4) 0x20: 0x00000000 (SPID3) 0x24: 0x00000000 (SPID3+4) 0x28: 0x00000000 (SPID4) 0x2c: 0x00000000 (SPID4+4) 0x30: 0x00000000 (SPID5) 0x34: 0x00000000 (SPID5+4) 0x38: 0x00000000 (SPID6) 0x3c: 0x00000000 (SPID6+4) 0x40: 0x00000000 (SPID7) 0x44: 0x4a000000 (SPID7+4) 0x50: 0x00000000 (BBAR) 0x54: 0x0006 (PREOP) 0x56: 0x463b (OPTYPE) 0x58: 0x05d80302 (OPMENU) 0x5c: 0xc79f01ab (OPMENU+4) 0x60: 0x00000000 (PBR0) 0x64: 0x00000000 (PBR1) 0x68: 0x00000000 (PBR2) 0x6c: 0x00000000 (PBR3)
SPI Read Configuration: prefetching disabled, caching enabled, OK. Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0x4e, id2 0x41 Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0x4e, id2 0x41 Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for Atmel AT25DF021, 256 KB: Programming OPCODES... done RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF041A, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF081, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF161, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF321, 4096 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF321A, 4096 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF641, 8192 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25F512B, 64 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25FS010, 128 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25FS040, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF041, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF081A, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF161, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF161A, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26F004, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Atmel AT45CS1282, 16896 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB011D, 128 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB021D, 256 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB041D, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB081D, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB161D, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB321C, 4224 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB321D, 4096 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB642D, 8192 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for AMIC A25L40P, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0x46, id2 0xfc Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0x46, id2 0xfc Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0x4e, id2 0x41 Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0x4e, id2 0x50 Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0x4e, id2 0x50 Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x4e, id2 0x41 Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Macronix MX25L512, 64 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX25L1005, 128 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX25L2005, 256 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX25L4005, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX25L8005, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX25L1605, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX25L3205, 4096 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX25L6405, 8192 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0x46, id2 0xfc Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0x46, id2 0xfc Probing for Numonyx M25PE10, 128 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Numonyx M25PE20, 256 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Numonyx M25PE40, 256 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Numonyx M25PE80, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Numonyx M25PE16, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for PMC Pm25LV010, 128 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for PMC Pm25LV016B, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for PMC Pm25LV020, 256 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for PMC Pm25LV040, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for PMC Pm25LV080B, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for PMC Pm25LV512, 64 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff Probing for Spansion S25FL016A, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for SST SST25VF016B, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for SST SST25VF032B, 4096 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for SST SST25VF040B, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for SST SST25VF080B, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x4e, id2 0x41 Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0x0, id2 0x0, id1 parity violation Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0x7e, id2 0x37, id1 parity violation Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x4e, id2 0x41 Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M25P10-A, 128 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M25P20, 256 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M25P40, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M25P40-old, 512 KB: RDID returned ff ff ff. RES returned 13. probe_spi_res: id 0x13 Probing for ST M25P80, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M25P16, 2048 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M25P32, 4096 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M25P64, 8192 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M25P128, 16384 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0x4e, id2 0x41 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x4e, id2 0x50 Probing for ST M29W010B, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0x4e, id2 0x41 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0x4e, id2 0x41 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x46, id2 0xfc Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x4e, id2 0x41 Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Winbond W25x10, 128 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Winbond W25x20, 256 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Winbond W25x40, 512 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Winbond W25x80, 1024 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Winbond W29EE011, 128 KB: === Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. === Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0x4e, id2 0x41, id1 parity violation Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x4e, id2 0x41, id1 parity violation Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x46, id2 0xfc Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0xff, did 0xff Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: vid 0x4e, did 0x41 Probing for Atmel unknown Atmel SPI chip, 0 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for EON unknown EON SPI chip, 0 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix unknown Macronix SPI chip, 0 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for PMC unknown PMC SPI chip, 0 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for SST unknown SST SPI chip, 0 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for ST unknown ST SPI chip, 0 KB: RDID returned ff ff ff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff No EEPROM/flash device found. If you know which flash chip you have, and if this version of flashrom supports a similar flash chip, you can try to force read your chip. Run: flashrom -f -r -c similar_supported_flash_chip filename
Note: flashrom can never write when the flash chip isn't found automatically.
I don't known if you have enough time to create your patch. Thanks for your help. Regards,
Yves
Hi Yves,
sorry for not getting back to you earlier. We are still working out the best infrastructure to handle chips such as yours.
I hope to have something testable at the end of this week.
Regards, Carl-Daniel
-
Carl-Daniel Hailfinger -
Dupont Yves