Same Node as BLE Mesh and BLE Server (Dual Role)

RE: Same Node as BLE Mesh and BLE Server (Dual Role)

AP — Tue, 17 Jun 2025 14:18:41 GMT

Hello Hung Bui,

It is working, Thanks!

RE: Same Node as BLE Mesh and BLE Server (Dual Role)

Hung Bui — Tue, 17 Jun 2025 11:47:45 GMT

Hi Antendra,
I don't really understand what you meant by doesn't support nrf5340dk.
I can build it for nRF5340dk without problem. Simply select the board and you can build it.

Note that there are two prj.conf. One in the main folder and one in sysbuild\ipc_radio

RE: Same Node as BLE Mesh and BLE Server (Dual Role)

AP — Tue, 17 Jun 2025 11:27:06 GMT

Hello Hung Bui,

Thanks for the update!

Attached software by you also doesn't support nrf5340dk, do I need to transfer files in new nrf5340 project as previous and then do the changes suggested by you?

do I need to place prj file from attached project to prj.conf inside sysbuild\ipc_radio. all or partial?

RE: Same Node as BLE Mesh and BLE Server (Dual Role)

Hung Bui — Tue, 17 Jun 2025 10:50:14 GMT

Hi Atendra,
You would need to have the configuration set for the radio core since the nRF53 has the separate radio core (running ipc_radio firmware).
So you need to add the configuration into prj.conf inside sysbuild\ipc_radio.
Please refer to other mesh samples. Note that you need to increase CONFIG_BT_EXT_ADV_MAX_ADV_SET=6 instead of 5 because one extra advertising set is used for the lbs.

Please find the attached project.

devzone.nordicsemi.com/.../ble_5F00_peripheral_5F00_lbs_5F00_coex.zip

RE: Same Node as BLE Mesh and BLE Server (Dual Role)

AP — Mon, 16 Jun 2025 14:41:25 GMT

devzone.nordicsemi.com/.../light_5F00_switch_5F00_coex.zip

Hello Hung Bui,

Thanks for your response, yes exactly what I need.
However this project is not supported for nrf5340dk.
I tried to use it by creating new project(or take light Switch example) for nrf5340dk and then replace files with your suggested project to build it.
This got build without any error but seems advertisement is not working.
I have Attached updated coexistence example for nrf5340dk for you reference.

below is output for you refrence.

Booting Mesh and Peripheral Coex v2.9.1 - unknown commit ***<\r><\n>
*** Using nRF Connect SDK v2.9.1-60d0d6c8d42d ***<\r><\n>
*** Using Zephyr OS v3.7.99-ca954a6216c9 ***<\r><\n>
Initializing...<\r><\n>
[00:00:00.430,633] <27>[0m<inf> fs_nvs: 8 Sectors of 4096 bytes<27>[0m<\r><\n>
[00:00:00.430,633] <27>[0m<inf> fs_nvs: alloc wra: 0, fe8<27>[0m<\r><\n>
[00:00:00.430,664] <27>[0m<inf> fs_nvs: data wra: 0, 0<27>[0m<\r><\n>
[00:00:00.454,254] <27>[1;33m<wrn> bt_hci_core: opcode 0x203a status 0x01 <27>[0m<\r><\n>
[00:00:00.454,254] <27>[1;33m<wrn> bt_hci_core: Controller does not support 'LE_READ_MAX_ADV_DATA_LEN'. Assuming maximum length is 31 bytes.<27>[0m<\r><\n>
[00:00:00.456,359] <27>[0m<inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)<27>[0m<\r><\n>
[00:00:00.456,390] <27>[0m<inf> bt_hci_core: HW Variant: nRF53x (0x0003)<27>[0m<\r><\n>
[00:00:00.456,420] <27>[0m<inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 121.4259 Build 3078678206<27>[0m<\r><\n>
[00:00:00.457,061] <27>[0m<inf> bt_hci_core: No ID address. App must call settings_load()<27>[0m<\r><\n>
Bluetooth initialized<\r><\n>
[00:00:00.484,588] <27>[0m<inf> bt_hci_core: Identity: EF:4E:DB:64:EE:FE (random)<27>[0m<\r><\n>
[00:00:00.484,619] <27>[0m<inf> bt_hci_core: HCI: version 6.0 (0x0e) revision 0x209a, manufacturer 0x0059<27>[0m<\r><\n>
[00:00:00.484,649] <27>[0m<inf> bt_hci_core: LMP: version 6.0 (0x0e) subver 0x209a<27>[0m<\r><\n>
[00:00:00.487,426] <27>[0m<inf> bt_mesh_provisionee: Device UUID: c416c145-10af-4be8-bbe9-3ebaef50e417<27>[0m<\r><\n>
[00:00:00.489,532] <27>[1;33m<wrn> bt_hci_core: opcode 0x2036 status 0x01 <27>[0m<\r><\n>
[00:00:00.489,562] <27>[1;31m<err> bt_mesh_pb_adv: Failed enabling advertiser<27>[0m<\r><\n>
[00:00:00.491,668] <27>[1;33m<wrn> bt_hci_core: opcode 0x2036 status 0x01 <27>[0m<\r><\n>
[00:00:00.491,699] <27>[1;31m<err> bt_mesh_pb_gatt: Failed enabling advertiser<27>[0m<\r><\n>
Mesh initialized<\r><\n>
Created a new identity for LBS: 1<\r><\n>
[00:00:00.493,896] <27>[1;33m<wrn> bt_hci_core: opcode 0x2036 status 0x01 <27>[0m<\r><\n>
Creating LBS service adv instance failed (err -5)

RE: Same Node as BLE Mesh and BLE Server (Dual Role)

Hung Bui — Mon, 16 Jun 2025 09:28:01 GMT

Hi Atendra,
I believe this sample does exactly what you need: https://docs.nordicsemi.com/bundle/ncs-2.4.1/page/nrf/samples/bluetooth/mesh/ble_peripheral_lbs_coex/README.html

It show you how you can have both Mesh and normal BLE server.