michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: Samples: update response_cb in periodical_adv_rps

Browse source 
Remove print "Failed to receive response...", if receive
BT_HCI_LE_ADV_EVT_TYPE_DATA_STATUS_RX_FAILED.

Problem: with cyw920829m2evk_02 device periodic_adv_rsp returns
multiple messages  “Failed to receive response….” in the terminal
log.

This happens because controller generates
HCI LE Periodic Advertising Response Report event for each
RspSlot. Because no RSP_DATA is observed in the OTA, which
is no scan device to transmit RSP_DATA, no RSP_DATA can be
received. Therefore, Data Status is 0xFF in all of these events,
which finally cause the messages  “Failed to receive response….”

Data_Status = 0xFF is expected because nothing is received
for that Rsp Slot.

Per spec, it’s not mandatory to generate these events,
So another vendors (e.g. Nordic)  might skip the HCI event
generation if Data_Status = 0xFF.

Signed-off-by: Nazar Palamar <nazar.palamar@infineon.com>
This commit is contained in:
Nazar Palamar 2024-07-10 15:51:35 +03:00 • committed by Alberto Escolar
commit b8690f7ea4
1 changed files with 0 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
samples/bluetooth/periodic_adv_rsp/src/main.c
View file

@ -92,9 +92,6 @@ static void response_cb(struct bt_le_ext_adv *adv, struct bt_le_per_adv_response
if (buf) { if (buf) {
printk("Response: subevent %d, slot %d\n", info->subevent, info->response_slot); printk("Response: subevent %d, slot %d\n", info->subevent, info->response_slot);
bt_data_parse(buf, print_ad_field, NULL); bt_data_parse(buf, print_ad_field, NULL);
} else {
printk("Failed to receive response: subevent %d, slot %d\n", info->subevent,
info->response_slot);
} }
} }