Mesh not working after reconnecting USB

[Natael]

Hello guys,

I am developing a BLE Mesh app with nRF52833DK. However, I have recently discovered a problem. It stops working the Mesh iI disconnect USB and then I Connect It. So the only solution I see is to provision them again. But this dont have any sense. 

How could I restore the funcionality develop?

Thank you,

Best regards :)

[Carl Richard]

Hello, Natael!

Could you please elaborate a bit on the problem. Does the application stop working when you disconnect USB? Does the sample use the USB in any way?

Note that we are short on staff due to the holidays, so there may be some delay in response time.

Best regards,
Carl Richard

[Natael]

Yeah sorry. I Will explain It a little more.

I have develop a coexistance BLE node(BLE + BLE Mesh) and some others node.

After I provisioned them throught the app, everything works fine. However, let's suppose for example I decide to power It off one of this node. Or another example of this could be that the battery of the coexistance BLE node goes to 0.

After this, the node It looks to be blocked and It doesnt work in the Mesh. So to use It again I have to provision It again. 

A little summary of this is:

1: Node provisioned => works fine.

2: node power off

3: Node power on again => Mesh funcionality doesnt work. Then I have to provision again to use It but in a Mesh app this doesnt have any sense. Configuration should be stored.

So my question is:

How can the provisioning information can be stored to avoid this cases or incidents?

I have seen that in the examples this information os stored because they keep working after some possible incident. However I dont ser how do you do It?

I Hope this explanation os better than the previous one.

Thank you,

Best regards.

[Carl Richard]

Hello again!

Thank you for the details.

A mesh device should stay provisioned in case of sudden reboots or other incidents, so there is something wrong here. Did you follow our guide on Integrating Bluetooth mesh into nRF5 SDK examples when developing your application?

Any logs or similar would be appriciated!

Best regards,
Carl Richard

[Natael]

I didnt really follow any guide hahaha.

But I have proved with dimming model and It doesnt happen this, I mean the configuration is saved(working with both SDKs)

Actually, I have detected something unusual. In the generic model-OnOff Server, when the value sent is On (1), the configuration is saved. However if I send an OFF(0) and disconnect the power, the configuration is not saved and It doesnt work even the buttons :(.

So what I think that is happening is that before disconnecting the power the value read is 0. After this, It read 1 and because of that It gets block. Maybe the configuration saved on the DSM (I have seen that the aprovisioning configuration is saved there) get corrupted.

The structure of this both Codes are the same and have a processing core statement which is 

"PERSISTENT_STORAGE = 1"

I would like to pass you any log, but I havent got any logger and the output of the serial Port is null (only in BLE + BLE Mesh Codes).

[Natael]

I have seen that the example works fine. At this moment the app (with BLE + ble Mesh) is not getting block. I uncomment the scene models and dtt and the Mesh handler.

However It doesnt save the last state when I powered off the device.

The only difference I could aprecciate was that I use bsp instead of hal library in the call-backs functions.

Could It be the problem?

[Carl Richard]

Hello again!

Apologies for the delayed answer on your case. A colleague pointed out that there may be differences in priorities between the BSP and HAL libraries that could interfere with normal mesh operation. Could you have a look at the documentation for Setting interrupt priority levels and see if the application is within the guidelines?

Best regards,
Carl Richard

[Natael]

Okey thank. Finllay i resolved the problem. Thank you for all :)

[Carl Richard]

Good to hear! It's our pleasure.

Best regards,
Carl Richard