• State Verified Answer
  • Replies 9 replies
  • Subscribers 64 subscribers
  • Views 384 views
  • Users 0 members are here
Attachments (5) Download All
Nordic Case Info
  • Case ID: 323831
Options

Synchronizing timout when using Periodic Advertising with Responses (PAwR)

ATla5

Hello,

I am currently evaluating the new feature called Periodic Advertising with Responses (PAwR) using Nordic's Softdevice controller.

Below you find project related information.

  • nRF52840 DK
  • nRF Connect SDK v2.6.0-rc1
  • nRF Connect Toolchain v2.6.0-rc1
  • Nordic's Softdevice Controller (since Zephyr's currently does not support the PAwR feature)
  • Zephyr samples: periodic_sync_rsp and periodic_adv_rsp 

I use this sample togheter with a second nrf52840 DK board that features the periodic_adv_rsp sample from Zephyr.

When launching Segger's RTT Viever for both samples I receive the following logging messages

     

periodic_sync_rsp                                                                        periodic_adv_rsp                                                                          

So far I have identified the following:

  • periodic_adv_rsp
    • HCI opcode 0x2082: HCI_LE_Set_Periodic_Advertising_Subevent_Data with status 0x07 (memory capacity exceeded)
  • periodic_sync_rsp
    • HCI LE controller command, opcode 0x2036: HCI_LE_Set_Extended_Advertising_Parameters with status 0x0C (Command disallowed)

The information was taken from the Bluetooth Core Specification 5.4 (Vol. 4 - Part E, 7.8 LE Controller Commands, Vol 1, Part F, 2 Error code description). 

The HCI related warning is located in zephyr/subsys/bluetooth/host/hci_core.c inside the function bt_hci_cmd_send_sync at line 335 (at least that's what I have identified).

Although I have identified the cause I do not know how to proceed. Do you have more information or can share insights in how to tackle this problem?

Am I missing any Kconfig option?

Best regards

ATla5

Note:

The specification states four cases related to 0x2036: HCI_LE_Set_Extended_Advertising_Parameters with status 0x0C

  • If Constant Tone Extensions are enabled for the advertising set and Secondary_Advertising_PHY specifies a PHY that does not allow Constant Tone Extensions, the Controller shall return the error code Command Disallowed (0x0C).
  • If the Host specifies that it requires a specific coding (i.e., value 0x03 or 0x04) in the Primary_Advertising_PHY_Options or Secondary_Advertising_PHY_Options and the Controller supports the LE Feature (Advertising Coding Selection) but is currently unable to provide all the required settings, then the Controller shall return the error code Command Disallowed (0x0C).
  • If the Host issues this command when advertising is enabled for the specified advertising set, the Controller shall return the error code Command Disallowed (0x0C).
  • If periodic advertising is enabled for the advertising set and the Secondary_Advertising_PHY parameter does not specify the PHY currently being used for the periodic advertising, the Controller shall return the error code Command Disallowed (0x0C).

Are one of these cases relevant for my problem?

Related