-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth support for all chips #93
Comments
I think there is no bluetooth for ESP32-S2? |
I just copy-pasted the list for all these issues haha my bad |
I think we can check ESP32-C2, don't we @bjoernQ? |
Do I understand correctly that "Bluetooth support" here is based on |
We can probably cut a release of bleps soon, it probably needs a bit of polish with some docs etc. Getting it out of "toy" state requires battle testing the thing, and contributions from the community to fill the gaps. |
Then maybe replace the words "toy state" with "early alpha", and add words like "contributions welcome" so people are motivated to contribute. "toy state" sounds to me like it isn't intended to ever be a real thing. |
It's important that esp-wifi doesn't depend on the bleps crate. What esp-wifi offers for Bluetooth is an HCI connection. For very simple use-cases like advertising only you could just pass it the HCI commands needed without using any stack. Unfortunately, there are not many options besides bleps for a no-std BLE stack currently. One promising crate is https://crates.io/crates/burble - they are considering making it no_std at some point. Another option would be to port/use Nimble (which is written in C). Initially bleps was really just meant to be used for the examples - that's why it says it's a toy. I think the biggest thing missing currently is pairing/bonding |
Update: I've started working on adding BLE for H2. |
The text was updated successfully, but these errors were encountered: