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

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

Amanda Hsieh — Fri, 07 Mar 2025 19:34:53 GMT

I suggest you seek help on Zephyr Discord https://discord.com/invite/Ck7jw53nU2 for their samples.

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

danix2k — Fri, 07 Mar 2025 15:07:36 GMT

Yes, I know about the documentation but the example it's exactly the same as bap_broadcast_source and there it's working (with the same functions and structs). Instead here it is not!

This is why I'm asking support

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

Amanda Hsieh — Fri, 07 Mar 2025 15:00:32 GMT

See the bt_bap_stream_ops API document.

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

danix2k — Fri, 07 Mar 2025 14:29:11 GMT

Hello Amanda,

I did some test this morning and I found the following points:

to start the broadcasting there is a semaphore that is "given" in stream_sent_cb()
It seems that stream_sent_cb() is called just 6 times and it stops
No issue in init phase or other point apparently

Do you know how stream_sent_cb() works? This function is assigned to this struct related to stream data.

static struct bt_bap_stream_ops stream_ops = {
	.started = stream_started_cb, .stopped = stream_stopped_cb, .sent = stream_sent_cb};

Thanks for your support.

Daniele

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

Amanda Hsieh — Thu, 06 Mar 2025 20:31:10 GMT

Please try to debug your project and find where it hangs.

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

danix2k — Thu, 06 Mar 2025 15:06:45 GMT

Hello Amanda,

Sorry for my late reply.

I tested your configuration and observed the same behavior you reported, but this is not the expected one. I mean, everything now seems to be configured correctly, but in the original bap_broadcast_source example, after the last log line, the application should start broadcasting data—which is not happening in this case.

I have attached the correct behavior from the bap_broadcast_source example for reference.

This "broadcasting" seems not starting in our project.

Do you have any other useful suggestion?

Thanks.

Regards,

Daniele

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

Amanda Hsieh — Mon, 03 Mar 2025 22:24:19 GMT

Hi,

From your sysbuild.cmake file, it seems the project would use the nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf for hci_ipc. You could try to add the following configs for hci_ipc:

CONFIG_BT_PER_ADV=y
CONFIG_BT_MAX_CONN=10
CONFIG_BT_CTLR_ADV_SET=10
CONFIG_BT_EXT_ADV_MAX_ADV_SET=10

# Zephyr Controller tested maximum advertising data that can be set in a single HCI command
CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=191

# Enable support for Broadcast ISO in Zephyr Bluetooth Controller
CONFIG_BT_CTLR_ADV_ISO=y

# Sufficient ISO PDU length for any BAP LC3 presets (155)
CONFIG_BT_CTLR_ADV_ISO_PDU_LEN_MAX=155

# Number of supported streams
CONFIG_BT_CTLR_ADV_ISO_SET=1
CONFIG_BT_CTLR_ADV_ISO_STREAM_MAX=2
CONFIG_BT_CTLR_ADV_ISO_STREAM_COUNT=2
CONFIG_BT_CTLR_ISOAL_SOURCES=2

# Support the highest SDU size required by any BAP LC3 presets (155) + 8 bytes of HCI ISO Data
# packet overhead (the Packet_Sequence_Number, ISO_SDU_Length, Packet_Status_Flag fields; and
# the optional Time_Stamp field, if supplied)
CONFIG_BT_CTLR_ISO_TX_BUFFER_SIZE=163

Then, it would get the output like this on nRF5340DK:

-Amanda H.

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

danix2k — Mon, 03 Mar 2025 10:58:47 GMT

Hi Amanda,

Thank you for your response. Based on your indications, I decided to use the latest version 2.9.0 of the bap_broadcast_source project from zephyr/samples/bluetooth to ensure compatibility and take advantage of the most recent updates. Initially, I encountered an error but I modified the configuration in the 2.9.0 project to resolve it (disabling USB)

From there, I started integrating the central_and_peripheral_hr example and adding Mesh functionalities. However, I am now facing an error in the same function call, but with a different error code opcode 0x2068 status 0x12:

*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
[00:00:00.305,267] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.305,297] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.305,297] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 3.7 Build 99
[00:00:00.307,128] <wrn> bt_ecc: ECC HCI commands not available
[00:00:00.307,250] <inf> bt_hci_core: Identity: F9:46:93:B3:2F:8E (random)
[00:00:00.307,281] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x0000, manufacturer 0x0059
[00:00:00.307,312] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0xffff
Bluetooth initialized
Load settings
Scan for HR service peripheral
Advertising started
[00:00:00.540,832] <inf> bt_mesh_provisionee: Device UUID: 11bcda3f-1161-448b-ae43-25c0ee9e4b74
Mesh initialized
Initializing lc3 encoder for stream 0
Creating broadcast source
Creating broadcast source with 1 subgroups with 2 streams
Initializing lc3 encoder for stream 1
Starting broadcast source
[00:00:00.564,483] <wrn> bt_hci_core: opcode 0x2068 status 0x12 str
Unable to start broadcast source: -22

I feel that we might be losing focus on the core issue of this ticket. Instead of discussing general configuration options, I believe we should concentrate on understanding the cause of this specific error I am now encountering.

Additionally, I can share the project here in the ticket, along with the modifications made to the hci_ipc project to support Mesh networking. Let me know how you’d like to proceed.

Thanks.
devzone.nordicsemi.com/.../ego_5F00_sim_5F00_broadcast_5F00_2.9.7z

devzone.nordicsemi.com/.../hci_5F00_ipc.7z

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

Amanda Hsieh — Fri, 28 Feb 2025 23:03:44 GMT

Hi,

opcode 0x2068 is BT_HCI_OP_LE_CREATE_BIG, and the status code can be found in the specification. See Vol. 1, Part F, Chapter 2.

[quote user=""]where I successfully integrated the broadcast_source and central_and_peripheral_hr examples from SDK 2.6.0[/quote]

Are you using the nrf/applications/nrf5340_audio/broadcast_source or zephyrsamples/bluetooth/broadcast_audio_source? If it's broadcast_audio_source, you can refer to overlay-bt_ll_sw_split.conf to adjust the configurations.

Do you get the same issue with nrf5340_cpunet_iso-bt_ll_sw_split.conf? If not, you refer to it to see what is missing.

[quote user="danix2k"] when do I need to use one of them? I mean, is it correct select nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf to use mesh functionalities or is not necessary? Can the SoftDevice controller be used for Mesh features just like the Zephyr one?[/quote]

In the NCS Bluetooth Mesh samples, the SoftDevice controller is used as the default for Mesh samples. You can use child_image/hci_ipc.conf to adjust the configs for /hci_ipc such as this example. Of course, you could use the Zephyr Bluetooth LE Controller if you want. but I usually suggest using the SoftDevice controller if you want to use the QDID for certification.

-Amanda H.

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

danix2k — Thu, 27 Feb 2025 08:29:18 GMT

Hello,

[quote userid="77782" url="~/f/nordic-q-a/119272/issue-integrating-mesh-with-broadcast-source-and-central-peripheral-hr-on-nrf5340/524927"] If you are using the nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf or nrf5340_cpunet_iso-bt_ll_sw_split.conf, both are enabled with the Zephyr Bluetooth LE Controller. Why would you think that related to SDC_HCI_OPCODE_CMD_LE_CREATE_BIG, which is the Softdevice controller API?[/quote]

The issue -5 (aka EIO) is after a core log message [00:00:00.721,801] <wrn> bt_hci_core: opcode 0x2068 status 0x07 that means SDC_HCI_OPCODE_CMD_LE_CREATE_BIG with memory allocation issue. I think that -5 is related to the previous memory error. Additionally that error code (SDC_HCI_OPCODE_CMD_LE_CREATE_BIG) is an standard error code provided by BT specification and it is not just related to Softdevice or Zephyr Controller; is my assumption correct?

As far as I understood this is the main issue here. I saw these type of logs when something on network core is not "working as expected" and this is why I have to change *.conf file in network core in the hci_ipc project.

[quote userid="77782" url="~/f/nordic-q-a/119272/issue-integrating-mesh-with-broadcast-source-and-central-peripheral-hr-on-nrf5340/524927"]The multiple configuration files available for the network core are designed to support different features and use cases, such as using the Zephyr Bluetooth LE Controller. (indicated by the "bt_ll_sw_split" part of the filename).[/quote]

About that: when do I need to use one of them? I mean, is it correct select nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf to use mesh functionalities or is not necessary? Can the SoftDevice controller be used for Mesh features just like the Zephyr one?

Thanks for your support.

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

Amanda Hsieh — Wed, 26 Feb 2025 20:02:25 GMT

[quote user="danix2k"]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?[/quote]

The multiple configuration files available for the network core are designed to support different features and use cases, such as using the Zephyr Bluetooth LE Controller. (indicated by the "bt_ll_sw_split" part of the filename).

[quote user="danix2k"]

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 (on network core I presume).

[/quote]

If you are using the nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf or nrf5340_cpunet_iso-bt_ll_sw_split.conf, both are enabled with the Zephyr Bluetooth LE Controller. Why would you think that related to SDC_HCI_OPCODE_CMD_LE_CREATE_BIG, which is the Softdevice controller API?

error -5 is EIO, meaning I/O error. Please check and ensure that you're calling the broadcast start function correctly.

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

danix2k — Wed, 26 Feb 2025 10:18:44 GMT

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 (on network core I presume).

Thanks for your support

UPDATE

From previous conf file I also added and changed the following params but the issue is still there.

CONFIG_BT_CTLR_ADVANCED_FEATURES=y
CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=750
CONFIG_BT_CTLR_SCAN_DATA_LEN_MAX=750

It's still something related to network core I think (ipc_hci fw)

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

Amanda Hsieh — Tue, 25 Feb 2025 17:52:10 GMT

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.

[quote user=""]I am using SDK 2.6.0 because SDK 2.9.0 did not work correctly with the broadcast_source example.[/quote]

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.

[quote user=""]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?[/quote]

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.

[quote user=""]Do you have any insights on what might be causing this new error?[/quote]

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.