Mesh-SDK v1.0.0: Light switch demo not working.

[Gaurav]

Hi,

I am trying to run the light switch example of the nRF5-SDK-for-Mesh-v1.0.0 on total 3 boards(1-client and 2-servers). I changed the no. of servers as mentioned in Readme file. But even after that, only 1 server gets provisioned as expected. For the other one, the provisioning process seems to get stuck somewhere and shows "Softdevice assert: 1:136746:0" in RTTViewer. (Using Segger Embedded Studio to flash to the boards.)

I have tested the same example for SDK-v0.9.2 with same nodes and it was working well there.

So, any idea as to what I could be doing wrong in this one.

Thanks.

Edit_26_12_17:
Using 3 nRF52832 based Murata module (link) and flashing the application using Embedded Studio.
As in attached images, only 1-server gets provisioned while other gives Softdevice error.
RTT_Light-switch_Client.JPG
RTT_Light-switch_server-2(with error).JPG
RTT_Light-switch_server-1.JPG

[David K.]

Dear all,

We are currently experiencing the same issue.

So, we have tested the Light / Switch example on the devKits and everything is working correctly. 1 Switch and 2 servers (the server count has been set to 2).

We have installed the code on other boards (same nrf52832 QFAA) and the code crashes with the same error... Our board runs the 32kHz crystal.

We are using the latest NRF SDK for Mesh.

Any idea on what may happen ? I would be happy to hear a solution has been found.

Regards,

David

[Hung Bui]

Hi David, 

Please make sure you erased the chip before you test. Data from previous firmware may mess up with the flash manager in mesh. 

If the issue persists, please use addr2line (addr2line -e filename <address>) to find where the error is thrown from. 

 

 

[David K.]

Hi Hung Bui,

The chip is erased. I am sure and positive about it. 

The issue to be more precise is the following : The device on which I am flashing the code is working for about 2 minutes. And then the error comes. All happens after the device is provisionned. I do not change the code between the DevKit and the Device.

Regarding addr2line, I am on MacOS and the tool is not accessible in a straight forward manner. So beginning of next week, I'll find out a linux machine to try. ATOS may be an option but I can't use it on the Stack hex file...

Regards.

[David K.]

So back on a linux Machine. I might be confused on the way using addr2line. because the only answer I get is ??:0

addr2line -e s132_nrf52_5.0.0_softdevice.hex 136746

So, compiling on a Mac, flashing using nrfjprog and doing a nrfjprog -e to erase the chip.

I'll dig a bit more... But any directions in which to look for would be appreciated.

Cheers,

D.

[Hung Bui]

You should use addr2line -e yourapplication.elf address 

Not the softdevice.hex file. 

[David K.]

Yep. I have tried. Unfortunately not much success.

The only complement : nrf_mesh_node_config.c,  108, Softdevice assert: 1:136746:0. But it was already displayed in original post.

I'll dig a bit more.

[Hung Bui]

@David: I have reported the issue to our R&D team. Will let you know if I hear anything from them.