About OpenThread tutorial

RE: About OpenThread tutorial

dejans — Tue, 25 Jul 2023 08:10:49 GMT

Hi Yuma,

You could have a look at OpenThread CLI and the list of CLI commands. There is also OpenThread CLI sample in the NCS documentation.

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Mon, 24 Jul 2023 09:01:40 GMT

Hi Dejan,

I have one more question.

What command should I use to send Thread messages in OpenThread CLI?
I was able to confirm that I can send a UDP message by using the "ot udp" command, but I couldn't find out how to send a Thread message by calling the README.

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Fri, 21 Jul 2023 14:38:28 GMT

Hi Yuma,

Thank you for your feedback.
I am glad that I was able to assist you so far and that the connection was successful.

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Fri, 21 Jul 2023 10:38:51 GMT

Hi Dejan,

I tried same procedure using two nRF52840-DKs (both version are v3.0.1).
As a result of execution, joiner connection was successful.

As I assumed, it was most likely a board version dependent issue.
I will proceed with the operation check in a successful environment, but it may be better to specify the recommended version of the board that runs each sample.

Thank you for helping me a lot.

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Tue, 11 Jul 2023 10:11:48 GMT

Hi,

[quote user="Yuma"]I followed the same procedure as you, and the result is the same as I told you before.[/quote]

Thank you for the update.

[quote user="Yuma"]I suspected a problem with the version of the board I was using, so I purchased a new board.
I'll try it again when my board arrives and let you know the results.[/quote]

Please let me know the results when you finish your testing.

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Tue, 11 Jul 2023 01:46:32 GMT

Hi Dejan,

Thank you for showing me the steps.
I followed the same procedure as you, and the result is the same as I told you before.

I suspected a problem with the version of the board I was using, so I purchased a new board.
I'll try it again when my board arrives and let you know the results.
Please let me know if you find anything new in your environment.

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Fri, 07 Jul 2023 14:18:33 GMT

Hi,

You could test your sequence as well.

There was one line missing from my previous reply which is "ot thread stop". So first I did

ot thread stop

on both devices. Then I continued with commissioner:

ot dataset init new
ot dataset commit active
ot ifconfig up
ot thread start
ot dataset
ot commissioner start

At this point I needed eui64 from the joiner. On the joiner:

ot eui64

With the value of eui64 from the output, I return to the commissioner:

ot commissioner joiner add <eui64_from_joiner_device> N0RD1C

When this is done, I go back to the joiner:

ot ifconfig up
ot joiner start N0RD1C
ot thread start

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Fri, 07 Jul 2023 08:42:01 GMT

Hi Dejan,

Thank you for your confirm the operation.

Do you expect to run joiner commands after running "ot commissioner joiner add" command on commissioner?
My understanding is to run the commands in the following order.

On the commissioner:

ot thread stop
ot dataset init new
ot dataset commit active
ot ifconfig up
ot thread start
ot dataset

On the joiner:

ot thread stop
ot eui64

On the commissioner:

ot commissioner start
ot commissioner joiner add <eui64_from_joiner_device> N0RD1C

On the joiner:

ot ifconfig up
ot joiner start N0RD1C
ot thread start

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Fri, 07 Jul 2023 07:19:39 GMT

Hi,

I have tested commissioning process with 2 nrf52840-dk boards, first v2.0.2 and second v3.0.0. I have seen both "Commissioner: Joiner remove ..." on the commissioner side and "Join failed [NotFound]" (or Error 13: Invalid state) on the joiner side. I do not think that these errors appeared as a result of different version of the development kits, but rather when the commands are executed on a wrong device or if the sequence of commands is not followed properly. Following the guide, you should first configure the commissioner (leader) and then the joiner.

On the commissioner:

ot thread stop
ot dataset init new
ot dataset commit active
ot ifconfig up
ot thread start
ot dataset
ot commissioner start
ot commissioner joiner add <eui64_from_joiner_device> N0RD1C

On the joiner:

ot eui64
ot ifconfig up
ot joiner start N0RD1C
ot thread start

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Wed, 05 Jul 2023 03:24:09 GMT

Hi Dejan,

I send the OpenThread CLI sample.

The operation confirmation environment is as follows.
- hardware
CPU: Intel Core i7-7700
Memory: 16GB
- software
OS: Ubuntu 20.04.6 LTS (x64)
J-Link Software and Document Pack: V7.88h
nRF Connect for Desktop: V4.1.2 Linux
nRF Connect SDK: V2.4.99

After installing each tool, the operation check procedure is as follows.
1. Launch nrfconnect-4.1.2-x86_64.appimage
2. Open Toolchain Manager.
3. Press "Open Terminal" on nRF Connect SDK v2.4.0
4. Build the sample by executing the following command on the started terminal.
cd nrf/samples/openthread/cli
west build -b nrf52840dk_nrf52840
5. Connect the nRF52840-DK to the PC and write the built sample to the nRF52840-DK (execute for 2 units)
west flash --erase
6. Execute OT commands according to the instructions in the commissioning tutorial.

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Tue, 27 Jun 2023 12:01:07 GMT

Hi,

Could you provide me with a sample project and all necessary steps for reproducing your issue?

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Tue, 27 Jun 2023 01:33:35 GMT

Hi Dejan,

> Have you tried using Windows?

No, I haven't.
Are you suggesting that the board may behave differently depending on which OS the nRF Connect SDK is launched on?

> Have you tried with both boards of the same version?

No.
Is my understanding correct that the v0.9.2 board and the v3.0.1 board have different hardware configurations to the extent that the Thread sample behavior is different?

> Have you tried using different boards, for example nrf52840-dk v2.0.2?

No.
The nRF52840-dk I purchased earlier this month was v3.0.1, so I'm assuming that the version of the board I will be purchasing additionally will also be v.3.x.x.

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Mon, 26 Jun 2023 13:47:48 GMT

Hi,

Have you tried using Windows?

Have you tried with both boards of the same version?

Have you tried using different boards, for example nrf52840-dk v2.0.2?

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Thu, 22 Jun 2023 13:08:45 GMT

Hi Dejan,

I sent the wrong log.
The correct Joiner (V3.0.1) log is below.

*** Booting Zephyr OS build v3.3.99-ncs1 ***


uart:~$ ot eui64
f4ce365f6f56d7d9
Done
uart:~$ ot ifconfig up
Done
uart:~$ ot joiner start N0RD1C
Done
Join failed [NotFound]
uart:~$

Do you have any idea what could be the possible cause for this result?

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Thu, 22 Jun 2023 10:15:58 GMT

Hi,

The logs from joiners in your 2 setups seem to be the same. There is no "Join failed [NotFound]" error on the joiner side in your first setup (joiner v3.0.1).

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Thu, 22 Jun 2023 06:11:39 GMT

He Dejan,

I understand those litimations to be "The Joining Device Credential is composed of at least 6 and no more than 32 uppercase alphanumeric ASCII characters (base32-thread, 0 to 9 and A to Y, with the exclusion of I, O, Q, and Z)."
According to that limitation, I use the string "NORDIC" with "O" replaced by 0 and "I" replaced by 1 as PSKd.

In my environment, I use two different versions of nRF52840DK. (V0.9.2 and V3.0.1)

Below is the log for setting up V0.9.2 as Commissioner and V3.0.1 as Joiner.
In this case, a "Join failed [NotFound]" error was displayed on the Joiner side.

Commissioner (v0.9.2)

*** Booting Zephyr OS build v3.3.99-ncs1 ***


uart:~$ ot thread stop
Done
uart:~$ ot dataset init new
Done
uart:~$ ot dataset commit active
Done
uart:~$ ot ifconfig up
Done
uart:~$ ot thread start
Done
uart:~$ ot dataset
Active Timestamp: 1
Channel: 19
Channel Mask: 0x07fff800
Ext PAN ID: eee8b1d35d500727
Mesh Local Prefix: fdc9:969:c6f8:ec5f::/64
Network Key: 18df0d4fd3aed28babc035336ac50817
Network Name: OpenThread-7895
PAN ID: 0x7895
PSKc: 0e14f6c19136fc34eb064edc20c483a6
Security Policy: 672 onrc
Done
uart:~$ ot commissioner start
Error 13: InvalidState
uart:~$ ot commissioner start
Error 13: InvalidState
uart:~$ ot commissioner start
Error 13: InvalidState
uart:~$ ot commissioner start
Error 13: InvalidState
uart:~$ ot commissioner start
Error 13: InvalidState
uart:~$ ot commissioner start
Commissioner: petitioning
Done
Commissioner: active
uart:~$ ot commissioner joiner add f4ce365f6f56d7d9 N0RD1C
Done
uart:~$

Joiner (v3.0.1)

*** Booting Zephyr OS build v3.3.99-ncs1 ***


uart:~$ ot eui64
f4ce36281bbf9601
Done
uart:~$ ot ifconfig up
Done
uart:~$ ot joiner start N0RD1C
Done
uart:~$

On the other hand, the log of setting up V3.0.1 as Commissioner and V0.9.2 as Joiner is below.
In this case, "Join failed [NotFound]" error is not displayed on Joiner side and "Commissioner: Joiner remove d3f93fad8484f27a" message was displayed on Commissioner side.

Commissioner (v3.0.1)

*** Booting Zephyr OS build v3.3.99-ncs1 ***


uart:~$ ot thread stop
Done
uart:~$ ot dataset init new
Done
uart:~$ ot dataset commit active
Done
uart:~$ ot ifconfig up
Done
uart:~$ ot thread start
Done
uart:~$ ot dataset
Active Timestamp: 1
Channel: 22
Channel Mask: 0x07fff800
Ext PAN ID: dfe7d89a0296e843
Mesh Local Prefix: fd67:bd59:ee13:8e7c::/64
Network Key: 689c180dbaa8a07a286745ffb5d95557
Network Name: OpenThread-c075
PAN ID: 0xc075
PSKc: 34ece973b65458eff346d4a0a7f4ef6c
Security Policy: 672 onrc
Done
uart:~$ ot commissioner start
Error 13: InvalidState
uart:~$ ot commissioner start
Error 13: InvalidState
uart:~$ ot commissioner start
Commissioner: petitioning
Done
Commissioner: active
uart:~$ ot commissioner joiner add f4ce36281bbf9601 N0RD1C
Done
Commissioner: Joiner remove d3f93fad8484f27a
uart:~$

Joiner (v0.9.2)

*** Booting Zephyr OS build v3.3.99-ncs1 ***


uart:~$ ot eui64
f4ce36281bbf9601
Done
uart:~$ ot ifconfig up
Done
uart:~$ ot joiner start N0RD1C
Done
uart:~$

If there is no problem with the command execution procedure or command contents, I suspect that the board version is the cause from the difference in execution results.
Please tell us your opinion.

Best regards,

Yuma Shimazu

RE: About OpenThread tutorial

dejans — Wed, 21 Jun 2023 09:44:00 GMT

Hi,

This might be due to the previous "ot commissioner joiner add" command. As stated in setting up commissioner, there are some encoding limitations.

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Tue, 20 Jun 2023 01:35:35 GMT

Hi Dejan,

I tried commissioning as described in the URL below.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/thread/overview/commissioning.html

However, when I run the "ot joiner start N0RD1C" command on the joiner device, it fails with the following message:
Join failed [Not Found]

What could be the reason for the failure?

My environment is below.
- nRF connect SDK 2.4.99
- nRF52840DK (one each for V0.9.2 and V3.0.1)
- Thread cli samples are already written on each board

Best regards,

Yuma

RE: About OpenThread tutorial

Yuma — Sat, 17 Jun 2023 14:50:13 GMT

Hi Dejan,

Thank you for your advice.

I installed NCS v2.4.0 and programmed the cli sample onto the board.
As a result, by sending the "ot state" command to the board via serial communication, I was able to confirm that there was a reply from the board.

I haven't been able to confirm Thread operation with cli yet, but I'm relieved to be able to confirm that the written sample seems to be working properly.

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Wed, 14 Jun 2023 06:39:04 GMT

Hi,

We have tested NRF Connect SDK (NCS) co-processor sample from NCS v2.4.0.

The tutorial for building RCP that you referred to is quite old. It is recommended to use NCS-based co-processor solution for building RCP firmware. You can read about NCS in the documentation. There you can also find guides how to install NCS automatically or manually. Documentation also provides resources about openthread co-processor communication. Additionally, it provides several thread samples where you can read specifically about thread co-processor sample.

Best regards,
Dejan

RE: About OpenThread tutorial

Yuma — Mon, 12 Jun 2023 08:23:36 GMT

Hi, Dejan

Is this the NCS v2.4.0 you indicated?

https://github.com/nrfconnect/sdk-nrf/releases/tag/v2.4.0

I guessed to use NCS instead of nRF Command Line Tools, but since NCS doesn't include nrfjprog, I wasn't sure how to use it.

Also, I tried the tutorial under the following environment, but the same error was output when starting ot-daemon.

Ubuntu: 20.04.6 LTS
JLink: V7.88f
nRF5x Command Line Tools: 10.21.0 Linux x86 x64
ARM GNU toolchain: 10.3-2021.10 x86 x64 linux

Could you tell me the version of each tool that you have confirmed to work properly?

Best regards,

Yuma

RE: About OpenThread tutorial

Yuma — Mon, 12 Jun 2023 03:09:15 GMT

Hi, Dejan

Thank you for your comment.

I have ubuntu 20.04, where can I get NCS v.2.4.0?
I tried looking it up but couldn't find it.

Best regards,

Yuma

RE: About OpenThread tutorial

dejans — Tue, 06 Jun 2023 21:37:36 GMT

Hi,

We have tested on Ubuntu 20.04 and NCS v2.4.0. There were no issues on our side. Could you try on Ubuntu 20.04 as well?

Best regards,
Dejan