Easy projects: Difference between revisions
Hailfinger (talk | contribs) |
Hailfinger (talk | contribs) (→flashrom: Added timing info, new chips, testing) |
||
| Line 5: | Line 5: | ||
=[[flashrom]]= | =[[flashrom]]= | ||
A tool to read/write coreboot/BIOS images from/to flash chips. | A tool to read/write coreboot/BIOS images from/to flash chips. | ||
==Add timing info to flash chip definitions== | |||
Go through the list of flash chips in flashchips.c inside the flashrom source. For each chip (except SPI chips), read through the data sheets and add a comment to the flash chip definition which contains the timing information in microseconds(!) for the probe sequence. | |||
This will make probing a lot more reliable. | |||
Every annotated chip helps. | |||
==Add the bus type to flash chip definitions== | ==Add the bus type to flash chip definitions== | ||
Go through the list of flash chips in flashchips.c inside the flashrom source. Look for chip definitions which have .bustype = CHIP_BUSTYPE_NONSPI and look at their data sheets. Read the data sheets and try to figure out the flash bus they use (Parallel/LPC/FWH/SPI). Change the bustype field to CHIP_BUSTYPE_PARALLEL etc. and post a patch to the list. | Go through the list of flash chips in flashchips.c inside the flashrom source. Look for chip definitions which have .bustype = CHIP_BUSTYPE_NONSPI and look at their data sheets. Read the data sheets and try to figure out the flash bus they use (Parallel/LPC/FWH/SPI). Change the bustype field to CHIP_BUSTYPE_PARALLEL etc. and post a patch to the list. | ||
This will make probing faster and more reliable. | |||
Even a single updated chip helps. | Even a single updated chip helps. | ||
[[Flashrom#Communication_bus_protocol]] has a writeup on how to figure out the bus type. | [[Flashrom#Communication_bus_protocol]] has a writeup on how to figure out the bus type. | ||
==Add new flash chip definitions== | |||
We have a few dozen chip IDs listed in flash.h, but not in flashchips.c. Find them, dig up the data sheets and add chip definitions for them to flashchips.c. You can use similar flash chips as a guideline. | |||
This will reduce the number of undetected chips. | |||
Every added chip broadens flashrom support. | |||
==Test flashrom== | |||
If you have a desktop (no laptops/notebooks/netbooks), please run | |||
flashrom | |||
and check if it finds your flash chip. If it does and any of the operations are listed as unsupported, we'd like to hear about it. If your flash chip is not found, we'd like to hear about it as well. | |||
In both cases, please send the output of | |||
flashrom -V | |||
to the coreboot mailing list (preferred) or to flashrom@coreboot.org | |||
=coreboot= | =coreboot= | ||
Revision as of 20:22, 1 June 2009
You probably came here trying to find a small (minutes to hours) and easy task where you can get your hands dirty and get results immediately.
If you're a coreboot or flashrom newbie, this page is for you.
flashrom
A tool to read/write coreboot/BIOS images from/to flash chips.
Add timing info to flash chip definitions
Go through the list of flash chips in flashchips.c inside the flashrom source. For each chip (except SPI chips), read through the data sheets and add a comment to the flash chip definition which contains the timing information in microseconds(!) for the probe sequence.
This will make probing a lot more reliable.
Every annotated chip helps.
Add the bus type to flash chip definitions
Go through the list of flash chips in flashchips.c inside the flashrom source. Look for chip definitions which have .bustype = CHIP_BUSTYPE_NONSPI and look at their data sheets. Read the data sheets and try to figure out the flash bus they use (Parallel/LPC/FWH/SPI). Change the bustype field to CHIP_BUSTYPE_PARALLEL etc. and post a patch to the list.
This will make probing faster and more reliable.
Even a single updated chip helps.
Flashrom#Communication_bus_protocol has a writeup on how to figure out the bus type.
Add new flash chip definitions
We have a few dozen chip IDs listed in flash.h, but not in flashchips.c. Find them, dig up the data sheets and add chip definitions for them to flashchips.c. You can use similar flash chips as a guideline.
This will reduce the number of undetected chips.
Every added chip broadens flashrom support.
Test flashrom
If you have a desktop (no laptops/notebooks/netbooks), please run
flashrom
and check if it finds your flash chip. If it does and any of the operations are listed as unsupported, we'd like to hear about it. If your flash chip is not found, we'd like to hear about it as well.
In both cases, please send the output of
flashrom -V
to the coreboot mailing list (preferred) or to flashrom@coreboot.org
coreboot
I'll skip explaining what coreboot is. The whole wiki is about this topic and I can't summarize it in one sentence.
coreboot v2
The workhorse version of coreboot. Lots of supported boards, but difficult to work with.
TODO: Add easy tasks here.
coreboot v3
The next generation version of coreboot. Few supported boards, still in the design testing phase, easy to work with.
TODO: Add easy tasks here.