Add support for using ESP32 pins to identify board for configuration. #147
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
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.
Adding initial support for using GPIO pin-based board variant detection. This will allow different boards to be identified and configuration be made without needing to use the config file on the SD card. This uses GPIO13 to identify whether it is a ESP32 A or B, and GPIO25, 26, 32, and 33 to create an identification byte. This will allow for up to 15 variants (1-15) to be detected, with the pulldowns creating a default configuration (0) that falls back on the config file as it has been functioning.
As we have already discussed, more work will need to be done to parameterize the device string for the CSV header.