One more followup. No solution yet, but I can confirm the presence of the bluetooth hardware.
$ udevadm info /sys/bus/sdio/devices/* P: /devices/platform/44000000.ocp/480d1000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:1 L: 0 E: DEVPATH=/devices/platform/44000000.ocp/480d1000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:1 E: DRIVER=brcmfmac E: OF_NAME=wifi E: OF_FULLNAME=/ocp/mmc@480d1000/wifi@1 E: OF_COMPATIBLE_0=brcm,bcm4329-fmac E: OF_COMPATIBLE_N=1 E: SDIO_CLASS=00 E: SDIO_ID=02D0:A9BF E: MODALIAS=sdio:c00v02D0dA9BF E: SUBSYSTEM=sdio E: USEC_INITIALIZED=6733035 E: ID_VENDOR_FROM_DATABASE=Broadcom Corp. E: ID_SDIO_CLASS_FROM_DATABASE=Non-standard SDIO interface P: /devices/platform/44000000.ocp/480d1000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:2 L: 0 E: DEVPATH=/devices/platform/44000000.ocp/480d1000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:2 E: DRIVER=brcmfmac E: SDIO_CLASS=00 E: SDIO_ID=02D0:A9BF E: MODALIAS=sdio:c00v02D0dA9BF E: SUBSYSTEM=sdio E: USEC_INITIALIZED=6756368 E: ID_VENDOR_FROM_DATABASE=Broadcom Corp. E: ID_SDIO_CLASS_FROM_DATABASE=Non-standard SDIO interface P: /devices/platform/44000000.ocp/480d1000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:3 L: 0 E: DEVPATH=/devices/platform/44000000.ocp/480d1000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:3 E: DRIVER=btsdio E: SDIO_CLASS=02 E: SDIO_ID=02D0:A9BF E: MODALIAS=sdio:c02v02D0dA9BF E: SUBSYSTEM=sdio E: USEC_INITIALIZED=6730172 E: ID_VENDOR_FROM_DATABASE=Broadcom Corp. E: ID_SDIO_CLASS_FROM_DATABASE=Bluetooth Type-A standard interface There are some BBAI related Bluetooth scripts from https://github.com/RobertCNelson/boot-scripts/tree/master/boot under /opt/scripts/boot on the debian images. And there's an hci0 interface listed in hciconfig but results in an error if you try to enable it. It's also missing a MAC address: $ ls -l /sys/class/bluetooth/hci0 lrwxrwxrwx 1 root root 0 Jan 7 20:03 /sys/class/bluetooth/hci0 -> ../../devices/platform/44000000.ocp/480d1000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:3/bluetooth/hci0 $ hciconfig 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 $ sudo hciconfig hci0 up Can't init device hci0: Input/output error (5) I've seen example hciattach commands for raspberry pi boards with similar hardware, but I haven't found one that helps on the BBAI. I'm hoping someone else can chime in. I plan to test with other stock debian images from the beagleboard site, as I've been using customized images. To determine if this is a kernel version issue or something I broke. Just for reference, the official site for the Linux driver appears to be: https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211 (this is for the mrcmfmac driver) On Tuesday, January 7, 2020 at 10:27:15 AM UTC-5, Bryan Schneiders wrote: > > Additionally, it appears there's a bb-bbai-firmware package that I've > successfully enabled the wlan interface with but no bluetooth yet. Even > though the package claims to support bluetooth. > > $ dpkg -s bb-bbai-firmware > Package: bb-bbai-firmware > Status: install ok installed > Priority: extra > Section: misc > Installed-Size: 993 > Maintainer: Robert Nelson <[email protected]> > Architecture: all > Version: 1.20190803.2-0rcnee0~buster+20190803 > Pre-Depends: firmware-brcm80211, bb-wl18xx-firmware > Description: beagleboard.org bbai firmware > bbai bluetooth firmware > > $ dpkg -L bb-bbai-firmware > /. > /lib > /lib/firmware > /lib/firmware/brcm > /lib/firmware/brcm/brcmfmac43455-sdio.beagleboard.org > ,am5729-beagleboneai.txt > /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob > /lib/firmware/brcm/brcmfmac43455-sdio_am5729-beagleboneai.bin > /lib/firmware/brcm/fw_bcm43455c0_ag.bin > /lib/systemd > /lib/systemd/system > /lib/systemd/system/bb-bbai-tether.service > /usr > /usr/bin > /usr/bin/bb-bbai-tether > /usr/share > /usr/share/doc > /usr/share/doc/bb-bbai-firmware > /usr/share/doc/bb-bbai-firmware/changelog.Debian.gz > > $ dmesg | grep brcm > [ 8.464243] brcmfmac: brcmf_fw_map_chip_to_name: using > brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006 > [ 8.651023] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: > Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 > > $ ip link show dev wlan0 > 5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode > DEFAULT group default qlen 1000 > link/ether 80:91:33:4a:43:6d brd ff:ff:ff:ff:ff:ff > > $ hcitool dev > Devices: > > > On Monday, January 6, 2020 at 11:21:40 AM UTC-5, Bryan Schneiders wrote: >> >> I haven't yet accessed the Wifi or Bluetooth capabilities on the board >> but am currently investigating the same. >> >> The scripts distributed with the debian images are built for the WiLink >> 1835 module found in the BeagleBone Black Wireless board ( >> http://www.ti.com/product/WL1835MOD). See the bb-wl18xx-firmware >> package and associated files. >> >> The BBAI board uses an AzureWave AW-CM256SM module instead. >> >> https://github.com/beagleboard/beaglebone-ai/wiki/System-Reference-Manual#69-wireless-communication-80211-ac--bluetooth-azurewave-aw-cm256sm >> >> The AzureWave site doesn't mention this particular module and has no >> software support information. A leaked copy of their product documentation >> has hardware details: >> >> https://storage.googleapis.com/wzukusers/user-26561200/documents/5b7d0fe3c3f29Ct6k0QI/AW-CM256SM_DS_Rev%2015_CYW.pdf >> >> The AW documentation says this module is based on the CYW43455 chipset. >> There may be helpful resources here: >> https://community.cypress.com/community/linux >> >> >> On Monday, November 18, 2019 at 9:23:55 AM UTC-5, [email protected] >> wrote: >>> >>> I just got a new AI board and wanted to play around with the bluetooth, >>> but when I launch bluetoothctl, the list command says no controllers found. >>> >>> Is there any information out there on setting up bluetooth on this >>> board? I have google'd everything I could think of with no avail. I have >>> run systemctl status bluetooth and there are no issues, am I missing >>> something? >>> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/97fb7584-2688-4095-8b79-7c3c11390dfb%40googlegroups.com.
