Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Embedded Linux Projects Using Yocto Project Cookbook
Embedded Linux Projects Using Yocto Project Cookbook

Embedded Linux Projects Using Yocto Project Cookbook: Over 70 hands-on recipes for professional embedded Linux developers to optimize and boost their Yocto know-how

eBook
€32.99
Paperback
€41.99
Subscription
Free Trial
Renews at €18.99p/m

What do you get with eBook?

Product feature icon Instant access to your Digital eBook purchase
Product feature icon Download this book in EPUB and PDF formats
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Table of content icon View table of contents Preview book icon Preview Book

Embedded Linux Projects Using Yocto Project Cookbook

Chapter 2. The BSP Layer

In this chapter, we will cover the following recipes:

  • Creating a custom BSP layer
  • Introducing system development workflows
  • Adding a custom kernel and bootloader
  • Building the U-Boot bootloader
  • Explaining Yocto's Linux kernel support
  • Describing Linux's build system
  • Configuring the Linux kernel
  • Building the Linux source
  • Building external kernel modules
  • Debugging the Linux kernel and modules
  • Debugging the Linux kernel booting process
  • Using the kernel tracing system
  • Managing the device tree
  • Debugging device tree issues

Introduction

Once we have our build environment ready with the Yocto project, it's time to think about beginning development work on our embedded Linux project.

Most of the embedded Linux projects require both custom hardware and software. An early task in the development process is to test different hardware reference boards and the selection of one to base our design on. We have chosen the Wandboard, a Freescale i.MX6-based platform, as it is an affordable and open board, which makes it perfect for our needs.

On an embedded project, it is usually a good idea to start working on the software as soon as possible, probably before the hardware prototypes are ready, so that it is possible to start working directly with the reference design.

But at some point, the hardware prototypes will be ready and changes will need to be introduced into Yocto to support the new hardware.

This chapter will explain how to create a BSP layer to contain those hardware-specific changes, as well as show how...

Creating a custom BSP layer

These custom changes are kept on a separate Yocto layer, called a Board Support Package (BSP) layer. This separation is best for future updates and patches to the system. A BSP layer can support any number of new machines and any new software feature that is linked to the hardware itself.

How to do it...

By convention, Yocto layer names start with meta, short for metadata. A BSP layer may then add a bsp keyword, and finally a unique name. We will call our layer meta-bsp-custom.

There are several ways to create a new layer:

  • Manually, once you know what is required
  • By copying the meta-skeleton layer included in Poky
  • By using the yocto-layer command-line tool

You can have a look at the meta-skeleton layer in Poky and see that it includes the following elements:

  • A layer.conf file, where the layer configuration variables are set
  • A COPYING.MIT license file
  • Several directories named with the recipes prefix with example recipes for BusyBox, the Linux kernel and an example module...

Introducing system development workflows

When customizing the software, there are some system development workflows that are commonly used, and we will introduce them in this recipe.

How to do it...

We will see an overview of the following development workflows:

  • External development
  • Working directory development
  • External source development

They are all used under different scenarios.

How it works...

Let's understand what the use of each of these development workflows is individually.

External development

In this workflow, we don't use the Yocto build system to build our packages, just a Yocto toolchain and the package's own build system.

The resulting source can be integrated into Yocto in the following ways:

  • With a recipe that fetches a released tarball.
  • With a recipe that fetches directly from a source-controlled repository.

External development is usually the preferred method for U-Boot and Linux kernel development, as they can be easily cross-compiled. Third-party packages in Yocto...

Adding a custom kernel and bootloader

Development in U-Boot and the Linux kernel is usually done externally to Yocto, as they are easy to build using a toolchain, like the one provided by Yocto.

The development work is then integrated into Yocto in one of two ways:

  • With patches added to the kernel and U-Boot bbappend files. This method will build the same source as the reference design board we are using as base, and apply our changes over it.
  • Using a different Git repository, forked from the Linux kernel and U-Boot Git repositories being used by the reference design, and using a bbappend file to point the recipe to it. This way, we can directly commit the changes to the repository and the Yocto build system will build them.

Usually a forked Git repository is only needed when the hardware changes are substantial and the work in the Linux kernel and bootloader is going to be extensive. The recommendation is to start with patches, and only use a forked repository when they become difficult to...

Building the U-Boot bootloader

In this recipe, we will go through the several development workflows described previously using the U-Boot bootloader as an example.

How to do it...

We will see how the following development workflows are applied to U-Boot:

  • External development
  • External source development
  • Working directory development

How it works...

Let's explain the three workflows, previously mentioned, in detail.

External development

We will use a Yocto toolchain to build the U-Boot source externally from the Yocto build system.

  1. Download and install a Yocto project cross-compilation toolchain for your host by going to the following:

    http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.1/toolchain/

    Tip

    Choose either the 32- or 64-bit version and execute the installation script, accepting the default installation location. It is recommended not to change the default location to avoid relocation issues.

  2. Find the upstream Git repository:
    $ bitbake -e u-boot-fslc | grep ^SRC_URI=
    SRC_URI=&quot...

Explaining Yocto's Linux kernel support

The Yocto project offers a kernel framework that allows us to work with the Linux kernel in different ways:

  • Fetching the source from a Git repository and applying patches to it. This is the path taken by the Freescale community BSP-supported kernels, as we saw previously.
  • The linux-yocto style kernels that generate the kernel source from a set of Git branches and leafs. Specific features are developed in branches, and a leaf is followed for a complete set of features.

In this recipe, we will show how to work with a linux-yocto style kernel.

How to do it...

To use a linux-yocto style kernel, the kernel recipe inherits the linux-yocto.inc file. A Git repository for a linux-yocto style kernel contains metadata either in the recipe or inside the kernel Git tree, in branches named with the meta prefix.

The linux-yocto style kernel recipes are all named linux-yocto and follow the upstream kernel development, rooted in the kernel.org repository. Once a new...

Introduction


Once we have our build environment ready with the Yocto project, it's time to think about beginning development work on our embedded Linux project.

Most of the embedded Linux projects require both custom hardware and software. An early task in the development process is to test different hardware reference boards and the selection of one to base our design on. We have chosen the Wandboard, a Freescale i.MX6-based platform, as it is an affordable and open board, which makes it perfect for our needs.

On an embedded project, it is usually a good idea to start working on the software as soon as possible, probably before the hardware prototypes are ready, so that it is possible to start working directly with the reference design.

But at some point, the hardware prototypes will be ready and changes will need to be introduced into Yocto to support the new hardware.

This chapter will explain how to create a BSP layer to contain those hardware-specific changes, as well as show how to work...

Creating a custom BSP layer


These custom changes are kept on a separate Yocto layer, called a Board Support Package (BSP) layer. This separation is best for future updates and patches to the system. A BSP layer can support any number of new machines and any new software feature that is linked to the hardware itself.

How to do it...

By convention, Yocto layer names start with meta, short for metadata. A BSP layer may then add a bsp keyword, and finally a unique name. We will call our layer meta-bsp-custom.

There are several ways to create a new layer:

  • Manually, once you know what is required

  • By copying the meta-skeleton layer included in Poky

  • By using the yocto-layer command-line tool

You can have a look at the meta-skeleton layer in Poky and see that it includes the following elements:

  • A layer.conf file, where the layer configuration variables are set

  • A COPYING.MIT license file

  • Several directories named with the recipes prefix with example recipes for BusyBox, the Linux kernel and an example module...

Introducing system development workflows


When customizing the software, there are some system development workflows that are commonly used, and we will introduce them in this recipe.

How to do it...

We will see an overview of the following development workflows:

  • External development

  • Working directory development

  • External source development

They are all used under different scenarios.

How it works...

Let's understand what the use of each of these development workflows is individually.

External development

In this workflow, we don't use the Yocto build system to build our packages, just a Yocto toolchain and the package's own build system.

The resulting source can be integrated into Yocto in the following ways:

  • With a recipe that fetches a released tarball.

  • With a recipe that fetches directly from a source-controlled repository.

External development is usually the preferred method for U-Boot and Linux kernel development, as they can be easily cross-compiled. Third-party packages in Yocto are also developed...

Adding a custom kernel and bootloader


Development in U-Boot and the Linux kernel is usually done externally to Yocto, as they are easy to build using a toolchain, like the one provided by Yocto.

The development work is then integrated into Yocto in one of two ways:

  • With patches added to the kernel and U-Boot bbappend files. This method will build the same source as the reference design board we are using as base, and apply our changes over it.

  • Using a different Git repository, forked from the Linux kernel and U-Boot Git repositories being used by the reference design, and using a bbappend file to point the recipe to it. This way, we can directly commit the changes to the repository and the Yocto build system will build them.

Usually a forked Git repository is only needed when the hardware changes are substantial and the work in the Linux kernel and bootloader is going to be extensive. The recommendation is to start with patches, and only use a forked repository when they become difficult to...

Building the U-Boot bootloader


In this recipe, we will go through the several development workflows described previously using the U-Boot bootloader as an example.

How to do it...

We will see how the following development workflows are applied to U-Boot:

  • External development

  • External source development

  • Working directory development

How it works...

Let's explain the three workflows, previously mentioned, in detail.

External development

We will use a Yocto toolchain to build the U-Boot source externally from the Yocto build system.

  1. Download and install a Yocto project cross-compilation toolchain for your host by going to the following:

    http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.1/toolchain/

    Tip

    Choose either the 32- or 64-bit version and execute the installation script, accepting the default installation location. It is recommended not to change the default location to avoid relocation issues.

  2. Find the upstream Git repository:

    $ bitbake -e u-boot-fslc | grep ^SRC_URI=
    SRC_URI="git://github...

Explaining Yocto's Linux kernel support


The Yocto project offers a kernel framework that allows us to work with the Linux kernel in different ways:

  • Fetching the source from a Git repository and applying patches to it. This is the path taken by the Freescale community BSP-supported kernels, as we saw previously.

  • The linux-yocto style kernels that generate the kernel source from a set of Git branches and leafs. Specific features are developed in branches, and a leaf is followed for a complete set of features.

In this recipe, we will show how to work with a linux-yocto style kernel.

How to do it...

To use a linux-yocto style kernel, the kernel recipe inherits the linux-yocto.inc file. A Git repository for a linux-yocto style kernel contains metadata either in the recipe or inside the kernel Git tree, in branches named with the meta prefix.

The linux-yocto style kernel recipes are all named linux-yocto and follow the upstream kernel development, rooted in the kernel.org repository. Once a new Yocto...

Describing Linux's build system


The Linux kernel is a monolithic kernel and as such shares the same address space. Although it has the ability to load modules at runtime, the kernel must contain all the symbols the module uses at compilation time. Once the module is loaded, it will share the kernel's address space.

The kernel build system, or kbuild, uses conditional compilation to decide which parts of the kernel are compiled. The kernel build system is independent of the Yocto build system.

In this recipe, we will explain how the kernel's build system works.

How to do it...

The kernel configuration is stored in a .config text file in the kernel root directory. The kbuild system reads this configuration to build the kernel. The .config file is referred to as the kernel configuration file. There are multiple ways to define a kernel configuration file:

  • Manually editing the .config file, although this is not recommended.

  • Using one of the user interfaces the kernel offers (type the make help command...

Configuring the Linux kernel


In this recipe, we will explain how to configure a Linux kernel using the Yocto build system.

Getting ready

Before configuring the kernel, we need to provide a default configuration for our machine, which is the one the Yocto project uses to configure a kernel. When defining a new machine in your BSP layer, you need to provide a defconfig file.

The Wandboard's defconfig file is stored under sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard-3.10.17/defconfig.

This would be the base defconfig file for our custom hardware, so we copy it to our BSP layer:

$ cd /opt/yocto/fsl-community-bsp/sources
$ mkdir -p meta-bsp-custom/recipes-kernel/linux/linux-wandboard- 3.10.17/
$ cp meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard- 3.10.17/defconfig meta-bsp-custom/recipes-kernel/linux/linux- wandboard-3.10.17/

We then add it to our kernel using meta-bsp-custom/recipes-kernel/linux/linux-wandboard_3.10.17.bbappend as follows:

# Copyright Packt Publishing 2015...

Building the Linux kernel


In this recipe, we will go through the development workflows described earlier using the Linux kernel as an example.

How to do it...

We will see how the following development workflows are applied to the Linux kernel:

  • External development

  • Working directory development

  • External source development

How it works...

Let's explain the three methodologies listed previously in detail.

External development

When compiling outside of the Yocto build environment, we can still use the Yocto-provided toolchain to build. The process is as follows:

  1. We will use the Yocto project cross-compilation toolchain already installed in your host.

  2. Clone the wandboard-org linux-wandboard repository locally:

    $ cd /opt/yocto
    $ git clone https://github.com/wandboard-org/linux.git linux-wandboard
    $ cd linux-wandboard
    
  3. Go to the branch specified in the linux-wandboard_3.10.17.bb recipe:

    $ git checkout -b wandboard_imx_3.10.17_1.0.2_ga origin/wandboard_imx_3.10.17_1.0.2_ga
    
  4. Compile the kernel source as follows...

Left arrow icon Right arrow icon

Description

If you are an embedded developer learning about embedded Linux with some experience with the Yocto project, this book is the ideal way to become proficient and broaden your knowledge with examples that are immediately applicable to your embedded developments. Experienced embedded Yocto developers will find new insight into working methodologies and ARM specific development competence.

Who is this book for?

If you are an embedded developer learning about embedded Linux with some experience with the Yocto project, this book is the ideal way to become proficient and broaden your knowledge with examples that are immediately applicable to your embedded developments. Experienced embedded Yocto developers will find new insight into working methodologies and ARM specific development competence.

What you will learn

  • Optimize your Yocto setup to speed up development and debug build issues
  • Introduce development workflows for the UBoot and the Linux kernel, including debugging and optimization methodologies
  • Customize your root filesystem with both already supported and new Yocto packages
  • Understand the open source licensing requirements and how to comply with them when cohabiting with proprietary programs
  • Bring professional embedded Yocto products to market in a timely manner
  • Optimize your production systems by reducing the size of both the Linux kernel and root filesystems

Product Details

Country selected
Publication date, Length, Edition, Language, ISBN-13
Publication date : Mar 30, 2015
Length: 324 pages
Edition : 1st
Language : English
ISBN-13 : 9781784396343
Category :

What do you get with eBook?

Product feature icon Instant access to your Digital eBook purchase
Product feature icon Download this book in EPUB and PDF formats
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want

Product Details

Publication date : Mar 30, 2015
Length: 324 pages
Edition : 1st
Language : English
ISBN-13 : 9781784396343
Category :

Packt Subscriptions

See our plans and pricing
Modal Close icon
€18.99 billed monthly
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Simple pricing, no contract
€189.99 billed annually
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just €5 each
Feature tick icon Exclusive print discounts
€264.99 billed in 18 months
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just €5 each
Feature tick icon Exclusive print discounts

Frequently bought together


Stars icon
Total 99.97
Embedded Linux Development with Yocto Project
€20.99
Embedded Linux Projects Using Yocto Project Cookbook
€41.99
Learning Embedded Linux using the Yocto Project
€36.99
Total 99.97 Stars icon

Table of Contents

6 Chapters
1. The Build System Chevron down icon Chevron up icon
2. The BSP Layer Chevron down icon Chevron up icon
3. The Software Layer Chevron down icon Chevron up icon
4. Application Development Chevron down icon Chevron up icon
5. Debugging, Tracing, and Profiling Chevron down icon Chevron up icon
Index Chevron down icon Chevron up icon

Customer reviews

Top Reviews
Rating distribution
Full star icon Full star icon Full star icon Full star icon Half star icon 4.4
(13 Ratings)
5 star 69.2%
4 star 15.4%
3 star 7.7%
2 star 0%
1 star 7.7%
Filter icon Filter
Top Reviews

Filter reviews by




Jos� Manuel Garc�a Llamas May 28, 2015
Full star icon Full star icon Full star icon Full star icon Full star icon 5
If you want a general and practical guide about YOCTO this book is not only a really helpful one but a also a perfect starting point.First chapters go deep into the first steps with YOCTO, so you will see what is needed to have YOCTO up and running, by setting the enviroment accordingly.From that point onwards, chapters 3 and 4, we are ready to work and configure BSP, Board Support Package, so that you can see all the software and packages needed to work with YOCTO.Once you jump into Chapters 4 and also 5, you will be able to go deeper with YOCTO, by having a look at its core. Furthermore, you will have a contact with different software packages in case you want to develop and application on top of YOCTO.In general I think this book is quite interesting, and almost everybody, who nowdays have a board like Raspberry Pi or a similar one, can quickly apply to these boards what is taught in this book.
Amazon Verified review Amazon
James K. Lewis May 30, 2015
Full star icon Full star icon Full star icon Full star icon Full star icon 5
If this book had been around back when I did embedded Linux it sure would have made my life easier. The author obviously knows the material very well and explains it using clear examples. I particularly liked the sections when he talks about building kernels. Overall a very good book and one I am glad is in my collection.
Amazon Verified review Amazon
RHansen Oct 15, 2016
Full star icon Full star icon Full star icon Full star icon Full star icon 5
Great, I learned more in the first 15 minutes than screwing around and reading the official docs for a week. Yocto takes a bit of getting use to, this book helps a LOT.
Amazon Verified review Amazon
Alexandre B Jun 11, 2015
Full star icon Full star icon Full star icon Full star icon Full star icon 5
This book is written as a set of recipes and this structure makes it is easy to find the answers you are looking for. It also explains the underlying concepts of the solution. It also includes more generic information and howtos about using, developing and debugging embedded Linux. It is definitively of good value once you start using Yocto Project.
Amazon Verified review Amazon
Nigel Webster Apr 12, 2017
Full star icon Full star icon Full star icon Full star icon Full star icon 5
Really good reference book to get you started with building Yocto Linux recipes
Amazon Verified review Amazon
Get free access to Packt library with over 7500+ books and video courses for 7 days!
Start Free Trial

FAQs

How do I buy and download an eBook? Chevron down icon Chevron up icon

Where there is an eBook version of a title available, you can buy it from the book details for that title. Add either the standalone eBook or the eBook and print book bundle to your shopping cart. Your eBook will show in your cart as a product on its own. After completing checkout and payment in the normal way, you will receive your receipt on the screen containing a link to a personalised PDF download file. This link will remain active for 30 days. You can download backup copies of the file by logging in to your account at any time.

If you already have Adobe reader installed, then clicking on the link will download and open the PDF file directly. If you don't, then save the PDF file on your machine and download the Reader to view it.

Please Note: Packt eBooks are non-returnable and non-refundable.

Packt eBook and Licensing When you buy an eBook from Packt Publishing, completing your purchase means you accept the terms of our licence agreement. Please read the full text of the agreement. In it we have tried to balance the need for the ebook to be usable for you the reader with our needs to protect the rights of us as Publishers and of our authors. In summary, the agreement says:

  • You may make copies of your eBook for your own use onto any machine
  • You may not pass copies of the eBook on to anyone else
How can I make a purchase on your website? Chevron down icon Chevron up icon

If you want to purchase a video course, eBook or Bundle (Print+eBook) please follow below steps:

  1. Register on our website using your email address and the password.
  2. Search for the title by name or ISBN using the search option.
  3. Select the title you want to purchase.
  4. Choose the format you wish to purchase the title in; if you order the Print Book, you get a free eBook copy of the same title. 
  5. Proceed with the checkout process (payment to be made using Credit Card, Debit Cart, or PayPal)
Where can I access support around an eBook? Chevron down icon Chevron up icon
  • If you experience a problem with using or installing Adobe Reader, the contact Adobe directly.
  • To view the errata for the book, see www.packtpub.com/support and view the pages for the title you have.
  • To view your account details or to download a new copy of the book go to www.packtpub.com/account
  • To contact us directly if a problem is not resolved, use www.packtpub.com/contact-us
What eBook formats do Packt support? Chevron down icon Chevron up icon

Our eBooks are currently available in a variety of formats such as PDF and ePubs. In the future, this may well change with trends and development in technology, but please note that our PDFs are not Adobe eBook Reader format, which has greater restrictions on security.

You will need to use Adobe Reader v9 or later in order to read Packt's PDF eBooks.

What are the benefits of eBooks? Chevron down icon Chevron up icon
  • You can get the information you need immediately
  • You can easily take them with you on a laptop
  • You can download them an unlimited number of times
  • You can print them out
  • They are copy-paste enabled
  • They are searchable
  • There is no password protection
  • They are lower price than print
  • They save resources and space
What is an eBook? Chevron down icon Chevron up icon

Packt eBooks are a complete electronic version of the print edition, available in PDF and ePub formats. Every piece of content down to the page numbering is the same. Because we save the costs of printing and shipping the book to you, we are able to offer eBooks at a lower cost than print editions.

When you have purchased an eBook, simply login to your account and click on the link in Your Download Area. We recommend you saving the file to your hard drive before opening it.

For optimal viewing of our eBooks, we recommend you download and install the free Adobe Reader version 9.