Course Outline

Introduction

Overview of Embedded Linux System Architecture for Government Use

Overview of Pocky and Bitbake for Government Projects

Preparing Your Development Environment for Government Applications

Preparation of Target Development Boards and Toolkits for Government Projects

Understanding the Yocto Project Source Tree for Government Use

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 Applications

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

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 Applications

Fixing Common Cross-Compilation Issues for Government Projects

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 Applications

Adding a Custom Image for Government Use

Creating a Custom Image for Government Projects

Generating Root Filesystems for Government Systems

Using the Yocto Project SDK for Government Development

Developing an Application Using the Poky SDK for Government Needs

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.
  • Understands the components that make up the Linux userspace on a desktop system.
  • Is proficient in generating and utilizing patches.
  • Can explain what GNU Make and Autotools are, as well as other available build systems.
  • Ideally, maintains at least one Linux package, either as an upstream author or within any traditional Linux desktop distribution.
  • Prior experience with embedded development is not necessary and does not substitute for the required 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