This page provides a listing of the Yocto Project machine configurations AMD releases for its evaluation and development platforms.

Table of Contents

Introduction

The Yocto Project is an open source community-driven build infrastructure hosted by the Linux Foundation. AMD is simplifying our embedded software build infrastructure by standardizing all embedded software build flows around native Yocto Project infrastructure.

Evaluation and Development Yocto Machine Configuration Layers

The table below provides a list of the Yocto machine configuration layers AMD releases for it’s evaluation and development platforms. For the most up-to-date information please consult the README.md file inside meta-xilinx-bsp.

PetaLinux Relationship to Yocto Project

PetaLinux has leveraged Yocto Project tooling as a backend since 2016 but the flows have not been identical. Below is a brief overview of the functional differences:

• PetaLinux packages are complete “starter projects” as BSP files. These files include not only source code but also nominal Vivado projects, pre-compiled boot firmware, and pre-compiled Linux kernel images and root filesystem configuration. Yocto Project depends on only a board-specific machine configuration that integrates with other standard Yocto Project collateral and tooling that are built-from source.

• PetaLinux uses a proprietary command set such as petalinux-config, petalinux-build, etc. whereas Yocto Project uses the standard bitbake command

• PetaLinux uses a different directory structure from Yocto Project for configuration files such as local.conf, *.bb, *.bbappend, etc.

• AMD does not provide back-porting of updates for PetaLinux BSP content. Yocto Project collateral (for example, a machine configuration) can be updated and integrated with newer Yocto Project tooling and software components for on-going maintenance or use in production environments.

Beginning with the 2024.1 release cycle, support for PetaLinux BSPs will be sunset over time in favor of native Yocto Project tooling. Not all boards will be migrated to Yocto Project infrastructure at once. Rather, AMD is migrating PetaLinux BSPs to standard Yocto Project infrastructure over time. For boards that have not yet been migrated to native Yocto infrastructure, please check for PetaLinux BSPs on the AMD Download Center.

Custom Boards and Boards without an Active Yocto Machine Configuration

For new designs (including all custom boards and evaluation boards without a pre-built Yocto machine configuration), AMD recommend that designers use the open source system device tree (SDT) and Yocto Project tooling to build custom infrastructure for the target board.

1. Automated Yocto machine configuration generation - GitHub - Xilinx/gen-machine-conf: Parse hardware design information to generate project specific machine configuration

2. System Device Tree Generator (SDTGen) - Xilinx/system-device-tree-xlnx (github.com)

3. Lopper - devicetree-org/lopper (github.com)

Deprecated BSP support in PetaLinux

Manual flows are also available to enable deprecated BSP by migrating using an active BSP available in the latest PetaLinux version.

• The flow and the Deprecated BSP to Existing BSP Mapping is documented in UG1144 PetaLinux Tools Documentation : Reference Guide : Deprecated BSP Support ( from version 2024.1) available on the AMD Technical Information Portal

• Steps to migrate the existing BSP to support the deprecated BSPs are outlined in the BSP "README" file in section "Steps to migrate BSP < BSP name>". Users should extract the existing BSP to follow migration steps from README file
  
  

Related Links

• Yocto Project machines files (inside meta-xilinx)

• PetaLinux-to-Yocto Command Cross Reference

• Moving from PetaLinux to Production Deployment

• Yocto Project Mega-Manual (root)

• Yocto Project Reference Manual

• Yocto Project BSP Developer’s Guide

• Yocto Project Development Tasks Manual