jlpoole/microReticulumTbeam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
microReticulum as used on the LilyGo T-Beam SUPREME
12 commits 2 branches 0 tags 2 MiB
Find a file
John Poole d0e5fc9ab7 Start of migration to microReticulumFirmware from microReticulm after Chad comment on Matrix clarifying the two projects and my conflating the two after returning from a test in Meshtastic. ChatGPT has handled the integration, but we have not tested the migration against any of the exercises. Note: the SD card exercise needs an Issue logged about its failure at start-up and the need to remove and re-insert a card before it can be read.
2026-02-14 09:22:55 -08:00
docs Start of migration to microReticulumFirmware from microReticulm after Chad comment on Matrix clarifying the two projects and my conflating the two after returning from a test in Meshtastic. ChatGPT has handled the integration, but we have not tested the migration against any of the exercises. Note: the SD card exercise needs an Issue logged about its failure at start-up and the need to remove and re-insert a card before it can be read. 2026-02-14 09:22:55 -08:00
exercises RTC keeps time between POWER OFF & ON, SD Card at start still needs work -- if card is in the slot, it is not readable until it is pulled on and then inserted. 2026-02-13 18:52:17 -08:00
external Start of migration to microReticulumFirmware from microReticulm after Chad comment on Matrix clarifying the two projects and my conflating the two after returning from a test in Meshtastic. ChatGPT has handled the integration, but we have not tested the migration against any of the exercises. Note: the SD card exercise needs an Issue logged about its failure at start-up and the need to remove and re-insert a card before it can be read. 2026-02-14 09:22:55 -08:00
img Exercises 00 & 01 working, Documentation still in progress, moving to my source control server. 2026-02-13 14:03:09 -08:00
shared/boards/tbeam-s3-core Exercises 00 & 01 working, Documentation still in progress, moving to my source control server. 2026-02-13 14:03:09 -08:00
tools Add host-side rns-provision tool and portable build infrastructure 2026-02-12 11:17:48 -08:00
.gitignore Exercises 00 & 01 working, Documentation still in progress, moving to my source control server. 2026-02-13 14:03:09 -08:00
.gitmodules Start of migration to microReticulumFirmware from microReticulm after Chad comment on Matrix clarifying the two projects and my conflating the two after returning from a test in Meshtastic. ChatGPT has handled the integration, but we have not tested the migration against any of the exercises. Note: the SD card exercise needs an Issue logged about its failure at start-up and the need to remove and re-insert a card before it can be read. 2026-02-14 09:22:55 -08:00
CMakeLists.txt Compiles, needs some extra tweaking 2026-02-12 10:53:31 -08:00
LICENSE Initial commit 2026-02-12 08:12:57 -08:00
README.md Start of migration to microReticulumFirmware from microReticulm after Chad comment on Matrix clarifying the two projects and my conflating the two after returning from a test in Meshtastic. ChatGPT has handled the integration, but we have not tested the migration against any of the exercises. Note: the SD card exercise needs an Issue logged about its failure at start-up and the need to remove and re-insert a card before it can be read. 2026-02-14 09:22:55 -08:00

README.md

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.