So that said, the question, so to speak, is what is actually missing to be able to run a2dp?
Now, to answer that, I think I need to clarify my understanding of the stack/problem
What I see: vhci talks to hci talks to (mainly) btu talks to (mainly) btm talks to (mainly) bta talks to the code we want to write. Btm on down looks complete. Bta looks about 1/2 complete. I noticed the obvious lack of non-le functions for basics like scanning. I pulled back a version of blue droid a2dp which was fairly easy to make compile. (Also still need to try the support profiles). Obviously I can't discover/get the uuids/connect to non-le devices in the current state. That doesn't look too hard to add (famous last words I know!) but I'm guessing there's more missing. In fact, looking at the bta function tables and seeing all the {NULL, NULL} has me a bit worried.
Am I following the code roughly correctly? Am I in the ball park for work required? Is express-if working on this/expected to release it soon? Or is it something they don't care about? (Since that's less iot than other things...)
Thanks for everything it is so far! Having learned how the whole Bluetooth stack is put together I have a strong appreciation for just how tough a problem it is! When I searched for freertos and bluedroid (hoping someone somewhere had a more complete version I could port) all I found were companies looking for engineers with knowledge of both! So thanks again for getting it this far along!
