/
Yocto Project related Release Notes

Yocto Project related Release Notes

Owned by Sandeep Gundlupet Raju (Unlicensed)
Last updated: Jan 08, 2025 by Kohn, Chris
6 min read

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)

AMD 2024.2 release is based on Scarthgap (5.0.4)

New Features or Enhancements in Scarthgap (5.0.4)

Upstream features in 5.0.4

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

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.

    WARNING: mc:microblaze-0-pmc:libxil-2024.1+gitAUTOINC+4b1aa02bd0-r0 do_configure: QA Issue: libxil: invalid PACKAGECONFIG: fpga-overlay [invalid-packageconfig] WARNING: mc:microblaze-0-psm:libxil-2024.1+gitAUTOINC+4b1aa02bd0-r0 do_configure: QA Issue: libxil: invalid PACKAGECONFIG: fpga-overlay [invalid-packageconfig]



Recipe License changes in Scarthgap (5.0.4)

This section is blank.

Recipe upgrades in Langdale Scarthgap (5.0.4)

  • 2024.2

    • Version 2024.2 has been added.

    • linux-xlnx 6.6.40 LTS

    • u-boot-xlnx 2024.01

Repos for Langdale Scarthgap (5.0.4)

meta-xilinx

meta-xilinx-tools

meta-jupyter

meta-amd-adaptive-socs

Release 4.1.4 (Langdale)

AMD 2023.2 and 2024.1 release is based on Langdale (4.1.4)

New Features or Enhancements in Langdale (4.1.4)

Upstream features in 4.1.4

AMD features in 4.1.4

Known Issues and Limitations in Langdale (4.1.4)

Upstream

  • Last CVE patches are applied by the YP community as of 04/28/2023 and no further CVE updates.

AMD

  • All the know issues and limitations are same as 4.1.2 except for PACKAGECONFIG warnings are observed in SDT builds.

Recipe License changes in Langdale (4.1.4)

This section is blank.

Recipe upgrades in Langdale (4.1.4)

  • 2023.2

    • Version 2023.2 has been added.

    • linux-xlnx 6.1.30 LTS

    • u-boot-xlnx 2023.01

  • 2024.1

    • Version 2024.1 has been added.

    • linux-xlnx 6.6 LTS

    • u-boot-xlnx 2024.01

Repos for Langdale (4.1.4)

meta-xilinx

meta-xilinx-tools

meta-jupyter

Release 4.1.2 (Langdale)

AMD 2023.1 release is based on Langdale (4.1.2)

New Features or Enhancements in Langdale (4.1.2)

Upstream features in 4.1.2

AMD Xilinx features in 4.1.2

  • Refer to 2023.1 Release Notes for Open Source Components

  • Initial support for Mesa LIMA drivers.

    • libmali is available but default is set to lima for Yocto Project distributions (without using meta-petalinux layer).

    • To enable libmali, set config variable in local.conf

      DISTRO_FEATURES:append:aarch64 = " libmali"

  • New tool called gen-machinceconf which accepts xsa as input and generates yocto bsp machine configuration file. Refer gen-machine-conf repo README for more details.

  • Instruction for creating a machine configuration file has been updated, Refer to https://github.com/Xilinx/meta-xilinx/blob/master/meta-xilinx-core/conf/machine/README

  • New docs directory for additional documentation, Refer https://github.com/Xilinx/meta-xilinx/docs

  • Renamed u-boot-zynq-scr recipe to u-boot-xlnx-scr

  • The default wic/wks file is provided in meta-xilinx/meta-xilinx-core/wic/xilinx-default-sd.wks

    • The default file uses ‘rootfs’, instead of ‘bootimg-partition’ for the /boot partition. This allows target package upgrade. ‘bootimg-partition’ is still supported.

    • The default file also uses --label boot. This ensures the constructed fstab will mount the correct partition(s).

  • Move AIE recipes from meta-xilinx-tools to meta-xilinx-core layer.

Known Issues and Limitations in Langdale (4.1.2)

Upstream

AMD Xilinx

  • Static Device Nodes error strings observed in systemd boot, This is due to xilinx_defconfig not including any configs which has static device nodes. Hence below warnings are expected and can be ignored safely.

[ 7.895663] systemd[1]: Create List of Static Device Nodes was skipped because of a failed condition check (ConditionFileNotEmpty=/lib/modules/6.1.5-xilinx-v2023.1/modules.devname).

  • Kernel Trace File System error strings observed in systemd boot, This is due to xilinx_defconfig not enabling tracing related configs. Hence below warnings are expected which can be ignored safely.

[ 7.851765] systemd[1]: Kernel Trace File System was skipped because of a failed condition check (ConditionPathExists=/sys/kernel/tracing).

  • ZynqMP SDT built images dont boot on HW when pl.dtsi is included in SDT. This is due to the bitstream not being packaged as part of boot.bin. To work around this issue specify the bitstream file after following README-setup by adding the below config variables in local.conf

BIF_BITSTREAM_ATTR = "bitstream" BIF_PARTITION_IMAGE[bitstream] = "${TOPDIR}/<PATH_TO_DIRECTORY>/project_1.bit" DEPENDS:remove:pn-xilinx-bootbin = "virtual/bitstream"

  • TMPDIR buildpath warnings are observed on several packages in both upstream and AMD Xilinx packages, These warnings can be ignored safely as there is no functional issue.

WARNING: wolfssl-5.5.2-r0 do_package_qa: QA Issue: File /usr/lib/libwolfssl.so.35.2.0 in package wolfssl contains reference to TMPDIR [buildpaths] WARNING: zocl-202310.2.15.0-r0 do_package_qa: QA Issue: File /lib/modules/6.1.5-xilinx-v2023.1/extra/zocl.ko in package kernel-module-zocl-6.1.5-xilinx-v2023.1 contains reference to TMPDIR [buildpaths]

  • PACKAGECONFIG warnings are observed in SDT builds and all the images are generated properly. These warnings can be ignored safely as there is no functional issue.

WARNING: mc:microblaze-0-pmc:libxil-2023.1_sdt_experimental+gitAUTOINC+4ab00f250f-r0 do_configure: QA Issue: libxil: invalid PACKAGECONFIG: qemu-usermode [invalid-packageconfig] WARNING: mc:microblaze-0-psm:libxil-2023.1_sdt_experimental+gitAUTOINC+4ab00f250f-r0 do_configure: QA Issue: libxil: invalid PACKAGECONFIG: qemu-usermode [invalid-packageconfig]

  • Using TCLIBC = "musl" in Yocto causes build failures - This is currently being investigated.

  • libMali doesn’t work with Weston 10.0, Refer AR 000035056

  • External media (USB keys) are auto-mounted with permissions which make them unavailable to the default petalinux user - users will need to su/sudo to root in order to access files on these devices.

  • When building an image using the MACHINE=smk-smk-k{v,r} machine configurations in Yocto for Kria, the resulting images do not contain the correct device-tree - users are advised to use the shared machine configuration MACHINE=k26-smk which will result in an image that can be booted on either the KV or KR board.

Recipe License changes in Langdale (4.1.2)

This section is blank.

Recipe upgrades in Langdale (4.1.2)

  • Version 2023.1 has been added.

  • linux-xlnx 6.1.30 LTS

  • u-boot-xlnx 2023.01

Repos for Langdale (4.1.2)

meta-xilinx

meta-xilinx-tools

meta-jupyter

Related content

© Copyright 2019 - 2022 Xilinx Inc. Privacy Policy