MicroPixel runs WebAssembly apps on Espressif microcontrollers. Apps use a C++23 SDK for graphics, input, audio, storage, and sensors, without depending on a board-specific SDK. The firmware manages hardware, app isolation, and the system UI.
| Chip | Board |
|---|---|
| ESP32-P4 | Metalio-Claw4 |
| ESP32-S31 | ESP-Mosaico |
| ESP32-S3 | ESP32-S3-BOX-3 |
| ESP32-S3 | LCKFB SZPI |
| ESP32-S3 | M5Stack CoreS3 |
| ESP32-S3 | SenseCAP Watcher |
The Host uses ESP-IDF 6.1 and a pinned WAMR fork. Apps are compiled to architecture-specific AOT v6 bundles. The ABI is still evolving.
Install the SDK and connect a device running MicroPixel firmware. App development does not require ESP-IDF.
micropixel init my-app --app-id com.example.my-app --title "My App"
cd my-app
micropixel --transport usb runrun builds, installs, starts the app, and follows its logs. Ctrl-C stops log streaming; the app keeps running.
See the quickstart and publishing guide.
Initialize submodules, activate ESP-IDF 6.1, and configure WASI SDK and the matching MicroPixel WAMRC. See the build guide (Chinese) for toolchain setup and flashing.
git submodule update --init --recursive
python3 -m pip install -r requirements-dev.txt
bash tools/p4.sh build-hostOther profiles: bash tools/s31.sh build-host and bash tools/s3.sh build-host <box3|szpi|cores3|watcher>.
- Guest SDK — app APIs and examples.
- Firmware — Host runtime and board support.
- Documentation — architecture, protocols, and development guides.
- Contributing.
Project-authored code, documentation, and assets use Apache-2.0, unless stated otherwise. See third-party notices for dependency licenses and exceptions.