I ran flashrom on an asus P4P800-VM motherboard and got this error:
tux tmp # flashrom -w P4PVM1018.rom
No coreboot table found.
Found chipset "Intel ICH5/ICH5R", enabling flash write... OK.
This chipset supports the following protocols: Non-SPI.
Calibrating delay loop... OK.
Found chip "SST SST49LF004A/B" (512 KB, FWH) at physical address
Flash image seems to be a legacy BIOS. Disabling checks.
Writing flash chip... ERASE FAILED at 0x00007810! Expected=0xff,
Read=0x3c, failed byte count from 0x00000000-0x0000ffff: 0x8732
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net channel #flashrom or
DO NOT REBOOT OR POWEROFF!
Steve Herber herber(a)thing.com work: 206-221-7262
Software Engineer, UW Medicine, IT Services home: 425-454-2399
as I can see are you using one port of an FT2232H for the SPI programming. Unfortunatly for germans, the chip and the converter board is only aviable from Digikey. Is it also possible to only use full speed with FT232 or even low Speed and V-USB?
If high speed is necessary, can the program be changed that it works with http://www-user.tu-chemnitz.de/~heha/bastelecke/Rund%20um%20den%20PC/USB2LP… ?
Thank you in advance.
Werbung bitte nicht beachten:
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
A successful flash chip operation is closely related to a few factors
other than the flash chip - southbridge, embedded controller, special
enabling operation of a particular board and the flashrom revision. Shall
we include other related information in the chip status table? Let us
put aside how to store the table first.
Any idea of what algorithm and bytes to use to update the CRC/Checksum
in the flash image?
The mac address is stored in the image. I have written a script to
update the mac address and know where the CRC/Checksum is. I have tried
various algorithms (those supported by Hex Workshop- Checksum-8 and -16,
CRC-8 and -16, etc. w/1's and 2's complements) but am unable to
duplicate a known checksum.
Hardware is a Kontron ETX Express module, flashrom reports: 'Found
Chipset "Intel ICH8M-E" ...', 'Found chip "SST SST25VF016B" ...'
Thanks in advance,
[fullquote for flashrom(a)flashrom.org]
On 23.03.2010 22:58, RayeR wrote:
> >That is very strange. Do you have a log?
> >SB600 should work fine. Maybe the SPI chip is not
> >attached to the SB600 but instead to the SuperI/O.
> >Can you try
> >flashrom -p it87spi
> Yes here's it:
> C:\F>flashrom.exe -p it87spi
> flashrom v0.9.1-r933
> Error: Programmer initialization failed.
OK, so it is not ITE IT87.
> C:\F>flashrom.exe -V -r
> flashrom v0.9.1-r933
> No coreboot table found.
> DMI string system-manufacturer: "Dell Inc. "
> DMI string system-product-name: "OptiPlex 320 "
> DMI string system-version: "Not Specified"
> DMI string baseboard-manufacturer: "Dell Inc. "
> DMI string baseboard-product-name: "0CU395"
> DMI string baseboard-version: " "
> DMI string chassis-type: "Tower"
> Found chipset "AMD SB600", enabling flash write... SPI base address is
> at 0xd8000
> Error accessing SB600 SPI registers, 0x1000 bytes at 0x000d8000
> dpmi mmap failed: No such file or directory (ENOENT)
Ah yes. That's a limitation of the DOS port of flashrom.
Usually the SB600 SPI base address is near the top of the address space
(4 GB). On your board it is below 1 MB, and AFAIK Rudolf said that we
can't map any region below 1 MB as uncached due to CWSDPMI/DJGPP
If anyone has an idea how to overcome these limitations, we can fix
flashrom for this special case.
> See PCI device listing attached.
> >The W25x40 supports multiple erase commands,
> >and your chipset does not allow flashrom to use
> >the spi_block_erase_20 command. Flashrom notices
> >that this command failed and tries another erase command which works.
> >Yes, strange. Maybe that happens as side effect from DJGPP compilation?
> I don't know...
> >It should try only 2 times. If it tries more often,
> >we have to check the code (bug?). I think Rudolf(?) said that there
> >are problems if we try to run a CWSDPMI app (dmidecode) from another
> >CWSDPMI app (flashrom).
> >Does it work if dmidecode.exe is in the PATH?
> >Hm. DMIDECODE.EXE is a name with 9+3 letters. That can't work on old
> Yes it works with dmidecode in path but nobody told me that I need it.
> On my home PC I already have dmidecode for DOS in my utilities
> directory. The file name is not problem because of DJGPP is smart
> and do some file name translation. If there's no LFN support it
> tries to look for "dmidecod.exe" and when run on LFN enabled OS
> it will use "dmidecode.exe". But it's different LFN truncating
> mode than windows use ("dmidec~1.exe"). I don't know why but e.g.
> DJGPP PKUNZIP tool use filename truncate this way without ~.
> But it would be better to check if both version of name exist and
> display non-confusing error message when nothing found.
Michael? Is there a good way to handle this?