Concurrent BIS and PAwR when using PAST

RE: Concurrent BIS and PAwR when using PAST

runsiv — Thu, 19 Dec 2024 06:08:50 GMT

Just an update on the fix: It will be merged into the NCS in the next nrfxlib-update so I would presume in maybe a release or two of NCS(not counting the one from last night).

Regards

Runar

RE: Concurrent BIS and PAwR when using PAST

Rai — Fri, 13 Dec 2024 10:26:20 GMT

Thank you! This fix worked for me.
Will this issue be addressed in a future update?

RE: Concurrent BIS and PAwR when using PAST

runsiv — Thu, 12 Dec 2024 13:48:44 GMT

Hi and thanks for the clarification

Our softdevice team has looked into it made this workaround for you which should fix the issue for you while they investigate a bit.

diff --
git a/samples/bluetooth/periodic_adv_rsp/src/main.c b/samples/bluetooth/periodic_adv_rsp/src/main.c
index 37d04306246..f42d651facc 100644
--- a/samples/bluetooth/periodic_adv_rsp/src/main.c
+++ b/samples/bluetooth/periodic_adv_rsp/src/main.c
@@ -10,6 +10,8 @@
 #include <zephyr/bluetooth/gatt.h>
 #include <zephyr/bluetooth/hci.h>
 
+#include <sdc_hci_vs.h>
+
 #define NUM_RSP_SLOTS 5
 #define NUM_SUBEVENTS 5
 #define PACKET_SIZE   5
@@ -27,11 +29,11 @@ static const struct bt_le_per_adv_param per_adv_params = {
        .interval_min = 0xFF,
        .interval_max = 0xFF,
        .options = 0,
-       .num_subevents = NUM_SUBEVENTS,
-       .subevent_interval = 0x30,
-       .response_slot_delay = 0x5,
-       .response_slot_spacing = 0x50,
-       .num_response_slots = NUM_RSP_SLOTS,
+       .num_subevents = 0,
+       .subevent_interval = 0,
+       .response_slot_delay = 0,
+       .response_slot_spacing = 0,
+       .num_response_slots = 0,
 };
 
 static struct bt_le_per_adv_subevent_data_params subevent_data_params[NUM_SUBEVENTS];
@@ -264,6 +266,14 @@ int main(void)
                return 0;
        }
 
+
+       sdc_hci_cmd_vs_allow_parallel_connection_establishments_t parallel_params = {.enable = 1};
+       err = sdc_hci_cmd_vs_allow_parallel_connection_establishments(&parallel_params);
+       if (err) {
+               printk("Failed to allow parallel connection establishment (err %d)\n", err);
+               return 0;
+       }
+
        /* Create a non-connectable advertising set */
        err = bt_le_ext_adv_create(BT_LE_EXT_ADV_NCONN, &adv_cb, &pawr_adv);
        if (err) {

Regards

Runar

RE: Concurrent BIS and PAwR when using PAST

Rai — Thu, 12 Dec 2024 12:17:45 GMT

Hi Runar,
Thank you for addressing this issue.

No, the BIG is created from a standard PADVB (I have set the num_subevents=0), and there are no issues during its creation. However, after creating the BIG (when setting num_subevents=0 and CONFIG_BT_PER_ADV_RSP=y), I am unable to establish a connection to another device, as mentioned in the example above.

For context, I currently have one PAwR and one BIS running without any problems. My goal is to connect to a peer device to send synchronization information via PAST.

Regards,
Rainer

RE: Concurrent BIS and PAwR when using PAST

runsiv — Thu, 12 Dec 2024 10:17:10 GMT

Just to verify, is the BIG from PAwR? SDC does not support creating a BIG from a PAwR train, which explains why it would fail. Setting num_subevents=0 will create a "normal" PADVB from which you can can create a BIG.

Regards

Runar

RE: Concurrent BIS and PAwR when using PAST

runsiv — Wed, 11 Dec 2024 12:17:48 GMT

I'm looking into the issue and I hope to get back to you tomorrow.

Regards

Runar