-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
no advertising with ESP32-C6 #645
Comments
Confirmed, error code 0x0207, BLE_ERR_MEM_CAPACITY when setting the advertisement data. Will advertise when commenting out the data setting and allow connection but crashes immediately. Looks to be caused by the memory system either not being initialized or missing a step somewhere. I haven't been able to get the debugging to work on the C6 as openocd can't find the config file. My suspicion is a memory conflict with the controller which is frustratingly closed source so I cannot walk through it. |
I am having this same issue as well with the esp32-c6-test branch. I'm using this library with a SparkFun ESP32-C6 Qwiic Pocket Development Board which uses a ESP32-C6 Mini-1 SoC. I'm not much of a C dev and Bluetooth is magic to me but please let me know if there's anything I can do to help here. Happy to test or validate any fixes for this library in Arduino or Platformio if needed. |
This is a pretty major mod to the upstream code and will take time to sort out, I will post here when there are changes pushed for testing. |
TAS moved to core 3.0.0 for TAS version 14+, and BLE seems broken. I am guessing this could be related? |
@btsimonh Not fully correct. Tasmota does use esp-nimble-cpp |
Pinned this issue to describe the difficulty in supporting future espressif mcu's. They have internally begun using NimBLE for the controller which causes many conflicts that I will try to describe.
With all of these factors considered, unless espressif or someone with more free time than me can help, I don't think the new devices using NimBLE controllers will ever be supported in a meaningful way. The only reasonable way to move this forward that I can see is integration into the Arduino core, perhaps as an option, which I may propose. Otherwise, please use esp-nimble-cpp with Arduino as a component instead of this repo if you need support for the esp32c6, esp32c2, esp32h2, and likely all new BLE enabled espressif MCU's 😢 |
sorry to hear that.. you've done a phenomemal job! |
@h2zero One of the many reasons you have listed why we (Tasmota) forked Arduino and IDF and build our own Arduino framework and use your great working I agree with you, as it is now The esp32-c6 is really a "monster" despite the fact it is only a single core MCU. Works fine with your BLE lib |
Thanks for the support! I wouldn't say this repo is dead yet though, still works for the older chips 🙂. |
Sorry don't want to be negative. I wrote dead for core > 2.x |
There is a silver lightning. espressif Arduino guys are working on a way to make it easy possible to configure and compile the Arduino libs for personal needs. |
That would be great if they did that 🙂. Just to clarify, this repo still works with core 3.x, just not with the newer chips. The interesting thing is I did get it to work as a scanner but advertising seems impossible. |
@mhaberler If espressif and Platformio doesn't find an agreement so that Arduino core 3.0.0 is not supported with Platformio, I am considering to do a Platformio Arduino 3.0.0 espressif32 core compatible with |
I've opened an issue upstream here: espressif/arduino-esp32#9835 Please add your thoughts if you would like. |
Closing this as C6/H2/C2 and all future BLE Espressif chip support will not be pursued here any further. See #685 |
This is a follow up for #642 ticket.
Branch: https://github.com/h2zero/NimBLE-Arduino/tree/esp32-c6-test
most recent Arduino Core 3.0.0-alpha3
NimBLE Server sketch from examples folder
The boot sequence is fine:
However, the ESP32-C6 device is not seen in Nordic tool.
When I build and run the sketch with the same Core but for ESP32-C3 target - everything looks just fine:
The text was updated successfully, but these errors were encountered: