APP01
Application runtime
Apps launch, exit, restart and restore state through a defined lifecycle rather than behaving as hard-coded screens.
HermitShell
A Rust embedded operating system for the Cardputer ADV.
active development no_std Rust · FreeRTOS + Embassy · dual-core ESP32-S3
PB-07 active development
SYS/DEVICE 04 CHANNELS PALOMA BB
- Target
- Cardputer ADV
- Language
- no_std Rust
- Kernel base
- FreeRTOS + Embassy
- Foreground apps
- One at a time
01
02
03
04
What is real today
A small operating system with an honest resource model.
HermitShell is a Rust embedded operating system for the Cardputer ADV. It runs one foreground user application at a time while concurrent system services continue handling networking, input, display and other shared responsibilities.
Applications have launch, exit, restart and state-restoration behavior. System services expose defined interfaces, persistent state has ownership and recovery rules, and hardware access follows explicit resource policy instead of every screen reaching directly into the device.
The single-foreground-app limit is deliberate. It matches the hardware and product rather than weakening the operating-system boundary with an unnecessary desktop multitasking imitation.
System shape
The operating-system boundary is the product.
Foreground simplicity sits on top of concurrent services, persistent state and controlled access to hardware.
SERV02
Concurrent services
FreeRTOS and Embassy keep networking, UI and device services running behind the active foreground app.
STATE03
Persistent ownership
Application data has explicit ownership, storage and recovery behavior.
HW04
Resource policy
Hardware and system capabilities are mediated through services instead of being globally reachable.
Current evidence
It behaves like an application environment, not one giant firmware image.
The distinction is visible in lifecycle, state, interfaces and resource management rather than in marketing language.
01
Lifecycle
Launch / exit / restart
Foreground applications have a reusable system-managed lifecycle.
02
Continuity
State restoration
Applications can return to owned persistent state after interruption or restart.
03
Concurrency
Background services
System work continues while a single user application owns the foreground.
04
Access
Policy-mediated
Shared hardware is managed through explicit system boundaries.
Operating principles
Constraints that keep the work honest.
Fit the hardware
Resource policy follows the actual embedded device.
Apps are not screens
Lifecycle and state make applications genuine system participants.
Services stay concurrent
Single foreground use does not imply single-tasking internals.
Boundaries stay explicit
Hardware ownership is mediated rather than accidental.
Connected work