Firefly Open Source Community

   Login   |   Register   |
New_Topic

RK3399 Bluetooth: No HCI device

176

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
176
Posted at 4/21/2017 07:00:03     
Hi,

I'm trying to get bluetooth up and running on a headless RK3399 running Ubuntu.  The kernel certainly seems to see it:

mitchekl@firefly:/usr/bin$ dmesg | egrep -i 'blue|firm'
[    0.000000] psci: PSCIv1.0 detected in firmware.
[    0.211503] Bluetooth: Core ver 2.21
[    0.211590] Bluetooth: HCI device and connection manager initialized
[    0.211626] Bluetooth: HCI socket layer initialized
[    0.211657] Bluetooth: L2CAP socket layer initialized
[    0.211707] Bluetooth: SCO socket layer initialized
[    1.781735] Bluetooth: HCI UART driver ver 2.3
[    1.785455] Bluetooth: HCI UART protocol H4 registered
[    1.807823] Bluetooth: HCI UART protocol LL registered
[    2.140563] Bluetooth: RFCOMM TTY layer initialized
[    2.143705] Bluetooth: RFCOMM socket layer initialized
[    2.146821] Bluetooth: RFCOMM ver 1.11
[    2.149865] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.152954] Bluetooth: BNEP filters: protocol multicast
[    2.155976] Bluetooth: BNEP socket layer initialized
[    2.159068] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    2.164293] Bluetooth: HIDP socket layer initialized
[    2.215665] of_get_named_gpiod_flags: parsed 'uart_rts_gpios' property of node '/wireless-bluetooth[0]' - status (0)
[    2.215672] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 83.
[    2.218233] of_get_named_gpiod_flags: can't parse 'BT,power_gpio' property of node '/wireless-bluetooth[0]'
[    2.218256] of_get_named_gpiod_flags: parsed 'BT,reset_gpio' property of node '/wireless-bluetooth[0]' - status (0)
[    2.218262] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 9.
[    2.220787] of_get_named_gpiod_flags: parsed 'BT,wake_gpio' property of node '/wireless-bluetooth[0]' - status (0)
[    2.220793] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 90.
[    2.223294] of_get_named_gpiod_flags: parsed 'BT,wake_host_irq' property of node '/wireless-bluetooth[0]' - status (0)
[    2.223300] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 4.
[    3.190778] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/config.txt

However, whenever I look for an hci device I find nothing.  I've tried the following, all to no avail:

mitchekl@firefly:/usr/bin$ rfkill list all
0: bt_default: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
mitchekl@firefly:/usr/bin$ sudo rfkill unblock bluetooth
mitchekl@firefly:/usr/bin$ systemctl status bluetooth
bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2017-04-20 15:38:03 PDT; 3min 46s ago
     Docs: man:bluetoothd(8)
Main PID: 23993 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─23993 /usr/lib/bluetooth/bluetoothd

Apr 20 15:38:03 firefly systemd[1]: Starting Bluetooth service...
Apr 20 15:38:03 firefly bluetoothd[23993]: Bluetooth daemon 5.37
Apr 20 15:38:03 firefly systemd[1]: Started Bluetooth service.
Apr 20 15:38:03 firefly bluetoothd[23993]: Starting SDP server
Apr 20 15:38:03 firefly bluetoothd[23993]: Bluetooth management interface 1.10 initialized
mitchekl@firefly:/usr/bin$ hciconfig dev
Can't get device info: No such device

Any idea what I'm doing wrong, or if there is a more fundamental issue?

Thanks!

Reply

Use props Report

1821

Credits

10

Prestige

17

Contribution

super moderator

Rank: 8Rank: 8

Credits
1821
Posted at 4/28/2017 16:40:25     
Hi,
the bluetooth is unavailable in ubuntu, we will fix it later.
Reply

Use props Report

176

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
176
Posted at 4/30/2017 00:39:27     
Thanks! Could you point me to a central list of things that are not working in Ubuntu?  It would save some effort.
Reply

Use props Report

32

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
32
Posted at 7/4/2017 18:59:27     
Hi,
any news on this topic? It happened to me with the latest ubuntu firmware that bluetooth worked and I paired a bluetooth keyboard successfully with the board. And it worked without problem until I rebooted system. But it happened only once and I saw an error (dmesg) that only 4 cores were successfully initialized and last 2 failed.
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list