Connectivity and Protocol Stacks

The criterion. An RTOS rarely lives in isolation: native, resource-constrained networking stacks (TCP/IP like lwIP, Wi-Fi, Bluetooth Low Energy) that integrate with the scheduler without stalling critical tasks.

How Revera answers it — honestly

Revera 0.1.0 ships no networking or protocol stack — no TCP/IP, no Wi-Fi, no BLE stack, no USB. This is a genuine gap against stack-rich RTOSes (Zephyr, NuttX), and we state it plainly rather than imply otherwise.

Revera is a kernel, not a networking OS. The intended model is that a stack (e.g. lwIP) runs as ordinary threads on top of the kernel — Revera provides the scheduling, synchronization, and isolation such a stack needs (a network stack’s worker threads are just threads; its buffers are just memory), but it does not bundle one.

Available from the project’s history (roadmap / on request — not in 0.1.0)

The project’s history includes radio-level primitives — not a connectivity stack, but the low layers a link is built on, HW-proven on nRF52:

  • BLE beacon — non-connectable advertising (ADV_NONCONN_IND on channels 37/38/39) straight on the radio, no stack.

  • NFC-A Type-2 tag emulation (NFCT) — the SoC answers READ from a static memory image.

  • PN532 NFC reader/tag device driver (over I²C/SPI).

These are peripheral/radio drivers (see Hardware Abstraction), not an IP or BLE protocol stack. A full stack is not on the near-term roadmap.

Learn more