Running RCP image on K32W USB dongle

[maunish_patel]

I have purchased new K32W USB dongles. I am trying to run openthread sample example on an ubuntu machine with  K32W dongle.

I have created RCP image for k32w  dongle from openthread github.(https://github.com/openthread/ot-nxp/blob/main/src/k32w0/k32w061/README.md)

I am running ot-deamon on the ubuntu PC using following command

#ot-daemon -v 'spinel+hdlc+uart:///dev/ttyUSB1?uart-baudrate=115200'.

But ot-deamon is failing to communicate with the K32W dongle and giving folloewing error

[./build/posix/src/posix/ot-daemon[23634]: Running OPENTHREAD/20200818-01178-gdeb2a4c97; POSIX; Aug 25 2021 15:50:40
./build/posix/src/posix/ot-daemon[23634]: Thread version: 3
./build/posix/src/posix/ot-daemon[23634]: [CRIT]-PLAT----: HandleRcpTimeout() at /home/maunish/src/openthread/src/posix/../../src/lib/spinel/radio_spinel_impl.hpp:2204: RadioSpinelNoResponse]

Do i need to make specific changes to communicate over USB for dongle?

is there any ready example for open thread RCP Image present for k32w?

[mihai_ignat]

Hello, all.

In order to provide closure for this topic, OT RCP support on K32W0 USB dongle is available as a binary in the K32W0 SDK starting with version 2.6.10. The binary can be found in /tools/wireless/ot-rcp folder under the ot-rcp-uart-no-fc-usb name, as binary and axf file. You can find the latest SDK by accessing this link .

otbr-agent needs an extra argument:

?uart-baudrate=1000000

Please see this comment also.

Looking forward for your confirmation of the example working.

BR,

Mihai

[mario_castaneda]

Hi @maunish_patel,

There is an example that we provide in our documentation.

I am running the example and I could provide any advice trying to run it.

Chapter 11 Running Border Router Application Scenarios

"\K32W061DK6\docs\wireless\OpenThread\OpenThread Demo Applications User Guide.pdf"

Regards,

Mario

[mario_castaneda]

Hi @maunish_patel,

I hope you are doing great. I am sorry for my late reply.

I am working on the RCP example. I will get back to you as soon as possible.

Regards,

Mario

[Ciberguardian]

@mario_castaneda Is there a way to get RCP running with an up-to-date ubuntu (20.04 LTS) and use an up-to-date (the openthread standard) OTBR docker image?

The procedure in the above referenced manual seems very outdated (Ubuntu 18.04) and requires a udoo board. The docker image itself is 21 months old!

• Flashing the precompiled SDK_2_6_4_K32W061DK6\middleware\wireless\openthread\openthread\output\k32w061\bin\ot-rcp.bin from the SDK with standard openthread/otbr:latest, fails on RCP version 1 (may be also due to the "old" precompiled version).

Nov 28 20:06:05 1bddcdc59126 otbr-agent[216]: 49d.18:20:43.752 [INFO]-PLAT----: RCP reset: RESET_SOFTWARE
Nov 28 20:06:05 1bddcdc59126 otbr-agent[216]: 49d.18:20:43.816 [NOTE]-PLAT----: RCP API Version: 1
Nov 28 20:06:05 1bddcdc59126 otbr-agent[216]: 49d.18:20:43.816 [CRIT]-PLAT----: RCP API Version 1 is not in the supported range [4-5]
Nov 28 20:06:05 1bddcdc59126 otbr-agent[216]: 49d.18:20:43.816 [CRIT]-PLAT----: CheckRcpApiVersion() at ../../third_party/openthread/repo/src/lib/spinel/radio_spinel_impl.hpp:413: RadioSpinelIncompatible

• Compiling all examples with the NXP described procedure, generates an ot-rcp.bin that is unrecognized by the "official" ot-otbr" docker build. USB detected - NXP USB recognized - full stop

Any (NXP) assistance is appreciated.

Jan K

Using both JN5189 as K32W dongles

[mario_castaneda]

Hi @Ciberguardian,

What is the process that you are doing?

Could you please share a screen of the issue that you have?

What is the docker that you are using for running this RCP?

Regards,

Mario

[Ciberguardian]

Hi Mario

i try to get the standard OBTR docker image working with the NXP JN5189 & K32w061 dongles.

On Ubuntu 20.04,

• I installed the MCUXpresso IDE,
• did a git clone of nxp-ot,
• unpacked the JN5189 & K32w061 SDK

The i executed the fix mr3 scripts, & export SDK and launched the build.

The ot-rcp.bin that gets build can be flashed with the NXP flasher (on windows) but is not recognized in OBTR and does not allow serial communication (which the FTD and MTD do allow).

On the other hand, if I flash the precompiled ot-rcp.bin image from the SDK, the docker OBTR does recognize the RCP but fails on API version 1, where it expects version 4-5.

(SDK/middleware/wireless/openthread/openthread/output/[JN5189 & K32w061]/bin/ot-rcp.bin )

Nov 30 14:18:04 a3b77834369d otbr-agent[215]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0
Nov 30 14:18:04 a3b77834369d otbr-agent[215]: 49d.17:56:00.381 [INFO]-PLAT----: RCP reset: RESET_SOFTWARE
Nov 30 14:18:04 a3b77834369d otbr-agent[215]: 49d.17:56:00.445 [NOTE]-PLAT----: RCP API Version: 1
Nov 30 14:18:04 a3b77834369d otbr-agent[215]: 49d.17:56:00.445 [CRIT]-PLAT----: RCP API Version 1 is not in the supported range [4-5]
Nov 30 14:18:04 a3b77834369d otbr-agent[215]: 49d.17:56:00.445 [CRIT]-PLAT----: CheckRcpApiVersion() at ../../third_party/openthread/repo/src/lib/spinel/radio_spinel_impl.hpp:413: RadioSpinelIncompatible

So I would like to have a ot-rcp.bin (preferably build with the IDE) that works with the current official docker image (OT 1.2 only) on a Raspberry Pi4.

The ancient Ubuntu 18.04 based docker image that is referenced in the manual, is not usable.

So any help is appreciated to have an up-to-date functional ot-rcp solution.

If you need any logs, just tell me which command to execute.

Jan K

[Ciberguardian]

hi @mario_castaneda,

any hints on how I can move forward ?

Jan K

[mario_castaneda]

Hi @Ciberguardian,

We are working on trying to update this version, but I can not warranty a release day for this update.

However, you could look at the points that we did for supporting this.

-Added full iptables kernel-support such that the IP-packets can be NAT’ed between the Thread
interface and the Ethernet interfaces;
-Installed the packets required by https://github.com/openthread/ot-br-posix.

Regards,

Mario

[Ciberguardian]

Can you share any updates on this ?

I am starting to investigate the Nordic dongles, because they seem to be more eager to support ot-rcp. Maybe I should not investigate you nxp solution because there is no assistance to build a (secure) backend.

Hope to get some positive news from you soon.

Jan K

[mario_castaneda]

Hi Jan,

Please look at the next community post.

https://community.nxp.com/t5/Wireless-Connectivity-Knowledge/OpenThread-Udoo-Neo-K32W-JN5189-Border-...

Please let me know if you have any other questions.

Regards,

Mario

[Ciberguardian]

I already investigated hte UDOO approach, but the image of the UDOO implementation is more than 2 years old and very out dated. Also the hardware is outdated and proprietary.

Where is the difficulty for NXP to provide an SDK that allows to correctly recompile a usable ot-rcp? For the FTD, MTD this seems no issue.

Openthread Border Router 1.2 provides lots of required functionality for today's cyber security posture.

So, what needs to be done to get a OTBR 1.2 compatible ot-rcp.bin file?

Jan K