To get the most out of this book

This books assumes some basic working knowledge of GNU/Linux systems and applications such as the bash shell and derivatives, as well as standard tools such as grep, patch, and diff. The examples have been tested with an Ubuntu 16.04 LTS system, but any Linux distribution supported by the Yocto project can be used.

The book is structured to follow the usual development workflow of an embedded Linux product, but chapters, or even individual recipes, can be read independently.

Recipes take a practical, hands-on approach using an NXP i.MX6-based system, the Wandboard Quad, as base hardware. However, any other i.MX-based hardware can be used to follow the examples.

Download the example code files

You can download the example code files for this book from your account at www.packtpub.com. If you purchased this book elsewhere, you can visit www.packtpub.com/support and register to have the files emailed directly to you.

You can download the code files by following these steps:

1. Log in or register at www.packtpub.com.
2. Select the SUPPORT tab.
3. Click on Code Downloads & Errata.
4. Enter the name of the book in the Search box and follow the onscreen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

• WinRAR/7-Zip for Windows
• Zipeg/iZip/UnRarX for Mac
• 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/Embedded-Linux-Development-Using-Yocto-Project-Cookbook-Second-Edition. We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!

Download the color images

We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: http://www.packtpub.com/sites/default/files/downloads/EmbeddedLinuxDevelopmentUsingYoctoProjectCookbookSecondEdition_ColorImages.pdf.

Conventions used

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "In this case, both imx6q.dtsi and ;imx6qdl-wandboard-revd1.dtsi are overlaid with the contents of imx6qp-wandboard-revd1.dts."

A block of code is set as follows:

#include "imx6q-wandboard-revd1.dts"                                             
#include "imx6qp.dtsi"                                                           
                                                                                 
/ {                                                                              
        model = "Wandboard i.MX6QuadPlus rev.D1";                                
}; 

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

# Allow override of WANDBOARD_GITHUB_MIRROR to make use of                       
# local repository easier                                                        
WANDBOARD_GITHUB_MIRROR ?= "git://github.com/wandboard-org/linux.git"

Any command-line input or output is written as follows:

$ cd /opt/yocto/fsl-community-bsp/wandboard/tmp/deploy/sdk/
$ ./poky-glibc-x86_64-core-image-minimal-cortexa9hf-neon-toolchain-2.4.sh  

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "Build the project by going to Project | Build Project."

Warnings or important notes appear like this.

Tips and tricks appear like this.