Hi Jürgen,
I remember a similar case where flashrom was unable to write, and that
board also had a second chipset match. We might have the same issue
here: To PCI devices with the same ID, one acts as southbridge and the
other one is unused. We might enable the wrong one here and might have
to refine detection a bit. OTOH, a flash chip is detected, so we know
that write was enabled on the address space mapped to the flash chip
(but that write enable might have not been done by flashrom).
Am 26.02.2012 20:38 schrieb Jürgen Trapp:
> ubuntu@ubuntu:~/coreboot$ sudo flashrom -VV
> flashrom v0.9.5.1-r1508 on Linux 3.0.0-12-generic (i686), built with libpci 3.1.7, GCC 4.6.1, little endian
> flashrom is free software, get the source code at http://www.flashrom.org
>
> Calibrating delay loop... OS timer resolution is 4001 usecs, 1093M loops per second, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 0 us, 10000 myus = 8001 us, 16004 myus = 16001 us, OK.
> Initializing internal programmer
> No coreboot table found.
> DMI string system-manufacturer: "Hewlett-Packard"
> DMI string system-product-name: "HP xw9300 Workstation"
> DMI string system-version: " "
> DMI string baseboard-manufacturer: "Hewlett-Packard"
> DMI string baseboard-product-name: "09C4h"
> DMI string baseboard-version: "Not Specified"
> DMI string chassis-type: "Mini Tower"
> Found chipset "NVIDIA CK804" with PCI ID 10de:0051. Enabling flash write... OK.
> WARNING: unexpected second chipset match: "NVIDIA CK804"
Side note: We should print the PCI ID for the second chipset match as well.
> ignoring, please report lspci and board URL to flashrom(a)flashrom.org
> with 'CHIPSET: your board name' in the subject line.
> The following protocols are supported: Non-SPI.
> Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0x65, id2 0xd0, id1 parity violation, id1 is normal flash content, id2 is normal flash content
> [...]
Could you run the following command as root and post the results?
lspci -nnvvxxx
That should help us determine which one of the CK804 southbridges we
should enable.
However, it is possible that we enabled the right southbridge due to
pure luck and there is a separate write protection (jumper or solder
bridge or something controllable in software). If that is the case,
somebody has to find out how to enable writes by reverse engineering or
by looking at the docs if the docs are good.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
Hi,
i have a problem with flash writing under HP XW9300.
I will use coreboot.rom with the board and i have a error (see attachments: output_flashrom_write)
Thank you for help.
Jürgen
Increase flashrom release number to 0.9.5.1
Informal ack by Stefan Tauner on IRC:
01:03 <stefanct> with the kfreebsd patch in, 0.9.5.1 is acked by me
too in case i am not around tomorrow...
Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net>
Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at>
Index: flashrom-0.9.5.1-release/Makefile
===================================================================
--- flashrom-0.9.5.1-release/Makefile (Revision 1507)
+++ flashrom-0.9.5.1-release/Makefile (Arbeitskopie)
@@ -277,7 +277,7 @@
# will not require subversion. The downloadable snapshots are already exported.
SVNVERSION := $(shell LC_ALL=C svnversion -cn . 2>/dev/null | sed -e "s/.*://" -e "s/\([0-9]*\).*/\1/" | grep "[0-9]" || LC_ALL=C svn info . 2>/dev/null | awk '/^Revision:/ {print $$2 }' | grep "[0-9]" || LC_ALL=C git svn info . 2>/dev/null | awk '/^Revision:/ {print $$2 }' | grep "[0-9]" || echo unknown)
-RELEASE := 0.9.5
+RELEASE := 0.9.5.1
VERSION := $(RELEASE)-r$(SVNVERSION)
RELEASENAME ?= $(VERSION)
--
http://www.hailfinger.org/