Hi I just wanted to ask, It would be nice if we can get Openthread Stack as softdevice similar to BLE. Do you have any plans for the same ?
Hi I just wanted to ask, It would be nice if we can get Openthread Stack as softdevice similar to BLE. Do you have any plans for the same ?
Hello,
The OpenThread Stack is not Nordic Semiconductor's property, which is why the libraries are included in nRF5_SDK_for_Thread_and_Zigbee_2.0.0_29775ac\external\openthread.
In the getting started guide for Thread on infocenter, it is explained how these libraries (binary files) are built, and also how you can compile the latest openthread stack under the "Building the latest OpenThread stack" section.
So the reason for why it isn't a binary file without source code is because it is in fact an open source library, not created by Nordic. Note that because of updates in the openthread stack, it may not run without modifications in the example if you build the latest release of openthread. This is described in the guide.
However, a snapshot of the openthread library is included in the SDK, and this one works without modifications of the examples.
Best regards,
Edvin
Hello,
The OpenThread Stack is not Nordic Semiconductor's property, which is why the libraries are included in nRF5_SDK_for_Thread_and_Zigbee_2.0.0_29775ac\external\openthread.
In the getting started guide for Thread on infocenter, it is explained how these libraries (binary files) are built, and also how you can compile the latest openthread stack under the "Building the latest OpenThread stack" section.
So the reason for why it isn't a binary file without source code is because it is in fact an open source library, not created by Nordic. Note that because of updates in the openthread stack, it may not run without modifications in the example if you build the latest release of openthread. This is described in the guide.
However, a snapshot of the openthread library is included in the SDK, and this one works without modifications of the examples.
Best regards,
Edvin
I got your point, can we put openthread stack and application as separate hex file, so that we can update the application and network stack individually during DFU process. As of now DFU is done which is single hex file which include both application and openthread code.
That is true,
You would have to compile it as a .hex file, in order to generate a packet with it. In addition you would have to do some modifications to the bootloader to accept openthread "softdevices". I am not quite sure where to start with this.
But there are some DFU examples in the SDK that works. As long as you use a certain build of the openthread lib-file, it shouldn't be a problem to perform the DFU? Why do you need it in two different .hex files?
BR,
Edvin
I want to update application and openthread (softdevice), separately. I don't know if it can be done with single hex file or we need two hex files.
please guide me to achieve this goal.
We don't have support for this. I also don't think it sounds like a good idea, as updating only one of the two may lead to having an application that doesn't work with the openthread stack version, which may lead to a bricked device (that would require re-programming physically).
So it is not possible with the current bootloader. It would probably be possible to implement, but this is not something you would have to attempt yourself.
Best regards,
Edvin
