yocto-kiss: updated to the Wrynose Yocto LTS release

meta-kissWe are pleased to announce that yocto-kiss, our minimal but realistic Yocto/OpenEmbedded reference setup, has been updated to the latest Wrynose Yocto LTS release (version 6.0). Following the addition of ZynqMP support and the move to a cleaner multi-layer architecture earlier this year, this update keeps the project aligned with the current Yocto LTS and brings several improvements we’d like to highlight.

What is yocto-kiss?

For those unfamiliar, yocto-kiss is a project that demonstrates the simplest yet fully functional Yocto/OpenEmbedded setup. It follows the KISS (Keep It Simple, Stupid) principle by providing a clean, well-organized layer structure that supports multiple boards while avoiding unnecessary complexity. The project currently supports four machines across TI, STMicroelectronics, NXP, and AMD/Xilinx architectures, each in its own BSP layer.

Updating to Wrynose

The move from Scarthgap (5.0) to Wrynose (6.0) represents two years of upstream evolution in the Yocto Project. You can find the full details of what’s new in the Wrynose release notes. The update involved migrating the distro layer (meta-kiss) and all four BSP layers (meta-kiss-ti, meta-kiss-st, meta-kiss-nxp, and meta-kiss-amd) to the new LTS. Notable changes include:

  • Make S relative to UNPACKDIR
  • Remove use of deprecated UBOOT_CONFIG syntax
  • Update to Linux 7.0 kernel
  • Use sysvinit instead of the new default (systemd)

You can read the full change in the pull request on GitHub.

See us at ELCE 2026 in Prague

We will be giving a talk at the Embedded Linux Conference Europe 2026 in Prague (October 7-9) titled:

Yocto BSP Layers: Breaking Free From Complexity
Mathieu Dubois-Briand & Köry Maincent, Bootlin
Friday, October 9, 09:50, South Hall 3 B

In this talk, we will examine common issues found in vendor-provided Yocto BSP layers and show how they introduce unnecessary complexity into embedded Linux projects. Much of what new users perceive as “Yocto complexity” actually comes from the design and maintenance practices used in vendor layers. Using yocto-kiss as a concrete example of a cleaner approach, we will demonstrate how layers can be organized to stay simple and maintainable — even as they scale to support multiple architectures.

If you are attending ELCE, come by our talk and say hello!

Try it yourself

The updated yocto-kiss project is available at github.com/bootlin/yocto-kiss. For example, to build for the BeagleBone Black board (codenamed dogbonedark in yocto-kiss):

kas build kas/kiss.yaml:kas/dogbonedark.yaml

As always, we welcome contributions, bug reports, and feedback. If you need help with your Yocto/OpenEmbedded setup, feel free to reach out to us.

Köry Maincent

Author: Köry Maincent

Köry Maincent is an embedded Linux and kernel engineer at Bootlin, which he joined in 2020.

Leave a Reply