hi @tc61,
that sounds like a pretty quick port probably. A few things might help:
- this (big) thread about porting to new hardware: Building for NRF52 boards (kinda unstructured, but might be worth skimming)
- in short you mostly need to just add an entry to platformio.ini and configuration.h (to assign gpios). See here for a recent board that did this: https://github.com/meshtastic/Meshtastic-device/commit/5595fb38c1464804c2efbf164755c9172190b1ea
- all of the hardware you listed is already supported so I think 95% of the work is just configuration.h
- if you have questions/problems post either here or in the developer slack channel and I’m sure someone will help.
re: walkie talkie
I bet that could be added nicely using the (young so you might find bugs?) plugin api. You’d define a new port number for ‘voice’ and send those packets when the user sends.
re: gps
gps is optional, if the device doesn’t have one the android app will auto fill-in (using the same protocol). But the reason I’m a fan:
- I wanted weeklong runtime with location data for nodes. The gps (+ heavier CPU) in the phone burns a lot of current in that case.
- Every node having high quality time will eventually allow us to save more power by leaving even lora receivers sleeping most of the time, and turning on briefly to see if anyone in the mesh wants to send something. (That said, for nodes without a phone or a built in GPS, they will use (less good but not horrible) network time (as long as at least one node in the mesh has a GPS or phone).
- really cheap now adays