Thingy 52 Mesh - Node and Bridge Communication Error

Hi,

I need assistance in nordic thingy52 ble communication. I am using node and bridge code from the https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo

If I burn the precompiles node and bridge code it works fine.

When I try to compile the code in the segger studio it compiles fine just give one warning which is the following.

taking address of packed member of 'struct <anonymous>' may result in an unaligned pointer value [-Waddress-of-packed-member]

Does this error cause ble communication configuration issues?

When both node and bridge code are running it does not communicate with each other and gives the following error.

when I turn on the first node the following error shows up when I debugged the bridge.

:INFO:===== Thingy mesh demo bridge started! =====  
:INFO:Init: 
m_ble         :INFO:on_adv_evt: BLE_ADV_EVT_FAST
MAC addr-> f1:81:bc:e3:31:a2 
m_ui          :INFO:Mode: BLE_UIS_LED_MODE_BREATHE 
<t:        746>, nrf_mesh_sdk.c,  153, Initializing softdevice
<t:        750>, nrf_mesh_sdk.c,  163, Initializing mesh stack
<t:        785>, nrf_mesh_sdk.c,  171, Enabling mesh stack
<t:        792>, main.c,  281, Setting up access layer and models
<t:     375876>, provisioner.c,  379, Local provisioning link established
<t:     377364>, provisioner.c,  365, Using static authentication
<t:     455878>, provisioner.c,  374, Static authentication data provided
<t:     469138>, main.c,  397, Provisioning complete. Adding address 0x0100.
<t:     469150>, provisioner.c,  181, Getting composition data
<t:     472259>, provisioner.c,  334, Local provisioning link closed
<t:    1452207>, main.c,  383, Configuration of device 0 failed

When I turn on the second node the same goes for it it fails the configuration as shown below

<t:    8101565>, provisioner.c,  379, Local provisioning link established
<t:    8102485>, provisioner.c,  365, Using static authentication
<t:    8113585>, provisioner.c,  374, Static authentication data provided
<t:    8191313>, main.c,  397, Provisioning complete. Adding address 0x0101.
<t:    8191323>, provisioner.c,  181, Getting composition data
<t:    8195791>, provisioner.c,  334, Local provisioning link closed
<t:    9174380>, main.c,  383, Configuration of device 0 failed

Please suggest as I am unable to proceed with any further development. 

Thanks

Parents
  • Hello Muhammed,

    I will have to get back to you on this.

    But note that this is a very old example, and mainly meant as a demonstration of what is possible. Even if you were to develop something using the nRF5 SDK for Mesh (now that the nRF Connect SDK is what is recommended), you would have to use version 1.0.1 of the Mesh SDK here. That is old. I even see that the required repo Nordic-Thingy52-FW is deprecated.

    The samples that are listed on infocenter and developer.nordicsemi is what is mainly supported.

    What version of Thingy52 are you using?

    Regards,

    Elfving

Reply
  • Hello Muhammed,

    I will have to get back to you on this.

    But note that this is a very old example, and mainly meant as a demonstration of what is possible. Even if you were to develop something using the nRF5 SDK for Mesh (now that the nRF Connect SDK is what is recommended), you would have to use version 1.0.1 of the Mesh SDK here. That is old. I even see that the required repo Nordic-Thingy52-FW is deprecated.

    The samples that are listed on infocenter and developer.nordicsemi is what is mainly supported.

    What version of Thingy52 are you using?

    Regards,

    Elfving

Children
No Data
Related