• State Verified Answer
  • Replies 12 replies
  • Subscribers 86 subscribers
  • Views 520 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 358646
Options

Missing BLE disconnect event (Supervision Timeout) - nRF9151 + nRF52840

tdfilip

Hello,

I'm using nRF9151 as a HCI host and nRF52840 as HCI controller (nRF52840 config is based on HCI lpuart example). Recently I updated NCS to 3.2.2 and I started observing the lack of disconnect event on a supervision timeout. The issue didn't occur when both (nRF9151 and nRF52840) apps were on NCS 3.1.0 but also it didn't occur when nRF9151 app was already using NCS 3.2.2 but the nRF52840 was still on NCS 3.1.0.

I found out that it was a known issue, which was fixed on NCS 2.8.0.
Are you aware of that issue on NCS 3.2.2? Maybe it is already fixed on newer NCS versions?

Regards
Filip

  • 0

    Hi,

    I am working on the issue and will confirm it with the team. You can expect an update by early next week. 

    Best Regards,

    Samruddhi

  • 0

    Hi Filip,

    Can you please provide some more details about what is happening on the Bluetooth when this occurs? Are you observing that the link is idle when the link drops and disconnect event is missing? And is there a lot of data transfer happening? Is this issue happening on many devices or is the issue happening on one device? Is it possible for you to provide sniffer log, log or hci-log/uart log between nRF52840 and the nRF91?

    Best Regards,

    Samruddhi

  • 0 in reply to Samruddhi Jadhav

    I'm forcing the issue to happen by powering off the peripheral device during the connection. It doesn't matter if there is a lot of data to be transferred - no matter what is happening during the connection, if I power off the peripheral device, the supervision timeout doesn't trigger a disconnect event. I've checked it only on one device for now.

    When the disconnect event is missing, the central device acts like it's still in connection. Here are the only logs that appear after the issue:

    00> [1970-01-01 00:00:51.136000]<err> lpuart: Empty receiver state:4
00> [1970-01-01 00:00:51.137000]<err> bt_driver: Unknown H:4 type 0x00
00> [1970-01-01 00:00:51.137000]<err> bt_driver: Unknown H:4 type 0x00
00> [1970-01-01 00:00:51.137000]<err> bt_driver: Unknown H:4 type 0x00
00> [1970-01-01 00:00:51.137000]<err> bt_driver: Unknown H:4 type 0x08
00> [1970-01-01 00:00:51.137000]<err> bt_hci_core: No connection for handle 1024

    Regards,
    Filip

  • 0 in reply to tdfilip

    Hi Filip,

    Thanks for providing the log. I am working on this issue with the team. Please note that there might be some delay in response time due to Easter. You can expect an update by next week. Thanks for your patience.

    Best Regards,

    Samruddhi

  • 0

    Hi Filip,

    Can you please provide some more details about your method? It would be great if you could send the .config for both the nrf91 and nrf52840 as well as the dts files. Could you also provide the connection parameters, connection interval, supervision timeout and peripheral latency so that we can look further into the issue?

    Best Regards,

    Samruddhi

Related
Terms of service