Sorry to dig this up but I am having the same problem as jonn and Bryan 
with a BBAI. 
Has anyone found a solution, in the meantime? 

Thanks!!
On Tuesday, April 21, 2020 at 8:08:25 AM UTC+2 jonn...@gmail.com wrote:

>   Yeah, an external BT device might be the solution but if the BT/BLE 
> feature is not support on the BBAI, then it should be stated as such and 
> listed as WiFi only.
>
> I've tried a few more things but still I can't get it to work or even show 
> an address.
>
> $ sudo modprobe hci_uart 
> debian@beaglebone:~$ sudo lsmod |grep hci
> hci_uart               69632  0
> btqca                  16384  1 hci_uart
> bluetooth             548864  11 btsdio,hci_uart,btqca,bnep
>
> systemctl enable bluetooth.service
> systemctl start bluetooth.service
>
>
> I am not sure why 'hciuart.service' is missing:
> $debian@beaglebone:~$ sudo systemctl status hciuart.service
> Unit hciuart.service could not be found
>
> $ sudo ls /lib/systemd/system/hciuart.service
> ls: cannot access '/lib/systemd/system/hciuart.service': No such file or 
> directory
>
>
> debian@beaglebone:~$ sudo lsmod |grep -i sdio
> btsdio                 16384  0
> bluetooth             548864  9 btsdio,bnep
>
>
> This is what I see from 'dmesg'
>
> debian@beaglebone:~$ dmesg  |grep -Ei 'blue|firm'
> [   23.488304] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: 
> Mar  1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4
> [   25.046041] vpe 489d0000.vpe: loading firmware vpdma-1b8.bin
> [   25.736322] Bluetooth: Core ver 2.22
> [   25.736564] Bluetooth: HCI device and connection manager initialized
> [   25.736605] Bluetooth: HCI socket layer initialized
> [   25.736636] Bluetooth: L2CAP socket layer initialized
> [   25.736745] Bluetooth: SCO socket layer initialized
> [   25.790364] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
> [   30.510745] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [   30.510768] Bluetooth: BNEP filters: protocol multicast
> [   30.510807] Bluetooth: BNEP socket layer initialized
> [ 1535.224971] Bluetooth: HCI UART driver ver 2.3
> [ 1535.224998] Bluetooth: HCI UART protocol H4 registered
> [ 1535.230749] Bluetooth: HCI UART protocol LL registered
> [ 1535.230779] Bluetooth: HCI UART protocol ATH3K registered
> [ 1535.230803] Bluetooth: HCI UART protocol Three-wire (H5) registered
> [ 1535.230821] Bluetooth: HCI UART protocol QCA registered
>
>
>
> Still, not working:
> $ sudo hciconfig -a
> hci0: Type: Primary  Bus: SDIO
> BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
> DOWN 
> RX bytes:0 acl:0 sco:0 events:0 errors:0
> TX bytes:0 acl:0 sco:0 commands:0 errors:0
> Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DH1 HV1 
> Link policy: 
> Link mode: SLAVE ACCEPT 
>
>
> debian@beaglebone:~$  sudo bluetoothd -d -n
> bluetoothd[1997]: Bluetooth daemon 5.50
> bluetoothd[1997]: src/main.c:parse_config() parsing /etc/bluetooth/main.
> conf
> bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “
> DiscoverableTimeout” in group “General”
> bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “
> PairableTimeout” in group “General”
> bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “
> Privacy” in group “General”
> bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “
> Name” in group “General”
> bluetoothd[1997]: src/main.c:parse_config() class=0x020100
> bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “
> DeviceID” in group “General”
> bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “
> ReverseServiceDiscovery” in group “General”
> bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “
> MinEncKeySize” in group “GATT”
> D-Bus setup failed: Name already in use
> bluetoothd[1997]: Unable to get on D-Bus
>
>
> debian@beaglebone:~$ sudo hciconfig hci0 up                               
>      
>  Can't init device hci0: Input/output error (5)
>
> debian@beaglebone:~$ sudo bluetoothctl
> Agent registered
> [bluetooth]# list
> [bluetooth]# show
> No default controller available
> [bluetooth]# power on
> No default controller available
>
>
> From what I can gather, this is the BT device on the BBAI but I am not 
> sure where to get a driver for it.
> https://deviwiki.com/wiki/AzureWave_AW-CM256SM
>
>
>
> I'm not sure what else to try.
>
> Cheers,
>
> Jon
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f4c802a5-e987-47be-b248-0806a2640a36n%40googlegroups.com.

Reply via email to