A new post titled "[GSoC] End user flash tool – week #10 #11#12" has been published on the coreboot blog. Find the full post at http://blogs.coreboot.org/blog/2015/08/16/gsoc-end-user-flash-tool-week-10-1112/

<p>Hello!</p>
<p>During weeks 10, 11 and 12 I worked on:</p>
<ul>
<li>functions for gathering hardware specific data</li>
<li>automating process of building coreboot image</li>
<li>GUI improvements</li>
</ul>
<h5>GATHERING HARDWARE SPECIFIC DATA</h5>
<p>As I mentioned in my last post, if coreboot image should be built automatically then application needs to collect hardware specific data. During last weeks I added functions responsible for:</p>
<ul>
<li><em>dumping VGABIOS from memory: </em>Some systems (like Lenovo T60 with ATI graphics) require adding VGABIOS dumped from memory to coreboot image, because factory BIOS patches it at runtime, so in certain cases using option rom extracted from factory BIOS may not work</li>
<li><em>getting EDID data: </em>to know what type of display panel is used in system</li>
<li><em>getting motherboard model name: </em>this is mandatory to recognize if we can install coreboot in system or if we have known working configuration</li>
</ul>
<h5>AUTOMATING PROCESS OF BUILDING COREBOOT IMAGE</h5>
<p>It is now possible to build and flash coreboot image by clicking few application buttons without taking care which options are correct for system. Of course this is not possible for all hardware configurations, for now this is very limited, but with time database of known good configurations will grow and more users will be able to flash coreboot in such easy way.</p>
<p><img class="alignnone  wp-image-3959" src="http://i1.wp.com/blogs.coreboot.org/files/2015/08/flash_tool_auto_tab.png?resize=490%2C351" alt="flash_tool_auto_tab" data-recalc-dims="1" /></p>
<p>Process of automated image building:</p>
<ol>
<li>Check if working configuration for system is known.</li>
<li>Check if configuration requires additional option rom.</li>
<li>If necessary, add option rom extracted from factory bios or extracted from running system memory.</li>
<li>Build image.</li>
</ol>
<h5>GUI IMPROVEMENTS</h5>
<p>I decided to change a look of &#8216;ROM options&#8217; tab. Previously just raw output of cbfs_tool with rom contents info was redirected to GUI log window. Now it is visible in a form of table, what in my opinion is more readable.</p>
<p><a href="http://i2.wp.com/blogs.coreboot.org/files/2015/08/cbfs_tool_GUI.png"><img class="alignnone  wp-image-3960" src="http://i2.wp.com/blogs.coreboot.org/files/2015/08/cbfs_tool_GUI.png?resize=494%2C359" alt="cbfs_tool_GUI" data-recalc-dims="1" /></a></p>
<h5>LAST WEEK AND FURTHER PLANS</h5>
<p>GSoC &#8220;pencils down&#8221; date is coming up on Friday, so only few days are left. I want to use this time for:</p>
<ul>
<li>writing project documentation</li>
<li>looking for bugs and fix them</li>
<li>code cleanup</li>
<li>adding new working configurations and testing them (I need your help with it)</li>
<li>change debug messages to information popups</li>
</ul>
<p>What after GSoC? I would like to still contribute, there is place for many improvements and possible extensions.</p>