BT connection timeouts with PAWR enabled

RE: BT connection timeouts with PAWR enabled

Hieu — Wed, 31 Jul 2024 14:01:59 GMT

Hi Leon,

The fix for this is merged here: https://github.com/zephyrproject-rtos/zephyr/pull/75824.

From that, we can be relatively sure that it will be in the next SDK release. However, on DevZone, we are not at liberty to talk about timeline. You will need to talk with a local Nordic sales representative for that.

Can the workaround solution that is discussed here work for you? If so, you can try to cherry pick the fix above.

RE: BT connection timeouts with PAWR enabled

Leon Weigel — Wed, 31 Jul 2024 08:58:32 GMT

Any chance that this problem will be resolved in the SDK soon?

RE: BT connection timeouts with PAWR enabled

saty9pd — Mon, 15 Jul 2024 08:44:08 GMT

That seems to work i now get a callback to my connection handler on timeout. Once the device it was trying to connect to became available it succeeded the next time bt_conn_le_create was called

RE: BT connection timeouts with PAWR enabled

Hieu — Fri, 12 Jul 2024 12:59:50 GMT

Could you please try this workaround?

Adding this line in hci_core.c after LOG_ERR("Invalid connection complete event");

enh_conn_complete((struct bt_hci_evt_le_enh_conn_complete *)evt);

The function le_enh_conn_complete_v2 should then look like this:

static void le_enh_conn_complete_v2(struct net_buf *buf)
{
 struct bt_hci_evt_le_enh_conn_complete_v2 *evt =
  (struct bt_hci_evt_le_enh_conn_complete_v2 *)buf->data;

 if (evt->adv_handle == BT_HCI_ADV_HANDLE_INVALID &&
     evt->sync_handle == BT_HCI_SYNC_HANDLE_INVALID) {
  /* The connection was not created via PAwR, handle the event like v1 */
  enh_conn_complete((struct bt_hci_evt_le_enh_conn_complete *)evt);
 }
#if defined(CONFIG_BT_PER_ADV_RSP)
 else if (evt->adv_handle != BT_HCI_ADV_HANDLE_INVALID &&
   evt->sync_handle == BT_HCI_SYNC_HANDLE_INVALID) {
  /* The connection was created via PAwR advertiser, it can be handled like v1 */
  enh_conn_complete((struct bt_hci_evt_le_enh_conn_complete *)evt);
 }
#endif /* CONFIG_BT_PER_ADV_RSP */
#if defined(CONFIG_BT_PER_ADV_SYNC_RSP)
 else if (evt->adv_handle == BT_HCI_ADV_HANDLE_INVALID &&
   evt->sync_handle != BT_HCI_SYNC_HANDLE_INVALID) {
  /* Created via PAwR sync, no adv set terminated event, needs separate handling */
  struct bt_le_per_adv_sync *sync;

  sync = bt_hci_get_per_adv_sync(evt->sync_handle);
  if (!sync) {
   LOG_ERR("Unknown sync handle %d", evt->sync_handle);

   return;
  }

  bt_hci_le_enh_conn_complete_sync(evt, sync);
 }
#endif /* CONFIG_BT_PER_ADV_SYNC_RSP */
 else {
  LOG_ERR("Invalid connection complete event");
  enh_conn_complete((struct bt_hci_evt_le_enh_conn_complete *)evt);
 }
}

RE: BT connection timeouts with PAWR enabled

saty9pd — Fri, 12 Jul 2024 09:15:10 GMT

Sorry if I am using the wrong terminology.

The central device (the one running the code I posted) is the one subscribing to the PAWR advertiser and sending responses back to it

RE: BT connection timeouts with PAWR enabled

Hieu — Fri, 12 Jul 2024 08:21:20 GMT

Hi saty9pd,

I forgot to ask, for this and https://devzone.nordicsemi.com/f/nordic-q-a/112920/pawr-prevents-cancelling-a-pending-connection, what PAwR role is this central device in?

Hieu

RE: BT connection timeouts with PAWR enabled

Hieu — Thu, 11 Jul 2024 21:38:47 GMT

Hi saty9pd,

Thank you for the information. I will relay this to our internal team. We will investigate this and get back to you.

Unfortunately, we are facing abnormally high loading, and it might take one or two weeks before we can follow up. Our apologies for the inconvenience.

Hieu