The Software Layer | Embedded Linux Projects Using Yocto Project Cookbook

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Embedded Linux Projects Using Yocto Project Cookbook

By : Alex Gonzalez

3.8 (8)

Embedded Linux Projects Using Yocto Project Cookbook

3.8 (8)

By: Alex Gonzalez

Overview of this book

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.

Preface

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

The Build System

The Build System

Introduction

Setting up the host system

Installing Poky

Creating a build directory

Building your first image

Explaining the NXP Yocto ecosystem

Installing support for NXP hardware

Building Wandboard images

Using the Toaster web interface

Running a Toaster Docker container

Configuring network booting for a development setup

Using Docker as a Yocto build system container

Sharing downloads

Sharing the shared state cache

Setting up a package feed

Using build history

Working with build statistics

Debugging the build system

The BSP Layer

The BSP Layer

Introduction

Creating a custom BSP layer

Adding a custom kernel and bootloader

Building the U-Boot bootloader

Describing Linux's build system

Configuring the Linux kernel

Building the Linux kernel

Building external kernel modules

Debugging the Linux kernel and modules

Debugging the Linux kernel booting process

Using the kernel function tracing system

Managing the device tree

Debugging device tree issues

The Software Layer

The Software Layer

Introduction

Exploring an image's contents

Adding a new software layer

Selecting a specific package version and provider

Adding supported packages

Adding new packages

Adding data, scripts, or configuration files

Managing users and groups

Using the sysvinit initialization manager

Using the systemd initialization manager

Installing package installation scripts

Reducing the Linux kernel image size

Reducing the root filesystem size

Memory-based root filesystems

Securing the root filesystem

Releasing software

Analyzing your system for compliance

Working with open source and proprietary code

Application Development

Application Development

Introduction

Introducing toolchains

Preparing an SDK

Using the extensible SDK

Using the Eclipse IDE

Developing GTK+ applications

Using the Qt Creator IDE

Developing Qt applications

Describing workflows for application development

Working with GNU make

Working with the GNU build system

Working with the CMake build system

Working with the SCons builder

Developing with libraries

Working with the Linux framebuffer

Using the X Windows system

Using Wayland

Adding a web browser application

Adding Python applications

Integrating the Open Java Development Kit

Integrating Java applications

Integrating Node.js applications

Running Docker application containers

Debugging, Tracing, and Profiling

Debugging, Tracing, and Profiling

Introduction

Analyzing core dumps

Native GDB debugging

Cross GDB debugging

Using strace for application debugging

Using the kernel's performance counters

Using static kernel tracing

Using dynamic kernel tracing

Using dynamic kernel events

Exploring Yocto's tracing and profiling tools

Tracing and profiling with perf

Using SystemTap

Using LTTng

Using blktrace

Other Books You May Enjoy

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

3.8 (8)

5 star

69.2%

4 star

15.4%

3 star

7.7%

2 star

0%

1 star

7.7%

Exploring an image's contents

We have already seen how to use the build history feature to obtain a list of packages and files included in our image. In this recipe, we will explain how the root filesystem is built so that we are able to track its components.

Getting ready

When packages are built, they are classified inside the working directory of your project (tmp/work) according to their architecture. For example, on a wandboard-quad build, we find the following directories:

all-poky-linux: This is used for architecture-independent packages
cortexa9hf-vfp-neon-poky-linux-gnueabi: This is used for cortexa9, hard floating point packages
wandboard_quad-poky-linux-gnueabi: This is used for machine-specific packages; in this case, wandboard-quad
x86_64-linux: This is used for the packages that form the host sysroot

BitBake will build all the packages included in its dependency list inside its own directory.

How to do it...

To find the build directory for a given package, we can execute the following...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Embedded Linux Projects Using Yocto Project Cookbook

Search

Your notes and bookmarks