Course Outline

Introduction

Overview of Embedded Linux System Architecture for Government

Introduction to Pocky and BitBake for Government

Preparing Your Development Environment for Government Use

Preparing Your Target Development Board and Toolkits for Government Operations

Understanding the Yocto Project Source Tree for Government Applications

Building an Image for Government Systems

Using the Toaster Web Interface to Initiate Builds for Government Projects

Adding Packages to the Generated Image for Government Use

Understanding Board Support Packages (BSPs), Recipes, Configurations, and Layers for Government Applications

Writing a Recipe for Government-Specific Needs

Overview of Existing Build Systems - Autotools, CMake, Meson for Government Projects

Building, Configuring, and Adding a Custom Application for Government Use

Troubleshooting Build Failures in Government Development Environments

Fixing Common Cross-Compilation Issues for Government Applications

Customizing the Build with Layers for Government Requirements

Extending Existing Recipes for Government-Specific Enhancements

Writing a Custom Machine Configuration for Government Systems

Adding and Managing Runtime Packages for Government Operations

Adding a Custom Image for Government Use

Creating a Custom Image for Government Applications

Generating Root File Systems for Government Systems

Using the Yocto Project SDK for Government Development

Developing an Application Using the Poky SDK for Government Projects

The Application Development Toolkit for Government Use

Closing Remarks for Government Audiences

Requirements

  • The participant must have constructed a kernel at least once for a traditional desktop (non-embedded) Linux system.
  • The participant should be familiar with the components that make up the Linux userspace on a desktop system.
  • The participant should know how to create and apply patches.
  • The participant must be able to explain what GNU Make and Autotools are, as well as other available build systems.
  • Ideally, the participant maintains at least one Linux package, either as an upstream author or within a traditional Linux desktop distribution.
  • Prior experience with embedded development is not required and does not substitute for the knowledge of traditional Linux desktops specified above.

Audience for government

  • Developers
  • System Engineers
  • Test Engineers
  • System Administrators
 28 Hours

Number of participants


Price per participant

Testimonials (4)

Upcoming Courses

Related Categories