Support heltec V3 board capabilities #100
Merged
Conversation
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
This was referenced Feb 23, 2023
This was referenced Feb 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR adds support for the latest V3 boards:
WIFI_Kit_32_V3andWIFI_LoRa_32_V3Without this, things like the screen, wifi, and lora do not work!
Because
heltec.cppchecks for specific board macros.Since Heltec now has a lot of boards in their inventory, I refactored
heltec.hto map each board to certain capabilities:Heltec_Wifi,Heltec_LoRa,Heltec_Screen,Heltec_VextThen I changed the code in
heltec.cppto check for capabilities, not specific boards.This will make it much easier to release new boards in the future.
Should fix #96 and #97
❤️ Heltec!