Watch how the entire embedded OS ecosystem builds, tests, and deploys — from hardware design to production.
KiCad schematics & YAML board definitions analyzed by ebuild analyze to extract pin maps, peripheral configs, and memory layouts.
ebuild sdk --target raspi4 generates cross-compilation toolchain, sysroot, headers, and pre-built libraries.
eos (HAL + Kernel + Services) → libeos.a
eboot (Secure Bootloader) → libeboot.a
eai → libeai.a • eni → libeni.a • eipc → libeipc.a
eApps (38 GUI apps + ebot) compiled into the ebot binary and application suite.
rootfs = eos + eboot + eai + eni + eipc + eApps. All components packaged into a deployable filesystem image.
→ eos-image-raspi4.cpio.gzEoSim boots the image in a VM. Runs 583+ tests across 52 platforms and 14 CPU architectures (GPIO, UART, SPI, I2C, crypto, OTA, AI).
→ 583 tests passedFlash to real hardware (RPi4, STM32, etc.). ebot connects to eai server at 192.168.1.100:8420.
How EoS components interact on a deployed device
Gated release pipeline — every commit passes 4 quality gates
52 hardware targets across 14 CPU architectures
14 CPU Architectures Supported
ARM Cortex-M • ARM Cortex-A • ARM Cortex-R • AArch64 • RISC-V 32 • RISC-V 64 • Xtensa • x86_64 (Intel/AMD) • MIPS • PowerPC • MicroBlaze • ARC • TriCore • RH850