## Yocto Project Quick Start

Copyright © 2010-2011 Linux Foundation

## Welcome!

Welcome to the Yocto Project! The Yocto Project is an open-source collaboration project focused on embedded Linux developers. Amongst other things, the Yocto Project uses the Poky build system to construct complete Linux images.

This short document will give you some basic information about the environment as well as let you experience it in its simplest form. After reading this document you will have a basic understanding of what the Yocto Project is and how to use some of its core components. This document steps you through a simple example showing you how to build a small image and run it using the QEMU emulator.

For complete information on the Yocto Project, you should check out the Yocto Project Website. You can find the latest builds, breaking news, full development documentation, and a rich Yocto Project Development Community into which you can tap.

Finally, you might find the Frequently Asked Questions (FAQ) for the Yocto Project at Yocto Project FAQ and the FAQ appendix located in the Yocto Project Reference Manual helpful.

Due to production processes, there could be differences between the Yocto Project documentation bundled in the release tarball and the Yocto Project Quick Start on the Yocto Project website. For the latest version of this manual, see the manual on the website.

## Introducing the Yocto Project Development Environment

The Yocto Project through the Poky build system provides an open source development environment targeting the ARM, MIPS, PowerPC and x86 architectures for a variety of platforms including x86-64 and emulated ones. You can use components from the Yocto Project to design, develop, build, debug, simulate, and test the complete software stack using Linux, the X Window System, GNOME Mobile-based application frameworks, and Qt frameworks.

The Yocto Project Development Environment

Yocto Project:

- Provides a recent Linux kernel along with a set of system commands and libraries suitable for the embedded environment.

- Makes available system components such as X11, Matchbox, GTK+, Pimlico, Clutter, GuPNP and Qt (among others) so you can create a richer user interface experience on devices that use displays or have a GUI. For devices that don't have a GUI or display you simply would not employ these components.

- Creates a focused and stable core compatible with the OpenEmbedded project with which you can easily and reliably build and develop.

- Fully supports a wide range of hardware and device emulation through the QEMU Emulator.

The Yocto Project can generate images for many kinds of devices. However, the standard example machines target QEMU full system emulation for x86, ARM, MIPS, and PPC-based architectures as well as specific hardware such as the Intel Desktop Board DH55TC. Because an image developed with the Yocto Project can boot inside a QEMU emulator, the development environment works nicely as a test platform for developing embedded software.

Another important Yocto Project feature is the Sato reference User Interface. This optional GNOME mobile-based UI, which is intended for devices with restricted screen sizes, sits neatly on top of a device using the GNOME Mobile Stack and provides a well-defined user experience. Implemented in its own layer, it makes it clear to developers how they can implement their own UIs on top of Yocto Linux.

## What You Need and How You Get It

You need these things to develop in the Yocto Project environment:

- A host system running a supported Linux distribution (i.e. recent releases of Fedora, openSUSE, Debian, and Ubuntu).

  For notes about using the Yocto Project on development systems that use older Linux distributions see

- The right packages.

- A release of Yocto Project.

### The Linux Distribution

The Yocto Project has been tested and is known to work on the current releases minus one of the following distributions. Follow this link for more information on distribution testing.

- Ubuntu

- Fedora

- openSUSE

The build system should be able to run on any modern distribution with Python 2.6 or 2.7. Earlier releases of Python are known to not work and the system does not support Python 3 at this time. This document assumes you are running one of the previously noted distributions on your Linux-based host systems.

If you attempt to use a distribution not in the above list, you may or may not have success - you are venturing into untested territory. Refer to OE and Your Distro and Required Software for information for other distributions used with the Open Embedded project, which might be a starting point for exploration. If you go down this path, you should expect problems. When you do, please go to Yocto Project Bugzilla and submit a bug. We are interested in hearing about your experience.

### The Packages

Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages.

If you are using a Fedora version prior to version 15 you will need to take some extra steps to enable `sudo`. See for details.

The packages you need for a Debian-based host are shown in the following command:

         $ sudo apt-get install sed wget cvs subversion git-core coreutils \
         unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk \
         python-pysqlite2 diffstat help2man make gcc build-essential \
         g++ desktop-file-utils chrpath libgl1-mesa-dev libglu1-mesa-dev \
         mercurial autoconf automake groff libtool xterm

The packages you need for an RPM-based host like Fedora and openSUSE, respectively, are as follows:

         $ sudo yum groupinstall "development tools"
         $ sudo yum install python m4 make wget curl ftp hg tar bzip2 gzip \
         unzip python-psyco perl texinfo texi2html diffstat openjade \
         docbook-style-dsssl sed docbook-style-xsl docbook-dtds \
         docbook-utils sed bc glibc-devel ccache pcre pcre-devel quilt \
         groff linuxdoc-tools patch linuxdoc-tools cmake help2man \
         perl-ExtUtils-MakeMaker tcl-devel gettext chrpath ncurses apr \
         SDL-devel mesa-libGL-devel mesa-libGLU-devel gnome-doc-utils \
         autoconf automake libtool xterm

         $ sudo zypper install python gcc gcc-c++ libtool \
         subversion git chrpath automake \
         help2man diffstat texinfo mercurial wget

### Yocto Project Release

You can download the latest release images for the Yocto Project on the Yocto Project Download page. Just go to the page and click the "Yocto Downloads" link found in the "Download" navigation pane to the right to view all available Yocto Project releases. Then, click the "Yocto Release" link for the release you want from the list to begin the download. Nightly and developmental builds are also maintained at . However, for this document a released version of Yocto Project is used.

## A Quick Test Run

Now that you have your system requirements in order you can give Yocto Project a try. This section presents some steps that let you do the following:

- Build an image and run it in the emulator

- Or, use a pre-built image and run it in the emulator

### Building an Image

In the development environment you will need to build an image whenever you change hardware support, add or change system libraries, or add or change services that have dependencies.

Building an Image

Use the following commands to build your image. The build process creates an entire Linux distribution, including the toolchain, from source.

The build process using Sato currently consumes about 50GB of disk space. To allow for variations in the build process and for future package expansion, we recommend having at least 100GB of free disk space.

By default, the Yocto Project searches for source code using a pre-determined order through a set of locations. If you encounter problems with the Yocto Project finding and downloading source code, see the FAQ entry "How does Poky obtain source code and will it work behind my firewall or proxy server?" in the Yocto Project Reference Manual.

         $ wget http://www.yoctoproject.org/downloads/poky/poky-bernard-5.0.1.tar.bz2
         $ tar xjf poky-bernard-5.0.1.tar.bz2
         $ source poky-bernard-5.0.1/poky-init-build-env poky-5.0.1-build

To help conserve disk space during builds you can add the following statement to your `local.conf` file. Adding this statement deletes the work directory used for building a package once the package is built.

         INHERIT += rm_work

- The first two commands extract the Yocto Project files from the release tarball and place them into a subdirectory of your current directory.

- The `source` command creates the `poky-5.0.1-build` directory and executes the `cd` command to make `poky-5.0.1-build` the working directory. The resulting build directory contains all the files created during the build. By default the target architecture is qemux86. To change this default, edit the value of the MACHINE variable in the `conf/local.conf` file.

Take some time to examine your `conf/local.conf` file found in the Yocto Project file's `conf`. The defaults should work fine. However, if you have a multi-core CPU you might want to set the variable BB_NUMBER_THREADS equal to twice the number of processor cores your system has. And, set the variable PARALLEL_MAKE equal to the number of processor cores. Setting these variables can significantly shorten your build time. By default, these variables are commented out.

Another consideration before you build is the package manager used when creating the image. By default, the Yocto Project build system uses the RPM package manager. You can control this configuration by using the `PACKAGE_CLASSES` variable. For additional package manager selection information, see Packaging - `package*.bbclass` in The Yocto Project Reference Manual.

Continue with the following command to build an OS image for the target, which is `core-image-sato` in this example. For information on the `&dash;k` option use the `bitbake --help` command or see BitBake section in the Yocto Project Reference Manual.

         $ bitbake -k core-image-sato

BitBake requires Python 2.6 or 2.7. For more information on this requirement, see the FAQ appendix in the Yocto Project Reference Manual.

The final command runs the image:

         $ runqemu qemux86

Depending on the number of processors and cores, the amount or RAM, the speed of your Internet connection and other factors, the build process could take several hours the first time you run it. Subsequent builds run much faster since parts of the build are cached.

### Using Pre-Built Binaries and QEMU

If hardware, libraries and services are stable you can get started by using a pre-built binary of the image, kernel and toolchain and run it using the emulator QEMU. This scenario is useful for developing application software.

Using a Pre-Built Image

For this scenario you need to do several things:

- Install the stand-alone Yocto toolchain tarball.

- Download the pre-built kernel that will boot with QEMU. You need to be sure to get the QEMU image that matches your target machine’s architecture (e.g. x86, ARM, etc.).

- Download the filesystem image for your target machine's architecture.

- Set up the environment to emulate the hardware and then start the QEMU emulator.

#### Installing the Toolchain

You can download the pre-built toolchain, which includes the `runqemu` script and support files, from . Toolchains are available for 32-bit and 64-bit development systems from the `i686` and `x86_64` folders, respectively. Each type of development system supports five target architectures. The tarball files are named such that a string representing the host system appears first in the filename and then is immediately followed by a string representing the target architecture.

         yocto-eglibc<host_system>-<arch>-toolchain-gmae-<release>.tar.bz2

         Where:
             <host_system> is a string representing your development system:
                    i686 or x86_64.

             <arch> is a string representing the target architecture:
                    i586, x86_64, powerpc, mips, or arm.

             <release> is the version of Yocto Project.

For example, the following toolchain tarball is for a 64-bit development host system and a 32-bit target architecture:

         yocto-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2

The toolchain tarballs are self-contained and must be installed into `/opt/poky`. The following commands show how you install the toolchain tarball given a 64-bit development host system and a 32-bit target architecture. The example assumes the toolchain tarball is located in `~/toolchains/`:

         $ cd /
         $ sudo tar -xvjf ~/toolchains/yocto-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2

#### Downloading the Pre-Built Linux Kernel

You can download the pre-built Linux kernel and the filesystem image suitable for running in the emulator QEMU from . Be sure to use the kernel and filesystem image that matches the architecture you want to simulate. Download areas exist for the five supported machine architectures: `qemuarm`, `qemumips`, `qemuppc`, `qemux86`, and `qemux86_64`.

Most kernel files have one of the following forms:

         *zImage-<kernel-rev>-qemu<arch>-<release>*.bin
         vmlinux-<kernel-rev>-qemu<arch>-<release>*.bin

         Where:
             <kernel-rev> is the base Linux kernel revision
                    (e.g. 2.6.37).

             <arch> is a string representing the target architecture:
                    x86, x86-64, ppc, mips, or arm.

             <release> is the version of Yocto Project.

#### Downloading the Filesystem

The filesystem image has two tarball forms: `ext3` and `tar`. You must use the `ext3` form when booting an image using the QEMU emulator. The `tar` form can be flattened out in your host development system and used for Yocto Project build purposes.

         yocto-image-<profile>-qemu<arch>-<release>.rootfs.ext3.bz2
         yocto-image-<profile>-qemu<arch>-<release>.rootfs.tar.bz2

         Where:
             <profile> is the filesystem image's profile:
                       lsb, lsb-dev, lsb-sdk, minimal, minimal-dev, sato, sato-dev, or sato-sdk.
                       For information on these types of image profiles, see
                       Reference: Images in the Yocto Project Reference Manual.

             <arch> is a string representing the target architecture:
                    x86, x86-64, ppc, mips, or arm.

             <release> is the version of Yocto Project.

#### Setting Up the Environment and Starting the QEMU Emulator

Before you start the QEMU emulator you need to set up the emulation environment. The following command form sets up the emulation environment.

         $ source /opt/poky/1.1/environment-setup-<arch>-poky-linux-<if>

         Where:
             <arch> is a string representing the target architecture:
                    i586, x86_64, ppc603e, mips, or armv5te.

             <if> is a string representing an embedded application binary interface.
                  Not all setup scripts include this string.

Finally, this command form invokes the QEMU emulator

         $ runqemu <qemuarch> <kernel-image> <filesystem-image>

         Where:
             <qemuarch> is a string representing the target architecture: qemux86, qemux86-64,
                        qemuppc, qemumips, or qemuarm.

             <kernel-image> is the architecture-specific kernel image.

             <filesystem-image> is the .ext3 filesystem image.

Continuing with the example, the following two commands setup the emulation environment and launch QEMU. This example assumes the root filesystem tarball has been downloaded and expanded, and that the kernel and filesystem are for a 32-bit target architecture.

         $ source /opt/poky/1.1/environment-setup-i686-poky-linux
         $ runqemu qemux86 bzImage-3.0-qemux86-1.1.bin \
         yocto-image-sato-qemux86-1.1.rootfs.ext3

The environment in which QEMU launches varies depending on the filesystem image and on the target architecture. For example, if you source the environment for the ARM target architecture and then boot the minimal QEMU image, the emulator comes up in a new shell in command-line mode. However, if you boot the SDK image QEMU comes up with a GUI.

Booting the PPC image results in QEMU launching in the same shell in command-line mode.