https://github.com/rugix/meta-rugix
Yocto layers and recipes for Rugix.
https://github.com/rugix/meta-rugix
embedded linux ota rugix yocto
Last synced: 5 months ago
JSON representation
Yocto layers and recipes for Rugix.
- Host: GitHub
- URL: https://github.com/rugix/meta-rugix
- Owner: rugix
- License: apache-2.0
- Created: 2025-04-10T19:04:02.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2026-01-31T11:08:03.000Z (5 months ago)
- Last Synced: 2026-01-31T23:34:22.351Z (5 months ago)
- Topics: embedded, linux, ota, rugix, yocto
- Language: BitBake
- Homepage: https://rugix.org
- Size: 33.2 KB
- Stars: 4
- Watchers: 1
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE-APACHE
Awesome Lists containing this project
README
# Rugix Yocto Layers
This repository provides Yocto layers for integrating [Rugix Ctrl](https://rugix.org/docs/ctrl) into a custom, [Yocto-based](https://www.yoctoproject.org) Linux distribution tailored to your embedded device.
Rugix Ctrl **enables secure and efficient over-the-air (OTA) updates and provides robust state management capabilities** designed to streamline the development and maintenance of embedded Linux devices at scale.
Rugix Ctrl is part of the [Rugix Project](https://rugix.org).
> [!WARNING]
> This repository is **work-in-progress and not intended for production use** at this time.
> We appreciate any feedback you may have regarding this Yocto integration.
> Feel free to [open an issue](https://github.com/silitics/meta-rugix/issues/new/choose).
Rugix Ctrl has all features you would expect from a state-of-the-art update solution and more:
- **Atomic A/B system updates** with popular bootloaders out of the box.
- **Streaming updates** as well as **adaptive delta updates** out of the box.
- Builtin **cryptographic integrity checks** _before_ installing anything anywhere.
- Supports **any update scenario**, including **non-A/B updates and incremental updates**.
- Supports **any bootloader and boot process** through [custom _boot flows_](https://rugix.org/docs/ctrl/advanced/boot-flows).
- **Robust state management mechanism** inspired by container-based architectures.
- Integrates well with [different fleet management solutions](https://rugix.org/docs/ctrl/advanced/fleet-management) (avoids vendor lock-in).
- Provides powerful interfaces to built your own update workflow upon.
Rugix Ctrl **supports or can be adapted to almost any requirements you may have** when it comes to robust and secure updates of your entire system as well as its individual components.
For details, check out [Rugix Ctrl's documentation](https://rugix.org/docs/ctrl) and the [documentation on the Yocto layers](https://oss.silitics.com/rugix/docs/ctrl/advanced/yocto-integration/).
## Getting Started
We provide [kas](https://github.com/siemens/kas)-based [examples](./examples/) to help you get started quickly.
## Provided Layers
The layer [`meta-rugix-core`](./meta-rugix-core/) provides everything required for installing Rugix Ctrl and building Rugix-compatible update bundles.
In addition the following board-specific layers are provided:
- [`meta-rugix-rpi-tryboot`](./meta-rugix-rpi-tryboot/): BSP layer for building Raspberry Pi images with [`tryboot`](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#fail-safe-os-updates-tryboot) support (official A/B update mechanism of Raspberry Pi). This requires a Raspberry Pi 4 (CM4, Raspberry Pi 400) or newer.
- [`meta-rugix-rpi-uboot`](./meta-rugix-rpi-uboot/): BSP layer for building Raspberry Pi images with U-Boot-based A/B updates. This is primarily meant as a reference implementation for U-Boot. If you have a newer Raspberry Pi model, use the `tryboot` integration.
The board-specific layers serve as **examples** for how to integrate Rugix Ctrl with specific boards.
Depending on your project and requirements, you may need to adapt those layers or write your own.
## ⚖️ Licensing
This project is licensed under either [MIT](https://github.com/silitics/rugix/blob/main/LICENSE-MIT) or [Apache 2.0](https://github.com/silitics/rugix/blob/main/LICENSE-APACHE) at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this project by you, as defined in the Apache 2.0 license, shall be dual licensed as above, without any additional terms or conditions.
---
Made with ❤️ for OSS by [Silitics](https://www.silitics.com)