What do I need to know to add mesh functionality into a normal BLE application ?
What do I need to know to add mesh functionality into a normal BLE application ?
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.
Requires:
How to test:
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:
void nrf_mesh_evt_handler(uint32_t sys_evt, void * p_context) {
nrf_mesh_on_sd_evt(sys_evt);
}
NRF_SDH_SOC_OBSERVER(m_nrf_mesh_observer, 0, nrf_mesh_evt_handler, NULL);
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)
Attachment:
UPDATE 12Jan2018
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.
Light switch server + ble app proximity
Hi Hung, I still get message that: "Cannot send. Device is busy.". I have changed inverval:
define MIN_CONN_INTERVAL MSEC_TO_UNITS(100, UNIT_1_25_MS)
define MAX_CONN_INTERVAL MSEC_TO_UNITS(500, UNIT_1_25_MS)
And removed errror related to ble_gatt which I have mentioned before. However the message is still present and I can not send data via mesh. It seems that provisioning is fine because the message "Successfully provisioned" is visible in server logs. Maybe I have changed wrong values in connection interval.
Hi Hung, I still get message that: "Cannot send. Device is busy.". I have changed inverval:
define MIN_CONN_INTERVAL MSEC_TO_UNITS(100, UNIT_1_25_MS)
define MAX_CONN_INTERVAL MSEC_TO_UNITS(500, UNIT_1_25_MS)
And removed errror related to ble_gatt which I have mentioned before. However the message is still present and I can not send data via mesh. It seems that provisioning is fine because the message "Successfully provisioned" is visible in server logs. Maybe I have changed wrong values in connection interval.