This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC33XX-SOFTWARE: CC33XX BLE Connection Fails with Reason 1 After Short Success

Part Number: CC33XX-SOFTWARE

Tool/software:

Hello,

I’ve successfully integrated the CC33XX Linux driver (v1.0.0.8) into my Yocto (Scarthgap) image. BLE scanning works fine, and I can find nearby devices using bluetoothctl.
However, when I try to connect to a BLE device, the connection succeeds momentarily but then disconnects shortly after with reason 1.

Procedure:

1- cd /usr/share/cc33xx
2- ./ap_start.sh
3- ./ ble_enble.sh
4- hciconfig hci0 up
none of them fails and then using bluetoothctl I scan for available devices then try to connect to one of them.

LOG from bluetoothctl:

[bluetooth]# connect D0:2E:AB:96:8B:65
Attempting to connect to D0:2E:AB:96:8B:65
hci0 D0:2E:AB:96:8B:65 type LE Public connected eir_len 15
[CHG] Device D0:2E:AB:96:8B:65 Connected: yes
Connection successful
[CHG] Device D0:2E:AB:96:8B:65 ServicesResolved: yes
[T115i SN:46775741]# info D0:2E:AB:96:8B:65
Device D0:2E:AB:96:8B:65 (public)
Name: T115i SN:46775741
Alias: T115i SN:46775741
Paired: no
Bonded: no
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Unknown (00005a90-0000-1000-8000-00805f9b34fb)
UUID: Unknown (0000fff0-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v02FEp0000d0110
ManufacturerData.Key: 0x02fe (766)
ManufacturerData.Value:
25 03 05 06 %...
hci0 D0:2E:AB:96:8B:65 type LE Public disconnected with reason 1
[CHG] Device D0:2E:AB:96:8B:65 ServicesResolved: no
[CHG] Device D0:2E:AB:96:8B:65 Connected: no


Any idea why the connection fails after short time?

Update:
the btmon-log shows that the remote sends a req. to update connection parameters and it gets rejected by the agent/kernel.

bluetoothd[3840]: < ACL Data TX: Handl.. flags 0x00 dlen 7 #65 [hci0] 7.031683
ATT: Read Request (0x0a) len 2
Handle: 0x0027 Type: PnP ID (0x2a50)
> ACL Data RX: Handle 3584 flags 0x02 dlen 16 #66 [hci0] 7.100355
LE L2CAP: Connection Parameter Update Request (0x12) ident 1 len 8
Min interval: 32
Max interval: 80
Peripheral latency: 0
Timeout multiplier: 400
< ACL Data TX: Handle 3584 flags 0x00 dlen 10 #67 [hci0] 7.100409
LE L2CAP: Connection Parameter Update Response (0x13) ident 1 len 2
Result: Connection Parameters rejected (0x0001)
> HCI Event: Number of Completed Packets (0x13) plen 5 #68 [hci0] 7.167702
Num handles: 1
Handle: 3584 Address: D0:2E:AB:96:8B:65 (Texas Instruments)
Count: 1
#65: len 7 (0 Kb/s)
Latency: 136 msec (50-136 msec ~109 msec)
> ACL Data RX: Handle 3584 flags 0x02 dlen 12 #69 [hci0] 7.211792
ATT: Read Response (0x0b) len 7
> HCI Event: Number of Completed Packets (0x13) plen 5 #70 [hci0] 7.253243
Num handles: 1
Handle: 3584 Address: D0:2E:AB:96:8B:65 (Texas Instruments)
Count: 1
#67: len 10 (0 Kb/s)
Latency: 152 msec (50-152 msec ~131 msec)
> HCI Event: Disconnect Complete (0x05) plen 4 #71 [hci0] 35.423326
Status: Success (0x00)
Handle: 3584 Address: D0:2E:AB:96:8B:65 (Texas Instruments)
Reason: Connection Timeout (0x08)
@ MGMT Event: Device Disconnected (0x000c) plen 8 {0x0001} [hci0] 35.423573
LE Address: D0:2E:AB:96:8B:65 (Texas Instruments)
Reason: Connection timeout (0x01)
@ MGMT Event: Device Disconnected (0x000c) plen 8 {0x0002} [hci0] 35.423573
LE Address: D0:2E:AB:96:8B:65 (Texas Instruments)
Reason: Connection timeout (0x01)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0002} [hci0] 35.447424
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
LE Address: D0:2E:AB:96:8B:65 (Texas Instruments)


  • Hi,

    I have a couple of ideas that could be happening here.

    First if you are trying to connect to a phone you will need to have the resolving list on this can be done by calling

    hcitool lerlon

    Another thing could be if this device has connected before, it could have been previously bonded but the key was not saved.

    What agent mode are you using in bluetoothctl?

    Best,

    Rogelio

  • Hi RogelioD,

    I am still stuck with the same issue, the pairing is successful and I can connect to the remote device but shortly after I get disconnect.
            Reason: Connection Timeout (0x08)

    I am not trying to connect to a phone, It is a ble-device produced by my company.

    The agent I am using is "NoInputNoOutput". 

    I wonder why I receive a supervision timeout after around 29 seconds, eventhough it is set to 4 seconds.

    ATT: Read Request (0xx0a) len 2
    Handle: 0x0027 Type: PnP ID (0x2a50)
    > HCI Event: Number of Completed Packets (0x13) plen 5 #97 [hci0] 10.239751
    Num handles: 1
    Handle: 3584 Address: 60:98:66:03:3D:CC (Texas Instruments)
    Count: 1
    #96: len 7 (0 Kb/s)
    Latency: 74 msec (65-929 msec ~83 msec)
    > ACL Data RX: Handle 3584 flags 0x02 dlen 12 #98 [hci0] 10.330054
    ATT: Read Response (0x0b) len 7
    Value[7]: 01fe0200001001
    Handle: 0x0027 Type: PnP ID (0x2a50)
    Value[7]: 01fe0200001001
    > HCI Event: Disconnect Complete (0x05) plen 4 #99 [hci0] 40.022603
    Status: Success (0x00)
    Handle: 3584 Address: 60:98:66:03:3D:CC (Texas Instruments)
    Reason: Connection Timeout (0x08)
    @ MGMT Event: Device Disconnected (0x000c) plen 8 {0x0001} [hci0] 40.022674
    LE Address: 60:98:66:03:3D:CC (Texas Instruments)
    Reason: Connection timeout (0x01)
    @ MGMT Event: Device Disconnected (0x000c) plen 8 {0x0002} [hci0] 40.022674
    LE Address: 60:98:66:03:3D:CC (Texas Instruments)
    Reason: Connection timeout (0x01)
    


    > HCI Event: LE Meta Event (0x3e) plen 31 #12 [hci0] 5.081573
    LE Enhanced Connection Complete (0x0a)
    Status: Success (0x00)
    Handle: 3584
    Role: Central (0x00)
    Peer address type: Public (0x00)
    Peer address: 60:98:66:03:3D:CC (Texas Instruments)
    Local resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
    Peer resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
    Connection interval: 100.00 msec (0x0050)
    Connection latency: 10 (0x000a)
    Supervision timeout: 4000 msec (0x0190)
    Central clock accuracy: 0x00


  • Hi Sabeeh,
    Do you have an idea what causes the problem?


  • After investigating the related kernel log, I found something failed regarding the driver:

    [   21.136880] cc33xx_driver cc33xx.2.auto: Direct firmware load for ti-connectivity/cc33xx-nvs.bin failed with error -2


    Can it be the reason for the improper behavior, that the chip failed to load nvs file?

  • Hi mohamed,

    This message is expected, and I wouldnt put to much thought into it.

    Could you run

    btmon &

    before running bluetoothctl to see if we can get a better explanation on why you are timing out. Also did you try running this ?

    hcitool lerlon

    Best,

    Rogelio