SRP Client Key and name conflicts #8864
-
Hi guys, Client key should be stored on non-volatile memory and be automatically loaded on reboot (excluding a device hard-reset of course). It seems that in my case (STM32WB stack) persistent data is not saving the key and when power goes down, at the next boot, I get
my code to send service to the server is the following, and of course, it works when it is firstly registered to the server otSrpClientSetCallback(NULL, _CP_SrpCallback, ci);
error = otSrpClientSetHostName(NULL, ci->EUI64);
error = otSrpClientAddService(NULL, &service);
error = otSrpClientSetHostAddresses(NULL, &otLocalMLEIDAddress, 1);
error = otSrpClientStart(NULL, &SRP); So my question is: is there any way to get the key from the openthrea API and later load it to the SRP Client? Or any way to manipulate the key? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The Thread Specification requires certain information to be stored in non-volatile (including the SRP Client key) - see OpenThread's platform requirements in include/openthread/platform/settings.h. If the Thread device is not able to store this information in non-volatile storage, then there will be other issues as well. |
Beta Was this translation helpful? Give feedback.
The Thread Specification requires certain information to be stored in non-volatile (including the SRP Client key) - see OpenThread's platform requirements in include/openthread/platform/settings.h. If the Thread device is not able to store this information in non-volatile storage, then there will be other issues as well.