Re: [flashrom] flashrom works with H67 Chip

[Stefan Tauner]

On Sat, 27 Aug 2011 23:39:18 -0500
Dr Lawrence M Fox  wrote:
> carlina@FOXBOX:~/Downloads/DOS$ sudo flashrom -w SH67H000.114
> flashrom v0.9.4-r1395 on Linux 2.6.38-11-generic (x86_64), built with libpci
> 3.1.7, GCC 4.5.2, little endian
> flashrom is free software, get the source code at http://www.flashrom.org
>
> Calibrating delay loop... OK.
> Found chipset "Intel H67".
> This chipset is marked as untested. If you are using an up-to-date version
> of flashrom please email a report to [e-mail] including a
> verbose (-V) log. Thank you!
> Enabling flash write... OK.
> This chipset supports the following protocols: FWH, SPI.
> Found Winbond flash chip "W25Q32" (4096 kB, SPI) at physical address
> 0xffc00000.
> Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Erase/write done.
> Verifying flash... VERIFIED.

Hello,

Thanks for your report!
I have marked the chipset as tested and will commit that later.
> carlina@FOXBOX:~/Downloads/DOS$ sudo flashrom -V -w SH67H000.114
> flashrom v0.9.4-r1395 on Linux 2.6.38-11-generic (x86_64), built with libpci
> 3.1.7, GCC 4.5.2, little endian
> flashrom is free software, get the source code at http://www.flashrom.org
>
> Calibrating delay loop... OS timer resolution is 1 usecs, 3360M loops per
> second, 10 myus = 10 us, 100 myus = 99 us, 1000 myus = 991 us, 10000 myus =
> 9922 us, 4 myus = 4 us, OK.
> Initializing internal programmer
> No coreboot table found.
> DMI string system-manufacturer: "Shuttle"
> DMI string system-product-name: "SH67H3"
> DMI string system-version: "1.0"
> DMI string baseboard-manufacturer: "Shuttle"
> DMI string baseboard-product-name: "FH67"
> DMI string baseboard-version: "1.0"
> DMI string chassis-type: "Desktop"

I have also added your mainboard (FH67) used in your barebone to our
list of supported boards, thank you.
> Found ITE Super I/O, ID 0x8772 on port 0x2e
> Found chipset "Intel H67" with PCI ID 8086:1c4a.
> This chipset is marked as untested. If you are using an up-to-date version
> of flashrom please email a report to [e-mail] including a
> verbose (-V) log. Thank you!
> Enabling flash write...
> […]
> Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2
> 0x4016
> Chip status register is 00
> Found Winbond flash chip "W25Q32" (4096 kB, SPI) at physical address
> 0xffc00000.
> […]
> Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef,
> id2 0x15
> Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Trying erase function 0...
> 0x000000-0x000fff:S, 0x001000-0x001fff:S, 0x002000-0x002fff:S,
> […]
> 0x3ff000-0x3fffff:S

all those :S tokens indicate that the erase+write cycle for this block
was skipped, because the content of the flash chip was equal to the
file. this is of course expected because you have written the same file
just before. i just mention it because this makes this log less
informative. writing it in verbose mode the first time, would have been
better for us. not a big deal though at all.
> Erase/write done.
> Verifying flash... VERIFIED.
> Restoring MMIO space at 0x7f3670ff48a0
> Restoring MMIO space at 0x7f3670ff489c
> Restoring MMIO space at 0x7f3670ff4898
> Restoring MMIO space at 0x7f3670ff4896
> Restoring MMIO space at 0x7f3670ff4894
> Restoring PCI config space for 00:1f:0 reg 0xdc