Building LinuxBIOS: Difference between revisions
mNo edit summary |
m (Reverted edits by Rizwan1218 (Talk) to last revision by JordanCrouse) |
||
(7 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
<noinclude>{{Translations}}</noinclude> |
|||
{{deprecated}} |
|||
== Warnings and Disclaimers == |
== Warnings and Disclaimers == |
||
Line 73: | Line 76: | ||
* [[Maintainer Notes]] |
* [[Maintainer Notes]] |
||
[[Category:Hardware]] |
|||
[[Category:Developers]] |
Latest revision as of 20:32, 25 July 2013
Warnings and DisclaimersThese instructions are new and subject to change. No assurance is made that this won't permanently harm your hardware. If you don't understand any of these steps, please stop and ask for clarification on the mailing lists or in IRC. You have now been officially warned. BuildromDuring boot, LinuxBIOS loads a small payload that consists of a minimal kernel and an initramfs image. We refer to this payload as the "ROM image". The ROM image is responsible for bringing up the system enough to try to load a full kernel from the NAND flash, a USB mass storage device, or the network. Buildrom is a small set of build scripts that facilitiates building the bootloader and ROM image (including the kernel and all the different utilities and scripts that make up the initramfs image). If you understand buildroot (from the uclibc team), then buildrom will look familiar - it is based on the same concept. Buildrom is a GNU Make based build system. Using a series of configuration files, the makefile will determine what packages need to be built. Each package is obtained from an upstream repository with wget and built locally on your machine. When all the packages have been built, the script pulls together all the binaries for the ROM image, and combines them into a .ELF file which is then used as the payload to build a LinuxBIOS ROM. Update - buildrom now builds ROM images for the SPI flash by default. You don't need to change anything from the default configuration. Getting buildromBuildrom is available from the OLPC GIT repository on http://dev.laptop.org. After installing git, run: $ git clone git://dev.laptop.org/users/jcrouse/buildrom This will make a copy of the tree in a folder called 'buildrom'. From time to time, you will want to make sure you are synced with the tree: $ cd buildrom; git pull Building the imageBuildrom requires the following tools on your development system to run:
To build the default image, just type $ make You will notice that the system will start downloading packages from the web with wget, and compiling them. If you are behind a proxy, don't forget to set http_proxy before starting. $ export http_proxy=<proxyurl>:<proxyport> Note that there is also one package (LinuxBIOS) that will be pulled down with SVN. If you have proxy worries, make sure your local SVN environment is correctly setup. Buildrom already sets all the important flags and other settings to build the tools and libraries so they can be included into the ROM. There are several configuration options you can play with once you are more familar with the system. Check Config.mk and read the comments. Using the ImageWhen the system is done building, you will have three files in the deploy/ directory:
The most important deliverable is the 1MB ROM image:
What Next? |