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?
