hello
I am doing a bluetooth on the TX2，and give the log：
[bluetooth]# connect 14:B9:68:84:0D:4D
Attempting to connect to 14:B9:68:84:0D:4D
[CHG] Device 14:B9:68:84:0D:4D Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
The steps are as follows:
nvidia@tegra-ubuntu:~$ sudo hciconfig hci0 up
nvidia@tegra-ubuntu:~$ hciconfig -a
hci0: Type: BR/EDR Bus: UART
BD Address: 00:04:4B:8C:A5:72 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:347423 acl:59 sco:0 events:8048 errors:0
TX bytes:6647 acl:59 sco:0 commands:520 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: ‘tegra-ubuntu’
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Version: 4.1 (0x7) Revision: 0x1000
LMP Version: 4.1 (0x7) Subversion: 0x610c
Manufacturer: Broadcom Corporation (15)
nvidia@tegra-ubuntu:~$ bluetoothctl
[NEW] Controller 00:04:4B:8C:A5:72 tegra-ubuntu [default]
[NEW] Device 47:B8:18:E3:1E:18 47-B8-18-E3-1E-18
[NEW] Device 88:0F:10:A3:F3:FA MI_SCALE
[NEW] Device C9:34:01:64:68:FC C9-34-01-64-68-FC
[NEW] Device EF:F0:06:49:57:EC MI Band 2
[DEL] Device EF:F0:06:49:57:EC MI Band 2
[DEL] Device C9:34:01:64:68:FC C9-34-01-64-68-FC
[DEL] Device 88:0F:10:A3:F3:FA MI_SCALE
[DEL] Device 47:B8:18:E3:1E:18 47-B8-18-E3-1E-18
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:04:4B:8C:A5:72 Discovering: yes
[NEW] Device EF:F0:06:49:57:EC MI Band 2
[NEW] Device 4E:1D:99:76:6C:D7 4E-1D-99-76-6C-D7
[NEW] Device 14:B9:68:84:0D:4D HUAWEI G6-U00
[bluetooth]# pair 14:B9:68:84:0D:4D
Attempting to pair with 14:B9:68:84:0D:4D
[CHG] Device 14:B9:68:84:0D:4D Connected: yes
Request confirmation
[agent] Confirm passkey 408416 (yes/no): yes
[CHG] Device 14:B9:68:84:0D:4D Modalias: bluetooth:v001Dp1200d1436
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 14:B9:68:84:0D:4D Paired: yes
Pairing successful
[CHG] Device 14:B9:68:84:0D:4D Connected: no
[bluetooth]# connect 14:B9:68:84:0D:4D
Attempting to connect to 14:B9:68:84:0D:4D
[CHG] Device 14:B9:68:84:0D:4D Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 14:B9:68:84:0D:4D Connected: no
Thank you very much if can you any ideas!
Have you used “rfkill” to disable the sw-block?
What is your bt device?
Please refer the latest L4T document (rel-28.2). The section of “Bluetooth Device Settings”.
1、I using the TX2 own BT
2、I do just as the L4T document,but the result is fail
[HUAWEI G6-U00]# connect 14:B9:68:84:0D:4D
Attempting to connect to 14:B9:68:84:0D:4D
Failed to connect: org.bluez.Error.Failed
dgw_1985,
Could you connect BT with other platform? Just to make sure tx2 BT is working.
Hi WayneWWW,
I’m afraid I’m also having the same issue.
First I ensured that the RF sw-block was disabled:
nvidia@tegra-ubuntu:~$ 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
nvidia@tegra-ubuntu:~$
Then I got to the point where both the Jetson TX2 and my phone are paired but they just won’t connect e.g…
Jetson available:
[bluetooth]# show
Controller 00:04:4B:A5:75:5D
Name: tegra-ubuntu
Alias: tegra-ubuntu
Class: 0x100000
Powered: yes
Discoverable: yes
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Message Notification Se… (00001133-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no
nvidia@tegra-ubuntu:~$
Phone available:
[bluetooth]# info 94:7B:E7:9A:0A:37
Device 94:7B:E7:9A:0A:37
Name: Galaxy S8
Alias: Galaxy S8
Class: 0x5a020c
Icon: phone
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: PANU (00001115-0000-1000-8000-00805f9b34fb)
UUID: NAP (00001116-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (a23d00bc-217c-123b-9c00-fc44577136ee)
Modalias: bluetooth:v0075p0100d0201
Paired devices:
[bluetooth]# paired-devices
Device 94:7B:E7:9A:0A:37 Galaxy S8
[bluetooth]#
but then I consistently get this error message:
[bluetooth]# connect 94:7B:E7:9A:0A:37
Attempting to connect to 94:7B:E7:9A:0A:37
[CHG] Device 94:7B:E7:9A:0A:37 Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 94:7B:E7:9A:0A:37 Connected: no
[bluetooth]#
Which, as you can see, connects the device but then almost immediately disconnects it.
Please advise.
Regards,
Dan.
As an extra bit of information, I’ve also been trying to connect a Bose SoundLink Mini2 Bluetooth speaker to the TX2 but with exactly the same result.
The phone and my speakers work fine separately, just not with the TX2.
It is hard to tell whether it is a problem of tx2 bluetooth hardware issue or L4T sw issue. Since L4T only provides limited bluetooth profile, I can only suggest you to try the bluetooth guidance in L4T document.
https://developer.nvidia.com/embedded/dlc/l4t-documentation-28-2-ga
Hi WayneWWW,
I just wanted to point out that I found the solution to my problem. If you want Bluetooth speakers to work with the Jetson, then yes, all you have to do is follow the suggestions on the L4T reference documentation.
However, if you’re wanting to send files between devices e.g. from the TX2 to a phone (or vice versa), ensure that they are successfully paired, trusted and unblocked first (which I had done previously). The part that I then failed to acknowledge is that Bluetooth Low Energy (BLE) will only connect when you’re trying to send something!
The is why, in my case, the TX2 would connect with my phone successfully but then immediately disconnect - it was because I wasn’t actually trying to send it anything, hence, it disconnected by itself. Finally, when I tried to send a simple PDF, it performed the whole connect / send / disconnect procedure on its own.
I hope this helps you too dgw_1985!
Hello,
I have a similiar problem, I can pair the Jetson TX2 with my device (Shimmer 3 GSR+) but not connect.
If I try with Bluetoothctl:
[bluetooth]# connect 00:06:66:71:3C:81
Attempting to connect to 00:06:66:71:3C:81
[CHG] Device 00:06:66:71:3C:81 Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 00:06:66:71:3C:81 Connected: no
I try with rfcomm:
nvidia@tegra-ubuntu:~$ sudo rfcomm connect 0 00:06:66:71:3C:81
[sudo] password for nvidia:
Can't create RFCOMM TTY: Operation not supported
It also does not work with iPhone to connect.
And I don’t think that it uses BLE, I think it uses the normal Bluetooth.
Any Ideas? I need it as a /dev/rfcomm0 device in a python script then.