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 在短暂成功后以原因1失败

Guru**** 2325560 points
请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1491544/cc33xx-software-cc33xx-ble-connection-fails-with-reason-1-after-short-success

器件型号:CC33XX-SOFTWARE

工具/软件:

您好:

我已成功集成 CC33XX Linux 驱动程序(v1.0.0.8) 我的 Yocto (Scarthgap) 基本映像。 BLE 扫描工作正常,我可以找到附近的设备使用bluetoothctl.
但是、当我尝试连接到 BLE 器件时、连接会暂时成功、但随后又成功 原因1稍后断开

步骤:

1- CD /usr/share/cc33xx
2 -./ ap_start.sh
3 -./ ble_enble.sh
4- hciconfig hci0 up
它们都不会失败,然后使用 bluetoothctl 我扫描可用的设备,然后尝试连接到其中一个。

日志 在 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


是否知道为什么短时间后连接失败?

更新:
btmon-log 显示远程设备发送请求。 以更新连接参数、并被代理/内核拒绝。

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)


  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好、

    我有几个想法可能会在这里发生。

    首先、如果您尝试连接到电话、则需要通过致电来完成此问题的解决列表

    hcitool lerlon

    另一种情况可能 是、如果此设备之前已连接、则可能之前已绑定、但未保存密钥。

    您在 bluetoothctl 中使用了什么代理模式?

    此致、

    Rogelio

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    嗨、RogelioD、

    我仍然遇到同样的问题、配对成功、我可以连接到远程设备、但在断开连接后不久。
        原因:连接超时(0x08)

    我不想连接到手机、这是我公司生产的双设备。

    我使用的代理是"NoInputNoOutput"。  

    我想知道为什么我会在大约29秒后收到监听超时(尽管设置为4秒)。

    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

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。


    尊敬的 Sabeeh:
    您是否知道导致问题的原因?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。


    在调查相关内核日志后、我发现与驱动程序有关的问题失败:

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


     芯片无法加载 NVS 文件是不正确行为的原因吗?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Mohamed:

    我不会再想这件事了,也不会再想太多了。

    请运行一下

    btmon &

    在运行 bluetoothctl 之前、看看我们是否可以更好地解释您为什么要超时。  你也尝试运行这个吗?

    hcitool lerlon

    此致、

    Rogelio