Add Bluetooth Proxy board definitions for wESP32 modules #142
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
x-cubed
force-pushed
the
main
branch
2 times, most recently
from
7ba6311
to
f1e504d
Compare
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.
The Silicognition wESP32 boards are ESP32 modules that have onboard ethernet supporting Power-over-Ethernet (PoE).
There are two hardware variants:
Both hardware variants use the same GPIO pinout, as described in the wESP32 Product Brief.
Given that these boards are similar to the Olimex ESP32 PoE ISO boards, I've used that file as the foundation for these wESP32 board files.
I've been able to successfully build both variants, and I've successfully deployed a Bluetooth Proxy on one of the LAN8270 wESP32 boards.