Failed to use periodic advertisement function on nRF5340dk

RE: Failed to use periodic advertisement function on nRF5340dk

UUmaker — Fri, 04 Jul 2025 13:56:39 GMT

SEGGER J-Link V8.18 - Real time terminal output
SEGGER J-Link (unknown) V1.0, SN=1050024275
Process: JLinkExe
*** Booting nRF Connect SDK v3.0.2-89ba1294ac9b ***
*** Using Zephyr OS v4.0.99-f791c49f492c ***
Starting Periodic Advertising Demo
[00:00:00.405,456] <wrn> bt_hci_core: opcode 0x203a status 0x01 
[00:00:00.405,487] <wrn> bt_hci_core: Controller does not support 'LE_READ_MAX_ADV_DATA_LEN'. Assuming maximum length is 31 bytes.
[00:00:00.407,592] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.407,623] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.407,653] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 137.20634 Build 2617349514
[00:00:00.409,942] <inf> bt_hci_core: Identity: F9:B9:AD:9A:8E:CD (random)
[00:00:00.409,942] <inf> bt_hci_core: HCI: version 6.0 (0x0e) revision 0x20f3, manufacturer 0x0059
[00:00:00.409,973] <inf> bt_hci_core: LMP: version 6.0 (0x0e) subver 0x20f3
[00:00:00.410,705] <wrn> bt_hci_core: opcode 0x2036 status 0x01 
Failed to create advertising set (err -5)

Hello Edvin

I am also using the new sysbuild, so what I should add to pic_radio.conf ? BTW, My NCS SDK version is 3.0.2.

Looking forward to your reply.

Thanks

RE: Failed to use periodic advertisement function on nRF5340dk

Shuhao Dong — Wed, 27 Nov 2024 10:35:49 GMT

Thank you Edvin, this solved my problem!

RE: Failed to use periodic advertisement function on nRF5340dk

Edvin — Tue, 26 Nov 2024 11:32:28 GMT

Hello,

The reason this doesn't work out of the box for the nRF5340 is that it is missing some configurations for the network application when running on a 2 core chip (as you mentioned).

Seeing as you are using NCS v2.7.0, you are either building using sysbuild or parent/child image builds. The way you add network core configurations depends on which one you are using. If you are not sure, please check your build log. If you are using child and parent image functionality, then you should see this a couple of times in your build log:

            ---------------------------------------------------------------------
            --- WARNING: Child and parent image functionality is deprecated   ---
            --- and should be replaced with sysbuild. Child and parent image  ---
            --- support remains only to allow existing customer applications  ---
            --- to build and allow porting to sysbuild, it is no longer       ---
            --- receiving updates or new features and it will not be possible ---
            --- to build using child/parent image at all in nRF Connect SDK   ---
            --- version 2.9 onwards.                                          ---
            ---------------------------------------------------------------------

If you are using parent child image functionality (not recommended for future development), add a folder called child_image, and inside there, add a file called hci_ipc.conf. The file should contain:

CONFIG_BT_BUF_ACL_RX_SIZE=251
CONFIG_BT_BUF_ACL_TX_SIZE=251
CONFIG_BT_EXT_ADV=y
CONFIG_BT_PER_ADV=y
CONFIG_BT_PER_ADV_SYNC_TRANSFER_SENDER=y
CONFIG_BT_PER_ADV_RSP=y

And this is your folder structure:

If you are using the new sysbuild, then you should add call this file ipc_radio.conf, and place it in a folder called "sysbuild" instead of "child_image". In addition, you need a couple of files to tell the sysbuild building system that you have an additional image. I copied them from the ncs\nrf\samples\bluetooth\peripheral_uart sample:

devzone.nordicsemi.com/.../additional-files.zip

(Kconfig.sysbuild and sysbuild.conf)

To build using sysbuild, there is a checkbox in the bottom of VS code when you configure your build configuration. If you are using command line to build, add the argument "--sysbuild".

Best regards,

Edvin