feat: add USB Companion Radio env for Heltec Wireless Paper#2315
Merged
liamcottle merged 1 commit intomeshcore-dev:devfrom Apr 18, 2026
Merged
Conversation
Collaborator
|
@ripplebiz can be safely merged |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds USB Companion Radio firmware environment for the Heltec Wireless Paper (ESP32-S3 + SX1262 + E-Ink).
Closes #2237
Changes
[env:Heltec_Wireless_Paper_companion_radio_usb]tovariants/heltec_wireless_paper/platformio.iniTesting
Tested on hardware (Heltec Wireless Paper):
Note: Full flash erase required before flashing (
pio run -t erase) to clear any data left by previously flashed firmware. Without erase, remnants in LittleFS from a previous firmware caused the Companion firmware to not initialize correctly.Note: The Heltec Wireless Paper uses a CP2102 USB-UART bridge (not native USB CDC). Connection via browser Web Serial API (e.g. meshcore.liamcottle.net) may fail due to DTR/RTS reset behavior. The MeshCore Android app connected via USB cable directly to the device worked correctly.