[FS#3527] On-Board Intel Bluetooth firmware not working due to two missing files

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - saket424 (saket424) 

Attached to Project - OpenWrt/LEDE Project
Summary - On-Board Intel Bluetooth firmware not working due to two missing files
Task Type - Bug Report
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - 
   

 Environment: Openwrt x86_64 snapshot Dec 22, 2020

ibt-firmware - 20201118-3

Description:
bluetooth finally works with openwrt snapshot on the odyssey https://www.seeedstudio.com/ODYSSEY-X86J4105864-p-4447.html

I had to copy the two missing files from ubuntu 20.04 intel firmware to /lib/firmware/intel instead of /usr/lib/firmware/intel

root at OpenWrt:~# grep -i bluetooth dmesg.log

[ 10.977163] Bluetooth: Core ver 2.22

[ 10.980827] Bluetooth: HCI device and connection manager initialized

[ 10.982803] Bluetooth: HCI socket layer initialized

[ 10.984697] Bluetooth: L2CAP socket layer initialized

[ 10.986626] Bluetooth: SCO socket layer initialized

[ 10.989246] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

[ 10.991006] Bluetooth: BNEP filters: protocol multicast

[ 10.992754] Bluetooth: BNEP socket layer initialized

[ 11.073509] Bluetooth: HCI UART driver ver 2.3

[ 11.075399] Bluetooth: HCI UART protocol H4 registered

[ 11.077318] Bluetooth: HCI UART protocol BCSP registered

[ 11.079240] Bluetooth: HCI UART protocol ATH3K registered

[ 11.081567] Bluetooth: HIDP (Human Interface Emulation) ver 1.2

[ 11.083526] Bluetooth: HIDP socket layer initialized

[ 11.288000] Bluetooth: RFCOMM TTY layer initialized

[ 11.289894] Bluetooth: RFCOMM socket layer initialized

[ 11.291778] Bluetooth: RFCOMM ver 1.11

[ 11.340970] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015

[ 11.345008] Bluetooth: hci0: Device revision is 2

[ 11.348458] Bluetooth: hci0: Secure boot is enabled

[ 11.350346] Bluetooth: hci0: OTP lock is enabled

[ 11.352222] Bluetooth: hci0: API lock is enabled

[ 11.354100] Bluetooth: hci0: Debug lock is disabled

[ 11.355948] Bluetooth: hci0: Minimum firmware build 1 week 10 2014

[ 11.401913] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi

[ 12.961480] Bluetooth: hci0: Waiting for firmware download to complete

[ 12.964139] Bluetooth: hci0: Firmware loaded in 1585771 usecs

[ 12.966825] Bluetooth: hci0: Waiting for device to boot

[ 12.979960] Bluetooth: hci0: Device booted in 12897 usecs

[ 12.982705] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc

[ 12.988010] Bluetooth: hci0: Applying Intel DDC parameters completed

I also did

opkg install ibt-firmware

root at OpenWrt:/lib/firmware/intel# ls -l

-rw-r--r-- 1 root root 14 Dec 22 23:15 ibt-17-16-1.ddc

-rw-r--r-- 1 root root 664012 Dec 22 23:15 ibt-17-16-1.sfi

-rw-r--r-- 1 root root 22069 Nov 28 17:19 ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq

-rw-r--r-- 1 root root 25853 Nov 28 17:19 ibt-hw-37.7.10-fw-1.0.2.3.d.bseq

-rw-r--r-- 1 root root 23105 Nov 28 17:19 ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq

-rw-r--r-- 1 root root 25775 Nov 28 17:19 ibt-hw-37.7.10-fw-1.80.2.3.d.bseq

-rw-r--r-- 1 root root 96 Nov 28 17:19 ibt-hw-37.7.bseq

-rw-r--r-- 1 root root 31056 Nov 28 17:19 ibt-hw-37.8.10-fw-1.10.2.27.d.bseq

-rw-r--r-- 1 root root 39295 Nov 28 17:19 ibt-hw-37.8.10-fw-1.10.3.11.e.bseq

-rw-r--r-- 1 root root 45954 Nov 28 17:19 ibt-hw-37.8.10-fw-22.50.19.14.f.bseq

-rw-r--r-- 1 root root 96 Nov 28 17:19 ibt-hw-37.8.bseq

root at OpenWrt:/lib/firmware/intel# opkg list-installed | grep ibt-firmware

ibt-firmware - 20201118-3

root at OpenWrt:/lib/firmware/intel#

root at OpenWrt:~# hciconfig hci0 up

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3527

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.