Mesh serial firmware can not control the node after reset, until the node reset again

RE: Mesh serial firmware can not control the node after reset, until the node reset again

tesc — Mon, 05 Jul 2021 13:26:29 GMT

Hi,

A serial interface for reading and writing the net state has been added. (It may have been there for quite some while, I have not looked up when exactly it was introduced.) This means you now have Net State Set and Net State Get for this purpose.

Regards,
Terje

RE: Mesh serial firmware can not control the node after reset, until the node reset again

tesc — Thu, 29 Aug 2019 10:54:43 GMT

Hi,

There is a workaround of enabling "PERSISTENT_STORAGE = 1", in which case the sequence number will be written to flash.

See https://devzone.nordicsemi.com/f/nordic-q-a/48496/mesh-serial-example-don-t-store-sequence-number for more details.

Would this solve the issue, enabling you to deploy?

Regards,
Terje

RE: Mesh serial firmware can not control the node after reset, until the node reset again

tesc — Thu, 29 Aug 2019 10:48:34 GMT

Hi,

Plan is to add serial API for setting sequence number. It is not yet implemented. What is the time frame for your project?

Regards,
Terje

RE: Mesh serial firmware can not control the node after reset, until the node reset again

timvan — Thu, 29 Aug 2019 10:10:00 GMT

Hi Hai and Tesc, we are also experiencing this problem. Unfortunately for us, it's not possible to hard reset all the deployed nodes if the serial device is reset. This is definitely a significant blockage for moving our mesh system into deployment.

Is there any update on whether the fix for this has been proposed and if so when will it be added?

Many Thanks,

Tim

RE: Mesh serial firmware can not control the node after reset, until the node reset again

tesc — Fri, 14 Dec 2018 09:48:27 GMT

Hi,

I can now confirm that it is because of the sequence number not being stored. We want to fix this by adding an API for setting the sequence number, but that is not yet implemented and I am not quite sure when we plan to do it. Would it be an acceptable workaround for now to rely on resetting the other board?

Regards,
Terje

RE: Mesh serial firmware can not control the node after reset, until the node reset again

Hai Nguyen — Wed, 05 Dec 2018 00:31:13 GMT

Thanks for your reply. For PyACI, I quit the interactive PyACI then press the reset button on PCA10040 to swipe out all keys and run PyACI again at beginning (load database, run Provisioner to load keys, setup GenericOnOff to control the node provisioned previously). To get it work again, I only press the reset button on the node (PCA10056) and can control on/off from PyACI.

Maybe it's the sequence number, because after I send the on/off command many times patiently, it works again. How I keep the sequence number for PyACI? Any way to reset the sequence number from the PCA10040

RE: Mesh serial firmware can not control the node after reset, until the node reset again

tesc — Tue, 04 Dec 2018 17:26:15 GMT

Hi,

How do you hard reset the PCA10040 and PyACI, and what do you do for getting it up and running again? And for provisioning, are you just following Interactive mesh provisioning and configuration?

I suspect it may have to do with sequence numbers. Each node uses a strictly increasing sequence number for each new message it sends out, in order to protect against replay attacks. This means the node has to keep track at all times of what is the highest sequence number it has used thus far. This is handled for other nodes, but I am not quite sure what happens for the PyACI node if it abruptly is shut down or the serial link is lost.

Regards,
Terje