|(38 intermediate revisions by 5 users not shown)|
The flashrom project will hopefully participate in GSoC 2013 under the patronage of [http://coreboot.org/GSoC coreboot's GSoC administration]. Depending on the number and quality of applications (for both projects) and available mentors, there will be usually one or two slots for flashrom projects. Most of the information on their site is also valid for flashrom students, please read them.
If you want to apply, it is probably a good idea to subscribe to our [ [Mailinglist|mailing list]] look at our page with [[easy projects]]. You can show us that you are able to work with our codebase and/ or read datasheets by solving some of the problems noted there. It is a good idea to talk to us before you start though (list items may be outdated or worked on by someone else already for example).
is [./of the is .
The list below is an idea collection. Individual list items may be too simple to serve as complete GSoC task on their own, but they are grouped to reasonable tasks. If you're interested, please talk to us on the [[ Mailinglist|flashrom mailing list]] and/or on IRC irc:// irc. freenode. net/ #flashrom
are to [://../
= libflashrom - Multiple UIs for flashrom =
for a [://..////?=].
libflashrom is the name for the part of flashrom's code that forms its core and should eventually be independent from any user interface. This allows easy creation of user interfaces and integration to existing applications. There exists a patch set implementing this idea by [ http:// patchwork. coreboot. org/ project/ flashrom/ list/? submitter= 3002 Nico Huber] already, but it was not reviewed yet. It would certainly be a good starting point for anyone looking into this project.
In general implementing this idea requires the following steps:
* code cleanup (e.g. removal of stray exit() calls and returning proper error codes instead)
* API design and implementation
*: It is not enough to just separate the code from the existing user interface. There must also be added some glue code so that the separate parts can be developed independently. For example there has to be a generic way to query programmer modules for their available options so that UI code can present them to the user without knowing about that specific programmer before. You can find a few thoughts at [[libflashrom]].
It is probably a good idea to work in parallel on a user interface so that you become aware of problems and missing API bits. It is also an easy way to evaluate your work. If we see that your UI code can work independent of the libflashrom code in the way it should while providing the interaction possibilities we deem useful, you have been definitely successful.
in a , have .
Some obvious UI ideas are:
* flashrom TUI ( text mode user interface) ( for command line and flashrom-as-payload)
* flashrom GUI ( graphics mode user interface) (should be cross-platform, has been tried a few times and may be based on those attempts)
There have been a number of attempts to create a flashrom GUI, but [[Qflashrom]] is probably the only one of interest for you.
= Design and implementation of a native USB flashing protocol =
to the .
All existing free USB-based flash programmers have a very naive interface.
. . just to the .
The SPI programmers usually act as a simple USB to SPI bridge, mostly tunneling the plain SPI traffic via a USB communications device class (CDC) aka. RS-232 tunnel.
the of firmware. to some a //..
Since USB communication has rather long round trip times this has some performance disadvantages.
It would be much more elegant to tell the programmer what to do more abstractedly instead of sending it the complete flash protocol communication contents which just needs to be forwarded to the chip.
a . .
This requires a lot of knowledge at the external programmer though because much of what flashrom does needs to be done by its firmware.
Adding an instruction set interpreted by the programmer might help to keep the complexity within sane bounds.
. the to and .
You can find some preliminary design ideas about such a protocol by Peter Stuge in his [http:// git. stuge. se/ ?p=qiprog. git;a =blob;f=doc/qiprog_protocol. txt git repo].
A programmer based on some embedded platform (e. g. an ARM cortex-m board) should be built utilizing the protocol to evaluate the performance and implementation effort.
ROM image parsing and preparation =
== of ==
flashrom does not analyze the images fed to it.
Therefor it is not able to detect if the image is correct for the target computer neither to automatically derive [[Board Enable|Board Enables]], detect write protected regions or bootblocks etc.
There exist a number of tools already to dissect, unpack and analyze images.
Some of them reside in the (aptly named) [http://www.coreboot.org/Bios_extract '''Bios extract'''] [http://review.coreboot.org/gitweb?p= bios_extract.git repository].
Another pair of tools are the ASUS BIOS tools [https://github.com/NikolajSchlej/FD44Editor FD44Editor] and [https://github.com/NikolajSchlej/FD44Copier FD44Copier] which can show, edit, and extract lots of information about the BIOS, the regions in the file, and prepare it to be flashed back. The companion thread here: [http://hardforum.com/showthread.php?t= 1726429 Tools to flash and recover BIOS on ASUS P8xxx boards] tells how to use them and what they do more in-depth.
Then there is '''ich_descriptor_tool''' residing in the flashrom repository, which is able to parse the descriptor region found on most Intel platforms and there is an automatic board enable finder authored by Roxfan which is yet unreleased.
The goal of this project is to unify (some of) the tools above, adding further functionality and creating a library that can be used to prepare images before they are fed to flashrom and possibly by flashrom itself.
Recovery of dead boards and onboard flash updates =
* flashrom as payload
* flashrom as UEFI application
* flashrom remote flashing for coreboot panic room mode
* flashrom remote flashing with modified SerialICE
= SPI bitbanging hardware support =
* flashrom support for Nvidia SPI chipset hardware (DONE)
* flashrom support for RayeR SPIPGM hardware (DONE)
* flashrom support for [[Paraflasher]] hardware
* flashrom support for Willem hardware (unfinished patch exists)
* flashrom support for some-yet-uninvented cheap universal LPC/FWH/SPI flasher hardware
* flashrom support for bitbanging LPC/FWH (code exists, Uwe Hermann needs to post it somewhere)
* flashrom support for bitbanging Parallel
= Generic flashrom infrastructure improvements =
* Automatic recovery in case something goes wrong
* Partial reflashing
* Bytewise flashing (similar to the point above)
* Support for multiple read and write functions per chip
= Locking and Unlocking =
Many chips support some kind of write protection. Currently flashrom just tries to disable it if needed to be able to write freely. [http://git.chromium.org/gitweb/?p=chromiumos/third_party/flashrom.git;a=summary Google's flashrom branch] has some further support, which was not accepted upstream. Your task would be to design and implement acceptable data structures, APIs and user interfaces to make a generic approach to lock and unlock of flash regions possible.
some to be , , of .
= Laptop support - Support for ECs (Embedded Controllers) =
This one is really HARD. If you' re lucky and if you have datasheets, you can add support for a single laptop in maybe 1 month. If you're unlucky, it can take the whole GSoC or more. If there is interest, we 'll try to find an embedded controller which won't cause you to give up in frustration. Still, it might be beneficial if you're willing to solder (to recover from a bricked board).
'in , we 't you to in .
= Support more chips - Implement (obscure and) unsupported features - Try to make flashrom write EEPROMs =
, ..for .
Most unsupported chips need some architectural work in flashrom's core because they behave substantially different to most other chips. The same applies to EEPROMs. Some yet unsupported features like OTP, locking or GPIO control may have been seen too obscure and not in the scope of flashrom. It might be fun to work on them and evaluate the resulting changes to flashrom's core. The main objective here is not to produce mergeable code for upstream, but to show what changes to the existing code would have to be done. If those are sustainable without breaking anything and do not bloat flashrom too much, integrating the code is of course a subgoal.
Information and Links
Flashrom is applying for participation in GSoC 2022 (also known as Google Summer of Code). We will update this page in March 2022 once the registration is confirmed.
You are very welcome to look at our list of project ideas in this doc.
If you are interested to propose your own idea for GSoC project, have a look at this template.
How to contact us
If you are interested in becoming a GSoC student, please have a look at our Contact page.
If you need to contact someone directly, Anastasia Klimchuk (aklm), Felix Singer (flx) and Angel Pons (hell) are our GSoC Admins.
Why you should choose a Flashrom project for GSoC
- Flashrom offers you the opportunity to work with modern hardware “right on the iron”.
- Hardware is fun. And it’s complicated. You will learn that datasheets are just loose guidelines to the hardware and real insight is gained by systematic tinkering.
- Flashrom is the only multi-platform open source solution for flash EEPROM reading/writing for lots of different devices: on-mainboard flash (for BIOS/EFI/coreboot), graphics/network card flash (for firmware), and dozens of specialized programmer devices. If you want to update your BIOS/EFI/coreboot or update some firmware from a running Linux/*BSD/... system, then flashrom is the only choice you have.
- Flashrom does hardware access (like firmware/drivers), but completely in user space and without the hassles present in firmware or OS kernels. That way you can write complex hardware access with ease.
- Flashrom has a worldwide developer and user base. Big companies like Google and individual users use and contribute to it.
- We are a very passionate team – so you will interact directly with the project initiators and project leaders.
- We have a friendly and helpful community. Flashrom has some extremely talented and helpful experts in all things flash active in the project, and many of our friends from the coreboot project participate in flashrom as well. They are ready to assist and mentor students participating in GSoC.
Contents of your application
Please have a look at our project proposal template here.
Contributor commitments & requirements
What does it mean to be a Flashrom GSoC contributor?
Google Summer of Code is a significant time commitment for you.
Medium-sized projects are estimated to take 175 hours, while large-sized projects are estimated to take 350 hours. The standard program duration is 12 weeks and in consultation with the mentor it can be extended to 22 weeks. Please keep in mind that the actual number of hours you spend on the project highly depends on your skills and previous experience.
GSoC provides some ways allowing you to be more flexible, but make sure that your schedule (exams, courses) give you sufficient amount of spare time.
- Prior to project acceptance, you need to demonstrate that you can work with the flashrom codebase.
- You need to be able to read and write C code.
- You need to be able to work with our git repository. Check our Development Guidelines for details.
- Look at Pending Patches to see what’s going on, who are our active developers and code reviewers, what does code review look like.
- By the time you have submitted your application, you should have downloaded and built flashrom as well as applied some patches. Run flashrom on real hardware or try at least the dummy programmer driver.
- Send a patch to Gerrit for review. Check Easy projects or ask for simple tasks on the mailing list or on IRC. Please include your flashrom output and test results in the commit message and/or comments to the patch.
- To pass and to be paid by Google, we require that you meet certain milestones.
- First, you should be in good standing with the community before the official start of the program. We suggest you post some design emails to the mailing list, and get feedback on them, both before applying, and during the "community bonding period" between acceptance and official start.
- You need to have made progress and committed significant code before the mid-term point and by the final.
- Once a week, you will post what’s happening on your project on the mailing list. This way you will measure and share progress with the community, and the community at large will be able to help you. GSoC is not a private contract between your mentor and you. If you have your own blog, you are very welcome to post updates there, and we will link your blog from our website.
- You need to be active on IRC and the mailing list. Sending massive patches for midterm and final without any communication in between is not sufficient.
We don't expect our contributors to be experts in our problem domain, but we don't want you to fail because some basic misunderstanding was in your way of completing the task.
And finally, here are official guidelines for contributors.