This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Merging sdk-14.2 with mesh_sdk

Hello,

I saw this, but I was struggling with the merge for quite a long time now. Is there any ready example for e.g. provisionee or provisioner from light_switch merged with ble_peripheral/ble_app_uart or ble_peripheral/ble_app_blinky?

Kind regards,

Michal

Parents
  • Hi,

    We have this example combining SDK v14.2 and Mesh v1.0

    You should follow this instruction:

    1. Download the mesh SDK v1.0 and nRF5 SDK v14.2

    2. Extract Mesh SDK v1.0 into nRF5 SDK v14.2, and rename the mesh SDK v1.0 to “mesh_sdk”, so the file structure will be like image description

    3. Extract the “ble_app_uart_mesh.zip” into “nRF5_SDK_14.2.0_17b948a\examples\ble_peripheral”

    4. Open the SES workspace and compile the project, and program to the nRF52-DK

    5. You can use “nRF-Toolbox UART” to test the firmware, after the client provisioned servers, you can send asci ‘0’ ~ ‘3’ to through NUS to control LEDs on servers.

    ble_app_uart_mesh.zip

Reply
  • Hi,

    We have this example combining SDK v14.2 and Mesh v1.0

    You should follow this instruction:

    1. Download the mesh SDK v1.0 and nRF5 SDK v14.2

    2. Extract Mesh SDK v1.0 into nRF5 SDK v14.2, and rename the mesh SDK v1.0 to “mesh_sdk”, so the file structure will be like image description

    3. Extract the “ble_app_uart_mesh.zip” into “nRF5_SDK_14.2.0_17b948a\examples\ble_peripheral”

    4. Open the SES workspace and compile the project, and program to the nRF52-DK

    5. You can use “nRF-Toolbox UART” to test the firmware, after the client provisioned servers, you can send asci ‘0’ ~ ‘3’ to through NUS to control LEDs on servers.

    ble_app_uart_mesh.zip

Children
Related