[flashrom] SST25VF016B flash chip is not respondin in INTEL EP80579 PROCESSOR using Flashrom utility

[sougata barik]

Hi,

   I am unable to use flashrom utility in my system. I am using EP80579
processor by Intel ans having one flashchip SST25VF061B which is
connected to the processor by SPI interface.
  

> [root at localhost flashrom-0.9.0]# ./flashrom -V
> Calibrating delay loop... 339M loops per second, 100 myus = 198 us. OK.
> No coreboot table found.
> Found chipset "Intel EP80579", enabling flash write... 
> BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
> 
> Root Complex Register Block address = 0xfed1c000
> GCS = 0xd70260: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x0 (SPI)
> Top Swap : not enabled
> SPIBAR = 0xfed1c000 + 0x3020
> 0x00: 0x800c     (SPIS)
> 0x02: 0x4140     (SPIC)
> 0x04: 0x00000000 (SPIA)
> 0x08: 0x0000411c (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: 0x00000000 (SPID7+4)
> 0x50: 0x00e00000 (BBAR)
> 0x54: 0x5006     (PREOP)
> 0x56: 0x163b     (OPTYPE)
> 0x58: 0x05200302 (OPMENU)
> 0x5c: 0x00016090 (OPMENU+4)
> 0x60: 0x00000000 (PBR0)
> 0x64: 0x00000000 (PBR1)
> 0x68: 0x00000000 (PBR2)
> 0x6c: 0x00000000 (PBR3)
> 
> WARNING: SPI Configuration Lockdown activated.
> Generating OPCODES... done
> SPI Read Configuration: prefetching disabled, caching enabled, OK.
> Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0x00, id2 0x00
> Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for AMD Am29F080B, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for Atmel AT25DF021, 256 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25DF041A, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25DF081, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25DF161, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25DF321, 4096 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25DF321A, 4096 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25DF641, 8192 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25F512B, 64 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25FS010, 128 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT25FS040, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT26DF041, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT26DF081A, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT26DF161, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT26DF161A, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT26F004, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for Atmel AT45CS1282, 16896 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT45DB011D, 128 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT45DB021D, 256 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT45DB041D, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT45DB081D, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT45DB161D, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT45DB321C, 4224 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT45DB321D, 4096 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT45DB642D, 8192 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for AMIC A25L40P, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0x00, id2 0x00
> Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0x00, id2 0x00
> Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff
> Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff
> Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for Macronix MX25L512, 64 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L1005, 128 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L2005, 256 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L4005, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L8005, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L1605, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L1635D, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L3205, 4096 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L3235D, 4096 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L6405, 8192 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX25L12805, 16384 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0x00, id2 0x00
> Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0x00, id2 0x00
> Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0xff, id2 0xff
> Probing for Numonyx M25PE10, 128 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Numonyx M25PE20, 256 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Numonyx M25PE40, 256 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Numonyx M25PE80, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Numonyx M25PE16, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for PMC Pm25LV010, 128 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for PMC Pm25LV016B, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for PMC Pm25LV020, 256 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for PMC Pm25LV040, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for PMC Pm25LV080B, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for PMC Pm25LV512, 64 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff
> Probing for Spansion S25FL016A, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for SST SST25VF016B, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for SST SST25VF032B, 4096 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for SST SST25VF040B, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for SST SST25VF040.REMS, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for SST SST25VF040B.REMS, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for SST SST25VF080B, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0xff, id2 0xff
> Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xea, id2 0xd0
> Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xea, id2 0xd0
> Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xea, id2 0xd0
> Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0x0b, id2 0x72
> Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xea, id2 0xd0
> Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> 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 0x00, id2 0x00
> Probing for SST SST49LF020, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, 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 0x00, id2 0x00
> Probing for ST M25P05-A, 64 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M25P10-A, 128 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M25P20, 256 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M25P40, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M25P40-old, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Invalid OPCODE 0xab
> Probing for ST M25P80, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M25P16, 2048 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M25P32, 4096 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M25P64, 8192 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M25P128, 16384 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff
> Probing for ST M29W010B, 128 KB: probe_jedec: id1 0xea, id2 0xd0
> Probing for ST M29W040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff
> Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff
> 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 0x00, id2 0x00
> Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0x00, id2 0x00
> Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0xea, id2 0xd0
> Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for Winbond W25x10, 128 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Winbond W25x20, 256 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Winbond W25x40, 512 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Winbond W25x80, 1024 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0xea, id2 0xd0
> Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xff, id2 0xff, 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 0xff, id2 0xff, id1 parity violation
> Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
> Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0xff, id2 0xff, id1 parity violation
> Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xff, id2 0xff, 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 0x00, id2 0x00, id1 parity violation
> Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x00, id2 0x00, id1 parity violation
> 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 0xff, did 0xff
> Probing for Atmel unknown Atmel SPI chip, 0 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for EON unknown EON SPI chip, 0 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for Macronix unknown Macronix SPI chip, 0 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for PMC unknown PMC SPI chip, 0 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for SST unknown SST SPI chip, 0 KB: Transaction error!
> run OPCODE 0x90 failed
> Probing for ST unknown ST SPI chip, 0 KB: Transaction error!
> run OPCODE 0x90 failed
> 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.
> [root at localhost flashrom-0.9.0]# 
> 






> [root at localhost flashrom-0.9.0]# ./flashrom 
> Calibrating delay loop... OK.
> No coreboot table found.
> Found chipset "Intel EP80579", enabling flash write... WARNING: SPI Configuration Lockdown activated.
> OK.
> 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.
> [root at localhost flashrom-0.9.0]# 
please tell me what should I change to work this utility.


Regards

Sougata


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com