Skip to content
Foundation · 501(c)(3) · MIT License

Open-source embedded systems for intelligent physical devices

From open hardware and secure boot to a real-time OS, developer tools, and on-device AI.

Open infrastructure for physical AI.Shipped profile: eAI Edge = eNI → eIPC → eAI
23Repositories
83Boards
14Books
Scroll to follow one board through every industry · drag to turn it 360°Scroll to follow one board through every industry · swipe sideways to turn it
01 · eHealth365

A ring for vitals, a patch for chemistry

eHealth365 pairs two wearable designs. The Smart Ring Pro is designed to measure heart rate, HRV, SpO₂, body temperature, sleep stages and activity. The Smart Patch Pro, worn one patch a week, is designed to measure glucose, sweat electrolytes, hydration and skin pH.

From eHealth365_CAD_Design/README.mdBoth are designed to connect to one mobile app over Bluetooth LE

eCAD Hardware · Design stageEoS profile: wearable
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
02 · eosHealth

A health band on the wrist

eosHealth holds four EoS Health designs: HEALTH-KEY ULTRA, HEALTH-BAND Neuro, HEALTH-RING and HEALTH-LAB. The HEALTH-BAND Neuro design is a wristband with a 44 mm case and a 1.4-inch AMOLED display, rated IP68.

From eosHealth_CAD_Design/HEALTH-BAND-Neuro/product_datasheet.mdCase 44 × 38 × 12 mm · 42 g with band

eCAD Hardware · Design stageEoS profile: watch
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
03 · eMedical

A 12-lead ECG on battery power

eMedical covers diagnostic, patient-care, surgical and laboratory designs. The eECG-12 design is a battery-powered 12-lead ECG with a 7-inch touch display, BLE 5.3 and Wi-Fi 6, designed for eight hours on its battery and to the IEC 60601-1 safety standard.

From diagnostic_equipment/product_datasheet.md · Design PhaseSTM32H7B3 MCU · ADS1298 8-channel 24-bit ECG front end

eCAD Hardware · Design stageEoS profile: medical
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
04 · eRadar360

360° awareness from the windshield

eRadar360 (Aegis One for OEMs) is a windshield-mounted car safety design. It is designed to fuse four sensor types: front and rear 77 GHz FMCW radar, five laser detectors spaced 72° apart for 360° coverage, and V2X radio.

From eRadar360_CAD_Design/README.md2× TI AWR2944 77 GHz radar · 5× InGaAs APD laser detectors · V2X

eCAD Hardware · Design stageEoS profile: automotive
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
05 · eTransport

Charts on the bridge

eTransport covers automotive, maritime and rail electronics. The eNav-ECDIS design is an electronic chart display for ships, with a 27-inch sunlight-readable display and encrypted S-57/S-63 electronic navigational charts.

From maritime_systems/product_datasheet.md · IEC 61174, SOLASNXP i.MX 8M Plus · NMEA 2000, NMEA 0183, AIS, Ethernet

eCAD Hardware · Design stageEoS profile: cockpit
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
06 · ePAM

A four-seat tilt-rotor

ePAM holds personal air and mobility designs: the Urban Drone, a space shuttle avionics board, an eco car and a combo unit. The Urban Drone design is a four-seat tilt-rotor eVTOL, shown here as a scale model.

From ePAM_CAD_Design/urban_drone/product_datasheet.mdWingspan 12 m extended, 4 m folded · MTOW 1,400 kg

eCAD Hardware · Design stageEoS profile: aerospace
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
07 · eAerospace

An inspection drone

eAerospace has the most models of any domain: avionics, CubeSats, flight control, navigation, launch systems and UAVs. The eMR-400 design is a multirotor inspection drone in the UAV and drone line.

From uav_drone_systems/product_datasheet.md · Design PhaseeMR-400 design targets: 1 kg payload, 45 min endurance, 10 km range

eCAD Hardware · Design stageEoS profile: drone
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
08 · eRobotics

A whole robot, built from five designs

eRobotics covers industrial robots, autonomous systems and robot components. This robot is assembled from five of them: the eAMR-500 mobile base, the eArm-7 seven-axis arm, the eGripper-3F hand, eVision-4K stereo eyes and the eLiDAR-360.

From autonomous_systems, industrial_robots and robot_components datasheetseAMR-500: 500 kg payload, 2 m/s, LiDAR SLAM · eArm-7: 10 kg, 1.3 m reach

eCAD Hardware · Design stageEoS profile: robot
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
09 · eAgriTech

A tractor that steers itself

The website lists eAgriTech as its own industry. Its design lives in the eRobotics autonomous-systems line: the eAgri-Tractor, an autonomous tractor designed to navigate by RTK GPS and LiDAR.

From eRobotics_CAD_Design/autonomous_systems/product_datasheet.mdeAgri-Tractor · design speed 3 m/s

eCAD Hardware · Design stageEoS profile: autonomous
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
10 · eFrontier

A robot arm for space

eFrontier explores bioelectronics, nanotechnology, neuromorphic computing, photonics, quantum control, space robotics and swarms. The eSRB-900 design is a space-robotics controller for a seven-axis arm on a rad-hard processor.

From space_robotics/product_datasheet.mdGR712RC dual-core LEON3FT · 50 krad(Si) dose target

eCAD Hardware · Design stageEoS profile: satellite
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
11 · eIndustrial

A controller for the plant floor

eIndustrial spans industrial electronics, sensors and infrastructure equipment. The ePLC-1000 design is a modular PLC for IEC 61131-3 programs on an NXP i.MX 8M Plus, with 32 digital inputs, 32 digital outputs, 16 analog inputs and 8 analog outputs.

From industrial_electronics/product_datasheet.md · Design PhaseFieldbus: PROFIBUS DP, PROFINET, EtherCAT, Modbus TCP/RTU

eCAD Hardware · Design stageEoS profile: plc
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
12 · eEnergy

A board that watches every cell

eEnergy covers battery products, renewable energy and power electronics. The eBMS-100A battery-management design is designed to monitor each cell, sense pack current, balance cells actively and protect against over-voltage, under-voltage, over-current, overheating and short circuits.

From battery_products/product_datasheet.md · Design PhaseeBMS-100A communication: CAN FD, SMBus, RS-485, BLE

eCAD Hardware · Design stageEoS profile: ev
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
13 · eSmartCity

Street lights that report back

eSmartCity has 13 lines, from civic sensing to waste management. The eSL-400 design twists into a street light's NEMA socket. It is designed to dim the lamp by ambient light, motion and schedule, meter its energy and report faults over LoRaWAN.

From street_lighting/product_datasheet.md · Design PhaseSocket: ANSI C136.41 7-pin NEMA twist-lock

eCAD Hardware · Design stageEoS profile: iot
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
14 · eMining

Four gases, one warning

eMining covers mining equipment, industrial safety and construction robots. The eGasDetect-4 design is a four-gas detector for oxygen, carbon monoxide, hydrogen sulphide and flammable gas, with audible, vibrating and visual alarms, designed to IP67.

From industrial_safety/product_datasheet.md · Design PhaseATEX design target: Ex ia IIC T4 Ga, Zones 0, 1 and 2

eCAD Hardware · Design stageEoS profile: industrial
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
15 · eEdgeAI

Four eyes, one decision

eEdgeAI is eight lines of edge-AI hardware: accelerators, inference servers, NPUs, sensor fusion, SLAM, speech, TinyML and vision. The eVIS-600 design synchronises four global-shutter cameras and runs object detection at 30 fps in 1080p on an i.MX 8M Plus NPU. Research horizon: AGI-enabling methods for autonomous physical systems. No achieved AGI system is claimed as available today.

From vision_processing/product_datasheet.md4× MIPI CSI-2 · <1 µs inter-camera skew · 850 nm IR strobe

eCAD Hardware · Design stageEoS profile: ai_edge
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
16 · eElectronics

Down to the silicon

eElectronics designs the parts themselves: components, semiconductors and emerging technology. The eASIC-Vision design is a computer-vision chip on a 7 nm process with 32 MB of on-chip SRAM, in a 25 × 25 mm BGA-576 package.

From semiconductor_products/product_datasheet.md · Design PhaseDesign targets: 100 TOPS (INT8) at 5 W typical

eCAD Hardware · Design stageEoS profile: computer
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
17 · eConsumer

One hub for the whole home

eConsumer covers smart home, smart devices and personal devices. The eHub-Pro design is a smart-home hub that speaks Matter 1.3, Zigbee 3.0, Z-Wave 700, BLE 5.3 and Wi-Fi 6, built on an NXP i.MX 8M Mini.

From smart_home/product_datasheet.md · Design PhaseThe same line includes a thermostat, a video doorbell, an indoor camera and an AI speaker

eCAD Hardware · Design stageEoS profile: smart_home
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
18 · eCybersecurity

A vault for keys

eCybersecurity designs hardware for trust: roots of trust, secure elements, TPMs and security appliances. The eHSM-9000 design is a network-attached hardware security module designed to generate, store and use keys inside a tamper-responsive boundary, and to erase them if its active mesh is breached.

From hardware_security_modules/product_datasheet.md · Design PhaseM-of-N smartcard quorum · certification target FIPS 140-3 Level 4

eCAD Hardware · Design stageEoS profile: crypto_hw
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
19 · eDefense

A computer with no fan to fail

eDefense has 19 lines, from ruggedised computing to sonar. The eRGD-2000 design is a rugged mission computer that cools by conduction through its chassis, so it needs no fan and can be sealed to IP67. It is designed for MIL-STD-810H shock and vibration.

From ruggedized_computing/product_datasheet.md · Design PhaseNXP i.MX 8M Plus with NPU · −40 °C to +71 °C operating

eCAD Hardware · Design stageEoS profile: server
Drag to turn it 360° · hover a part for detailsSwipe sideways to turn it 360° · tap a part for details
20 · Full-body robot

The board docks, and a body wakes up

At the centre of the hall stands a full-body robot built only from eRobotics designs: eServo-200 drives in its 26 rotary joints, eActuator-50 push rods at the ankles, eGripper-3F hands, eVision-4K eyes and an eLiDAR-360 crown. The core board docks behind the chest window, and EoS brings the body up.

Concept · assembled from eRobotics datasheetsEvery part is an eRobotics design; the body itself is not a datasheet product

Concept · built from eRobotics partsEoS profile: robot
Drag to walk around the robot · hover a part for detailsSwipe sideways to walk around it · tap a part for details
21 · Full-body robot

Two eyes for depth, one laser for the room

eVision-4K gives the head 4K stereo cameras with depth over Gigabit Ethernet. The eLiDAR-360 crown sweeps the whole hall: 360°, 100 m of range and 0.1° resolution. EoS would turn both into data the rest of the body can use.

From robot_components/product_datasheet.mdeVision-4K: 4K stereo + depth, GbE · eLiDAR-360: 100 m, 0.1°, Ethernet

Concept · built from eRobotics partsEoS profile: robot
Drag to walk around the robot · hover a part for detailsSwipe sideways to walk around it · tap a part for details
22 · Full-body robot

Walking is a real-time job

Every step means reading the IMU and the 23-bit joint encoders, then updating every drive on time. Each eServo-200 closes its own 20 kHz current loop; EoS would run the joint loops and keep the balance task ahead of everything else.

From robot_components/product_datasheet.mdeServo-200: 200 W at 48 V, EtherCAT CoE (CiA 402), ±0.01° position accuracy

Concept · built from eRobotics partsEoS profile: robot
Drag to walk around the robot · hover a part for detailsSwipe sideways to walk around it · tap a part for details
23 · Full-body robot

Hands that pick, check and place

Each hand is an eGripper-3F: three adaptive fingers, an 80 mm span and 50 N of grip, on RS-485. The robot picks up a part, lifts it to its eyes to check it, then places it in a tray.

From robot_components/product_datasheet.mdeGripper-3F: 3-finger adaptive gripper · 80 mm span · 50 N · RS-485

Concept · built from eRobotics partsEoS profile: robot
Drag to walk around the robot · hover a part for detailsSwipe sideways to walk around it · tap a part for details
24 · Full-body robot

Stops in one call, updates over the air

An emergency stop has to beat every other task. EoS's motor service stops a motor in one call, and the scheduler runs that task first. Afterwards, new firmware arrives over the air into the spare A/B slot, and eBoot checks its signature before switching.

From eos services/motor and services/otaeos_motor_ctrl_emergency_stop() · A/B slots with SHA-256 checks

Concept · built from eRobotics partsEoS profile: robot
Drag to walk around the robot · hover a part for detailsSwipe sideways to walk around it · tap a part for details
25 · Every industry

Eighteen domains, one open collection

Every design in this hall, and every part of the robot at its centre, is part of eCAD Hardware: 125 product lines and 292 named models. Each carries a datasheet, and most add a bill of materials and a power simulation. All are at design stage; no routed PCB or Gerbers yet. The repository is published under the MIT licence.

Ten future conceptseBCI-Lite, eCubeSat-1U, eEdu-Kit, eFarm, eHand, eHive, eHydro, eMeshGrid, eRover-Mini, eVision

eHealth365eosHealtheMedicaleRadar360eTransportePAMeAerospaceeRoboticseAgriTecheFrontiereIndustrialeEnergyeSmartCityeMiningeEdgeAIeElectronicseConsumereCybersecurityeDefenseFull-body robot
eHealth365 · 2 lines · 2 models

Smart Ring Pro + Smart Patch Pro

Design stage

Two wearables, one ring and one patch, each with its own sensors and a shared phone app.

Devices
2
Smart Patch ProSmart Ring Pro

eHealth365_CAD_Design

EoS · wearable profile

How EoS would run it

Profile in eosNot validated on this hardware

Docked here, the core board would boot EoS built with the wearable product profile: 17 features switched on, 4 of them services with working code today.

How EoS would work here
  1. Heart-rate, SpO₂ and temperature samples would pass through the EoS sensor service, whose filtering and calibration are working code.
  2. Bluetooth LE to the phone app would use the BLE HAL class, which is a stub today.
  3. Updates would land through the OTA service: its A/B state machine and SHA-256 checks are in code, but it does not write flash yet.
GPIOUARTSPItimerADCBLEdisplaytouchIMUNFCflashRTCcryptoOTAfilesystempowersensor

eos · products/wearable.h

eMedical · 4 lines · 19 models

eECG-12

Design stage

A 12-lead ECG design with a 7-inch 1024 × 600 touch display and a 7.4 V 5000 mAh battery.

Leads
12
Battery
8h design
eECG-12eEEG-32eUS-ProePM-500eBA-100ePCR-96eCentri-24KeSeq-NanoeSpec-UVeLab-AutoeVent-ProeInfuse-200eO2-5LeRehab-ArmeProsth-HandeSurgBot-7eESG-400eEndo-4KeSurgNav-3D

eMedical_CAD_Design

EoS · medical profile

How EoS would run it

Profile in eosNot validated on this hardware

Docked here, the core board would boot EoS built with the medical product profile: 13 features switched on, 4 of them services with working code today.

How EoS would work here
  1. The ADS1298 ECG front end talks SPI. EoS's SPI driver is register code for STM32F4 only, so the STM32H7 here needs its own port.
  2. Each lead would be a sensor-service channel with filtering (working code).
  3. The os service keeps an audit log and integrity checks, and the security service holds keys and an access list (working code). No EoS build is certified for medical use.
GPIOUARTSPItimerADCBLEdisplaycryptosecuritypowersensorsafetyaudit

eos · products/medical.h

eAerospace · 17 lines · 57 models

eMR-400

Design stage

A multirotor inspection drone design; the line also includes fixed-wing, VTOL cargo and swarm designs.

Payload
1kg target
Endurance
45min target
eATM-3000eATM-RSUeATM-TWReAPT-900eAPT-VDGSeAPT-APReFC-1000eNAV-500eADC-200eFD-1080eCOM-400eXPDR-1090eCUBE-3U-OBCeCUBE-EPSeCUBE-ADCSeCUBE-3UeFCS-2000eFCS-2000MeACE-400eGNSS-400+37 more

eAerospace_CAD_Design

EoS · drone profile

How EoS would run it

Profile in eosNot validated on this hardware

Docked here, the core board would boot EoS built with the drone product profile: 23 features switched on, 6 of them services with working code today.

How EoS would work here
  1. Four motors fit inside the motor service's limit of eight: its PID speed loops and trajectories are working code.
  2. The motor (ESC) and IMU HAL classes are stubs today, so nothing drives real hardware yet.
  3. GNSS position comes from the gps service (NMEA parsing, working code); updates would arrive through the OTA A/B service.
GPIOUARTSPItimerADCPWMwifiBLEcameramotorGNSSIMUradarDMAOTAflashWDTfilesystempowernetsensormotor ctrlsafety

eos · products/drone.h

eRobotics · 3 lines · 15 models

A full robot from five designs

Design stage

An autonomous mobile manipulator: base, arm, gripper, vision and LiDAR are each an eRobotics design.

Designs combined
5
Arm axes
7
eAMR-500eWarehouse-1TeDelivery-BoteAgri-TractoreSecurity-PatroleArm-7eWeld-6eAssemble-4ePick-DeltaeCobot-5eServo-200eActuator-50eGripper-3FeVision-4KeLiDAR-360

eRobotics_CAD_Design

EoS · robot profile

How EoS would run it

Profile in eosNot validated on this hardware

Docked here, the core board would boot EoS built with the robot product profile: 15 features switched on, 3 of them services with working code today.

How EoS would work here
  1. The arm's 7 joints plus the base's 4 hub motors make 11 motors, more than the 8 the motor service tracks per image today, so this robot needs that limit raised or two EoS images.
  2. LiDAR, cameras and the IMU sit behind HAL stub classes; the sensor service (working code) holds up to 16 sensors.
  3. The priority scheduler keeps the safety stop ahead of everything else, and eos_motor_ctrl_emergency_stop() halts a motor in one call (working code).
GPIOUARTSPII2CtimerADCPWMwifiBLEcameramotorIMUnetsensormotor ctrl

eos · products/robot.h

eEnergy · 3 lines · 15 models

eBMS-100A

Design stage

A battery-management design with per-cell monitoring and active balancing.

Interfaces
4
eBMS-100AeLiPack-10kWheESS-100kWhePPS-5kWeSBM-SmarteDCDC-5kWeUPS-10kVAeMotorDrive-22kWePDU-SmarteBreaker-SmarteSolarInv-10kWeSolarTrackereWindCtrl-50kWeMicrogrid-100eSCC-60A

eEnergy_CAD_Design

EoS · ev profile

How EoS would run it

Profile in eosNot validated on this hardware

Docked here, the core board would boot EoS built with the ev product profile: 31 features switched on, 9 of them services with working code today.

How EoS would work here
  1. The LTC6813 talks SPI, and each cell would be a sensor-service channel with filtering (working code). Its 18 cells exceed the service's 16 channels today.
  2. Over-voltage, over-current and short-circuit protection would run as the highest-priority kernel task.
  3. CAN FD and BLE are HAL stubs, and the power service is bookkeeping only, so real readings come from the BMS itself.
GPIOUARTSPItimerADCDACPWMCANethernetmotorIMUGNSSdisplaytouchDMAflashRTCWDTcellularwifiBLEcryptosafetyauditpowernetsensormotor ctrlOTAfilesystemmulticore

eos · products/ev.h

eSmartCity · 13 lines · 25 models

eSL-400

Design stage

A NEMA twist-lock lighting controller design with dimming, metering and LoRaWAN.

Product lines
13
eCS-200eDIS-600eGOV-500eEMR-800eHUM-400eKSK-900ePS-1200eRUR-700eSL-400e5G-SmalleIoT-GWeRouter-ProeNetMonePrivNeteTrafficCtrleParkSensoreStreetLighteEnvStationeSafety-CameSM-3P+5 more

eSmartCity_CAD_Design

EoS · iot profile

How EoS would run it

Profile in eosNot validated on this hardware

Docked here, the core board would boot EoS built with the iot product profile: 17 features switched on, 5 of them services with working code today.

How EoS would work here
  1. LoRaWAN is not in EoS yet; it appears only in the docs.
  2. Dimming from 1% to 100% would use the PWM HAL class and 0–10 V the DAC class; both are stubs today.
  3. Metered voltage and current fit the sensor service's voltage and current types (working code).
GPIOUARTSPItimerADCwifiBLEcellularflashRTCWDTcryptoOTAfilesystempowernetsensor

eos · products/iot.h

eEdgeAI · 8 lines · 8 models

eVIS-600

Design stage

A four-camera embedded vision design with a hardware ISP, IR strobe and GigE Vision output.

Cameras
4
NPU
2.3TOPS
eAI-2000eINF-4000eNPU-800eSFU-500eSLM-700eSPX-300eTML-100eVIS-600

eEdgeAI_CAD_Design

EoS · ai_edge profile

How EoS would run it

Profile in eosNot validated on this hardware

Docked here, the core board would boot EoS built with the ai_edge product profile: 22 features switched on, 6 of them services with working code today.

How EoS would work here
  1. Detection on the NPU would go through eAI, whose default build returns stub inference today.
  2. The four cameras would use the camera HAL class, a stub today.
  3. The nearest EoS board is imx8m (i.MX 8M Mini); the kernel's AMP support would split vision from strobe timing (working code).
GPIOUARTSPItimerUSBethernetwificameraaudioGPUPCIeDMAflashRTCSDIOcryptoOTApowernetsensorfilesystemmulticore

eos · products/ai_edge.h

EoS · robot profile

The same board, docked in the chest

Profile in eosConcept body

The core board that toured the hall docks behind the chest window. It would boot EoS built with the robot product profile: 15 features, including motor control and sensors.

Features
15
Joints
30
GPIOUARTSPII2CtimerADCPWMwifiBLEcameramotorIMUnetsensormotor ctrl

eos · products/robot.h

EoS · boot order

EoS wakes the body

Kernel + init · working codeeBoot · host-tested

Power-on follows the same chain as the Chain of Trust story; then EoS brings the body up from the inside out, joint by joint.

Boot, step by step
  1. eBoot's stage-0 checks stage-1, which verifies the Ed25519-signed EoS image (host-tested; not yet booted on hardware).
  2. The kernel starts its priority scheduler, and the init service starts each service in dependency order, with restart policies and a watchdog.
  3. In this concept, sensors come up before motors, so every joint knows where it is before it may move.
eBootkernel schedulerinit servicesensor servicemotor service

eBoot · eos kernel/ · services/init

eRobotics · eVision-4K

Stereo eyes with depth

Design stage

Two 4K cameras, a hand's width apart, see depth the way people do. The datasheet lists 4K stereo plus depth over Gigabit Ethernet.

How EoS would see
  1. EoS would read the cameras through its camera HAL class, a stub today.
  2. Frames would go to eAI for detection; eAI's default build returns stub inference.
Output
4Kstereo + depth
Link
GbE
camera HALEthernet HALeAI

eRobotics_CAD_Design/robot_components

eRobotics · eLiDAR-360

A full turn of laser range

Design stage

The crown sweeps the hall. Every dot is a simulated return from the floor, the pedestals and the designs standing on them.

How EoS would map the room
  1. EoS would take the point cloud over Ethernet; the radar/LiDAR HAL class is a stub today.
  2. The sensor service (working code) filters and calibrates up to 16 sensors, so a full point cloud would need its own path.
Range
100m
Resolution
0.1°
radar/LiDAR HALsensor servicesockets (host builds)

eRobotics_CAD_Design/robot_components

eRobotics · eServo-200

A servo drive in every joint

Design stage

Each rotary joint is an eServo-200 EtherCAT drive whose own STM32G474 closes a 20 kHz current loop. Two eActuator-50 push rods move each ankle.

How EoS would drive the joints
  1. EoS's motor service (working code) runs PID speed and position loops and trajectories for each motor.
  2. It tracks 8 motors per image today, so a 30-joint body needs that limit raised or one EoS controller per limb.
  3. EtherCAT itself is not in EoS yet.
Drives
26
Encoders
23bit
motor servicemotor HALEtherCAT

robot_components · eos services/motor

EoS · real time

Balance is a deadline

Kernel · working codeIMU HAL · stub

The amber ring is the centre of mass; the green outline is the support polygon under the feet. Keep one inside the other on every cycle, and the robot stays up.

How EoS would keep it upright
  1. The kernel's priority scheduler would run the balance task first, and priority-inheritance mutexes stop a slower task from blocking it.
  2. Message queues would carry joint targets from the planner to the motor task, paced by software timers.
  3. The IMU HAL class is a stub today; the kernel and the sensor service are working code.
priority schedulerPI mutexesmessage queuessoftware timersIMU HAL

eos kernel/src/task.c · sync.c · ipc.c

eRobotics · eGripper-3F

Three fingers that adapt

Design stage

Two fingers and an opposed thumb close around the part with up to 50 N and report back over RS-485.

How EoS would grip
  1. EoS would talk to the gripper over a UART-based RS-485 link; the UART driver is register code for STM32F4 only.
  2. The reach itself is a motor-service trajectory for each arm joint (working code).
Span
80mm
Grip
50N
UART HALmotor trajectories

eRobotics_CAD_Design/robot_components

EoS + eAI

Eyes guide the hand

eAI · stub inference

Before placing the part, the robot lifts it to its eyes and checks it with stereo depth.

What it would take
  1. Recognising the part is a job for eAI, the planned on-device AI layer; its default build returns stub inference today.
  2. The eNI → eIPC → eAI pipeline described in the docs is not wired up in code yet.
eAI runtimeeIPCcamera HAL

eAI · eIPC

EoS · motor service

Stop in one call

e-stop · working code

An emergency stop zeroes a motor's target speed, PID output and integrators in a single call, and every light on the body turns red.

How EoS would stop it
  1. eos_motor_ctrl_emergency_stop() is working code; a full-body stop would call it for every joint, then hold position.
  2. The eArm-7 datasheet targets ISO 10218-1 and IEC 62061 SIL 2 for the arm; a whole humanoid would need its own safety case.
e-stop callfunctional-safety case

eos services/motor/src/motor_ctrl.c

EoS · OTA + eBoot

Update without a cable

OTA · partialeBoot · host-tested

New firmware drops into the spare A/B slot. eBoot verifies its Ed25519 signature and version before switching, and can roll back.

How the update would land
  1. The EoS OTA service is an A/B state machine with SHA-256 checks; today it hashes chunks but does not write flash.
  2. eBoot's slot selection, signature checks and anti-rollback are host-tested and have not run on hardware yet.
OTA serviceeBoot A/B + rollbackEd25519 verify

eos services/ota · eBoot

Scroll
Loading the 3D model

This browser can't run the 3D model, so you're seeing the still image. Every chapter still works as you scroll.

EmbeddedOS Ecosystem

EoS KernelCoreeBootSecurityeIPCPlatformeAIAIeosllmAIeNINeuraleDBDataeAppsAppseBrowserUIeOfficeAppsebuildBuildEoStudioIDEEoSimSimulationeCAD HardwareHardwareKids EditionEducationeNetPlannedeSecPlanned
23Repositories
83Boards
300+APIs
60+Apps
4Health devices
14Books
The board, part by part

Every component, and the bus that reaches it

Click or tap any part. U1 runs EoS; every other part hangs off its own bus, and each says how EoS uses it today. The board is illustrative; the statuses come from the code.

EMBEDDEDOS · EoS REFERENCE · REV A
Our Mission

Embedded computing should be free to learn and free to build on

The Embedded Operating Systems Research Foundation is a 501(c)(3) public charity (EIN 41-4821627). We exist to advance open-source embedded systems research, education, and technology for the public benefit, accountable to our community, not to shareholders. Every line of code we publish is MIT licensed and free, forever.

Open-source software, permanently free

The kernel, bootloader, drivers, build tools, and every application we ship are MIT licensed and developed in public on GitHub. No paid tiers, no license fees, no vendor lock-in.

Free education for engineers and students

14 full-length technical books, free certification exams, a Kids Edition for classrooms, and paid internships for students and new graduates, all at no cost to learners.

Public-benefit research

We publish our research openly, including patent filings for health-monitoring hardware, so that clinicians, universities, and other nonprofits can build on the work rather than license it.

Architecture and maturity

An Illustrative Reference Architecture

Seven layers, the same ones you scrolled through, each with what is built and tested and what is still planned. Illustrative reference only. Individual projects and integrations have different maturity levels; planned elements are not yet available products.

eBoot

Two-stage secure boot: Ed25519 + SHA-512 image check, A/B slots and recovery. Host-tested; key storage needs board hooks.

WorkingKeys: board hooks

EoS HAL

One driver API on every target. The dispatch layer, GPIO on Linux and the devicetree parser work; 28 extended classes are stubs.

Dispatch28 stubs

EoS kernel

Priority scheduler, priority-inheritance mutexes, semaphores, events, queues and a validated heap. 45 CTest suites on hosts.

Working

EoS services

18 libraries: motor and sensor control, OTA, crypto, networking, files and debug. Flash writes and an MCU network stack are planned.

In codeSome planned

eIPC · eDB

Authenticated messages between services and devices; a multi-model data store with 38 endpoints. Both are working prototypes.

Prototypes

Apps

The eApps catalogue (124 entries), the eBrowser engine and 11 eOffice apps; packages install as verified .eapp files. Many apps are templates.

In codeTemplates

On-device AI

eosllm runs models with three real back ends; eNI works in simulation; eAI's runtimes are placeholders today.

eosllmeAI runtimes
The ecosystem

The Complete Embedded Ecosystem

Every component you need to build, deploy and manage embedded systems, each described as it stands in its repository today.

On the device9 repositories

  • eBootWorking

    Signed two-stage boot with A/B slots and recovery; not yet booted on hardware.

  • EoS kernelWorking

    Real-time kernel with priority scheduling, sync and queues; tested on hosts.

  • eIPCPrototype

    Authenticated messages between processes and devices; Go core and a C SDK.

  • eDBPrototype

    Multi-model data store: five models, 38 endpoints, 42 passing tests.

  • eosllmWorking

    Runs language models on the device with three real back ends; 160 tests.

  • eAIFramework

    The on-device AI layer; its model runtimes are placeholders today.

  • eBrowserEngine

    Browser engine for embedded displays; JavaScript and the sandbox are planned.

  • eOfficePrototype

    11 office apps with 741 tests.

  • eAppsCatalogue

    124 catalogue entries; many apps are templates.

To build and test it3 repositories

  • ebuildWorking

    One CLI to create, build, flash and simulate; knows 171 MCUs, 826 tests.

  • EoStudio7 of 13

    Design studio and IDE: 7 of its 13 editors are real; 40 code generators.

  • EoSimWorking

    Simulator with 153 platforms and 2,117 passing tests.

Health Technology

4 Health Devices · 2 Patents Pending

In-development open hardware designs for health-monitoring research. Physical reliability and clinical validation are pending.

HEALTH-KEY ULTRA

A USB-C research design for exploring ECG, blood-oxygen, breath-alcohol, temperature, UV and motion sensing. Validation is pending.

HEALTH-BAND Neuro

A wristband research design for sEMG gesture studies, biometric sensing and TENS exploration. No therapeutic benefit is claimed.

HEALTH-RING

A concept ring for researching optical and electrical sensing. Clinical measurement has not been validated.

HEALTH-LAB

A biosensor patch concept for health-monitoring research.

Open Hardware

eCAD Hardware · 18 domains, 292 models

Open designs from smart rings to a tilt-rotor eVTOL, in 125 product lines. Every one is at design stage with a datasheet, and most add a bill of materials and a power simulation. A dev-board CAD database adds 322 reference boards, 186 of them verified.

Why EmbeddedOS

The Operating System for Every Device

Built by embedded engineers, for any embedded hardware. Every design decision prioritizes reliability, security, and developer experience.

Real-Time Scheduling

Priority-driven scheduling with priority inheritance; timing is characterized per target.

Signed From the First Instruction

Ed25519-signed boot and authenticated messages; hardware key storage needs board hooks.

Connectivity, Honestly

Wi-Fi, BLE, Ethernet and CAN are defined in the HAL; sockets work on hosts and MCU stacks are planned.

Developer Friendly

ebuild, EoStudio and EoSim, 14 technical books, documentation and free certification.

Modular Architecture

Use only what you need, from the bare kernel to the full application stack.

Broad Hardware Coverage

83 board descriptors across 55 architectures. Maturity varies by target; a descriptor is not a validated port.

Foundation Community

Built by the Community, for the Community

EmbeddedOS is a 501(c)(3), community-driven project, built by embedded engineers for any embedded hardware. Every line of code, every document, and every tool prioritizes reliability, security, and developer experience.

25 repositories in public

Developed openly on GitHub, 23 of them MIT licensed.

14 books to learn from

Full-length technical books, free for everyone.

10 fuzz harnesses

Plus CodeQL and Scorecard across the organisation.

Every claim checked

This page says what works, what is partial and what is planned.

Open Source · 501(c)(3) · MIT License

Ready to build on EmbeddedOS?

Join engineers building the next generation of embedded systems. Free, foundation-backed, and 501(c)(3) forever.