We currently working on a tutorial on how to merge a mesh application into our nRF5 SDK BLE example. We will update this thread when we finish. For now we provide a quick example so that you can follow.
Mesh stack operates on the timeslot feature provided by the same softdevice used on the nRF5 SDK. So it requires little modification in the Mesh stack to be integrated into a normal BLE example. In fact only modification in the application code needed.
Attached here is an example that we merge the light control server example into ble_app_uart.
For SDK v15.1 and Mesh SDK v2.0.1 please scroll down to the answer on 15th June.
How to test:
Copy Mesh SDK into a "mesh" folder inside "components" folder in SDK v14.1
Unzip the ble_app_uart - MESH into \examples\ble_peripheral in SDK v14.1
Edit PERSISTENT_STORAGE define in nrf_mesh_config_code.h to 0
Build and flash the example. It should work as both ble_app_uart and light control server
Limitation:
Permanent storage of provisioning and configuration is not stored on flash. After reboot, the device would require provisioning again. We are working to fix this. The reason is the flash management on 2 SDKs are not the same and can conflict.
Only S132 v5.0, PCA10040, and SES is supported in the example for now.
Connection interval of BLE application have to be changed >100ms to give enough time for mesh
How to integrate into your own application:
Include all the source file from Mesh example
Include all header folders from Mesh example in Project Option -> Common -> Preprocessor -> Include Directories
Include Preprocessor Definitions in mesh example ( same setting tab as above).
Customize the simple_hal.c to not use GPIOTE_IRQHandler() as it conflicts with the gpiote driver in the SDK
Set PERSISTENT_STORAGE to 0
Edit main.c to add mesh init functions and define.
Add nrf_mesh_evt_handler to SOC observer list with NRF_SDH_SOC_OBSERVER for example:
Add nrf_mesh_on_ble_evt((ble_evt_t *)p_ble_evt); to BLE observer list with NRF_SDH_BLE_OBSERVER; or just simply add it into ble_evt_handler(). (Optional)
Example for SDK v14.2 and Mesh v1.0, nRF52840 and nRF52832:
Light switch client + ble app uart . Send BLE command on NUS service with '0' '1' '2' '3' as button press. Copy mesh SDK into mesh_sdk folder inside nRF5 SDK folder.
I think there is an issue with the scanner and mesh stack. Tested here showed that after the first BLE scanning period the mesh stack didn't work after that. I will take a look.
@Toaster: It's hard to give you recommendation without knowing the application. Mesh and Thread are a little bit different. One is routed mesh and one is flood mesh. They do have some overlapping but has their own pros and cons depends on the application.
I think there is an issue with the scanner and mesh stack. Tested here showed that after the first BLE scanning period the mesh stack didn't work after that. I will take a look.
@Toaster: It's hard to give you recommendation without knowing the application. Mesh and Thread are a little bit different. One is routed mesh and one is flood mesh. They do have some overlapping but has their own pros and cons depends on the application.
