[flashrom] Intel S5000PAL: Flash Not Found

Sean Everson sean.everson at gmail.com
Wed Mar 19 17:18:00 CET 2014


*All,I have a number of Intel S5000PAL motherboards that I would like to
use FLASHROM to manage if at all possible.  According to the Intel Docs
at:http://download.intel.com/support/motherboards/server/s5000pal/sb/s5000pal_s5000xal_tps_r2_0.pdf
<http://download.intel.com/support/motherboards/server/s5000pal/sb/s5000pal_s5000xal_tps_r2_0.pdf>The
box contains the 6321ESB chipset which is listed as supported on the
flashrom.org <http://flashrom.org> wiki page.When I try to use FLASHROM to
read the flash I get an error message that the flash is not found.  Can
someone provide me with some guidance on what additional information or
steps I can take to investigate this further?I am including the output from
flashrom -V below.Thanks for your help!--Sean# ./flashrom -V -p internal -r
/tmp/bios.binflashrom v0.9.7-r1764 on Linux 2.6.32.24 (x86_64)flashrom is
free software, get the source code at http://www.flashrom.org
<http://www.flashrom.org>flashrom was built with libpci 3.2.1, GCC 4.7.1,
little endianCommand line (5 args): ./flashrom -V -p internal -r
/tmp/bios.binCalibrating delay loop... OS timer resolution is 1 usecs,
2824M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999
us, 10000 myus = 10025 us, 4 myus = 4 us, OK.Initializing internal
programmerNo coreboot table found.Using Internal DMI decoder.DMI string
chassis-type: "Rack Mount Chassis"DMI string system-manufacturer:
"Intel"DMI string system-product-name: "T5000PAL"DMI string system-version:
"Not Specified"DMI string baseboard-manufacturer: "Intel"DMI string
baseboard-product-name: "T5000PAL0 "DMI string baseboard-version: "FRU Ver
0.05"W836xx enter config mode worked or we were already in config mode.
W836xx leave config mode had no effect.Active config mode, unknown reg 0x20
ID: f2.Please send the output of "flashrom -V" to flashrom at flashrom.org
<flashrom at flashrom.org> with W836xx: your board name: flashrom -Vas the
subject to help us finish support for your Super I/O. Thanks.Found chipset
"Intel 631xESB/632xESB/3100" with PCI ID 8086:2670. Enabling flash write...
0xfff80000/0xffb80000 FWH IDSEL: 0x00xfff00000/0xffb00000 FWH IDSEL:
0x00xffe80000/0xffa80000 FWH IDSEL: 0x00xffe00000/0xffa00000 FWH IDSEL:
0x00xffd80000/0xff980000 FWH IDSEL: 0x00xffd00000/0xff900000 FWH IDSEL:
0x00xffc80000/0xff880000 FWH IDSEL: 0x00xffc00000/0xff800000 FWH IDSEL:
0x00xff700000/0xff300000 FWH IDSEL: 0x40xff600000/0xff200000 FWH IDSEL:
0x50xff500000/0xff100000 FWH IDSEL: 0x60xff400000/0xff000000 FWH IDSEL:
0x70xfff80000/0xffb80000 FWH decode enabled0xfff00000/0xffb00000 FWH decode
enabled0xffe80000/0xffa80000 FWH decode enabled0xffe00000/0xffa00000 FWH
decode enabled0xffd80000/0xff980000 FWH decode enabled0xffd00000/0xff900000
FWH decode enabled0xffc80000/0xff880000 FWH decode
enabled0xffc00000/0xff800000 FWH decode enabled0xff700000/0xff300000 FWH
decode disabled0xff600000/0xff200000 FWH decode
disabled0xff500000/0xff100000 FWH decode disabled0xff400000/0xff000000 FWH
decode disabledMaximum FWH chip size: 0x400000 bytesSPI Read Configuration:
prefetching disabled, caching enabled, BIOS_CNTL = 0x03: BIOS Lock Enable:
enabled, BIOS Write Enable: enabledWarning: Setting Bios Control at 0xdc
from 0x02 to 0x01 failed.New value is 0x03.OK.The following protocols are
supported: FWH.Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1
0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash
contentProbing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x9b, id2
0x0c, id1 is normal flash content, id2 is normal flash contentProbing for
Intel 82802AC, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 parity
violation, id1 is normal flash content, id2 is normal flash contentProbing
for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is
normal flash content, id2 is normal flash contentProbing for PMC Pm49FL004,
512 kB: probe_jedec_common: id1 0x9b, id2 0x0c, id1 is normal flash
content, id2 is normal flash contentProbing for Sharp LHF00L04, 1024 kB:
probe_82802ab: id1 0xc9, id2 0x78, id1 parity violation, id1 is normal
flash content, id2 is normal flash contentProbing for SST SST49LF002A/B,
256 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash
content, id2 is normal flash contentProbing for SST SST49LF003A/B, 384 kB:
probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash contentProbing for SST SST49LF004A/B,
512 kB: probe_jedec_common: id1 0x9b, id2 0x0c, id1 is normal flash
content, id2 is normal flash contentProbing for SST SST49LF004C, 512 kB:
probe_82802ab: id1 0x9b, id2 0x0c, id1 is normal flash content, id2 is
normal flash contentProbing for SST SST49LF008A, 1024 kB:
probe_jedec_common: id1 0xc9, id2 0x78, id1 parity violation, id1 is normal
flash content, id2 is normal flash contentProbing for SST SST49LF008C, 1024
kB: probe_82802ab: id1 0xc9, id2 0x78, id1 parity violation, id1 is normal
flash content, id2 is normal flash contentProbing for SST SST49LF016C, 2048
kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal
flash content, id2 is normal flash contentProbing for ST M50FLW040A, 512
kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is normal flash content, id2 is
normal flash contentProbing for ST M50FLW040B, 512 kB: probe_82802ab: id1
0x9b, id2 0x0c, id1 is normal flash content, id2 is normal flash
contentProbing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xc9, id2
0x78, id1 parity violation, id1 is normal flash content, id2 is normal
flash contentProbing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xc9,
id2 0x78, id1 parity violation, id1 is normal flash content, id2 is normal
flash contentProbing for ST M50FW002, 256 kB: probe_82802ab: id1 0xea, id2
0xd0, id1 is normal flash content, id2 is normal flash contentProbing for
ST M50FW016, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity
violation, id1 is normal flash content, id2 is normal flash contentProbing
for ST M50FW040, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is normal
flash content, id2 is normal flash contentProbing for ST M50FW080, 1024 kB:
probe_82802ab: id1 0xc9, id2 0x78, id1 parity violation, id1 is normal
flash content, id2 is normal flash contentProbing for Winbond W39V040FA,
512 kB: probe_jedec_common: id1 0x9b, id2 0x0c, id1 is normal flash
content, id2 is normal flash contentProbing for Winbond W39V040FB, 512 kB:
probe_jedec_common: id1 0x9b, id2 0x0c, id1 is normal flash content, id2 is
normal flash contentProbing for Winbond W39V040FC, 512 kB:
probe_jedec_common: id1 0x9b, id2 0x0c, id1 is normal flash content, id2 is
normal flash contentProbing for Winbond W49V002FA, 256 kB:
probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is
normal flash contentProbing for Winbond W39V080FA, 1024 kB:
probe_jedec_common: id1 0xc9, id2 0x78, id1 parity violation, id1 is normal
flash content, id2 is normal flash contentProbing for Winbond W39V080FA
(dual mode), 512 kB: probe_jedec_common: id1 0x9b, id2 0x0c, id1 is normal
flash content, id2 is normal flash contentNo EEPROM/flash device
found.Note: flashrom can never write if the flash chip isn't found
automatically.Restoring PCI config space for 00:1f:0 reg 0xdc*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.flashrom.org/pipermail/flashrom/attachments/20140319/c63f4f9a/attachment.html>


More information about the flashrom mailing list