Repository navigation
Add heltec rc52 - #3032
Add heltec rc52#3032Quency-D wants to merge 8 commits into
Conversation
|
We will check and optimize power consumption of this board. |
IoTThinks
left a comment
IoTThinks
left a comment
There was a problem hiding this comment.
There are two places with missing '+<helpers/ui/NullDisplayDriver.cpp>' in
heltec_rc52_without_display_companion_radio_ble and heltec_rc52_without_display_companion_radio_usb
Please help to check.
|
@IoTThinks Thanks for catching this. I added +<helpers/ui/NullDisplayDriver.cpp> to both the BLE and USB without-display companion-radio environments in commit dd83853. While verifying the builds, I also updated the RC52 GPS initialization to use the current NmeaGpsDriver / MicroNMEALocationProvider API. Both affected environments now compile and link successfully. |
|
Great. Thanks and enjoy your day. |
|
Thanks! Please feel free to let me know if you run into any issues during testing. Enjoy your day too! |
Use pin index 0, which maps to NRFX_SPIM_PIN_NOT_USED, to avoid the nRF52 SPI constructor indexing g_ADigitalPinMap[255]. Remove the absent MISO shutdown reset so the sentinel cannot reset physical P0.00. Follows the variant-side fixes in meshcore-dev#3188 and meshcore-dev#3189. Validated heltec_rc52_repeater and heltec_rc52_companion_radio_ble builds. ELF disassembly confirms the MISO lookup uses map[0]=0xFF instead of the +1020-byte read and shutdown has no P0.00 reset. No hardware testing performed.
This PR adds Heltec RC52 support as a new nRF52840 board target for MeshCore.
It introduces the heltec_rc52 board definition, variant files, and PlatformIO environments for the core RC52 firmware matrix: repeater, room server, companion radio over BLE/USB, and KISS modem, with display and without-display variants where applicable.
The RC52 display path uses the shared NV3001B driver with injected SPI1 support for the nRF52 display bus. The default NV3001B ESP32 hardware SPI behavior remains unchanged for existing boards.