Skip to content
June 2025 6 min read Release

eos-platform 1.0: One Toolchain, Every EoS Profile

After eighteen months of incremental releases, the eos-platform meta-distribution reaches 1.0 with stable APIs, a unified package manifest, and reproducible builds across all 52 supported boards.

What is eos-platform?

eos-platform is the meta-distribution layer that sits above the EoS kernel. It bundles the kernel, HAL drivers, system services (eDB, eIPC, eLogger, eNet), and the eApps runtime into a single versioned manifest. Before 1.0, each component had its own release cadence, making reproducible builds difficult. Now, a single manifest.yml pins every component to a tested combination.

Stable API surface

The 1.0 release freezes the public C API for all 14 modules (HAL, Kernel, Multicore, Crypto, OTA, Sensors, Motor, Filesystem, Power, Networking, Debug, Drivers, Services, Logging). Any code written against the 1.0 API will compile without changes on any future 1.x release. Breaking changes require a 2.0 bump.

Unified package manifest

The new manifest.yml format specifies the board target, kernel profile (minimal, standard, full), enabled services, and pinned app versions. ebuild reads this manifest and produces a deterministic firmware image. The same manifest checked into git produces the same binary on any CI machine.

Reproducible builds

All 52 board targets now produce bit-for-bit identical binaries when built from the same manifest and source tree. This is a prerequisite for the upcoming safety-certified profile (IEC 62443, ISO 26262 ASIL-B) where binary reproducibility is a compliance requirement.