Issue Integrating Mesh with Broadcast Source and Central & Peripheral HR on nRF5340

[danix2k]

Hello,

I am working on an nRF5340-based project where I successfully integrated the broadcast_source and central_and_peripheral_hr examples from SDK 2.6.0. Both functionalities are working correctly. However, when I try to add the mesh functionality, I encounter the following error:

[00:00:00.710,754] bt_hci_core: opcode 0x2036 status 0x07
[00:00:00.710,784] bt_mesh_pb_adv: Failed enabling advertiser
[00:00:00.710,845] bt_mesh_adv_ext: Mesh advertiser not enabled

I am using SDK 2.6.0 because SDK 2.9.0 did not work correctly with the broadcast_source example.

Additionally, I noticed that in the mesh_light_switch example, ipc_radio is used in the core network, whereas in the other examples, hci_ipc is used instead. Could this be a potential cause of the issue? If so, what would be the recommended approach to align these components correctly?

Do I need to make any specific configurations or modifications to enable the mesh advertiser properly in this context?

Thanks in advance for your support!

UPDATE

I have identified that the opcode 0x2036 - 0x07 error was caused by a lack of resources for ext advertise. I noticed that it was using hci_ipc (still on SDK version 2.6.0), so I modified the sysbuild.cmake to use the configuration file nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf (instead of nrf5340_cpunet_iso-bt_ll_sw_split.conf), adding:

CONFIG_BT_EXT_ADV_MAX_ADV_SET=10

With this configuration, the previous error disappeared. However, I am now encountering a new issue:

[00:00:00.681,488] <inf> bt_mesh_provisionee: Device UUID: 11bcda3f-1161-448b-ae43-25c0ee9e4b74
Mesh initialized
Failed to set periodic advertising parameters (err -134)

Do you have any insights on what might be causing this new error?

Thanks

[Amanda Hsieh]

Hi,

If your Bluetooth mesh device running as an ADV-bearer with BIS, Please be aware that Bluetooth mesh is not based on a synchronization mechanism, which means there could be packets from other devices at any time. That's why the RX window is turned on all the time from a normal mesh node. Therefore, the collision between BIS ISO and mesh packets would be expected and cause the audio quality to be poor, or cannot receive every packet from the mesh network. 

I am using SDK 2.6.0 because SDK 2.9.0 did not work correctly with the broadcast_source example.

Do you mean the applications/nrf5340_audio/broadcast_source? Usually, I would suggest using the latest version to get better support. You could raise a new support case for v2.9.0 Audio issues. 

Additionally, I noticed that in the mesh_light_switch example, ipc_radio is used in the core network, whereas in the other examples, hci_ipc is used instead. Could this be a potential cause of the issue? If so, what would be the recommended approach to align these components correctly?

Since nRF Connect SDK v2.7.0, the nRF Bluetooth and mesh samples previously used the HCI IPC (also known as hci_ipc) radio core firmware, which has been updated to use the IPC radio firmware.

This change is part of an effort to standardize the radio core firmware across different types of samples. The IPC radio firmware (ipc_radio) is a more versatile solution that can support multiple protocols, including Bluetooth and IEEE 802.15.4.

Do you have any insights on what might be causing this new error?

Try to increase CONFIG_BT_CTLR_ADV_DATA_LEN_MAX. You could also refer to nrf5340_cpunet_iso-bt_ll_sw_split.conf. It might help.  

Regards,
Amanda H.

[danix2k]

Hello,

First of all, thank you for your previous response!

I have a question regarding the core network configuration for hci_ipc. Why are there multiple configuration files available? Specifically, what is the difference between nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf and nrf5340_cpunet_iso-bt_ll_sw_split.conf? When should each one be used, and how do we specify which one to use?

Additionally, I have fixed the previous errors by adding the following missing configurations in mesh.conf:

CONFIG_BT_EXT_ADV_MAX_ADV_SET=10 
CONFIG_BT_PER_ADV=y 
CONFIG_BT_BUF_ACL_RX_SIZE=251 
CONFIG_BT_BUF_ACL_TX_SIZE=251 
CONFIG_BT_PER_ADV_RSP=y 
CONFIG_BT_CTLR_ADV_EXT=y 
CONFIG_BT_CTLR_ADV_DATA_CHAIN=y 
CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=191 
CONFIG_BT_CTLR_SCAN_DATA_LEN_MAX=191 
CONFIG_BT_CTLR_ADV_ISO=y

These additional configurations have resolved all the previous issues. However, I am now encountering a new error:

[00:00:00.721,801] <wrn> bt_hci_core: opcode 0x2068 status 0x07 
Unable to start broadcast source: -5

Do you have any insights into what might be causing this new error? This is related to 

SDC_HCI_OPCODE_CMD_LE_CREATE_BIG with memory issue i think.

Thanks for your support