3

Background

I'm trying to get a BlueZ based userspace app running on a embedded Linux board to use nRF52832 as a Bluetooth connectivity chip. Seems like nRF52832 doesn't support the HCI interface.

  • If a Bluetooth device isn't registered as a HCI device (hciconfig returning nothing) does that mean it's impossible to use BlueZ for it?
  • In this talk (9:32) the BlueZ software architecture mentions HW drivers. Could those mean specific drivers for controlling the chips that don't expose the HCI interface?
  • There seems to be an official GATT driver mentioned in your link. It looks like it provides UART-like connectivity. Have you tried it? – Dmitry Grigoryev Nov 21 '16 at 17:38
  • 1
    @DmitryGrigoryev Yes, I perceive that as a Nordic specific API which would vendor lock me to their chip while interfacing the bluetooth devices through BlueZ would remain the API vendor neutral – TheMeaningfulEngineer Nov 21 '16 at 17:59
1

Alan, did you consider posing it in the linux-bluetooth mailing list? http://marc.info/?l=linux-bluetooth Though most of the posts there are patches and bugs, some questions are about such stuff, and most of these questions are addressed.

Regards, Rami Rosen

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.