Hi everyone, I’ve been diving into the world of Bluetooth Mesh with my nRF5340 DK and wanted to share some insights and tips I’ve gathered along the way. While the documentation is a great starting point, I noticed that the nRF5340 wasn’t officially supported in the Bluetooth Mesh DFU Target sample, which piqued my curiosity.
Initially, I encountered some errors related to enabling the advertiser, specifically the HCI command 0x2036 failing with status 0x01. After some research, I realized that the issue stemmed from the dual-core architecture of the nRF5340. The application core was configured for extended advertising, but the network core’s BLE controller wasn’t set up accordingly.
To resolve this, I created a network core configuration file to enable extended advertising support. Here’s a quick rundown of what worked for me:
- File Structure: I set up the following structure:
target/
├── sysbuild/
│ └── ipc_radio/
│ └── prj.conf
├── prj.conf
└── sysbuild.conf
-
Configuration File: In
sysbuild/ipc_radio/prj.conf, I added the necessary configurations, including enabling extended advertising support withCONFIG_BT_CTLR_ADV_EXT=y. This change ensures that the BLE controller supports the required HCI commands for Bluetooth Mesh. -
Build Process: I built the project using the commands:
west build -b nrf5340dk/nrf5340/cpuapp --pristine
west flash
After implementing these steps, the Bluetooth Mesh DFU Target sample worked seamlessly on my nRF5340 DK. It’s fascinating how tweaking the network core configuration can resolve such issues. I’m now curious to explore more advanced configurations and see how they can enhance the functionality of my setup.
If anyone else is experimenting with Bluetooth Mesh on the nRF5340 DK, I’d love to hear your experiences or any tips you might have. Happy tinkering! 