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.
This commit is contained in:
parent
544d459c9b
commit
d0e5fc9ab7
4 changed files with 57 additions and 0 deletions
11
README.md
11
README.md
|
|
@ -2,3 +2,14 @@
|
|||
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.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue