HOW TO RUN BOOT.ELF INSTALL
HOW TO RUN BOOT.ELF DRIVERS
HOW TO RUN BOOT.ELF UPDATE

HOW TO RUN BOOT.ELF DRIVERS

Generic Drivers / Enable early (pre-RAM) usbdebug = Enable Generic Drivers / USB 2.0 EHCI debug dongle support = Enable Mainboard / ROM chip size = size of flash chipР вЂќР’В¬hipset / Include CPU microcode in CBFS = Do not include microcode updates (NOTE: you probably want to enable it on some systems)Р вЂќР’Вevices / Use native graphics initialization = enable (NOTE: not available on all systems)Р вЂќР’Вisplay / Keep VESA framebuffer = disable (disable for text-mode graphics, enable for coreboot vesa framebuffer) Mainboard / Mainboard vendor = Name of manufacturer General / Use CMOS for configuration values = enable (CMOS defaults are located in your boards directory src/mainboard/OEM/MODEL/fault)

(note that this assumes presence of native graphics initialization on the given board, which is not universally available in coreboot)

More detailed example (generic) configuration (tweak accordingly):

In ROM chip size select the exact size of the flash ROM chip you want to flash the coreboot image on.

In Mainboard model select your exact mainboard name.

In Mainboard vendor select the vendor of your board.

In that menu (which may look familiar, as other projects such as the Linux kernel or busybox use the same system), select at least the following options: $ make nconfig (easier to navigate, uses ncurses) Once you have the desired sources (and 3rdparty modules, if needed) checked out, you can configure the build-time options of coreboot:

HOW TO RUN BOOT.ELF UPDATE

If you do this, run `git submodule update -checkout` again to make sure the 3rdparty modules are in sync with the sources. If your board is listed and you want to try a known-working version, click the 'upstream tree' link to find the commit hash and then check it out in git: It is worth checking the Supported Motherboards page to see if your mainboard is known to work with a particular version of coreboot. The last step is important! It checks out a sub-repository in the 3rdparty directory. filo.elf, or coreinfo.elf) which you can use with coreboot (see below).Р вЂќР вЂЎirst, get the latest coreboot version from our git repository:

The result of this step should be an ELF file (e.g.

Please check Payloads and the wiki page for the respective payload for details.

Each payload may have different build instructions and requirements, however most of the time a 'make' command will suffice.

First you need to download the source code for the payload of your choice and build it.

If, however, you need to build a payload that is currently not included in the coreboot build system: It runs Option ROMs, is able to discover boot devices and provides a very simple boot menu. Most beginners want to use the default SeaBIOS payload. The majority of the payloads supported by coreboot are built automatically once they are selected and configured as described in the next section.

HOW TO RUN BOOT.ELF INSTALL

doxygen (for generating/viewing documentation)Р вЂќР’Вebian apt-get install git build-essential gnat flex bison libncurses5-dev wget zlib1g-dev Building a payload (Optional).

flex and bison (for regenerating parsers).

gcc / g++ / gnat (gcc-multilib is ideal, makes building payloads a lot easier).

How to run boot.elf