Beagleboard:BeagleBoneBlack Rebuilding Software Image

From eLinux.org
Revision as of 09:27, 27 January 2014 by Prpplague (talk | contribs) (Created page with "= Sources = Angstrom It is highly recommended that you always use the latest version of the Software. For instructions on updating the Angstrom Software on your BeagleBone B...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Sources

Angstrom

It is highly recommended that you always use the latest version of the Software. For instructions on updating the Angstrom Software on your BeagleBone Black go to Updating the Software

If you power off the board without using the Power Button to do it, you can corrupt the data in the eMMC Flash. For instructions on reflashing the Angstrom Software on your BeagleBone Black go to Updating the Software

Software Sources

   Bootloader: http://www.denx.de/wiki/U-Boot/SourceCode (git://git.denx.de/u-boot.git)
   Kernel: http://github.com/beagleboard/kernel/tree/3.8
   Root file system: http://github.com/beagleboard/meta-beagleboard

To access the getting started guide do the following:

1) Go to http://github.com/jadonk/beaglebone-getting-started. 2) At the top of the page next to the "Clone in Windows" button, click the ZIP button. 3) Unzip that folder into a separate directory. 4) Open the readme file.

Build Instructions

All Angstrom binaries are built using OpenEmbedded. This document described the steps necessary to setup an environment where you can build images and packages yourself.

If you just want a simple toolchain, please read our simplified development setup instructions

The OE host distributions wiki has information about needed packages on your host and possible tweaks for e.g. SElinux. Step 1

get the setup scripts: Go to the the setup-scripts repository and clone it, the URLS are on top of that page. You should end up doing something like:

git clone https://github.com/Angstrom-distribution/setup-scripts

Step 2

If you are behind a firewalling proxy, have a look at the oebb.sh file, it has built-in proxy handling.

Start building: MACHINE=beagleboard ./oebb.sh config beagleboard MACHINE=beagleboard ./oebb.sh update MACHINE=beagleboard ./oebb.sh bitbake virtual/kernel

That will build the kernel for you. Substitute "beagleboard;" with the machine you want to build for, e.g.:

   c7x0 - For pxa25x zaurus clamshells (SL-C700, SL-C750, SL-C760, SL-C860, SL-7500)
   spitz - For pxa27x zaurus clamshells with a microdrive (SL-C3000, SL-C3100, SL-C3200)
   akita - For pxa27x zaurus clamshells without a microdrive (SL-C1000)
   tosa - For the SL-C6000
   h2200 - For the iPAQ h2200 series
   hx4700 - For the iPAQ hx4700
   om-gta01 - For the neo1973 phone

Or get some inspiration from looking in conf/machine in the various layers in the sources directory

  1. Build some more # you can specify machine on the cmdline: MACHINE=your_machine ./oebb.sh bitbake console-image MACHINE=your_machine ./oebb.sh bitbake systemd-gnome-image

Step 3

Building for a different machine or C library is just a matter of changing the MACHINE= or TCLIBC statement in local.conf to a new value. There is ABSOLUTELY no need for using different directories for that; Angstrom takes care of all the details, it was specifically designed for this.

For a general introduction to setting up OpenEmbedded, see GettingStarted wiki page. If you run into trouble following the below tutorial, have a look at the GettingStarted wiki page, that contains information on all kinds of cornercases. The tutorial below is kept simple on purpose.