This page cover release notes for Yocto Project related meta layers such as meta-xilinx, meta-xilinx-tools, meta-jupyter and so on.

Table of Contents

Release 5.0.4 (Scarthgap)

New Features or Enhancements in Scarthgap (5.0.4)

Upstream features in 5.0.4

• Refer Yocto Project Scarthgap (5.0.4) release notes page https://docs.yoctoproject.org/5.0.4/migration-guides/index.html

AMD features in 5.0.4

• Refer to 2024.2 Release Notes for Open Source Components

• meta-xilinx:

  General:

  • Merge in 2024.2 support

  • Update gen-machine-conf to 2024.2 version

  • Update README files

  • Update layer dependencies

  • For the system device-tree workflow, the layer meta-xilinx-experimental has been replaced by meta-xilinx-standalone-sdt

• meta-microblaze:

  • Microblaze binutils has been rebased to Scarthgap binutils

  • Microblaze GCC has been rebased to Scarthgap gcc-13

  • Microblaze GDB has been rebased to Scarthgap gdb

  • Microblaze newlib has been rebased to Scathgap newlib

• meta-vitis-tc:

  • New layer which is used to configure and build Vitis specific multilib toolchains

• meta-xilinx-bsp:

  • Deprecated - this layer will go away at some point

  • Only a single FSBL bbappend remains that will be moved, leaving this layer empty in the future

  • XSCT based BSPs have been moved to meta-xilinx-tools

• meta-xilinx-contrib:

  • minor updates for ml605-qemu-microlbazeel

• meta-xilinx-core:

  • Now depends on meta-arm (and thus meta-arm-toolchain) for the trusted-firmware-a recipe

  • HDF_MACHINE is no longer used, see meta-xilinx-tools

  • Add cortexa9 as a known tune for Zynq7

  • XRT has been updated, aie is now enabled by default for all aarch64 configurations

  • Included '-generic' machines are designed to be inherited, not used directly. See meta-xilinx-tools for qemu information.

  • Introduce new 'common' machines:

    • zynq-common

    • zynqmp-common

    • zynqmp-mali-common

    • versal-common

    • versal-net-common

    The common machines are designed to build an OS (not firmware components) that should work across the breadth of the individual SoC family. Note with and without the proprietary Mali400 library are not runtime compatible, thus two different configurations for zynqmp. For an SoC with various MACHINE_FEATURES, consider these to be supersets where the unsupported features should fail gracefully at runtime, with the known exception of the mali400 library.

• meta-xilinx-demos:

  • New layer

  • Include various demonstration and example applications moved from other layers

• meta-xilinx-mali400:

  • New layer

  • Includes all mali400 related components and changes for ZynqMP EV and EG

  • Be sure to check the README.md for usage information

• meta-xilinx-multimedia:

  • New layer

  • Includes all of the multimedia related components including VCU and VDU support

• meta-xilinx-standalone:

  • Introduce XILINX_WITH_ESW to select how the embeddedsw components will be built.

  • xilinx-standalone distributions disabled 'buildpaths' QA warning.
    Dynamic replacement of build paths is known to not work on most baremetal configurations.

  • Add RFSoC exampes and related components

  • All baremetal configurations now get --disable-tm-clone-registry

• meta-xilinx-standalone-sdt:

  • Previously meta-xilinx-experimental

  • Implementes the System Device-Tree workflow for firmware and baremetal components

  • Layer (bbappends) are only enabled if XILINX_WITH_ESW is set to 'sdt'

• meta-xilinx-vendor:

  • Removed ultra96 (v1) no longer supported, See AvNet for Ultra96v2 information

• meta-xilinx-virtualization:

  • New layer

  • Move all virtualization related items to this layer

• meta-xilinx-tools:

  • Large amount of restructuring to include the machines that used to be in meta-xilinx-bsp

  • All machine files were regenerated with the current version of gen-machine-conf

  • All machine files now include the specific xsct (vivado) version they are associated with
    machines should set XILINX_XSCT_VERSION to select the correct toolset

  • Layer (bbappends) are only enabled if XILINX_WITH_ESW is set to 'xsct'

  • All machine files now contain the URL reference to their XSA file.

    • Obsolete HDF_BASE, HDF_PATH, HDF_NAME, HDF_MACHINE

    • Introduce HDF_URI and HDF_URI[sha256sum]

  • Machine files for various Vivado versions are included, referencing the version-less machine file will use XILINX_XSCT_VERSION to select the correct one to use

  • All machines were automatically generated with items from the 'scripts' directory, this can be used as a guide for making changes or create custom machines

  • XSCT download is now controlled and managed by a recipe, xsct-native

• meta-amd-adaptive-socs:

  • New repository

• meta-amd-adaptive-socs-core:

  • New layer

  • Intended to contain board specific components relating to SDT workflow (currently empty)

• meta-amd-adaptive-socs-bsps:

  • New layer

  • Contains reference boards created by the SDT (System Device-tree) workflow

  • See the 'scripts' directory for how these files are generated

Known Issues and Limitations in Scarthgap (5.0.4)

Upstream

• See https://git.yoctoproject.org/poky/tree/documentation/migration-guides/release-notes-5.0.4.rst?h=scarthgap#n6 CVE patches are applied by the YP community.

• meta-ros2-jazzy hardware-interface fails to build with Scarthgap, See meta-ros2-jazzy hardware-interface fails to build with Scarthgap · Issue #1219 · ros/meta-ros

AMD

• pl fw files doesn't install on rootfs using dfx_user_dts bbclass

• PACKAGECONFIG warnings are observed in SDT builds(Full Bitstream loading, Segmented Config and DFx designs) and all the images are generated properly. These warnings can be ignored safely as there is no functional issue.