nRF5340-DK and Bluetooth mesh chat example.

RE: nRF5340-DK and Bluetooth mesh chat example.

bert svensson — Tue, 13 Jul 2021 10:46:13 GMT

Ah, set CONFIG_BT_LL_SW_SPLIT in the network core, now I get it.

I managed to solve the problem by doing as you said and then flash the device with the nRF connect programmer, but when I flashed the device from the terminal using "west flash", then the chat project replaced the network core with it's own version, without the CONFIG_BT_LL_SW_SPLIT parameter set, even when it was correctly set in the chat example project.

RE: nRF5340-DK and Bluetooth mesh chat example.

Hung Bui — Tue, 13 Jul 2021 09:43:16 GMT

Hi Bert,
I couldn't reproduce the issue here.
Could you please try to compile the hci_rpmsg separately (make sure you changed CONFIG_BT_LL_SW_SPLIT = y for this project) and flash the netcore, and app core again ?

RE: nRF5340-DK and Bluetooth mesh chat example.

bert svensson — Tue, 13 Jul 2021 08:35:10 GMT

config_bt_ll_sw_split is already set in the example, see: (line 23)

https://github.com/nrfconnect/sdk-nrf/blob/master/samples/bluetooth/mesh/chat/prj.conf

The network core is flashed, other examples work, both BLE and mesh, just not the chat example.

Also, bt_enable() works just fine, it is just the mesh part ( bt_mesh_init(...) ) that wont initialize in that particular example.

RE: nRF5340-DK and Bluetooth mesh chat example.

Hung Bui — Mon, 12 Jul 2021 16:47:04 GMT

Hi Bert,

Have you flashed the NRF53 netcore with the Zephyr BLE controller ?
Note that unlike other BLE application, the mesh application requires you to use Zephyr BLE controller instead of Nordic's Softdevice controller. Please have a look here.
You would need to use CONFIG_BT_LL_SW_SPLIT = y in prj.conf in the hci_rpmsg project and reflash the netcore (and then app core with the meshchat code).