microReticulum as used on the LilyGo T-Beam SUPREME
John Poole
398f0d8761
Fix late packet callback binding for inbound Links Handle the case where an inbound Link payload is decrypted before the app packet callback has been installed on that Link object. When Link::receive() sees decrypted plaintext with no packet callback, it now invokes the owner destination’s link-established callback as a late binding opportunity, then dispatches the already-decrypted payload if the callback was installed. This prevents valid inbound Link messages from ending at RNSLINKRX event=no_packet_callback after decrypt_ok, and allows the app-level RX handler to report the received payload. |
||
|---|---|---|
| docs | ||
| exercises | ||
| external | ||
| firmware/fieldtest_beacon | ||
| img | ||
| lib | ||
| shared | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| LICENSE | ||
| notes_Feb_18_2026.txt | ||
| README.md | ||
| SETUP_REQUIRED.txt | ||
microReticulumTbeam
microReticulum For Field Testing With LilyGo T-Beam SUPREMES
Field Testing Only. Used to specially program a group of T-Beams, each having the others' contact information and keys, which are then deployed in the field with people moving about to capture what was successfully sent and received and at what coordinates. Data is stored on SD cards and then retrieved at the end of the test an dumped into a PostgreSQL databse for analysis.
Dependency Direction
This repo is migrating from external/microReticulum to external/microReticulum_Firmware.
Goal:
- Reuse upstream T-Beam SUPREME integration work in
microReticulum_Firmware. - Avoid reimplementing already-solved board integration (PMU, SD, RTC, GPS, LoRa setup).
Status:
- Migration plan is tracked in
docs/microreticulum_firmware_migration.md. - Existing exercises remain functional during migration.