e5b44ab4dc
probe/read/erase/write. That is incorrect. A bit of confusion comes from how the #defines are named. We call them TEST_BAD_*, but the message printed by flashrom says: "This flash part has status NOT WORKING for operations:" Something that is unimplemented is definitely not working. Neither of the chip entries mentioned above has erase or write functions implemented, so erase and write are not working. Since their size is unknown, we can't read them in. That means read is not working as well. Probing is a different matter. If a chip-specific probe function had matched, we wouldn't have to handle the chip with the "unknown xy SPI chip" fallback. I'm tempted to call that "not working" as well, but I'm open to discussion on this point. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by: Uwe Hermann <uwe@hermann-uwe.de> git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4177 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1 |
||
---|---|---|
.. | ||
82802ab.c | ||
am29f040b.c | ||
board_enable.c | ||
cbtable.c | ||
chipset_enable.c | ||
COPYING | ||
coreboot_tables.h | ||
en29f002a.c | ||
flash.h | ||
flashchips.c | ||
flashrom.8 | ||
flashrom.c | ||
ichspi.c | ||
it87spi.c | ||
jedec.c | ||
layout.c | ||
m29f002.c | ||
m29f400bt.c | ||
Makefile | ||
mx29f002.c | ||
physmap.c | ||
pm49fl00x.c | ||
README | ||
sb600spi.c | ||
sharplhf00l04.c | ||
spi.c | ||
spi.h | ||
sst28sf040.c | ||
sst39sf020.c | ||
sst49lf040.c | ||
sst49lfxxxc.c | ||
sst_fwhub.c | ||
stm50flw0x0x.c | ||
udelay.c | ||
w29ee011.c | ||
w39v040c.c | ||
w39v080fa.c | ||
w49f002u.c | ||
wbsio_spi.c |
------------------------------------------------------------------------------- flashrom README ------------------------------------------------------------------------------- flashrom is a utility for reading, writing, and erasing flash ROM chips. It's often used to flash BIOS/coreboot/firmware images. It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash, or SPI. (see http://coreboot.org for details on coreboot) Build Requirements ------------------ To build the flashrom utility you need to install the following packages: * pciutils * pciutils-devel / pciutils-dev / libpci-dev * zlib-devel / zlib1g-dev Usage ----- $ flashrom [-rwvEVfLhR] [-c chipname] [-s exclude_start] [-e exclude_end] [-m [vendor:]part] [-l file.layout] [-i imagename] [file] -r | --read: read flash and save into file -w | --write: write file into flash (default when file is specified) -v | --verify: verify flash against file -E | --erase: erase flash device -V | --verbose: more verbose output -c | --chip <chipname>: probe only for specified flash chip -s | --estart <addr>: exclude start position -e | --eend <addr>: exclude end postion -m | --mainboard <[vendor:]part>: override mainboard settings -f | --force: force write without checking image -l | --layout <file.layout>: read rom layout from file -i | --image <name>: only flash image name from flash layout -L | --list-supported: print supported devices -h | --help: print this help text -R | --version: print the version (release) If no file is specified, then all that happens is that flash info is dumped and the flash chip is set to writable. Exit status ----------- flashrom exits with 0 on success, 1 on most failures but with 2 if /dev/mem (/dev/xsvc on Solaris) can not be opened and with 3 if a call to mmap() fails. coreboot Table and Mainboard Identification -------------------------------------------- flashrom reads the coreboot table to determine the current mainboard. If no coreboot table could be read or if you want to override these values, you can specify -m, e.g.: $ flashrom -w --mainboard AGAMI:ARUMA agami_aruma.rom See the 'Supported mainboards' section in the output of 'flashrom -L' for a list of boards which require the specification of the board name, if no coreboot table is found. ROM Layout Support ------------------ flashrom supports ROM layouts. This allows you to flash certain parts of the flash chip only. A ROM layout file looks like follows: 00000000:00008fff gfxrom 00009000:0003ffff normal 00040000:0007ffff fallback i.e.: startaddr:endaddr name All addresses are offsets within the file, not absolute addresses! If you only want to update the normal image in a ROM you can say: flashrom -w --layout rom.layout --image normal agami_aruma.rom To update normal and fallback but leave the VGA BIOS alone, say: flashrom -w -l rom.layout -i normal -i fallback agami_aruma.rom Currently overlapping sections are not supported. ROM layouts should replace the -s and -e option since they are more flexible and they should lead to a ROM update file format with the ROM layout and the ROM image in one file (cpio, zip or something?). Supported Flash Chips / Chipsets / Mainboards --------------------------------------------- Please check the output of 'flashrom -L' for the list of supported flash chips, chipsets/southbridges, and mainboards. See also http://coreboot.org/Flashrom for more details.