• State Not Answered
  • Replies 1 reply
  • Subscribers 73 subscribers
  • Views 108 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 341323
Options

nRF5340_CLAA , I have difficulty directly connecting to the Bluetooth on a Windows host

Jaden Huang

I am developing an application using the nRF5340 Bluetooth chip and have encountered an issue.

When I use the nRF5340_CLAA package, I have difficulty directly connecting to the Bluetooth on a Windows host.

The connection gets stuck during the MTU exchange process.

However, this issue does not occur when connecting to a mobile phone or a BLE Dongle.

Strangely, when I switch to the nRF5340_QKAA package, the problem disappears. Can you help me analyze why this is happening?

I am using the same version of the software, specifically version 2.7. Does the software need to be modified based on different package types?

Parents
  • 0
    The connection gets stuck during the MTU exchange process.

    Can you try to set CONFIG_BT_GATT_AUTO_UPDATE_MTU=n and CONFIG_BT_AUTO_DATA_LEN_UPDATE=n?

    Strangely, when I switch to the nRF5340_QKAA package, the problem disappears. Can you help me analyze why this is happening?

    Is the only difference the package, or is there also any differences to 32kHz clock source?

    Kenneth

Reply
  • 0
    The connection gets stuck during the MTU exchange process.

    Can you try to set CONFIG_BT_GATT_AUTO_UPDATE_MTU=n and CONFIG_BT_AUTO_DATA_LEN_UPDATE=n?

    Strangely, when I switch to the nRF5340_QKAA package, the problem disappears. Can you help me analyze why this is happening?

    Is the only difference the package, or is there also any differences to 32kHz clock source?

    Kenneth

Children
No Data
Related
Terms of service