reticulum-cFIRMWARE INSTALLERSource & releases ↗

OPEN MESH. YOUR HARDWARE.

A radio, ready
for your network.

Install reticulum-c over USB, then set up your LoRa node.
Your firmware and settings stay between this browser and your board.

No account. No cloud connection.
Just your browser and a USB cable.

01 / HARDWARE

What are we connecting?

Choose the exact board and radio variant. A matching chip alone does not mean a matching pin map.

Loading firmware catalogue…

02 / FIRMWARE

Install your firmware.

Not connected

Select your board above to get started.

Installation mode

Checking available firmware…

Downloads & checksums

These checksums come from this site's catalog. They detect corrupted downloads, not a compromised host; the release archives on GitHub carry an independent SHA256SUMS.

Activity log

03 / SETUP

Make it your node.

LoRa starts disabled. Read the saved settings, choose your parameters, then save them to the board.

No settings session

After clicking Connect, press RESET on the board within the countdown shown below (60 seconds). The board restarts, and the connection is restored automatically. Stop any serial monitor first.

Node settings

Settings are only sent after a setup prompt is detected.

01

A node, or an RNode modem.

By default reticulum-c runs the Reticulum node on your board. It answers /echo and /info and can bridge USB or Wi-Fi to LoRa. “Run as: RNode modem” makes the board a LoRa modem for Sideband or rnsd instead (short checks only; optional Bluetooth with a PIN, tested on the T-Echo only; Sideband on Android connected over BLE and the board exchanged packets with a second station; in Sideband turn on “Device requires BLE”). The T-Echo and T-Beam Supreme show a status page, with the Bluetooth PIN only while pairing. RNode EEPROM provisioning is not used.

02

Know what’s been tested.

“Bench tested” means a short hardware exchange on T-Echo and Supreme SX1262. Other boards have build and model coverage. Range, sustained load, and stock RNode interoperability remain unverified.

03

Keep a recovery path.

Use a data-capable USB cable. If a device will not connect, follow its BOOT / RESET instructions. UF2 and command-line firmware downloads remain available below each release.