periodic_adv_rsp sample fails on nRF5340-dk

[jose321]

Hi,

[Alex B. speaking]

I have flashed an unmodified periodic_adv_rsp sample to the nRF5340-dk and it builds and flashes successfully. However I get the following terminal output:

*** Booting nRF Connect SDK v2.5.2 ***
Starting Periodic Advertising Demo
[00:00:00.518,127] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.518,188] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.518,188] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 141.732 Build 3324398027
[00:00:00.519,775] <inf> bt_hci_core: Identity: EC:96:13:A9:B2:B9 (random)
[00:00:00.519,805] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x2168, manufacturer 0x0059
[00:00:00.519,836] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x2168
[00:00:00.521,728] <wrn> bt_hci_core: opcode 0x2036 status 0x01
Failed to create advertising set (err -5)

Do you know what the cause of this is?

Kind regards,
Alex

[Susheel Nuguru]

Thanks for the report, Acknowledge that I see the same.

1) Will make an internal bug report to track and fix this.

2) Will try to debug it and comeup with a workaround if possible. be back to you when I have some more info on this. 

[Susheel Nuguru]

One of my colleague has seen this before. In our solutions the problem is that hci_rpmsg sample we have does not enable periodic advertising by default and with this Zephyr sample using hci_rpmsg on netcore (child_image) needs to enable periodic advertising in the config file.

Please unzip this child image folder in your project folder like below and prestine build your project. 

4011.child_image.zip

You can see that the child image adds a configuration file with the sample name and enables EXT and periodic advertising.

And the periodic advertising is started as normal

[Susheel Nuguru]

We are working on this and the team is trying to fix this for next release. 

For your reference the internal ticket number is NCSIDB--1220. 

[Susheel Nuguru]

Hi, The solution I gave you might not be complete.

CONFIG_BT_PER_ADV_SYNC_TRANSFER_SENDER=y
CONFIG_BT_PER_ADV_RSP=y

are also needed. So the recommended way is copying the zephyr/samples/bluetooth/periodic_adv_rsp/prj.conf contents to zephyr/samples/bluetooth/periodic_adv_rsp/child_image/hci_rpmsg.conf.

We are working on a hardware model upgrade in upstream Zephyr which will help to run this sample on multi core chips out of the box. For now, multicore chips needs a child image config file that mimics the features required.