Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Sigurd Hellesvik — Wed, 13 Oct 2021 09:03:45 GMT

I managed to reproduce your error.

It seems that otbr-agent use 115200 as the default baud rate.
Change the baud rate of the RCP uart by editing the overlay file in "coprocessor/boards" folder.

Does this fix your problem?

Regards,
Sigurd Hellesvik

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Mohinish — Tue, 12 Oct 2021 15:27:54 GMT

I tried changing the USB cable but still giving the same issue. I am using NCS v1.7 to build NRF52840 RCP target and OT-BR commit e149a60eb to build on Raspberry Pi 3B. Please try reproducing the issue.

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Sigurd Hellesvik — Thu, 07 Oct 2021 07:52:09 GMT

Hi Mohinish

A Thread node can be in different states.

The detached state means that the node is set up correctly, and thread is active, but that it is not yet part of any Thread network.
The leader state means that the Thread device is a part of a Thread network, and it is also the leader of the Thread network.
The leader state means that the Thread device is a part of a Thread network, but it is not the leader.

The "connect session failed: Connection refused" response you get could indicate that the Raspberry Pi has lost connection with the nRF52840DK.
This could be due to a defect in the USB cable. Could you try to change to another USB cable for the nRF52840DK and see if you still get the "connect session failed: Connection refused" error?

Spinel is a client used for communicate with the NCP(nRF52840DK). The error message in your earlier logs,"RadioSpinelNoResponse", could indicate that the Raspberry Pi does not have a connection to the NCP. So try the setup as well after you change the USB cable, and see if this is still there

Regards,
Sigurd Hellesvik

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Mohinish — Thu, 07 Oct 2021 05:53:02 GMT

Hi Marjeris,

I tried running 'sudo ot-ctl state' commands but it tends to return different results.

pi@raspberrypi:~ $ sudo ot-ctl state
detached
Done
pi@raspberrypi:~ $ sudo ot-ctl state
leader
Done
pi@raspberrypi:~ $ sudo ot-ctl state
connect session failed: Connection refused
pi@raspberrypi:~ $ sudo ot-ctl state
connect session failed: Connection refused
pi@raspberrypi:~ $ sudo ot-ctl state
detached
Done

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Marjeris Romero — Mon, 04 Oct 2021 11:27:56 GMT

Hi Mohinish,

About NCP support, Google decided to drop support for it in OT-BR. NCS still supports NCP build, but if someone wants to use it they should implement their own host side border router.

Could you try to run 'ot-ctl state' to check if you have contact with the RCP device? As it says that the RCP status is detached...

Best regards,

Marjeris

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Mohinish — Sat, 02 Oct 2021 14:04:46 GMT

Hi Marjeris,

I tried forming a Thread Network from OTBR Web GUI and it showed me even operation successful. But If I go to the status tab it is showing me this.

Below are otbr-agent service logs:

Oct 2 15:02:08 raspberrypi systemd[1]: otbr-agent.service: Main process exited, code=exited, status=6/NOTCONFIGURED
Oct 2 15:02:08 raspberrypi systemd[1]: otbr-agent.service: Failed with result 'exit-code'.
Oct 2 15:02:14 raspberrypi systemd[1]: otbr-agent.service: Service RestartSec=5s expired, scheduling restart.
Oct 2 15:02:14 raspberrypi systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 312.
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-UTILS---: Running 0.3.0-e149a60eb
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-UTILS---: Thread version: 1.2.0
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-UTILS---: Thread interface: wpan0
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-UTILS---: Backbone interface: wlan0
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-UTILS---: Radio URL: trel://wlan0
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-PLAT----: RCP reset: RESET_POWER_ON
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [NOTE]-PLAT----: RCP API Version: 4
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-PLAT----: Backbone interface is configured to wlan0 (3)
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Set state callback: OK
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Stop Thread Border Agent
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-ADPROXY-: Stopped
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-DPROXY--: stopped
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Initialize OpenThread Border Router Agent: OK
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-UTILS---: Border router agent started.
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Thread is down
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Stop Thread Border Agent
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-ADPROXY-: Stopped
Oct 2 15:02:14 raspberrypi otbr-agent[3479]: [INFO]-DPROXY--: stopped
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Thread is up
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Stop Thread Border Agent
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-ADPROXY-: Stopped
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-DPROXY--: stopped
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-ADPROXY-: Started
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Publish meshcop service OpenThread_BorderRouter._meshcop._udp.local.
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-MDNS----: Add service: OpenThread_BorderRouter._meshcop._udp (ref: 0x1f01a88)
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-ADPROXY-: Publish all hosts and services
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-DPROXY--: started
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [INFO]-AGENT---: Start Thread Border Agent: OK
Oct 2 15:02:19 raspberrypi otbr-agent[3479]: [CRIT]-PLAT----: HandleRcpTimeout() at ../../third_party/openthread/repo/src/lib/spinel/radio_spinel_impl.hpp:2202: RadioSpinelNoResponse
Oct 2 15:02:20 raspberrypi systemd[1]: otbr-agent.service: Main process exited, code=exited, status=6/NOTCONFIGURED
Oct 2 15:02:20 raspberrypi systemd[1]: otbr-agent.service: Failed with result 'exit-code'.
Oct 2 15:02:25 raspberrypi systemd[1]: otbr-agent.service: Service RestartSec=5s expired, scheduling restart.
Oct 2 15:02:25 raspberrypi systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 313.
Oct 2 15:02:25 raspberrypi otbr-agent[3489]: [INFO]-UTILS---: Running 0.3.0-e149a60eb
Oct 2 15:02:25 raspberrypi otbr-agent[3489]: [INFO]-UTILS---: Thread version: 1.2.0
Oct 2 15:02:25 raspberrypi otbr-agent[3489]: [INFO]-UTILS---: Thread interface: wpan0
Oct 2 15:02:25 raspberrypi otbr-agent[3489]: [INFO]-UTILS---: Backbone interface: wlan0
Oct 2 15:02:25 raspberrypi otbr-agent[3489]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000
Oct 2 15:02:25 raspberrypi otbr-agent[3489]: [INFO]-UTILS---: Radio URL: trel://wlan0
Oct 2 15:02:25 raspberrypi otbr-agent[3489]: [INFO]-PLAT----: RCP reset: RESET_POWER_ON
Oct 2 15:02:25 raspberrypi otbr-agent[3489]: [NOTE]-PLAT----: RCP API Version: 4

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Mohinish — Thu, 30 Sep 2021 17:39:32 GMT

Hi Marjeris,

RCP worked for me with NCS v1.7 and OT-BR commit e149a60eb.

I would like to know how to run OT-BR with NCS NCP architecture? Can you point me to tutorials that have detailed setup procedures?

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Marjeris Romero — Mon, 20 Sep 2021 13:43:28 GMT

Hi again,

Before NCS v1.7 we didn't officially support OT-BR with NCS RCP. If using NCS v.16.99 (latest) you can use the recommended commit for OT-BR: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thread_tools.html#installing-otbr-manually-raspberry-pi

Or you can work with OT-BR master and vanilla nRF52xxx RCP, built directly through OpenThread, not through NCS, has described in https://openthread.io/codelabs/openthread-border-router#1

NCS v.1.7 will be released with better support for OT-BR.

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Marjeris Romero — Mon, 20 Sep 2021 11:17:30 GMT

Hi Mohinish,

[quote user="Mohinish Naik"]Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [CRIT]-PLAT----: RCP API Version 3 is not in the supported range [4-4][/quote]

Based on the log report it seems to be some mismatch between APIs, I am checking if there is a recommended commit of the OT-BR example that should be used with NCS v1.6.1.

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Mohinish — Thu, 16 Sep 2021 18:14:12 GMT

Hi Marjeris,

I tried building as per your suggestion but still getting the error. Below I have put the otbr-agent service logs:

Sep 16 18:57:20 raspberrypi systemd[1]: otbr-agent.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Sep 16 18:57:20 raspberrypi systemd[1]: otbr-agent.service: Failed with result 'exit-code'.
Sep 16 18:57:25 raspberrypi systemd[1]: otbr-agent.service: Service RestartSec=5s expired, scheduling restart.
Sep 16 18:57:25 raspberrypi systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 632.
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [INFO]-UTILS---: Running 0.3.0-3bdb2fe63
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [INFO]-UTILS---: Thread version: 1.2.0
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [INFO]-UTILS---: Thread interface: wpan0
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [INFO]-UTILS---: Backbone interface: wlan0
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [INFO]-UTILS---: Radio URL: trel://wlan0
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [INFO]-PLAT----: RCP reset: RESET_POWER_ON
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [NOTE]-PLAT----: RCP API Version: 3
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [CRIT]-PLAT----: RCP API Version 3 is not in the supported range [4-4]
Sep 16 18:57:26 raspberrypi otbr-agent[1543]: [CRIT]-PLAT----: CheckRcpApiVersion() at ../../third_party/openthread/repo/src/lib/spinel/radio_spinel_impl.hpp:412: RadioSpinelIncompatible
Sep 16 18:57:26 raspberrypi systemd[1]: otbr-agent.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Sep 16 18:57:26 raspberrypi systemd[1]: otbr-agent.service: Failed with result 'exit-code'.

I would also like to know how I can implement OTBR with NRF52840 as NCP. Can you point me to some tutorial?

RE: Issue Running Open Thread Border Agent on Raspberry Pi 3 with NRF52840 as Network Co-processor (NCP)

Marjeris Romero — Thu, 16 Sep 2021 07:12:48 GMT

[quote userid="107803" url="~/f/nordic-q-a/79529/issue-running-open-thread-border-agent-on-raspberry-pi-3-with-nrf52840-as-network-co-processor-ncp"]Step 3: Built and Flashed nrf/samples/openthread/coprocessor example on NRF52840DK from NRF Connect SDK (NCS) v1.6.1[/quote]

Hi Mohinish,

I am sorry for the late reply, I will be looking into this today. Do you remember if you have configured the co-processor sample as NCP or RCP before building and flashing into the nRF52840 DK?

For using the co-processor sample together with the Openthread border router you will need to configure the sample as a radio co-processor (RCP), the default for the sample is for NCP architecture.

Can you try following the steps in Configuring a radio co-processor when building the co-processor sample: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thread_tools.html#configuring-a-radio-co-processor

And running this line:

west build -p always -b nrf52840dk_nrf52840 nrf/samples/openthread/coprocessor/ -- -DOVERLAY_CONFIG="overlay-rcp.conf ../cli/overlay-thread_1_2.conf"

instead of

west build -b nrf52840dk_nrf52840 --build_dir build_nrf52840dk_nrf52840

Remember also to --erase when flashing. Do also step 2.b for dissabling the mass storage functionality.

Let me know if this helps.

Best regards,

Marjeris