RE: Does each version of ncs correspond to an OpenThread Border Router docker image version?

AHaug — Thu, 10 Aug 2023 08:19:59 GMT

Regarding 4): It is stated in the documentation that you either have to follow the instructions in the OTBR codelab tutorial which explains how you create a Thread network with command line or you may open localhost:8080. Item 7 in https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/thread/tools.html#running-otbr-using-docker states this.

Kind regards,
Andreas

RE: Does each version of ncs correspond to an OpenThread Border Router docker image version?

AHaug — Wed, 09 Aug 2023 13:15:50 GMT

Hi Chuck,

Happy to hear that you're able to debug the light_bulb using chip-tool and otbr in Docker!

[quote user=""]The value of "fd11:22::/64" in step 2 represents the value of On-Mesh prefix. Is it filled in randomly?[/quote]

The prefix is not filled randomly. In the case of "fd" and "fe" they are so called "local", either Link-local or Mesh-local prefixes https://openthread.io/guides/thread-primer/ipv6-addressing

[quote user=""]I know that the items pulled from docker in Step 3 correspond to different ncs versions. What is the reason for this? If I want to test whether the chips of other manufacturers are different mirror versions, I have tried to implement the commissioning experiment of the chips of other manufacturers by chip-tool with the mirror of ncs V2.3.0, which seems impossible[/quote]

The reason for why there exists so many versions of CHIP which corresponds to different versions of NCS is due to changes in between the versions of both CHIP and NCS. When we release for instance NCS v2.3.0 we are running a multitude of tests to verify that the items we test for are qualified for release and we can only guarantee that a specific version(s) of the different software tools, programs, libraries and such. It does not make sense to use the same version of CHIP for NCS v2.0.0 and v2.4.0 because both the SDK and CHIP has had numerous changes, fixes and improvements in between the versions

[quote user=""]The last parameters in Step 4 are also custom?[/quote]

I think the same answer as the first question also goes here

[quote user=""]After implementing step 6 in the command line, it seems necessary to open the IP address corresponding to the Raspberry PI in the local browser and add the suffix ":8080", click in the "FORM" to generate the Thread network. Can this step be implemented through the command line? And I wonder if the point of this step is just to generate the Thread network that I built? Do you need to connect to the public network to authenticate anything through the server?[/quote]

I will have to check up on the last one. I will get back to you with something constructive once I know more.

Kind regards,
Andreas