Repository navigation
Linux builds
Self-contained Linux builds (musl, fully static: OpenSSL and bzip2 are linked in, nothing to install on the device).
| Archive | Runs on |
|---|---|
linux-x86_64-musl |
PCs, servers, virtual machines |
linux-aarch64-musl |
Raspberry Pi 3/4/5 and Zero 2 with a 64-bit OS, Jetson, Orange Pi and similar |
linux-armv7-musl |
Raspberry Pi 2/3/Zero 2 with a 32-bit OS and similar |
linux-armv6-musl |
Raspberry Pi Zero and 1 (also runs on the armv7 boards) |
Each archive holds bin/ (the node daemon and tools), include/ and lib/ (static libraries, OpenSSL and bzip2 for static linking, a CMake package), BUILDINFO and the documentation. To link the SDK from CMake: -DCMAKE_PREFIX_PATH=<unpacked directory> -DOPENSSL_USE_STATIC_LIBS=ON. The Linux library needs a POSIX host with OpenSSL; use these builds on the computer a radio is attached to.
Microcontroller firmware (example node, serial interface; Wi-Fi TCP on ESP32 once provisioned; optional LoRa radio, off until configured)
reticulum-c-<version>-mcu-<board>.zip holds the firmware images, flash.txt with the exact flashing commands for that board, BUILDINFO (version, commit, toolchain versions), the manual and a README. The firmware is a Reticulum leaf node with one HDLC serial interface (the Reticulum SerialInterface framing): a host running reticulum-c-node or rnsd with the board as a SerialInterface routes between the board and the network. It announces reticulum_c.mcu.example and answers /echo and /info. It uses the portable crypto backend and the small mcu capacity profile (no OpenSSL).
Wi-Fi (ESP32 and ESP32-S3 archives). Unprovisioned images start in serial mode and contain no Wi-Fi credentials; updates that preserve settings retain the selected mode. To join a network, provision the board after flashing: run tools/wifi-config.sh from the archive (writes the Wi-Fi settings as an NVS image with esptool, no console needed; --arduino for the PlatformIO archives, which replaces their NVS partition and so their identity), or send the line rnc-config on the serial port within 2 seconds after reset (or press BOOT) and use the set/save/reboot console. The board then connects as a TCP client to a node's TCPServerInterface (same HDLC framing). The TCP link is plaintext and unauthenticated at the transport level and the credentials are stored unencrypted in flash; MANUAL.md has the details. The nRF52 archives have no Wi-Fi.
LoRa radio (the eight PlatformIO board archives). Each of those images contains a driver for its board's radio (SX1262 on the Heltec V3, T3-S3, T-Beam Supreme, RAK4631, T114 and T-Echo; SX1276 on the Heltec V2 and the T-Beam v1.0/1.1) and a Reticulum LoRa interface whose over-the-air format is meant to be compatible with stock RNodes on the same frequency and modem settings (header byte with sequence nibble and split flag, packets above 254 bytes in two frames, private-network sync word, CRC on, explicit header). lora.mode leaf makes LoRa the node's only interface; lora.mode gateway adds it to the serial or Wi-Fi interface with Reticulum transport on. The radio is off, and never transmits, until you have set the mode and all of frequency, bandwidth, spreading factor, coding rate and transmit power (console set lora.freq 868.1 ... or tools/wifi-config.sh --lora-mode ...); no default settings are in any image. You are responsible for a legal frequency, power and duty cycle where you use the board; the power setting is the power at the chip's output. The airtime budget defaults to 1% of every hour. Hardware bench testing covers a T-Echo leaf and Supreme SX1262 gateway at 915 MHz, including routed /echo and /info. Other boards retain build/model coverage; range, sustained load and stock RNode interoperability are unverified. The ESP-IDF archives are generic images without a board selection and have no radio; select a LoRa board in idf.py menuconfig and build from source to get one. The Supreme SX1262 target initializes its AXP2101 radio rail. Supreme LR1121 variants and T-Beam v1.2 are not supported.
| Archive | Board | Build |
|---|---|---|
mcu-esp-idf-esp32 |
ESP32 boards: Heltec WiFi LoRa 32 V2, LilyGo T-Beam, TTGO LoRa32 and similar | ESP-IDF 5.4.4 |
mcu-esp-idf-esp32s3 |
ESP32-S3 boards: Heltec WiFi LoRa 32 V3, T-Beam Supreme, T3-S3, T-Deck and similar | ESP-IDF 5.4.4 |
mcu-heltec_wifi_lora_32_v3, mcu-heltec_wifi_lora_32_v2, mcu-ttgo_t_beam, mcu-lilygo_t3_s3, mcu-lilygo_t_beam_supreme |
the named ESP32 / ESP32-S3 boards | Arduino (PlatformIO) |
mcu-wiscore_rak4631, mcu-heltec_t114, mcu-lilygo_t_echo |
RAKwireless RAK4631, Heltec Mesh Node T114, LilyGo T-Echo (nRF52840; UF2 and DFU files) | Arduino (PlatformIO) |
Updating an existing node. ESP32 merged.bin overwrites identity NVS (and provisioned settings on PlatformIO); use the separate-parts command in flash.txt to preserve NVS with the same partition layout. nRF52840 UF2/DFU files update only the application and preserve the internal file system, bootloader and SoftDevice; an existing compatible Adafruit bootloader is required.
Browser installer. Install and configure over USB offers the eight exact PlatformIO boards, versioned downloads and this firmware's rnc-config console. Its main-commit builds can include changes newer than a tagged release archive. In desktop browsers with Web Serial, ESP32 updates verify SHA-256 downloads and MD5 flash contents using separate parts; a factory erase requires an explicit choice and confirmation. nRF52840 uses acknowledged application-only serial DFU, with UF2 downloads also available. The setup form preserves a saved Wi-Fi password when left blank; explicitly select an open network to remove it. This uses reticulum-c provisioning, not RNode EEPROM/KISS configuration.
esp-idf-component.tar.gz is the protocol core and the example application as ESP-IDF components (use it with EXTRA_COMPONENT_DIRS). platformio-library.tar.gz is the same as a PlatformIO library (library.json; lib_deps = file:///path). Both are source archives.
Limits. The boards talk to a host over serial or USB (or, on ESP32 once provisioned, over Wi-Fi and TCP), and over LoRa once configured (see above). In these node modes they have no Bluetooth; Bluetooth LE is available only in rnode mode. Hardware coverage is the short T-Echo/Supreme SX1262 bench exchange described above, including serial provisioning and routed LoRa requests; other boards have build/model coverage. Wi-Fi hardware behavior, range, sustained load and stock RNode interoperability remain unverified. The same application logic passes host tests against reticulum-c-node and the reference Reticulum. The nRF52 board definitions for the RAK4631, T114 and T-Echo are derived from the Adafruit nRF52840 Feather and assume the Adafruit bootloader; serial DFU has been exercised on the T-Echo. It is a leaf node (no forwarding) unless the LoRa gateway mode is configured. The rnode mode (a host-driven LoRa modem for Sideband or rnsd, over USB or, once a PIN is set, Bluetooth LE) has been run on a T-Echo: driven over USB by this project's host adapter, and over Bluetooth LE from a Linux PC and from Sideband on one Android phone, which connected while the T-Echo exchanged packets with a Supreme over the air. Sideband showing the announces the board receives, other phones, rnsd, the reference RNodeInterface in its own Bluetooth mode (over USB it configured the T-Echo and sent announces with its default timing; through a Bluetooth bridge only once its 0.25 second readback wait was lengthened), range, and the ESP32 Bluetooth transport (compiled only) remain unverified.
Check every download with sha256sum -c SHA256SUMS.
What's Changed
- Evict a route when the path table is full, and learn paths whether or not the announce can be relayed by @mondain in #86
- Record the reference RNodeInterface and Supreme gateway findings by @mondain in #87
- Release 0.5.2 by @mondain in #88
Full Changelog: v0.5.1...v0.5.2