Zhiyang
November 29, 2018, 7:20pm
1
I tried to control bluetooth in TX2.
After I login to bluetoothctl command, it shows following error:
[bluetooth]# power on
No default controller available
[bluetooth]# show
No default controller available
However, I have checked following command and it seems everything goes well.
# hciconfig -a
hci0: Type: BR/EDR Bus: UART
BD Address: 00:04:4B:8C:98:BE ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:1469 acl:0 sco:0 events:87 errors:0
TX bytes:2589 acl:0 sco:0 commands:87 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'jetson-tx2-07c42aa'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.1 (0x7) Revision: 0x1000
LMP Version: 4.1 (0x7) Subversion: 0x610c
Manufacturer: Broadcom Corporation (15)
# hcitool dev
Devices:
hci0 00:04:4B:8C:98:BE
rivs@arroway:/$ bluetoothctl
# rfkill list
0: bluedroid_pm: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Crisliu7,
Could you try to scan other devices?
Zhiyang
November 30, 2018, 3:43pm
3
I could use hcitool scan
to scan other devices. However, I have to use bluetoothctl
to make TX2 discoverable and pairable.
Hi Crisliu7,
Could you try using default setting to connect the BT?
All settings → Bluetooth
what do you mean by “default setting”?
Hi Crisliu7,
Default setting means from below path to connect BT:
System Settings → Bluetooth → Turn on Bluetooth → Try to pair your BT device.
Thanks!
But my TX2 doesn’t have desktop, I can only control the bluetooth from command line.
Hi Crisliu7,
Test with bluetoothctl tool, confirmed I can paring successful on TX2/JetPack-3.3.
[bluetooth]# pair B4:CE:F6:30:52:16
Attempting to pair with B4:CE:F6:30:52:16
[CHG] Device B4:CE:F6:30:52:16 Connected: yes
Request confirmation
[agent] Confirm passkey 382962 (yes/no): yes
[CHG] Device B4:CE:F6:30:52:16 Modalias: bluetooth:v000Fp1200d1436
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 Paired: yes
Pairing successful
Please following below link steps to test again or please try with JetPack-3.3:
https://docs.ubuntu.com/core/en/stacks/bluetooth/bluez/docs/reference/pairing/outbound
carolyuu:
Hi Crisliu7,
Test with bluetoothctl tool, confirmed I can paring successful on TX2/JetPack-3.3.
[bluetooth]# pair B4:CE:F6:30:52:16
Attempting to pair with B4:CE:F6:30:52:16
[CHG] Device B4:CE:F6:30:52:16 Connected: yes
Request confirmation
[agent] Confirm passkey 382962 (yes/no): yes
[CHG] Device B4:CE:F6:30:52:16 Modalias: bluetooth:v000Fp1200d1436
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device B4:CE:F6:30:52:16 Paired: yes
Pairing successful
Please following below link steps to test again or please try with JetPack-3.3:
https://docs.ubuntu.com/core/en/stacks/bluetooth/bluez/docs/reference/pairing/outbound
Yep, when you login to bluetoothctl, you can see your bluetooth controller on TX2. However, for my TX2, it always shows
No default controller available
I can do nothing because the bluetoothctl cannot detect there is bluetooth controller on my TX2.
However, the
hcitool dev
shows there is really bluetooth component on my TX2
Zhiyang
December 7, 2018, 3:35am
10
Here is my status
rivs@zelda:/$ hcitool dev
Devices:
hci0 00:04:4B:8C:D8:44
rivs@zelda:/$ rfkill list
0: bluedroid_pm: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[bluetooth]# show
No default controller available
[bluetooth]# scan on
No default controller available
Hi Crisliu7,
Please try below command and run bluetoothctl tool again:
sudo rfkill unblock bluetooth
Zhiyang
December 7, 2018, 3:56am
12
it seems no use, cuz it already shows no block here
0: bluedroid_pm: Bluetooth
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Hi Crisliu7,
What’s image version are you using on TX2?
Please try JetPack-3.3 (r28.2.1). Thanks!
Zhiyang
December 7, 2018, 4:05pm
14
Here is my info
rivs@zelda:~/jetsonUtilities$ python jetsonInfo.py
NVIDIA Jetson TX2
L4T 28.2.0 [ JetPack UNKNOWN ]
Board: t186ref
Ubuntu 16.04.4 LTS
Kernel Version: 4.4.38-l4t-r28.2+g174510d
CUDA NOT INSTALLED
I would suggest you to use the original Jetpack with HDMI connected and try with GUI.
If GUI still has error during BT scan/pair, please share the result of kernel log with command “dmesg” after the connection.