Skip to content

Latest commit

 

History

History
 
 

embedded

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 

README.md

Embedded

On-device firmware and the native layers it runs on. The embedded firmware turns a supported ESP32 into a myrmic swarm node that hosts WebAssembly cells — the application logic — on the WAMR runtime, reachable over WiFi (myrmic transport) and BLE (user transport).

The Signal Layer is an optional native layer that feeds those cells sensor readings and drives actuators. It matters when a cell needs hardware I/O, but the firmware hosts cells with or without it — a networking- or GPIO-only cell needs none of it.

flowchart LR
    SL["signal-layer/<br/>native sensor & actuator I/O<br/><b>· optional ·</b>"]
    FW["esp-hal/<br/>ESP32 WAMR firmware<br/>hosts cells · myrmic + BLE"]
    Cells["WASM cells<br/>your application logic"]
    FW --> Cells
    SL -. taps .-> Cells
Loading

What's in here

Directory What it is
esp-hal/ The ESP32 firmware ecosystem and the core of the embedded stack: the WAMR WASM runtime that hosts cells, the modem-esp32 firmware (myrmic + BLE transports, flash/AOT layout, memory tuning), and low-level crates (MMU, storage). Start here.
signal-layer/ Optional native I/O layer: sensor drivers, actuator outputs, processing steps, and the tap registry cells read from. Chip-agnostic — the ESP-specific glue (board manifests, pipelines, esp-codegen) lives under esp-hal/signal-layer/.
examples/ Runnable example firmware binaries (onboarding and Zenoh-ping over BLE and TCP).

The hardware-in-the-loop suite that flashes real boards and asserts against live behaviour lives with the runner it needs, in a separate CI repository, not in this tree.

Cells themselves aren't here — they're WASM modules under ../sdk/. This tree is the firmware that hosts them and the native layers it exposes to them.

Where to start