The kernel is fine, i've tested it on a xenial image: -add to config.txt:
dtoverlay=pi3-miniuart-bt core_freq=250 -grab raspberry's bluez and bluez-firmware packages: https://archive.raspberrypi.org/debian/pool/main/b/bluez-firmware/bluez- firmware_1.2-3+rpi1_all.deb and install both -reboot your board, then: $ dmesg | grep tty ... [ 4.589607] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2 the PL011 tty is the one we want, and it's the ttyAMA0: $ hciattach /dev/ttyAMA0 bcm43xx 921600 noflow - bcm43xx_init Flash firmware /lib/firmware/BCM43430A1.hcd Set Controller UART speed to 921600 bit/s Device setup complete $ hcitool dev Devices: hci0 B8:27:EB:BA:51:89 Turn on bluetooth on your phone and make it discoverable: $ hcitool scan Scanning ... A4:B4:C8:6E:0D:5A My Android phone A couple of notes: 1) the bluez-firmware contains the adapter fw files, so it's mandatory (though it install the files in /lib/firmware while our hcitool search for stuff in /etc/firmware) 2) I've tried to reproduce it with our bluez package/hcitool, but we are missing something - so i extracted all the relevant patches from raspbery's bluez package, applied to the ubuntu one and tested again: it was a bit better, but i was still getting a timeout during fw loading, so for this example i decided to use raspberry's deb - ironically, after the first timeout, if i rerun hcitool, this time it worked fine and the adapter was configured succesfully -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674509 Title: Unable to find bluetooth device on RPi3 running Ubuntu Core 16 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1674509/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
