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 The motherboard has the 6321ESB chipset which is listed as supported on the 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 have pasted the flashrom -V output here: http://pastebin.com/Rr24eXa5 Thanks for your help! --Sean On Wed, Mar 19, 2014 at 12:18 PM, Sean Everson <[email protected]> wrote: > 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 > > > The box contains the 6321ESB chipset which is listed as supported on the > 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.bin > > flashrom 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 > > > flashrom was built with libpci 3.2.1, GCC 4.7.1, little endian > > Command line (5 args): ./flashrom -V -p internal -r /tmp/bios.bin > > Calibrating 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 programmer > > No 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 > > [email protected] with W836xx: your board name: flashrom -V > > as 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: 0x0 > > 0xfff00000/0xffb00000 FWH IDSEL: 0x0 > > 0xffe80000/0xffa80000 FWH IDSEL: 0x0 > > 0xffe00000/0xffa00000 FWH IDSEL: 0x0 > > 0xffd80000/0xff980000 FWH IDSEL: 0x0 > > 0xffd00000/0xff900000 FWH IDSEL: 0x0 > > 0xffc80000/0xff880000 FWH IDSEL: 0x0 > > 0xffc00000/0xff800000 FWH IDSEL: 0x0 > > 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 disabled > > 0xff600000/0xff200000 FWH decode disabled > > 0xff500000/0xff100000 FWH decode disabled > > 0xff400000/0xff000000 FWH decode disabled > > Maximum FWH chip size: 0x400000 bytesSPI Read Configuration: prefetching > disabled, caching enabled, > > BIOS_CNTL = 0x03: BIOS Lock Enable: enabled, BIOS Write Enable: enabled > > Warning: 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 content > > Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is > normal flash content, id2 is normal flash content > > Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xea, id2 0xd0, > id1 is normal flash content, id2 is normal flash content > > Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x9b, id2 0x0c, > id1 is normal flash content, id2 is normal flash content > > Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xea, id2 > 0xd0, id1 is normal flash content, id2 is normal flash content > > Probing 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 > content > > Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x9b, id2 > 0x0c, id1 is normal flash content, id2 is normal flash content > > Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 > is normal flash content, id2 is normal flash content > > Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xc9, id2 > 0x78, id1 parity violation, id1 is normal flash content, id2 is normal flash > content > > Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is > normal flash content, id2 is normal flash content > > Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is > normal flash content, id2 is normal flash content > > Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is > normal flash content, id2 is normal flash content > > Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is > normal flash content, id2 is normal flash content > > Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x9b, id2 > 0x0c, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x9b, id2 > 0x0c, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x9b, id2 > 0x0c, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xea, id2 > 0xd0, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xc9, id2 > 0x78, id1 parity violation, id1 is normal flash content, id2 is normal flash > content > > Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 > 0x9b, id2 0x0c, id1 is normal flash content, id2 is normal flash content > > No 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 > > _______________________________________________ flashrom mailing list [email protected] http://www.flashrom.org/mailman/listinfo/flashrom
