OpenThread CLI example doesn't join

[duv_FT]

Hi all,

I am trying to test OpenThread protocol for an application that we have and we want to use the CLI interface as the application logic should stay in the application processor and the nRF52 should be used as a modem. 

I am trying to get the CLI example running on Laird's development board as I cannot get my hands on nRF52840-DK right now as it is not available yet with the distributors I can order from. Based on the shematic two are very similar wiht buttons and LEDs on the same pins and the UART for the CLI is accessable. I am using the SDK v 1.0.0

I have successfully loaded the CLI example onto the board and I can run it and send commands over the UART. 

The problem is that when I follow the description I end up with two networks instead of the second powered node becoming a child.

This is the CLI correspondence code for first powered node:

panid 0xabcdDone
> ifconfig up
Done
> thread start
Done
> state
leader
Done
> ipaddr
fdde:ad00:beef:0:0:ff:fe00:fc00
fdde:ad00:beef:0:0:ff:fe00:dc00
fdde:ad00:beef:0:307a:dd2:4474:ea26
fe80:0:0:0:dc13:4d00:1f38:964b
Done
>

After powering up the second node I do the following:

panid 0xabcd
Done
> ifconfig up
Done
> scan
| J | Network Name | Extended PAN | PAN | MAC Address | Ch | dBm | LQI |
+---+------------------+------------------+------+------------------+----+-----+-----+
| 0 | OpenThread | dead00beef00cafe | abcd | de134d001f38964b | 11 | -39 | 216 |
Done
thread start
Done
> state
leader
Done
>

As it can be seen from the second node communication it can see the network but it decides to make its own which is not supposed to happen if I am reading the tutorial correctly. The keys should've been pre-shared and the second node should join the first network however that doesn't happen.

Then if I try to commission the other node I run into another issue.

On the first node I execute the following

> commissioner start
Done
> commissioner joiner add * PSSKK
Done
>

After reprogramming the second node when I do a scan I get following:

> scan
| J | Network Name | Extended PAN | PAN | MAC Address | Ch | dBm | LQI |
+---+------------------+------------------+------+------------------+----+-----+-----+
> | 1 | OpenThread | dead00beef00cafe | abcd | de134d001f38964b | 11 | -39 | 216 |
Done

which should indicate that the second node should be able to join. However attempting to join resutls in not found

joiner start PSSKK
Done
>
> Join failed [NotFound]

I get the same result when I try with commissioner set to allow only a specific node using eui64 of the node

> commissioner start
Done
> commissioner joiner add 765296676ddbdf98 PSSKK

and then running on second node

joiner start PSSKK
Done
> 
> Join failed [NotFound]

Is there any way that I can make the node connect to a set network panID?

I find it weird that it the radio sees the network when scanning but cannot connect to it. Am I missing something? Is this a board problem? If the examples are limited to only working on nRF52840-DK is there a document that shows what should I change in order to make it work on a custom board

Any help would be appreciated

DUV

[Edvin]

Hello,

Your first approach should work just fine. I just tested it with 2x nRF52840. Screenshot from terminals below:

 

Are you sure that the first one is still running when you try to run the second one? 

Do you use the same .hex file for both boards?

 

Since you are using a custom board. Do you have a LFXTAL? Since it is a possible source of error. Can you try to set both:

#define CLOCK_CONFIG_LF_SRC 0

and 

#define NRFX_CLOCK_CONFIG_LF_SRC 0

and try to compile again, and flash the output .hex file to both boards?

 

Best regards,

Edvin

[duv_FT]

Hi Edvin,

Thanks for the answer. It was totally the LFXTAL not connected properly issue.

The stack now behaves better, as it took quite a long time previously to become the leader after powering up.

I can connect the boards and send the messages

Thank you for your help!

Duv