Repository navigation
Add heltec rcc6 - #2981
Add heltec rcc6#2981Quency-D wants to merge 4 commits into
Conversation
|
We will check and optimize power consumption of this board. |
|
I can merge this PR for rc52 fine: #3032 Are they intentional? |
IoTThinks
left a comment
IoTThinks
left a comment
There was a problem hiding this comment.
This is a breaking and major change.
It breaks the PR of rc52.
| } | ||
|
|
||
| void NV3001BDisplay::writeCommand(uint8_t cmd) { | ||
| void NV3001BDisplay::beginTransport() { |
There was a problem hiding this comment.
This is a breaking and major change.
It breaks the PR of rc52.
| digitalWrite(PIN_TFT_SCL, LOW); | ||
| #else | ||
| spi.beginTransaction(SPISettings(SPI_FREQUENCY, MSBFIRST, SPI_MODE0)); | ||
| #endif |
There was a problem hiding this comment.
This is a breaking and major change.
It breaks the PR of rc52.
| int cursor_x = 0; | ||
| int cursor_y = 0; | ||
|
|
||
| void beginTransport(); |
There was a problem hiding this comment.
This is a breaking and major change.
It breaks the PR of rc52.
No, this wasn't intentional. I developed the display support for RCC6 and RC52 independently and didn't consider compatibility between the two implementations at the time. My plan was to wait until one of the PRs is merged, then update the other to resolve the conflicts and ensure both boards are supported. Thanks for pointing this out! |
|
I have merged rc52 into my variant for power consumption testing. You may help to adjust this PR a bit to fit RC32 (already merged) and RC52 (merged to my variant). |
merge Dev
Preserve SPI bus injection and platform-specific initialization alongside the RCC6 software SPI transport. Keep explicit nullptr construction compatible on ESP32.
This PR adds Heltec RCC6 support as a new ESP32-C6 board target for MeshCore.
It introduces the
heltec_rcc6board definition, variant files, and PlatformIO environments for the core RCC6 firmware matrix: repeater, room server, companion radio over BLE/USB/WiFi, and KISS modem, with display and without-display variants where applicable.The RCC6 display path uses the NV3001B driver with an opt-in software SPI transport and ESP32-C6 fast GPIO support. The default NV3001B hardware SPI behavior remains unchanged for existing boards.