heltec-ht62-esp32c3-sx1262: Assign GPIO18 and GPIO19 to I2C #4147
Conversation
This file contains 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 pull request has been mentioned on Meshtastic. There might be relevant details there: https://meshtastic.discourse.group/t/heltec-ht-ct62-support-meshtastics-future/11391/15 |
caveman99
requested changes
Jun 20, 2024
ndoo
force-pushed
the
ht-ct62-i2c
branch
2 times, most recently
from
636160a
to
51dd71c
Compare
|
Pushed changes to address the review feedback. Still very much an RFC, given the very limited GPIO available, we have to figure out what mapping makes the most sense for the community. Why Heltec exposed GPIO that were already connected to the SX1262 beats me, probably just due to PCB routing limitations or not using blind vias, with however many layers they are using. |
caveman99
approved these changes
Jun 20, 2024
I2C is not defined on schematics, but these are the only free GPIO exposed on the castellated pads. There are pin mux conflicts: GPIO18 = USB_DN and GPIO19 = USB_DP. Since the HT-DEV-ESP provides a CP2102, re-use these ports for I2C instead since it's more useful (attaching peripherals vs. connecting to a host PC). Boards which use the native ESP32 USB will require a separate variant (refer to Heltec HRU-3601 variant for example). Perhaps a "heltec_esp32c3_usb" variant would make things easier? Took the opportunity to clean up the variant's header files too. Signed-off-by: Andrew Yong <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I2C is not defined on schematics, but these are the only free GPIO exposed on the castellated pads.
There are pin mux conflicts: GPIO18 = USB_DN and GPIO19 = USB_DP.
Since the HT-DEV-ESP provides a CP2102, re-use these ports for I2C instead since it's more useful (attaching peripherals vs. connecting to a host PC). Boards which use the native ESP32 USB will require a separate variant (refer to Heltec HRU-3601 variant for example).
Perhaps a "heltec_esp32c3_usb" variant would make things easier?
Took the opportunity to clean up the variant's header files too.
Relevant forum post/discussion in Heltec HT-CT62 support - Meshtastic’s future?#14.