Downloads and Release Notes
For Yocto-related release notes see: Yocto Project related Release Notes
Important Information
AMD delivers embedded Linux for supported boards through the Embedded Development Framework (EDF), using Yocto Project machine configurations and System Device Tree (SDT) flows on a Linux host. Prebuilt images are ready-to-run outputs for supported boards; EDF does not use downloadable BSP files, unlike PetaLinux. Refer to the Yocto Project Machine Configuration Support page for the current AMD support policy.
These prebuilt images, source code, and machine configurations target demonstration and evaluation use. Before production deployment, apply relevant security updates and provide an in-field update mechanism for the life of the product.
Supported Boards and Scope
This page covers published EDF artifacts for supported AMD evaluation boards across the Versal, Versal AI Edge Series Gen 2, and MicroBlaze V device families. The 26.06.1 update rebuilds a subset of the 26.06 release; for artifacts covering the device families it does not rebuild, use the 26.06 release notes.
Published images target the listed boards. Custom boards can use EDF build inputs and machine-configuration flows, but published prebuilt images are not guaranteed to boot unchanged on custom hardware.
Release Overview
Use the following table to jump to the download area that matches what you are trying to do.
Flow |
Description |
Go To Section |
|---|---|---|
Run on hardware |
Prebuilt boot firmware and common disk images for supported platforms; no build required. |
EDF Boot Firmware - OSPI Flash / SPI Boot Images / Common Disk Images |
Develop software |
Cross-compilation toolchain SDKs for application development. |
|
Emulate without hardware |
Prebuilt packages for booting supported platforms under QEMU. |
|
Flash boot assets |
Additional boot assets published outside the download tables. |
|
Build Your Own (Optional – Offline Builds) |
EDF source mirror and shared-state cache for offline builds. |
EDF Yocto Downloads and sstate-cache |
If your use case is not directly covered, start with Common Disk Images for evaluation or Application SDKs for application development.
EDF Boot Firmware - OSPI Flash
Board-specific EDF boot firmware that bundles the recovery
loader, the A/B update mechanism, and boot.pdi for flashing to board
OSPI storage. Combine these board-specific images with the common
disk images described in the sections that follow.
Lounge OSPI Images
Common Disk Images (WIC and BMAP)
Common disk images for use with board-specific EDF boot firmware. These images target a CPU family (for example, Cortex-A53 or Cortex-A78) and are not board-specific. Use them together with the EDF boot firmware images listed above.
Platform |
Device Family |
File Type |
Download Location |
Artifact Name |
Size |
MD5 Sum |
|---|---|---|---|---|---|---|
amd-cortexa72-common |
Versal |
SD WIC |
|
312 MiB |
4d226d9a59cb402778c2078ade2bc9f4 |
|
amd-cortexa72-common |
Versal |
SD WIC bmap |
|
3.76 KiB |
f16ab70b257f7e47b2f93258e8c5d39d |
|
amd-cortexa72-common |
Versal |
License & Sources |
|
4.94 GiB |
8491fe3c046f8404deadb66efc67d715 |
|
amd-cortexa78-mali-common |
Versal AI Edge Series Gen 2 |
UFS WIC |
|
334 MiB |
56c8cc5ae80442d08993fbdb4b56990a |
|
amd-cortexa78-mali-common |
Versal AI Edge Series Gen 2 |
UFS WIC bmap |
|
3.88 KiB |
2dc54873e360136ae5da2d4e2f487876 |
|
amd-cortexa78-mali-common |
Versal AI Edge Series Gen 2 |
SD WIC |
|
334 MiB |
fba234d8877ee59102b595054609d791 |
|
amd-cortexa78-mali-common |
Versal AI Edge Series Gen 2 |
SD WIC bmap |
|
3.76 KiB |
e25a823af019b2416731bcdf410d2bd2 |
|
amd-cortexa78-mali-common |
Versal AI Edge Series Gen 2 |
License & Sources |
|
4.97 GiB |
f85e79cae4f752c6f4c329f2372e9c07 |
SPI Boot Images (MCS and BIN)
MCS/BIN images provide a complete SPI boot solution for supported evaluation boards based on the MicroBlaze V RISC-V architecture. The images include all components required for booting the platform, including PDI, U-Boot SPL, U-Boot, Linux kernel, and root filesystem.
Note
SPI boot images for the SCU200 Rev A and SCU200 Rev B boards are available to select customers only. Contact your AMD Field Application Engineer (FAE) to request access.
Application SDKs
Cross-compilation toolchain SDKs for developing applications that target EDF-based Linux images. Each SDK is built for a specific CPU architecture. Install the SDK on your Linux host to cross-compile applications without building the full EDF image.
Platform |
File Type |
Download Location |
Artifact Name |
Size |
MD5 Sum |
|---|---|---|---|---|---|
amd-cortexa72 |
SDK Installer |
|
1.41 GiB |
ac778d41e580666376f3d3867b842342 |
|
License & Sources |
|
3.81 GiB |
80089df7a9a51990edc25ee04d7c345e |
||
amd-cortexa78-mali |
SDK Installer |
|
1.42 GiB |
42464041f47fc0490cb3a0c94840ac6a |
|
License & Sources |
|
3.83 GiB |
ecb7d4614afd6970a00dde3a97487cbf |
QEMU Prebuilt Packages
Use these packages to boot and test supported platforms in emulation without physical hardware.
Lounge QEMU Prebuilt
Note
QEMU prebuilt packages for the VRK160, VRK165, VPK360, and VEK386 boards are available to select customers only. Contact your AMD Field Application Engineer (FAE) to request access.
Boot Assets
Additional boot assets published outside the artifact download tables.
Note
Boot assets for the VRK160 Rev B, VRK165 Rev B, VPK360, and VEK386 boards are available to select customers only. Contact your AMD Field Application Engineer (FAE) to request access.
EDF Yocto Downloads and sstate-cache
Note
The Yocto downloads and sstate-cache are optional. Download them only if you need to build EDF offline or want to pre-populate the build cache locally. When building from a connected host, you do not need these artifacts: BitBake fetches sources and populates the shared-state cache automatically during the first build. Source Downloads and Shared State Cache explains both flows.
Name |
Download Location |
Artifact Name |
Size |
MD5 Sum |
|---|---|---|---|---|
downloads |
|
34.96 GiB |
2b4f14a61ebf5a55fcac2be5477556ac |
|
sstate-cache |
|
40.3 GiB |
ae30d753dbe43c5e2c1158f27cf96a57 |
Known Issues and Limitations
Linux/Bare-Metal |
Components |
Platform/SoC Supported |
Description |
Work-Around Article Link |
To be fixed version |
|---|---|---|---|---|---|
Supported Linux Host Distributions
The following table lists the Linux host distributions on which AMD supports building EDF v26.06 from source. Each row’s test priority is AMD’s internal verification priority for that host in the v26.06 release.
Test Priority |
OS |
Version |
Extended |
Notes |
|---|---|---|---|---|
High |
Ubuntu |
24.04.3 LTS |
No |
New host for the v26.06 release. |
Medium |
AlmaLinux |
9.4 |
No |
|
Medium |
AlmaLinux |
8.10 |
Yes |
|
Medium |
openSUSE Leap |
15.4 |
Yes |
AMD continues to validate Leap 15.4 even though the upstream Yocto Project Scarthgap release no longer sanity-tests any openSUSE Leap version. Leap 15.4 was sanity-tested when Scarthgap was first released; upstream has stopped testing Leap on later Scarthgap maintenance updates, which does not imply Leap stops working with those updates. |
Medium |
Rocky Linux |
9.6 |
No |
|
Medium |
Ubuntu |
22.04.5 LTS |
No |
Baseline used by the published “Yocto EDF Docker Build Image (Ubuntu 22.04)” container. |
Low |
Ubuntu |
22.04.4 LTS |
No |
|
Low |
Ubuntu |
22.04.3 LTS |
No |
Host Tool Requirements
Appearing in the preceding table means AMD validates the host. It
does not mean the distribution’s default packages are enough to
build EDF from source. The “Extended buildtools
Needed” column answers that per host. Yes means the build
needs the extended Yocto Project buildtools tarball installed
and sourced first; see
Prepare the Build Host Tools.
The AMD-provided EDF Docker build image is the alternative, since
that image already carries a conforming toolchain.
A Yes does not always mean a published version falls short. A
host can meet every Yocto Project minimum and still fail to
compile an individual native tool.
The Yocto Project publishes the current minimum versions and the tarball variants in Required Git, tar, Python, make and gcc Versions (Yocto Project Reference Manual, Scarthgap).
Not Supported
For the v26.06 release, AMD does not support building EDF on the following host families, regardless of version:
Microsoft Windows, including any Linux distribution running inside the Windows Subsystem for Linux (WSL)
Red Hat Enterprise Linux (RHEL). RHEL is not validated by AMD; AlmaLinux is the binary-compatible substitute in the preceding supported-distribution table.
SUSE Linux Enterprise Server (SLES)
Amazon Linux
For distributions that do appear in the preceding supported-distribution table, AMD only validates the specific point releases shown in that table. Other point releases of the same distribution are out of scope for the v26.06 host-distribution support matrix.
Upstream Yocto Project Sanity-Tested Distributions
EDF v26.06 builds on top of the Yocto Project
Scarthgap release. The upstream
Scarthgap SANITY_TESTED_DISTROS set covers extra
hosts (for example, Debian, Fedora, and CentOS Stream). Those
hosts can build EDF, but AMD does not validate them for
the v26.06 release. The Yocto Project publishes the
upstream lists in:
Release Information
Yocto Project Source Repositories
AMD-Controlled Layers
Component |
Location |
|---|---|
meta-amd-adaptive-socs |
https://github.com/Xilinx/meta-amd-adaptive-socs/tree/rel-v2026.1 |
meta-amd-edf |
|
meta-kria |
|
meta-vitis |
|
meta-xilinx |
|
meta-xilinx-tsn |
Imported Layers
Note
EDF v26.06 is based on the Yocto Project Scarthgap release.
The EDF v26.06 poky checkout is on the
scarthgapbranch at the upstreamyocto-5.0.16/scarthgap-5.0.16tag.DISTRO_VERSIONinmeta-poky/conf/distro/poky.confreads 5.0.15, not 5.0.16; this mismatch is not introduced by EDF.The Ahead / Behind counts are a release-day snapshot, measured against each upstream branch as it stood when this release was built. Upstream keeps moving afterwards, so the behind figure describes the release rather than the present day and is not recomputed between releases.
The Upstream Source column gives the canonical upstream repository for each layer, as identified from the OpenEmbedded Layer Index (https://layers.openembedded.org/). Two cases are worth noting:
For
meta-openampandmeta-jupyterthe Layer Index lists an AMD/Xilinx repository as the canonical upstream, so their Upstream Source and Location refer to the same project.For
pokyandmeta-openembeddedthe Layer Index registers the contained layers (meta-pokyandmeta-oerespectively); the Upstream Source points at the repository that contains them.
Component |
Location |
Upstream Source |
Upstream Branch |
Upstream Commit ID |
Ahead / Behind |
EDF’s Relationship to Upstream |
|---|---|---|---|---|---|---|
meta-arm |
scarthgap |
a81c19915b |
0 / 7 |
Snapshot of upstream scarthgap with no AMD-only commits; trails the upstream tip by 7 commits. |
||
meta-jupyter |
scarthgap |
5e47ac5efa |
1 / 0 |
Carries 1 AMD-only commit on top of the upstream scarthgap tip; upstream tip is fully contained. |
||
meta-mingw |
scarthgap |
bd9fef71ec |
0 / 3 |
Snapshot of upstream scarthgap with no AMD-only commits; trails the upstream tip by 3 commits. |
||
meta-openamp |
master |
bdbdb0b02a |
162 / 0 |
Upstream Xilinx meta-openamp has no scarthgap branch, so the upstream baseline is master frozen at commit bdbdb0b02a. EDF v26.06 carries 162 AMD-developed commits on top of that base. Treat this layer as AMD-managed rather than scarthgap-aligned. |
||
meta-openembedded |
https://github.com/Xilinx/meta-openembedded/tree/rel-v2026.1 |
scarthgap |
4d3e2639de |
0 / 290 |
Snapshot of upstream scarthgap with no AMD-only commits; trails the upstream tip by 290 commits. |
|
meta-qt5 |
scarthgap |
227cf5e7b6 |
0 / 0 |
Identical to upstream scarthgap tip. |
||
meta-ros |
scarthgap |
d149a6264d |
10 / 200 |
AMD fork that has diverged from upstream: 10 AMD commits on top of an older upstream scarthgap base, and missing 200 newer upstream commits (the upstream tip is not contained). |
||
meta-security |
scarthgap |
b13f1705d7 |
0 / 0 |
Identical to upstream scarthgap tip. |
||
meta-virtualization |
https://github.com/Xilinx/meta-virtualization/tree/rel-v2026.1 |
scarthgap |
6415d78637 |
17 / 21 |
AMD fork that has diverged from upstream: 17 AMD commits on top of an older upstream scarthgap base, and missing 21 newer upstream commits (the upstream tip is not contained). |
|
meta-zephyr |
scarthgap |
b1f6967a3f |
3 / 0 |
AMD fork ahead of upstream: contains the upstream scarthgap tip plus 3 commits. |
||
poky |
scarthgap |
1d54d1c473 |
0 / 621 |
Snapshot of upstream poky scarthgap with no AMD-only commits. Sits on the yocto-5.0.16 / scarthgap-5.0.16 tag; trails the upstream tip by 621 commits. |
System Software (SSW) Source Repositories
Component |
Branch |
Commit id |
URL |
Git Tag |
Upstream Version |
|---|---|---|---|---|---|
XRT |
2026.1 |
|
|||
zephyr-amd |
xlnx_rel_v2026.1 |
|
xilinx_v2026.1.1 |
||
linux-xlnx |
xlnx_rebase_v6.18_LTS |
|
xlnx_rebase_v6.18_LTS_2026.1.1 |
6.18_LTS |
|
u-boot-xlnx |
xlnx_rebase_v2026.01 |
|
xlnx-rebase-v2026.01_2026.1.1 |
2026.01 |
|
arm-trusted-firmware |
xlnx_rebase_v2.14_update1 |
|
xlnx-rebase-v2.14_2026.1.1 |
2.14 |
|
optee_os |
xlnx_rebase_v4.9.0 |
|
xlnx-rebase-v4.9.0_2026.1.1 |
4.9.0 |
|
optee_examples |
xlnx_rebase_v4.9.0 |
|
xlnx-rebase-v4.9.0_2026.1.1 |
4.9.0 |
|
optee_test |
xlnx_rebase_v4.9.0 |
|
xlnx-rebase-v4.9.0_2026.1.1 |
4.9.0 |
|
embeddedsw |
xlnx_rel_v2026.1.1 |
|
xilinx_v2026.1.1 |
||
qemu-devicetrees |
xlnx_rel_v2026.1.1 |
|
xilinx_v2026.1.1 |
||
qemu |
xlnx_rel_v2026.1.1 |
|
xilinx_v2026.1.1 |
||
xen |
xlnx_rebase_4.21 |
|
xlnx-rebase-v4.21_2026.1.1 |
4.21 |
|
mali-userspace-binaries |
xlnx_rel_v2024.2 |
|
xilinx_v2026.1.1 |
||
libmetal |
2026 |
|
xilinx_v2026.1.1 |
||
open-amp |
2026 |
|
xilinx_v2026.1.1 |
||
vcu-firmware |
master |
|
xilinx_v2026.1.1 |
||
vcu2-firmware |
master |
|
xilinx_v2026.1.1 |
||
vcu-ctrl-sw |
master |
|
xilinx_v2026.1.1 |
||
vcu2-ctrl-sw |
master |
|
xilinx_v2026.1.1 |
||
vcu-modules |
master |
|
xilinx_v2026.1.1 |
||
vcu2-modules |
master |
|
xilinx_v2026.1.1 |
||
vcu-omx-il |
master |
|
xilinx_v2026.1.1 |
||
vcu2-omx-il |
master |
|
xilinx_v2026.1.1 |
||
vdu-omx-il |
master |
|
xilinx_v2026.1.1 |
||
vdu-modules |
master |
|
xilinx_v2026.1.1 |
||
vdu-ctrl-sw |
master |
|
xilinx_v2026.1.1 |
||
vdu-firmware |
master |
|
xilinx_v2026.1.1 |
||
hdmi-modules |
master |
|
xilinx_v2026.1.1 |
||
hdmi21-modules |
master |
|
xilinx_v2026.1.1 |
||
dp-modules |
master |
|
xilinx_v2026.1.1 |
||
lopper |
xlnx_rel_v2026.1.1 |
|
xilinx_v2026.1.1 |
||
multimedia-notebooks |
xlnx_rel_v2026.1 |
|
xilinx_v2026.1.1 |
||
gstreamer |
xlnx-rebase-v1.22.12 |
|
xlnx-rebase-v1.22.12_2026.1.1 |
1.22.12 |
|
bootgen |
master |
|
xilinx_v2026.1.1 |
||
libdfx |
master |
|
xilinx_v2026.1.1 |
||
linux-examples |
xlnx_rel_v2026.1 |
|
xilinx_v2026.1.1 |
||
imagebuilder |
xlnx_rel_v2026.1 |
|
xilinx_v2026.1.1 |
||
dfx-mgr |
master |
|
xilinx_v2026.1.1 |
||
xmutil |
master |
|
|||
kria-dashboard |
xlnx_rel_v2026.1 |
|
|||
xlnx_platformstats |
master |
|
|||
linux-image_update |
master |
|
|||
image-selector |
main |
|
xilinx_v2026.1.1 |
||
image-recovery |
main |
|
xilinx_v2026.1.1 |
||
image-recovery-linux |
main |
|
xilinx_v2026.1.1 |
||
platform-management-notebooks |
xlnx_rel_v2023.2 |
|
xilinx_v2026.1.1 |
||
xlnx-board-id-data |
xlnx_rel_v2026.1 |
|
xilinx_v2026.1.1 |
||
aie-rt |
xlnx_rel_v2026.1 |
|
xilinx_v2026.1.1 |
||
kria-base-firmware |
xlnx_rel_v2023.1 |
|
xilinx_v2026.1.1 |
||
tsn-talker-listener |
main |
|
xilinx_v2026.1.1 |
||
tsn-utils |
main |
|
xilinx_v2026.1.1 |
||
isp-modules |
master |
|
xilinx_v2026.1.1 |
||
g78ae-userspace-binaries |
r54p1-12eac0 |
|
xilinx_v2026.1.1 |
||
malig78ae-kbase |
r54p1-12eac0 |
|
xilinx_v2026.1.1 |
||
malig78ae-arbitration |
r54p1-12eac0 |
|
xilinx_v2026.1.1 |
||
openamp-system-reference |
2026 |
|
xilinx_v2026.1.1 |
||
opencv_modules_xlnx |
main |
|
xilinx_v2026.1.1 |
||
amr |
master |
|
xilinx_v2026.1.1 |
||
OpenAMP-notebooks |
main |
|
|||
RAFT |
2026.1 |
|
|||
qemu-bootbin-helper |
main |
|
xilinx_v2026.1.1 |
||
scmi-server |
main |
|
xilinx_v2026.1.1 |
||
gen-machine-conf |
xlnx_rel_v2026.1 |
|
xilinx_v2026.1.1 |