nrf5340 audio dk error with periodic_sync_conn and periodic_adv_conn

[Ben Schoeler]

Hi, I am trying to use the periodic advertising connection examples and get Hci errors:

opcode 0x2036 status 0x01
Failed to create advertising set (err -5)

I am on NCS 2.6.1

Thank you

[Ben Schoeler]

Hi, 

It seems after much trial and error of adding various CONFIG_* flags to hci_ipc.conf and proj.conf, I am able to get both examples to compile and get past the initial error in my post.

However, they do not seem to sync up, and there are more errors  Is this expected to work on the nrf5340?  

periodic_sync_conn:

Failed to send response (err -22)
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
Starting Periodic Advertising with Responses Synchronization Demo
[00:00:00.286,071] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.286,132] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.286,163] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
[00:00:00.288,330] <inf> bt_hci_core: Identity: D3:6A:6E:FE:F0:6C (random)
[00:00:00.288,360] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
[00:00:00.288,360] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x218f
Found periodic advertising.
Creating Periodic Advertising SyncWaiting for periodic sync
Synced to 48:DE:63:E8:82:AA (random) with 0 subevents
[00:00:00.631,011] <wrn> bt_hci_core: opcode 0x2084 status 0x01
Failed to set subevents to sync to (err -5)
Periodic sync established.
[00:00:00.633,361] <wrn> bt_hci_core: opcode 0x2042 status 0x0c
Failed to stop scanning (err -5)
Stopped scanning
Responding with own addr: 67:80:B8:26:F6:64 (random)
Failed to send response (err -22)
Responding with own addr: 4F:CA:D9:9B:42:95 (random)
Failed to send response (err -22)
Responding with own addr: 62:97:05:C6:CD:66 (random)
Failed to send response (err -22)
Responding with own addr: 63:4D:0B:32:6D:FE (random)
Failed to send response (err -22)
Responding with own addr: 4B:E3:AD:90:08:58 (random)
Failed to send response (err -22)
Responding with own addr: 47:2F:08:FC:06:22 (random)
Failed to send response (err -22)
Responding with own addr: 67:05:7D:59:6F:F3 (random)
Failed to send response (err -22)
Responding with own addr: 50:D2:D7:A4:23:5F (random)
Failed to send response (err -22)
Responding with own addr: 49:76:48:50:A1:4E (random)

periodic_adv_conn:

*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
Starting Periodic Advertising Demo
[00:00:00.285,400] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.285,430] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.285,461] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
[00:00:00.287,658] <inf> bt_hci_core: Identity: E9:81:61:BD:F4:96 (random)
[00:00:00.287,658] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
[00:00:00.287,689] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x218f
Start Periodic Advertising
Starting Periodic Advertising Demo2

Strangely, the sync'd address does not much the address given in the logs from the periodic_adv_conn device, either.

[Elfving]

Hello again, and I am deeply sorry about the delay on this case.

Due to the summer period, and people taking time off, there is a lot to do here on DevZone. Please inform your RSM if you need more urgent help than what is provided here. He will have an easier time escalating this.

Now regarding the problem, it seems to have been reported before. Like my colleague mentions in that case, NCSIDB--1220 is being worked on.

One solution mentioned there is to add some configurations to the child image. Are those the ones you tried, and refered to in your newest response?

Regards,

Elfving