FGARWikiMain Page | About | Help | FAQ | Special pages | Log in

Printable version | Disclaimers | Privacy policy

Testing Flashrom

From FGARWiki

Contents

Testing Flashrom

All of these directions are meant for being followed in a terminal.

on Ubuntu, open Applications->Accessories->Terminal

Installing Flashrom

If you are loading this from Ubuntu the first time, use the following code.

If this is the second time loading flashrom and you are seeking to fix any problems with the newest version, download the newest version from the flashrom official page [1] sand extract to the home directory.

Open up a command line terminal. Input

Next type

If there are problems, try inputting

Then open the directory where the new version built in and check the version to double check.

Checking for Flashrom Support

run flashrom, with no arguments to get a report of the support level the chipset in this machine has.

you're looking for:

Oddities

different parts have various levels of support in flashrom. if the chip you're using has operations that have been untested, you will see a large warning, in between some "triple equals" lines.

If ERASE is not yet verified

Run through the below operations, then performs the steps for reporting results back to flashrom.

If WRITE is not yet verified

Run through the below operations, then performs the steps for reporting results back to flash

Reading the ROM Contents

Verifying the read operation worked

First, lets make sure read created a file, and that it has a non-zero length.

this should show a non-zero size in the first column (size of the rom in kilobytes), and the nakme of the rom file in the second column, like such:

256 romfile.bin

Next lets read through the romfile.out to see if theres any strings we recognize as being 'obviously part of a bios'.

Just look through this for obvious bios strings, such as support for floppies, or boot sector stuff.

Erasing a ROM

WARNING: this clears the rom's contents, and if a board reboots after this, it will come up blank, if you do not write a new rom to it. THIS CAN DESTROY BOARDS!

Verifying an Erase

First, we need to read the now empty rom contents to a file, and verify that it is indeed empty.

To read the empty rom contents to a file:

To verify the read generated a file:

To search for strings in this empty rom:

This last step should generate no output. If it does, something has gone horribly wrong.

Writing the Contents back to the Flash


This should produce a lot of output, ending in 'SUCCESS' 'verifying flash... VERIFIED', and 'COMPLETE'. if you don't see those three phrases, again, something has gone horribly wrong.

Preparing Results for Flashrom

Flashrom needs the output of three commands run as root, and saved. they are:

Collecting flashrom -V output

to collect the output of most unix commands, we merely have to redirect the output to a file, with the greater than symbol, so run:

This should create a file in your local directory called flashrom-V.out. to verify it is not empty:

Collecting lspci output

lspci is the utility that lists the PCI devices in your lachine (or AGP, or pci-x-133, or PCI-E, or...)

to collect its output, run the following command:

Again, to verify the command generated a non-empty file, we'll use du.

Collecting superiotool output

superiotool is not installed by default. to install it:

after installation, run superiotool, again saving the output using file redirection.

Collecting Oddities

If you were told to by the warning presented by flashrom's output, you may need to collect the output of a flashrom command.

Erase

If the erase command needs to be logged, re-verify you have a valid romfile.out, then run the erase in verbose mode, verify the erase, and re-install the rom contents.

To log the Erase Command:

To Restore the flashrom's contents:


Write

If the write command needs to be logged, re-verify you have a valid romfile.out, then run the write in verbose mode, verify the written data.

To log the Write Command:

submitting results to flashrom

we need to submit any of the data collected to paste.flashrom.org, then submit the returned addresses to flashrom@flashrom.org.

First, open up all the above collected data files in gedit. from there, we're going to cut and paste the contents into the page at paste.flashrom.org

To open up in gedit:

  gedit superiotool-deV.out lspci.out flashrom-V.out
  gedit superiotool-deV.out lspci.out flashrom-EV.out flashrom-V.out
  gedit superiotool-deV.out lspci.out flashrom-Vw.out flashrom-V.out
  gedit superiotool-deV.out lspci.out flashrom-Vw.out flashrom-V.out flashrom-EV.out


Then cut and paste each of these files with a brief description before it into the 'Program Output' pane. then hit the 'browse' button next to 'File Name', and select the 'romfile.out' rom image.

send these IDs to flashrom@flashrom.org

Retrieved from "http://wiki.freegeekarkansas.org/fgar/Testing_Flashrom"

This page has been accessed 1,186 times. This page was last modified on 13 January 2012, at 21:07. Content is available under Attribution-Share Alike 3.0 Unported.


Find

Browse
Main Page
Community portal
Current events
Recent changes
Random page
Help
Edit
View source
Editing help
This page
Discuss this page
New section
Printable version
Context
Page history
What links here
Related changes
My pages
Log in / create account
Special pages
New pages
File list
Statistics
More…