CONFIG_OPENTHREAD_NETWORKKEY in prj.conf not working.

RE: CONFIG_OPENTHREAD_NETWORKKEY in prj.conf not working.

Amanda Hsieh — Tue, 29 Aug 2023 15:49:14 GMT

Hi,

As I explained previously, these values from Kconfig are set only in openthread_start() . The only way to jump into that function is if from, and only if CONFIG_OPENTHREAD_MANUAL_START flag is set: https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/net/l2/openthread/openthread.c#L591-L596

If you want to be able to set networkkey and channel, you will have to implement openthread API calls (as in the snippet in the previous reply). Of course, he can use KConfig entries there, and even reuse CONFIG_OPENTHREAD_NETWORKKEY etc.

-Amanda H.

RE: CONFIG_OPENTHREAD_NETWORKKEY in prj.conf not working.

SteveKranz — Sat, 26 Aug 2023 00:13:39 GMT

Hi Amanda,

I guess I was hopeful that I could construct a build image that had defaults that represented what I had specified in the prj.conf file.E.g overriding the defaults that normally would be used. But maybe you are saying that is not a valid manner to accomplish this? Still curious if maybe there is a setting I'm missing in prj.conf or alternate syntax that might get me there. Thanks in advance.

Steve.

PuzL Labs, LLC

RE: CONFIG_OPENTHREAD_NETWORKKEY in prj.conf not working.

Amanda Hsieh — Tue, 22 Aug 2023 12:52:54 GMT

Hi,

It depends on what you want to achieve. For example for the CLI sample, you can enable automatic Thread startup with the flag: CONFIG_OPENTHREAD_MANUAL_START=n

Then, in Zephyr, openthread_start() is called which sets flags used by you, but Thread starts automatically.

If you look into openthread_start()implementation, you can see that Thread API functions otLinkSetChannel() and otThreadSetNetworkKey() are used. you can also be called for example from main.c in our CLI sample, setting channel and networkkey without starting Thread. Sample code:

int main(void)
{
 otNetworkKey networkKey;
 struct openthread_context *ot_context = openthread_get_default_context();
 net_bytes_from_str(networkKey.m8, 16, (char *)"00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff");
 otThreadSetNetworkKey(ot_context->instance, &networkKey);
 otLinkSetChannel(ot_context->instance, 15);
}

Also, our CoAP samples show how the default networkkey and channel can be set, and used with openthread_start() call.

Regards,
Amanda H.

RE: CONFIG_OPENTHREAD_NETWORKKEY in prj.conf not working.

SteveKranz — Mon, 21 Aug 2023 14:56:49 GMT

Thanks Amanda, I am glad to hear you can reproduce the issue and are checking with the team. As for the alternate way you suggested, yes, that is what I've been doing as a [temp] workaround, but really need to have a solution where the build right out of the gate has the desired defaults and not requiring any additional user CLI interaction on first boot.

Thanks again, I hope to hear something back soon.

Steve K.

PuzL Labs, LLC.

RE: CONFIG_OPENTHREAD_NETWORKKEY in prj.conf not working.

Amanda Hsieh — Mon, 21 Aug 2023 14:27:55 GMT

Hi,

I can reproduce the issue with NCS v2.4.1 CLI sample and nRF52840DK. I would check with the team.

The alternate way is to set the network key and channel with commands as the commands. See the example in the CLI sample documentation.

Regards,
Amanda Hsieh