otInstanceFactoryReset does not work properly.

[H-ogawa]

Hi,

Added a function to the coap_client sample code that executes otInstanceFactoryReset by pressing a button and sets it to factory shipping mode. However, it appears that the device just reset and did not delete all settings stored in non-volatile memory.
The CLI factroyreset command removes configurations stored in non-volatile memory.

I'm using the same API that I'm running in the CLI, so why would there be a difference?

I'm using SDK v2.5.0.

Best regards,

Hiroki

[Jørgen Holmefjord]

Hi,

Can you post the exact code you have used to call the API?

Are you using the unmodified coap_client sample from nRF Connect SDK v2.5.0, or have you made other modifications?

Are you testing this on a nRF52840 DK?

Best regards.
Jørgen

[H-ogawa]

Hi, Jorgen

Thank you for reply.

The part of the code that executes the API is as follows.

I am trying to run it when I press BTN3.

I am modifying the sample code, but I am changing the cli mode while it is still valid. If you run the ot factoryreset command in this changed state, the factory default mode will be set.

I'm using a custom board, not the nRF52840 DK. The pin assignments have also been changed to use buttons on the custom board, and we have confirmed that btn3 processing is performed using printk.

Best regards,

Hiroki

[Jørgen Holmefjord]

Hi,

The coap_client sample have default networkkey set in the prj.conf file, have you removed this? And have you enabled CONFIG_OPENTHREAD_JOINER_AUTOSTART?

The openthread_start() function will load the default config if no commissioned dataset is found and the joiner is not configured to autostart.

Best regards,
Jørgen

[H-ogawa]

Hi,Jorgen

I'm doing it without using openthread_start. Therefore, by default it is not affected by network keys or CONFIG_OPENTHREAD_JOINER_AUTOSTART.
Just to be sure, I deleted the network key and enabled CONFIG_OPENTHREAD_JOINER_AUTOSTART, but there was no change.
After further investigation, implementing a process that runs otInstanceFactoryReset when otDatasetIsCommissioned is enabled in the coap_client_utils_init method results in a factory default state. However, if otInstanceFactoryReset is executed within the button process instead of within the coap_client_utils_init method, the factory default state will not be set.
Is there a rule to determine when to call otInstanceFactoryReset?

Best regards,

Hiroki

[Jørgen Holmefjord]

Can you try to run otInstanceFactoryReset in main thread based on a flag from the GPIO/button press instead of calling it directly in the button handler? The handler may run in interrupt context, where not all APIs will function properly.