Kria SOMs & Starter Kits
The purpose of this page is to provide developers with information and links to collateral available for the Kria Production SOMs and Starter Kits, including documentation, pre-built images, firmware updates, and GitHub repositories. It is meant to augment other official documentation found at the Kria SOM product page at amd.com.
Table of Contents
- 1 Kria Platforms Overview
- 1.1 Production SOMs
- 1.2 Starter Kits
- 1.2.1 KV260 Starter Kit
- 1.2.2 KR260 Starter Kit
- 1.2.3 KD240 Starter Kit
- 1.3 Kria Product Summary
- 2 Getting Started
- 3 Developer Resources
- 3.1 K26 Documentation
- 3.2 K24 Documentation
- 3.3 Kria Shared Documentation
- 3.4 Starter Kit Pre-Built Software
- 3.4.1 K26 Starter Kit Linux
- 3.4.1.1 Ubuntu LTS
- 3.4.1.2 K26 Embedded Linux (Yocto)
- 3.4.1.3 K26 PetaLinux
- 3.4.2 K26 Boot Firmware Updates
- 3.4.3 K24 Starter Kit Linux
- 3.4.3.1 Ubuntu Server LTS
- 3.4.3.2 K24 Embedded Linux (Yocto)
- 3.4.4 K24 Boot Firmware Updates (Yocto)
- 3.4.1 K26 Starter Kit Linux
- 3.5 On-Target Utilities
- 3.6 Boot FW Update Process
- 3.7 Boot FW QSPI Memory Map
- 3.8 Bitstream Management
- 3.9 Fan Control
- 3.10 PetaLinux & Ubuntu LTS
- 4 AMD-Xilinx Tools Support
- 4.1 Yocto Build instructions
- 4.2 PetaLinux Board Support Packages
- 4.2.1 K26 Platforms
- 4.2.2 K24 Platforms
- 4.2.3 PetaLinux Tools Release Notes
- 4.2.3.1 PetaLinux 2023.1 Release
- 4.2.3.2 PetaLinux 2022.1 Release
- 4.2.4 PetaLinux Build instructions
- 4.2.5 Regenerating boot firmware from BSP
- 4.3 Yocto Vs PetaLinux Support and Released Artifacts
- 4.4 Vivado Board Support Packages
- 4.4.2 SOM XDC Files
- 5 Kria Evaluation & Applications
- 6 Custom & Production SOM Design Guidance
- 6.1 Hardware
- 6.1.1 K26 Devices
- 6.1.2 K24 Devices
- 6.1.3 K26 Qualification Data
- 6.2 Firmware
- 6.2.1 MPSoC PMU FW
- 6.3 Linux
- 6.3.1 Fan Control
- 6.1 Hardware
- 7 Known Issues & Limitations
- 7.1 All Starter Kits
- 7.2 Ubuntu
- 7.3 K24 & KD240 Starter Kit
- 7.4 KR260 Starter Kit
Kria Platforms Overview
Xilinx Kria is a portfolio of System-On-Modules (SOMs) designed for edge applications in a variety of use cases and production settings. The K26 and K24 SOMs are meant to be integrated directly into a customers production design and the SOM Starter Kit (e.g. KV260, KR260, KD240) are an evaluation and early development platform. The Kria lineup simplifies and accelerates the system development, helping you get your product to market faster.
Production SOMs
K26
The K26 system-on-module (SOM) is a production ready hardware platform. The K26 SOM is shipped without any preloaded FW or SW configurations in the non-volatile memory devices (QSPI and eMMC). The K26 SOMs do not include ECC support.
K24
The K24 system-on-module (SOM) is a production ready hardware platform. The K24 SOM is shipped without any preloaded FW or SW configurations in the non-volatile memory devices (QSPI and eMMC). The I-grade K24 SOM includes ECC support while the C-grade K24 SOM does not.
Starter Kits
Kria Starter Kits are intended to be used for initial evaluation and early development platform for the K26 and K24 SOM. They consist of either a K26 or K24 SOM coupled with an application focused carrier card. The Kria Starter Kits are shipped with a pre-loaded boot FW stored in the QSPI non-volatile memory device and a preset boot mode configuration of QSPI32. Details on QSPI memory configuration and content are outlined below. A pre-built Kria Starter Kit Linux image is provided for each SOM variant set of Starter Kits. Pre-built applications are then made available over-the-air (OTA) via Linux package feeds. Details on the Kria Starter Kit Linux images and example applications are outlined below.
KV260 Starter Kit
The KV260 is an evaluation kit based on the K26 SOM focused on vision applications. There are two revisions of KV260. The main functional difference is that KV260 rev2 enables auto focus for IAS sensors. Refer to UG1089 Interfaces chapter for more information.
KV260 V1 |
|
---|---|
KV260 V1 Starter Kit | KV260 V2 Starter Kit |
KV260 V1 Starter Kit Interfaces | KV260 V2 Starter Kit Interfaces |
KR260 Starter Kit
The KR260 is an evaluation kit based on the K26 SOM focused on robotics and machine vision applications.
KD240 Starter Kit
The KD240 is an evaluation kit based on the K24 SOM focused on electric drives and motor applications.
Kria Product Summary
As outlined on this page there are variants of production and corresponding starter kit SOMs. The starter kits are built with SOMs that are component/part population only variants of the production SOM. The following table summarizes the key functional difference in the Kria product variants.
Module | eMMC Populated | Thermal Solution | Temperate Range |
K26 Production SOM - C Grade | Yes | Heat spreader plate | 0C to 85C |
K26 Production SOM - I Grade | Yes | Heat spreader plate | -40C to 100C |
K24 Production SOM - C Grade | Yes | Heat spreader clam shell | 0C to 85C |
KV260 Starter Kit SOM | No | Fansink | 0C to 35C |
KR260 Starter Kit SOM | No | Fansink | 0C to 35C |
KD240 Starter Kit SOM | No | Passive heat sink | 0C to 35C |
Getting Started
First time Kria Starter Kit users should refer to the on-line “Getting Started” guide for their kit:
Developer Resources
The following section provides links to the product documentation, pre-built firmware and software binaries, and application examples.
The Kria adventure map is a map of links to help users discover useful documentation according to their evaluation stages.
Additional technical assets and resources such as 3D CAD model, bill of materials, carrier schematic, carrier PCB layout and schematic source files can be accessed in the Carrier Card Design Resources section of the following Kria Starter Kit product pages:
K26 Documentation
K24 Documentation
Kria Shared Documentation
Starter Kit Pre-Built Software
The Kria Starter Kits use a two stage boot process. The primary boot firmware is pre-installed at the factory on the QSPI device. The secondary boot device is an SD card containing the Linux kernel and Linux root filesystem (rootfs). The Starter Kit pre-built FW and SW are aligned with their specific Starter Kits. The K26 and K24 Starter Kit SD card images are available in the tables below. When using pre-built applications from the Xilinx App Store you need to ensure to align your Starter Kit Linux version with the target application assumed Linux version.
The K26 based Starter Kits are supported with Ubuntu Desktop 22.04 and the K24 Starter Kits are supported with Ubuntu Server 22.04. The configurations between the two Ubuntu OS are primarily the same with the primary functional difference being the inclusion of the desktop GUI.
K26 Starter Kit Linux
The K26 Kria Starter Kits supported with Ubuntu Desktop 22.04 for the initial out-of-box support and example applications. An embedded Linux built within Yocto is also provided as a reference implementation for customers intending to target a custom embedded Linux during evaluation and production. Each Starter Kit also has a corresponding PetaLinux BSP. The Ubuntu Desktop 22.04 is the primary OS targeted by the KV260 and KR260 pre-built applications and out of box workflows.
Ubuntu LTS
The following table outlines the Ubuntu images available for the Kria Starter Kit. For additional details on the Ubuntu support for Kria see the Xilinx Ubuntu Wiki. Kria Ubuntu default login:
Username: ubuntu
Password: ubuntu (Will be prompted to change on first login)
Kira Starter Kit users of Ubuntu 22.04 LTS should update their boot FW to the recommended version in the table below to ensure full platform functionality.
Legacy KV260 kits REQUIRE the 2022.1 boot FW update prior to booting Ubuntu 22.04. Update should be completed with your current Linux image or via the Boot Image Recovery tool.
Starter Kit Ubuntu Image | Description | Kits Supported | Recommended FW | Download Link |
---|---|---|---|---|
Ubuntu Server 24.04 | Kria K26 and K24 unified Starter Kit Ubuntu Server 24.04 image | KV260, KR260, KD240 | 01.02 K26 Boot FW Update or later | |
Ubuntu Desktop 22.04 LTS | Kria K26 Starter Kit Ubuntu Desktop 22.04 image | KV260, KR260 | 2022.1 K26 Boot FW Update or later, except bootfw 1.04 |
Kria Ubuntu 22.04 LTS has the following known limitations:
Suspend/resume functionality is not supported including Ethernet wake-on-LAN (WOL)
Audio playback on DisplayPort occasionally produces a “clicking” noise in concert with actual audio playback
KV260: Legacy boot FW (2021.1) will not boot the Ubuntu 22.04 image. Upgrade to 2022.1 Boot FW prior to loading Ubuntu 22.04 image.
KR260 USB2.0 devices not functional on U46 interfaces. Upgrade to 2022.1 Boot FW.
Display port does not work on Ubuntu 22.04 + boot FW1.04 - use boot FW 1.02 instead.
K26 Embedded Linux (Yocto)
Starting with 2023.1 the Kria Starter Kits embedded Linux reference image has been built natively in Yocto to support users not using the Xilinx specific PetaLinux tool. The Kria Yocto reference image is built to support multiple platforms while the PetaLinux BSPs only support a single static HW configuration. Thus you will find a Yocto reference image that supports both K26 Starter Kits (KV260, KR260), while PetaLinux has a 1-to-1 mapping of BSPs to individual platforms. For additional details on Kria platform Yocto support see the Kria App Dev Guide. For details on Yocto vs PetaLinux support for Kria, refer to Kria SOMs & Starter Kits | Yocto Vs PetaLinux Support and Released Artifacts.
Yocto image default login for 2024.2 and older:
Username: petalinux
Password: Will be prompted to change on first login
Yocto image default login for 2025.1 and newer:
Username: amd-edf
Password: Will be prompted to change on first login
K26 Starter Kit Yocto Image | Description | Kits Supported | Recommended FW | Download Link |
---|---|---|---|---|
Kria generic Starter Kit embedded Linux 2025.1 | Kria Starter Kit embedded Linux with amd-edf login | KV260, KR260, KD240 | 01.04 K26 Boot FW Update or later | |
Kria generic Starter Kit embedded Linux 2024.2 | Kria Starter Kit embedded Linux | KV260, KR260, KD240 | 01.02 K26 Boot FW Update or later | |
Kria K26 Starter Kit embedded Linux 2023.2 | Kria K26 Starter Kit embedded Linux | KV260, KR260 | 01.02 K26 Boot FW Update or later | |
Kria K26 Starter Kit embedded Linux 2023.1 | Kria K26 Starter Kit embedded Linux | KV260, KR260 | 2023.1 K26 Boot FW Update or later |
K26 PetaLinux
The following table outlines the PetaLinux based pre-built Linux images. Default login:
Username: petalinux
Password: Will be prompted to change on first login
K26 Starter Kit PetaLinux Image | Description | Kits Supported | Recommended FW | Download Link |
---|---|---|---|---|
Kria K26 Starter Kit 2022.1 | 2022.1 PetaLinux Starter Kit Linux pre-built SD card image | KV260, KR260 | 2022.1 K26 Boot FW Update | |
Kria K26 Starter Kit 2021.1 | 2021.1 PetaLinux Starter Kit Linux pre-built SD card image | KV260 | 2021.1 K26 Boot FW Update 2 or later | |
Kria K26 Starter Kit 2020.2.2 | 2020.2.2 PetaLinux Starter Kit Linux pre-built SD card image | KV260 | 2020.2.2 K26 Boot FW Update or later |
PetaLinux Images SD Card Boot “Update”
After initial boot of a new SD card image it is best practice to execute sudo dnf update (PetaLinux) or sudo apt update (Ubuntu) in order to update core utilities that may have been released following the SD card image release.
In some scenarios it may be required to clean the local dnf cache first. To do so execute sudo dnf clean all
With 2021.1 package feeds when doing dnf update you will see a number packages that are flagged for update but are only revision metadata updates. You do not need to install these dnf tracked changes, but if you do it will only update/align the associated revision information.
K26 Boot Firmware Updates
K24 Starter Kit Linux
The K24 Kria Starter Kits supported with Ubuntu Server 22.04 for the initial out-of-box support and example applications. An embedded Linux built within Yocto is also provided as a reference implementation for customers intending to target a custom embedded Linux during evaluation and production. Each Starter Kit also has a corresponding PetaLinux BSP. The Ubuntu Server 22.04 is the primary OS targeted by the KD240 pre-built applications and out of box workflows.
Ubuntu Server LTS
The following table outlines the Ubuntu images available for the K24 Kria Starter Kit. For additional details on the Ubuntu support for Kria see the Xilinx Ubuntu Wiki. Kria Ubuntu default login:
Username: ubuntu
Password: ubuntu (Will be prompted to change on first login)
Starter Kit Ubuntu Image | Description | Kits Supported | Recommended FW | Download Link |
---|---|---|---|---|
Ubuntu Server 24.04 | Kria K26 and K24 Starter Kit unified Ubuntu Server 24.04 image | KV260, KR260, KD240 | 01.02 K24 Boot FW Update or later | |
Ubuntu Server 22.04 LTS | Kria K24 Starter Kit Ubuntu Server 22.04 image | KD240 | 2023.1 K24 Boot FW Update or later |
Known issue:
on certified Ubuntu 22.04 kd05, RS485 driver is not present as it is in the process of being upstreamed. It is still available on Ubuntu 22.04 kd03 version
K24 Embedded Linux (Yocto)
The K24 Kria Starter Kits embedded Linux reference image has been built natively in Yocto to support users not using the Xilinx specific PetaLinux tool. The Kria Yocto reference image is built to support multiple platforms while the PetaLinux BSPs only support a single static HW configuration. Thus you will find a Yocto reference image that supports both K24 Starter Kits (KD240), while PetaLinux has a 1-to-1 mapping of BSPs to individual platforms. For additional details on Kria platform Yocto support see the Kria App Dev Guide. For additional details on Kria platform Yocto support see the Kria App Dev Guide. For details on Yocto vs PetaLinux support for KRia, refer to Kria SOMs & Starter Kits | Yocto Vs PetaLinux Support and Released Artifacts.
Yocto image default login for 2024.2 and older:
Username: petalinux
Password: Will be prompted to change on first login
Yocto image default login for 2025.1 and newer:
Username: amd-edf
Password: Will be prompted to change on first login
K24 Starter Kit Yocto Image | Description | Kits Supported | Recommended FW | Download Link |
---|---|---|---|---|
Kria generic Starter Kit embedded Linux 2025.1 | Kria Starter Kit embedded Linux with amd-edf login | KV260, KR260, KD240 | 01.04 K24 Boot FW Update or later | |
Kria generic Starter Kit embedded Linux 2024.2 | Kria Starter Kit embedded Linux | KV260, KR260, KD240 | 01.02 K24 Boot FW Update or later | |
Kria K24 Starter Kit embedded Linux 2023.2 | Kria K24 Starter Kit embedded Linux | KD240 | 01.02 K24 Boot FW Update or later | |
Kria K24 Starter Kit embedded Linux 2023.1 | Kria K24 Starter Kit embedded Linux | KD240 | 2023.1 K24 Boot FW Update or later |
Known issue:
RS485 Driver is not integrated in PetaLinux 2023.2, refer to AR000035701 for more information.
K24 Boot Firmware Updates (Yocto)
On-Target Utilities
The Kria runtime software provides a number of platform management helper utilities available under a common wrapper called “xmutil”. The following table summarizes these utilities which can be called using “xmutil <utility name>” in both Starter Kit Linux OS variants available. Use the -h or help functions with each utility to get detailed use instructions. Using sudo is required with many of the xmutil functions. The utilities and procedures are the same for all Kria Starter Kits.
Utility Name | Description |
---|---|
xmutil boardid | Reads all board EEPROM contents. Prints information summary to command line interface. |
xmutil bootfw_status | Reads primary boot device information. Prints A/B status information, image IDs, and checksums to command line interface. |
xmutil bootfw_update | Tool for updating the primary boot device with a new boot image in the inactive partition. |
xmutil getpkgs | Queries Xilinx package feeds and provides a summary to the debug interface of relevant packages for the active platform based on board ID information. NOTE: This functionality is not supported in Kria Ubuntu. |
xmutil listapps | Queries on the target hardware resource manager daemon of pre-built applications that are available on the platform and provides a summary to the debug interface. |
xmutil loadapp | Loads the integrated HW+SW application inclusive of the bitstream, and starts the corresponding pre-built application software executable. |
xmutil unloadapp | Removes accelerated application inclusive of unloading its bitstream. |
xmutil xlnx_platformstats | Reads and prints a summary of the following performance related information: CPU frequency, RAM usage, temperature, and power information. NOTE: The PS APB-DRP access to PL SysMon access is assumed by this utility. If PL SysMon access is not available the PL Temperature will read -280C. See this section of UG1085 for details on configurations that change PS to PL SysMon access. |
xmutil ddrqos | Utility for changing configuration of PS DDR quality of service (QoS) settings. Initial implementation focuses on PS DDR memory controller traffic class configuration. |
xmutil axiqos | Utility for changing configuration of PS/PL AXI interface quality of service (QoS) settings. Initial implementation focuses on AXI port read/write priority configurations. |
xmutil pwrctl | Utility for PL power control and status |
xmutil desktop_disable | Disables the desktop environment NOTE: This functionality is not supported in Kria Ubuntu Server. |
xmutil desktop_enable | Enables the desktop environment NOTE: This functionality is not supported in Kria Ubuntu Server. |
xmutil dp_bind | Binds the display driver |
xmutil dp_unbind | Unbinds the display driver |
Boot FW Update Process
Boot FW QSPI Memory Map
The Kria Starter Kit boot mode pins are set for QSPI boot mode. The xmutil and Boot Image Recovery tools provide a facility for updating one of the boot FW partitions of the QSPI device. If you desire to temporarily use a different boot mode for testing you must set the MPSoC BOOT_MODE_USER Register at 0xff5e0200 and issue a reset to override the board default.
The boot FW of the Kria Starter Kits is pre-loaded at time or production in the SOM QSPI memory. This device is intentionally isolated from the SD card to ensure that the board is always in a bootable state and SW developers can primarily focus on OS level updates and late bound loading of bitstreams. Sectors of the QSPI device are locked during production to prevent accidental overwrite in customer systems; with the only sectors that can be over-written are the A and B boot partitions discussed above and supported by the xmutil and Boot Image Recovery tools. The QSPI memory map and read/write access is defined in the following table.
Offset | Description | Access | Linux mtd |
---|---|---|---|
0x0 | Image Selector Application | R | 0 |
0x80000 | Image Selector Application - Fall back | R | 1 |
0x100000 | Persistent Register | R/W | 2 |
0x120000 | Persistent Register - Backup | R/W | 3 |
0x140000 | Reserved | - | 4 |
0x200000 | “Image A” - BOOT.BIN | R/W | 5 |
0xF00000 | Image Selector - Catch A | R | 6 |
0xF80000 | “Image B” - BOOT.BIN | R/W | 7 |
0x1C80000 | Image Selector - Catch B | R | 8 |
0x1D00000 | Reserved | - | 9 |
0x1E00000 | Boot Image Recovery Tool | R | 10 |
0x2000000 | Boot Image Recovery Tool- Backup | R | 11 |
0x2200000 | U-Boot Storage Variables | R/W | 12 |
0x2220000 | U-Boot Storage Variables - Backup | R/W | 13 |
0x2240000 | QSPI Image Version Information | R | 14 |
0x2280000 | Secure OS Storage | R/W | 15 |
0x22A0000 | User Space | R/W | 16 |
Bitstream Management
The Kria Starter Kits use a dynamic bitstream management practice to allow different application bitstreams to be swapped without rebooting the entire platform. The default behavior of Kria Starter Kits is that the platform is booted to Linux with no bitstream loaded. A daemon called dfx-mgr provides the infrastructure for tracking bitstreams that are on the file system and loading/unloading the different bitstreams and their device tree overlays. For details on dfx-mgr operation see: GitHub - Xilinx/dfx-mgr
A default bitstream is loaded after boot as part of the dfx-mgr startup, which bitstream is loaded is determined by the dfx-mgr daemon configuration file located in “/etc/dfx-mgrd/daemon.conf”. Kria Starter Kit Linux images include a default bitstream loaded is called “k2*-starter-kits” has no functional PL logic but provides an EMIO mapping to the carrier card fan control pin via an EMIO and enables the PL SysMon functionality. Removing this bitstream will effectively disable active fan control as the physical pin is no longer accessible to Linux.
Kria users can still make use of a boot time loaded bitstream as used in many legacy Xilinx workflows by generating a custom BOOT.BIN with their bitstream integrated. Details on using a “flat” (non-overlay design) with the PetaLinux Starter Kit BSPs is provided in the Kria App Dev Guide.
Fan Control
Starting with the 2022.1 images Kria Starter Kit pre-built software includes active fan control using the Linux fancontrol library which uses ZU+ PS TTC0 subsystem. The K26 Starter Kit fan pin is connected to PL pin HDA20 (physical pin A12) and thus in order to access it users need to ensure to provide an EMIO pin mapping between TTC0-Clk2 and HDA20. This is accounted for in the Xilinx generated platforms and reference bitstreams. If user wants to use the same fan control mechanism then they need to account for this EMIO mapping when generating their custom bitstream designs.
The KD240 Starter Kit ships with a passive heatsink but does have HW hooks for active fan control via J13 jumper on the KD carrier card if users want to add a 12V fan to their system. In K24 the fan control pin is connected to HDA08_CC PL pin.
PetaLinux & Ubuntu LTS
Running the shutdown command enables PetaLinux or Ubuntu to bring the system down in a manner that ensures file system disk writes complete before storage devices are unmounted. For best practice, the sudo shutdown -h now
command should be executed before removing power to the board. Since these embedded Linux implementations can make use of journaled file systems, which minimize the amount of data loss, an improper shutdown by removing power before devices are unmounted can trigger a lengthy automatic disk integrity check at next boot and result in longer than expected boot times on Starter Kits.
Kria is supported with both a pre-built Ubuntu LTS Linux image as well as being enabled within the PetaLinux development tool and Xilinx Yocto layers. The following table provides an summary of the intended scope that Ubuntu and PetaLinux have in the context of Kria SOM and Starter Kits, supporting the development life-cycle from initial out-of-box (OOB) evaluation to customer end product production.
| Ubuntu LTS | PetaLinux |
---|---|---|
Intent | Support of a great OOB experience with a desktop environment and a rich set of Linux libraries available and tested as part of the Ubuntu community. Intended initially as an evaluation and early development platform on Kria, it can also be used for production with Canonical's assistance. | Embedded Linux development tool focused on Xilinx silicon and device specific feature enablement via board support packages (BSPs) and pre-built reference(s). |
Updates | Kria Ubuntu OS is a Canonical certified OS that is supported with regular updates (e.g. security patches) from Canonical. A new LTS version of Ubuntu is provided every two years and each release is supported by Canonical for up to 10 years. | Snapshot image release aligned with Xilinx tools release (e.g. 2022.1) with no regular/planned updates until next Xilinx tools release (e.g. 2022.2). |
Pre-built apps | Kria example application final end-to-end verification and pre-built public release will be to the Ubuntu OS. | Kria example applications will build inside the PetaLinux tool but will not be fully verified nor released as pre-built packages. |
Application customization | User can customize userspace applications via on-target development and/or standard Ubuntu development tools/workflows. | User can customize userspace applications via on-target development and/or PetaLinux supported cross-compilation environment. |
Kernel customization | LTS certified kernel is maintained by Canonical. User can modify and build their own derivative kernel but is then outside the scope of the certified image and Canonical support. | Tool enables full customization of the kernel. |
Path to production | If user requires an officially certified and supported Ubuntu OS for their production system they must reach out to Canonical. Production systems are assumed to have custom hardware (carrier card or chip down). If any modifications to Ubuntu are needed to support custom hardware customers are encouraged to engage directly with Canonical to maintain certification. https://ubuntu.com/support Canonical has very strict rules about what can be labeled as Ubuntu - please see more here: https://ubuntu.com/legal/intellectual-property-policy | User can use the PetaLinux and or Yocto to create their own fully custom embedded Linux. |
Development Flow | On-target compilation. Cross-compilation. Sysroot provided by Canonical. | On-target compilation. Cross-compilation. Sysroot provided by Yocto eSDK - Tight integration with Vivado & Vitis tool sets. |
AMD-Xilinx Tools Support
Yocto Build instructions
Starting from 2023.1, there is Yocto support for Kria SOM Starterkits. Refer to Yocto Kria Support documentation for more information. There are support for generating .wic image, boot.bin or qspi images.
PetaLinux Board Support Packages
PetaLinux Board Support Packages (BSP) include pre-built images and a pre-defined configuration to rebuild the images from scratch.
In 2024.2 and prior, only XSCT flow is used to generate BSPs and Kria artifacts. in 2024.2, SDT flow is added and legacy XSDT flow continues to be supported during the transition period. Refer to this page for more details on the new SDT flow. in 2025.1 and newer, only SDT flow is supported.
K26 Platforms
The Kria K26 products are supported with three BSPs which are analogous to the “SOM” and “Starter Kit” hardware configurations outlined above. Be sure to use the BSP aligned with your selected tools version and target platform.
Product BSP | Description | BSP Download Link |
---|---|---|
KR260 Starter Kit | The KR260 Starter Kit SOM BSP implements a multi-domain (staged boot process) and application agnostic OS which is used to create their own custom boot FW (BOOT.BIN) and/or Linux image reference image. This BSP enables the same peripherals that are defined in the Vivado KR260 Starter Kit board file. | 2025.1 SDT flow - AMD download 2024.2 SDT flow - AMD download ========================== 2024.2 XSCT Flow - AMD download 2024.1 XSCT Flow - Xilinx download 2023.2 XSCT Flow - Xilinx download 2023.1 XSCT Flow - Xilinx download 2022.2 XSCT Flow - Xilinx download 2022.1 XSCT Flow - Xilinx download |
KV260 Starter Kit | The KV260 Starter Kit SOM BSP implements a multi-domain (staged boot process) and application agnostic OS which is used to create their own custom boot FW (BOOT.BIN) and/or Linux image reference image. This BSP enables the same peripherals that are defined in the Vivado KV260 Starter Kit board file. | 2025.1 SDT flow - Xilinx download 2024.2 SDT flow - Xilinx download ========================== 2024.2 XSCT flow - Xilinx download 2024.1 XSCT Flow - Xilinx download 2023.2 XSCT Flow - Xilinx download 2023.1 XSCT Flow - Xilinx download 2022.2 XSCT Flow - Xilinx download 2022.1 XSCT Flow - Xilinx download 2021.1 XSCT Flow - Xilinx download 2020.2.2 XSCT Flow - Xilinx download |
K26C/I Production SOM Applies to K26C/I SOM | The K26 Production SOM is a “starter” BSP configuration for customers beginning their production carrier card design. This BSP implements only the hardware peripherals implemented on the K26 SOM itself (e.g. DDR, QSPI, eMMC), with the exception of assuming the carrier card implements PS UART1 on MIO36-37. This BSP enables the same peripherals that are defined in the Vivado K26C and K26I SOM board files. The prebuilt wic image in this BSP is configured to run out of eMMC. Note: That the production SOMs are shipped with no content on the QSPI. See UG1091 for details on setting boot mode configurations during carrier card design. | 2025.1 SDT Flow - Xilinx download 2024.2 SDT Flow - Xilinx download ========================== 2024 XSCT flow - Xilinx download 2024.1 XSCT Flow - Xilinx download 2023.2 XSCT Flow - Xilinx download 2023.1 XSCT Flow - Xilinx download 2022.2 XSCT Flow - Xilinx download 2022.1 XSCT Flow - Xilinx download 2021.1 XSCT Flow - Xilinx download 2020.2.2 XSCT Flow - Xilinx download |
K24 Platforms
The Kria K24 product is supported with two BSPs which are analogous to the “SOM” and “Starter Kit” hardware configurations outlined above. Be sure to use the BSP aligned with your selected tools version and target platform.
Product BSP | Description | BSP Download Link |
---|---|---|
KD240 Starter Kit | The KD240 Starter Kit BSP implements a multi-domain (staged boot process) and application agnostic OS which is used to create their own custom boot FW (BOOT.BIN) and/or Linux image reference image. This BSP enables the same peripherals that are defined in the Vivado KD240 Starter Kit board file. | 2025.1 SDT flow - AMD download 2024.2 SDT flow - AMD download ========================= 2024.2 XSCT Flow - AMD download 2024.1 XSCT Flow - AMD download 2023.2 XSCT Flow - AMD download 2023.1 PLNX Update 1 XSCT Flow - AMD download |
K24C Production SOM | The K26C Production SOM is a “starter” BSP configuration for customers beginning their production carrier card design. This BSP implements only the hardware peripherals implemented on the K24 C grade SOM itself (e.g. LPDDR with ecc disabled, QSPI, eMMC), with the exception of assuming the carrier card implements PS UART1 on MIO36-37. This BSP enables the same peripherals that are defined in the Vivado K24C SOM board files. Note: That the production SOMs are shipped with no content on the QSPI. See UG1091 for details on setting boot mode configurations during carrier card design. | 2025.1 SDT flow - AMD download 2024.2 SDT flow - AMD download ========================== 2024.2 XSCT Flow - AMD download 2024.1 XSCT Flow - AMD download 2023.2 XSCT Flow - AMD download 2023.1 PLNX Update 1 XSCT Flow - AMD download |
K24I Production SOM | The K26I Production SOM is a “starter” BSP configuration for customers beginning their production carrier card design. This BSP implements only the hardware peripherals implemented on the K24 I grade SOM itself (e.g. LPDDR with ecc enabled, QSPI, eMMC), with the exception of assuming the carrier card implements PS UART1 on MIO36-37. This BSP enables the same peripherals that are defined in the Vivado K24I SOM board files. Note: That the production SOMs are shipped with no content on the QSPI. See UG1091 for details on setting boot mode configurations during carrier card design. | 2025.1 SDT flow - AMD download 2024.2 SDT flow - AMD download ========================= 2024.2 XSCT Flow - AMD download 2024.1 XSCT Flow - AMD download 2023.2 XSCT Flow - AMD download
|
PetaLinux Tools Release Notes
PetaLinux 2023.1 Release
The Kria K26 platforms are supported in the original PetaLinux 2023.1 release, which can be found in PetaLinux 2023.1 tools download page.
The Kria K24 platforms require the PetaLinux “Update 1” tools package to be installed via the PetaLinux upgrade process to use the K24C and KD240 PetaLinux BSPs. See the PetaLinux upgrade instructions at this link.
PetaLinux 2022.1 Release
The Kria SOM is supported in the PetaLinux 2022.1 release through an eSDK update captured under the 2022.1 PetaLinux Update 1, you need to ensure you upgrade your PetaLinux 2022.1 installation prior to using the Kria Starter Kit 2022.1 BSPs.
In order to use the KV260 and KR260 Starter Kit 2022.1 BSPs you must first install the Update 1 package from the PetaLinux 2022.1 tools download page. Instructions on how to do the upgrade are captured in the PetaLinux Update 1 release notes. Later eSDK updates (e.g. Update 3) can also be applied to automatically pull in bug fixes included the later incremental eSDK update releases.
PetaLinux Build instructions
Building with PetaLinux tool is dependent on first having a proper PetaLinux install aligned with the BSP version being used. See PetaLinux user guide (UG1144) for install requirements and instructions. Most Kria BSPs are release asynchronous to the main tools release and require an eSDK update prior to building with the corresponding Kria BSP. See the Kria PetaLinux BSP table above for guidance.
Note the instructions below are examples and should be adjusted for your specific HW configuration. A given dtb file may apply to a multiple board revisions, thus do not follow just the file name but use the “compatible” string of the corresponding dts file to identify which device tree file applies to a given board revision.
The following provide short-hand instructions for building a Kria BSP, which given the primary/secondary boot design requires special handling in steps #4 and #5 relative to non-primary/secondary boot platforms.
petalinux-create -t project -s <kria_starterkit>.bsp
cd <kria_starter_kit_petalinux_folder>
petalinux-build
petalinux-package --boot --u-boot --force
Final image packaging steps by platform
2023.2 for KV260, KR260, KD240:
KV260: petalinux-package --wic --images-dir images/linux/ --bootfiles "ramdisk.cpio.gz.u-boot,boot.scr,Image,system.dtb,system-zynqmp-sck-kv-g-revB.dtb"
KR260: petalinux-package --wic --images-dir images/linux/ --bootfiles "ramdisk.cpio.gz.u-boot,boot.scr,Image,system.dtb,system-zynqmp-sck-kr-g-revB.dtb"
KD240: petalinux-package --wic --images-dir images/linux/ --bootfiles "ramdisk.cpio.gz.u-boot,boot.scr,Image,system.dtb,system-zynqmp-sck-kd-g-revA.dtb"
2022.1, 2022.2, 2023.1:
KV260: petalinux-package --wic --images-dir images/linux/ --bootfiles "ramdisk.cpio.gz.u-boot,boot.scr,Image,system.dtb,system-zynqmp-sck-kv-g-revB.dtb" --disk-name "mmcblk1"
KR260: petalinux-package --wic --images-dir images/linux/ --bootfiles "ramdisk.cpio.gz.u-boot,boot.scr,Image,system.dtb,system-zynqmp-sck-kr-g-revB.dtb" --disk-name "sda"
KD240 ( 2023.1 only) : petalinux-package --wic --images-dir images/linux/ --bootfiles "ramdisk.cpio.gz.u-boot,boot.scr,Image,system.dtb,system-zynqmp-sck-kd-g-revA.dtb" --disk-name "sda"
2020.2 & 2021.1 BSPs (KV260 only): petalinux-package --wic --bootfiles "ramdisk.cpio.gz.u-boot boot.scr Image system.dtb"
Regenerating boot firmware from BSP
After building PetaLinux, enter below command to generate a new BOOT.BIN. Note if only developing and adjusting Linux functionality a user does NOT need to update the BOOT.BIN of the target.
petalinux-package --boot --u-boot --force
© Copyright 2019 - 2022 Xilinx Inc. Privacy Policy