Not entirely sure about your scenario here, but if the dongle simply expects HCI communication and you manage to get a /dev/ttyUSB0 or whatever on NuttX side, then you should be able to use the bt_uart bridge to expose the controller to NuttX. From then on, you can choose to use NuttX host layer or an external one such as nimBLE.
Best, Matias On Wed, Mar 24, 2021, at 14:34, Tim wrote: > I hope this is not too much if a newbie/dumb question as I have tried to > research this first. > > > > I've been playing with Nuttx on a SAMA5D2-XULT board ahead of porting to my > custom board (SAMA5D27C-5M, actually), especially in regard to USB Host > functionality as that's what's drawn me to NuttX in the first place. > > > > USB memory sticks are recognised and I can mount them (not got automount to > work, yet - I'm still learning!; and date/time stamping of files written > doesn't seem to work either) - nice to have things like this work "out of > the box"! > > > > I can also build in Bluetooth support and the demo app, but as far as I can > tell there are no actual Bluetooth host drivers in NuttX to properly support > a detected Bluetooth device. My custom board actually has a SiLabs Bluetooth > module on it (connected to the SAM via UART and proven to work) but I quite > like the idea of just using plug-in Bluetooth devices instead :) > > > > I can see the device is detected (it gets powered, and dmesg reports stuff) > but no drivers are loaded as best as I can tell. Is that correct or have I > missed something? > > > > Drivers are not my strong point but, if I'm right and a driver will be > needed, is a generic Linux driver a good place to start were I to look to > add/create one to NuttX? Or maybe someone has already done this? > > > > > > Thanks, > > > > Tim. > > > >
