About OpenThread tutorial

[Yuma]

Hi, I'm trying to run a tutorial that does OpenThread process with nRF52840-DK.

The URL for reference is below.

https://openthread.io/codelabs/openthread-hardware?hl=ja#0

I'm doing it in order from the first step, but I get an error at the "Start OpenThread Daemon" step and can't proceed.

In addition, I confirmed that the nRF52840-DK was detected as ttyACM0 just before.

--- log start --------------------

sudo ./build/posix/src/posix/ot-daemon -v 'spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=115200'
./build/posix/src/posix/ot-daemon[3558]: Running OPENTHREAD/thread-reference-20230119-423-gfd1a247ae; POSIX; Jun 6 2023 02:22:15
./build/posix/src/posix/ot-daemon[3558]: Thread version: 4
./build/posix/src/posix/ot-daemon[3558]: 49d.17:15:15.166 [C] Platform------: Too many rcp failures, exiting
./build/posix/src/posix/ot-daemon[3558]: 49d.17:15:15.166 [C] Platform------: RecoverFromRcpFailure() at radio_spinel_impl.hpp:2333: Failure

--- log end ---------------------

The execution environment is below.

OS Name: Ubuntu 22.04.2 LTS

OS Type: 64-bit

SEGGER J-Link: V7.88e 64-bit DEB Installer

nRF5x Command Line Tool: V10.21.0 Linux x86 64

ARM GNU toolchain: gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2

Are there any possible solutions for this situation?

[Yuma]

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

[Yuma]

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

[Yuma]

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

[dejans]

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

[Yuma]

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

[dejans]

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

[Yuma]

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

[dejans]

Hi,

Yuma said:

I followed the same procedure as you, and the result is the same as I told you before.

Thank you for the update. 

Yuma said:

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 the results when you finish your testing.

Best regards,
Dejan

[Yuma]

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

[dejans]

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

[Yuma]

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

[dejans]

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