NCS 1.6.0: The coprocessor (RCP) build for nrf52840 DK can't work as a RCP for latest ot-br-posix (2021-07)

[ThreadApp]

We tried two build options:

1. thread version 1.1 with 

# Set OpenThread NCP architecture
CONFIG_OPENTHREAD_COPROCESSOR=y
CONFIG_OPENTHREAD_COPROCESSOR_RCP=y

CONFIG_OPENTHREAD_THREAD_VERSION_1_1=y

with ot-br-posix (github.com/.../6e5576e9cb6f0da71ae96e3948a59683c58f5b11) also configured to be thread version 1.1 

2. thread version 2.2 

CONFIG_OPENTHREAD_COPROCESSOR_RCP=y

CONFIG_OPENTHREAD_THREAD_VERSION_1_2=y
CONFIG_OPENTHREAD_DUA=y
CONFIG_OPENTHREAD_MLR=y
CONFIG_OPENTHREAD_BACKBONE_ROUTER=y
CONFIG_OPENTHREAD_MAC_SOFTWARE_TX_SECURITY_ENABLE=y

with ot-br-posix(https://github.com/openthread/ot-br-posix/commit/6e5576e9cb6f0da71ae96e3948a59683c58f5b11) configured to be thread version 1.2

Both can't work, the otbr-agent log show that it can't establish stable link with the RCP

Please help to solve this basic question.

[Øyvind]

Hello, 

Nordic Semiconductor support team is currently understaffed due to summer vacations. Please expect slow response from our team.

---

I have forwarded your question to our Thread team. Will provide an answer within the week.

Kind regards,
Øyvind

[Øyvind]

Hello again, 

Can you please provide more information on what guide you are following to configure the RCP? What sample exactly are you using? In the OpenThread.io guide on RCP Joiner, there is a section on connecting native USB. This sections states "you must use the nRF USB port on the nRF52840 board to communicate with the RCP host (Linux machine)".

Please provide more information.

Thank you!

Kind regards,
Øyvind

[ThreadApp]

Dear Øyvind,

    Actually I have successfully setup a thread network with nRF52840 USB Dongles, with one be RCP which connected to Linux machine, and others to be FTD. Yet I found that that RCP dongle behavior badly due to it always miss lots of thread packets which cause the thread network unstable. So I tried with the DK board with ncs1.6.0 as above to be the RCP, the problem is that (from the OTBR logs) the OTBR host can't establish correct management link with the RCP, that is the host didn't think the RCP to be legal, so the thread network can't be formed.  

   Would you please also try the similar setup? ( Actually it is the similar as your formally released setup for DK, the difference is only the OTBR version to be the above git commit)

Thanks, 

Yours.

[Øyvind]

Hello, 

ThreadApp said:

I have successfully setup a thread network with nRF52840 USB Dongles,

Are you referring to the Configuring a radio co-processor chapter in the NCS Thread documentation?  This uses the OpenThread nRF52840 examples which we have no control over, I'm afraid. 

Currently, the nRF52840 Dongle is not supported in the official NCS Thread samples. 

 

ThreadApp said:

tried with the DK board with ncs1.6.0 as above to be the RCP, the problem is that (from the OTBR logs) the OTBR host can't establish correct management link with the RCP, that is the host didn't think the RCP to be legal, so the thread network can't be formed

 Are you getting any errors? Can you please provide the log from the OTBR showing the difference between the Dongle RCP and the DK RCP? Have you connected the cable to the correct USB port, as explained under Connecting to native USB?

 

ThreadApp said:

 Would you please also try the similar setup? ( Actually it is the similar as your formally released setup for DK, the difference is only the OTBR version to be the above git commit)

You are referring to this commit: https://github.com/openthread/ot-br-posix/commit/6e5576e9cb6f0da71ae96e3948a59683c58f5b11 ?

And using the NCS Thread:Co-prosessor sample to connect with the OTBR? With the following configuration: 

2. thread version 2.2 

CONFIG_OPENTHREAD_COPROCESSOR_RCP=y

CONFIG_OPENTHREAD_THREAD_VERSION_1_2=y
CONFIG_OPENTHREAD_DUA=y
CONFIG_OPENTHREAD_MLR=y
CONFIG_OPENTHREAD_BACKBONE_ROUTER=y
CONFIG_OPENTHREAD_MAC_SOFTWARE_TX_SECURITY_ENABLE=y

with ot-br-posix(https://github.com/openthread/ot-br-posix/commit/6e5576e9cb6f0da71ae96e3948a59683c58f5b11) configured to be thread version 1.2

What other devices are you running in the Thread network? 

  

 

ThreadApp said:

always miss lots of thread packets which cause the thread network unstable

Can you elaborate on what packets it misses?

Thanks for providing as much information as possible for our Thread developers.

Kind regards,

Øyvind