Building Coreboot, VBoot for QEMU

158 views
Skip to first unread message

David Gilhooley

unread,
Feb 2, 2017, 9:41:51 AM2/2/17
to Chromium OS discuss
Hello,

I am looking for a way to build the RO firmware for x86 QEMU. I know that it is possible to run the entirety of ChromeOS in QEMU, and QEMU is used in a couple of your testing frameworks. I think this should be a relatively easy task, I am wondering what ebuilds I should use and if there is any way to only build Coreboot, Depthcharge, and Vboot without the rest of the kernel (this is all I am looking to test and I assume only building those would be much faster).

Thanks in advance for your help!

David

David Gilhooley

unread,
Feb 2, 2017, 2:33:54 PM2/2/17
to Chromium OS discuss
So looking at this further what I am really trying to do is build the vboot_reference library for x86 so I can link it to my own program and run it in QEMU.

It looks like I should be able to do this but running the following command

  make FIRMWARE_ARCH=x86

returns with preferred-stack-boundary should be between 4 and 12 
and when I fix that it complains about inttypes.h not existing, which should be a standard library.

This happens whether I build vboot_reference on my own system or in the chroot. 

Is my only option to build all of ChromiumOS and then take the vboot_fw.a library out of vboot_reference?

Best,
David

Laël

unread,
Apr 8, 2017, 1:32:51 PM4/8/17
to Chromium OS discuss


Le jeudi 2 février 2017 20:33:54 UTC+1, David Gilhooley a écrit :
So looking at this further what I am really trying to do is build the vboot_reference library for x86 so I can link it to my own program and run it in QEMU.

It looks like I should be able to do this but running the following command

  make FIRMWARE_ARCH=x86

returns with preferred-stack-boundary should be between 4 and 12 
and when I fix that it complains about inttypes.h not existing, which should be a standard library.
Since you succeeded in building your firmware could you upload your firmware image as attachment here, please ? The only I’m getting with my builds is loop reboots.
Reply all
Reply to author
Forward
0 new messages