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

nRF52 Proxy Mesh SDK Support

Hi,

   We are currently using the Proxy Mesh SDK (V 2.2.0) for our application along with nRF52 15.0.0 SDK. We need to migrate it to the latest Proxy Mesh SDK and NRF52 SDK. 

  Could you please suggest the latest Proxy Mesh SDK and supporting nRF52 SDK for migration.

Regards,

Ram

  • Hi,

    The latest Mesh SDK is v4.2.0 and it supports nRF5 SDK v16.0.0.

    You can find the migration guide for Mesh here.

  • HI Mttrinh,

    1. As suggested we have started working  nRF5_SDK_16.0.0 and nRF5_SDK_17.0.2 with nrf5_SDK_for_Mesh_v4.2.0.

    2. When we run the mesh client example and we are able to provision the node using  nRF Mesh APP.

    3. After provisioning when we close the nRF Mesh APP and then we reopen the app and try to connect again to our device then  device is going to exception state. Please find the snippet below.

    4. But the same behavior as mentioned in Above Point number 3 is not observed in nRF 52840-DK this is weird.

    Hope i am able to provide all the inputs for this situation and would seek your help at the earliest.

  • Additional information : When we use nRF5_SDK_15.0.0 the above mentioned behavior is not observed and we are struck.

  • Just to clarify, when you use nRF5 SDK 15.0.0 then this issue doesn't occur?

    ramachandra said:
    nRF5_SDK_16.0.0 and nRF5_SDK_17.0.2

    Which of these are you using? Have you made any modifications to the client example from the SDK?

    Everything is working fine when you use the nRF52840-DK? Which device are you using when this issue occur?

  • Hi Mttrinh,

      Please find the inline comments below

        1. Just to clarify, when you use nRF5 SDK 15.0.0 then this issue doesn't occur?

               Ram: Yes when we have used nRF SDK 15.0.0 the issue was not present and it was not going to exception and asserting.

                  

        2. nRF5_SDK_16.0.0 and nRF5_SDK_17.0.2

        3.  Everything is working fine when you use the nRF52840-DK? Which device are you using when this issue occur?

                    Ram: Yes with the nordic SDK the issue is not observed, we are able to provision and unprovision 'n' number of times, even if we open and close the nordic mesh app we are not getting any exception. 

               We have developed our own BLE board for our application which is having similar chipset and configuration as Nordic DK, In this we are observing the issue.

      We are suspecting If there are any timing related parameter dependencies which can be configured in sdk_config.h file, If yes please suggest.  I have attached the sdk_config.h which we are currently using which we got along with mesh sdk

    Please let us know if anymore inputs required.

    Regards,

    Ram3051.sdk_config.h

Related