sylvioalves
commented
2 months ago ESP32 in Zephyr only supports BLE, not BT classic. Converting this from BUG to Enhancement accordingly.
Open xG3nesis opened 2 months ago
sylvioalves
commented
2 months ago ESP32 in Zephyr only supports BLE, not BT classic. Converting this from BUG to Enhancement accordingly.
xG3nesis
commented
1 month ago I must confess, @sylvioalves, your answer has left me a bit underwhelmed. So, I have a trio of puzzlers for you:
If BT Classic isn't supported, how come my ESP32-PICO-D4 is happily chatting away via a simple Bluetooth RFCOMM serial connection? Magic?
If BT Classic isn't part of the deal, why not shout it from the rooftops in the Bluetooth documentation?
And lastly, if BT Classic is out of the picture, why didn't your post (updated on the 17th of june) include a neon sign making it clear which Bluetooth flavor (Classic or BLE) we're working with?
sylvioalves
commented
1 month ago Hi @xG3nesis, nice to hear that it is working as we have not yet tested it.
Let me tell you the background and reasoning that I consider it is not supported (yet).
When we started working on ESP32xx Bluetooth support in Zephyr, BT classic was still marked as "EXPERIMENTAL". We then decided to only add BLE support. It means we implemented and tested only BLE sample codes (and provide necessary changes to make it work). BT classic support was not handled in any way, neither checking nor testing. Up to now, we have not yet worked on it. That is the reason I initially considered this is not implemented. So it is really interesting to see it is already in place as you mentioned before.
For item 3) of the development overview, you are correct, we could have split BT/BLE in different lines to make it clear.
Anyway, thanks for enlightening me with kindly words about BT classic. I still do not have the solution for the issue though.
sylvioalves
commented
1 month ago It is also worth mentioning that there are some hidden BT configurations in ESP32 adapter. Those configurations (at least a few) could be related to BT classic. Take a look in this file to evaluate as well: https://github.com/zephyrproject-rtos/hal_espressif/blob/zephyr/zephyr/esp32/include/bt/esp_bt.h#L156
rftafas
commented
1 month ago Up to now, we have not yet worked on it. That is the reason I initially considered this is not implemented. So it is really interesting to see it is already in place as you mentioned before.
I'd like also to add that BT Classic is not on our roadmap either. But, being open source, if the community decides to go for it, we will help as much as possible (same applies to several other subsystems/features).
Hello everyone!
I'm working on implementing an A2DP Source using the A2DP source sample for my M5Stack Atom Echo, which is based on the ESP32-Pico-D4 architecture.
Everything seems to function correctly up to the AVDTP/A2DP establishment process. However, after my ESP32 connects to the L2CAP layer and opens channels, it immediately loses the connection, displaying the error message 0x13. I understand this indicates "Remote User Terminated Connection," but I'm encountering the same error message on my Kali VM (target on which i'm attempting to connect).
The goal, after establishing the AVDTP connection, is to discover the available "Stream Endpoints." Unfortunately, I'm currently unable to achieve this.
Logs and console output Below, you'll find my code and console output from my ESP32:
Here is a screenshot from my Kali VM:
This is what my
main.clooks like :Environment (please complete the following information):
Thank you in advance for your assistance! 😄