OpenThread Border Router for matter: RCP API Version out of supported range using NRF52480 USB dongle

I'm trying to evaluate Matter network for the first time. I'm using the following:

  • 1x Laptop with Ubuntu 20.04 with OTBR using Docker installed by following step by step the guide: Matter over Thread: Configuring Border Router and controller on one device .
  • 1x NRF52840 USB dongle flashed Thread: Co-processor sample, and configured with overlay-usb.conf and usb.overlay from NRF Connect v2.3.0. The Co-processor is configured successfully using the step2 in the guide.
  • 1x NRF52840 DK flashed with Matter Door lock sample from NRF Connect v2.3.0.

When I run the docker image using the following command I get the following log regarding the RCP API version:

May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: New relevant interface eth0.IPv4 for mDNS.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: New relevant interface lo.IPv6 for mDNS.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: New relevant interface lo.IPv4 for mDNS.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: Network interface enumeration completed.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: Registering new address record for fd11:db8:1::2 on eth0.*.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: Registering new address record for 172.18.0.2 on eth0.IPv4.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: Registering new address record for ::1 on lo.*.
May  4 15:02:41 79ba6d31de40 avahi-daemon[185]: Registering new address record for 127.0.0.1 on lo.IPv4.
May  4 15:02:42 79ba6d31de40 rsyslogd: rsyslogd's groupid changed to 101
May  4 15:02:42 79ba6d31de40 rsyslogd: rsyslogd's userid changed to 101
May  4 15:02:42 79ba6d31de40 rsyslogd:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="118" x-info="http://www.rsyslog.com"] start
May  4 15:02:42 79ba6d31de40 avahi-daemon[185]: Server startup complete. Host name is 79ba6d31de40.local. Local service cookie is 3973522570.
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: [NOTE]-AGENT---: Running 0.3.0-1813352247
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: [NOTE]-AGENT---: Thread version: 1.3.0
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: [NOTE]-AGENT---: Thread interface: wpan0
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: [NOTE]-AGENT---: Backbone interface: eth0
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/radio?uart-baudrate=1000000
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: [INFO]-NCP-----: OpenThread log level changed to 5
May  4 15:02:43 79ba6d31de40 otbr-web[241]: [INFO]-WEB-----: Running 0.3.0-1813352247
May  4 15:02:43 79ba6d31de40 otbr-web[241]: [INFO]-WEB-----: Border router web started on wpan0
May  4 15:02:43 79ba6d31de40 otbr-web[241]: [ERR ]-WEB-----: OpenThread daemon is not running.
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: 49d.17:34:36.163 [I] Platform------: RCP reset: RESET_POWER_ON
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: 49d.17:34:36.163 [I] Platform------: RCP reset: RESET_POWER_ON
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: 49d.17:34:36.166 [N] Platform------: RCP API Version: 8
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: 49d.17:34:36.167 [C] Platform------: RCP API Version 8 is not in the supported range [4-6]
May  4 15:02:43 79ba6d31de40 otbr-agent[213]: 49d.17:34:36.167 [C] Platform------: CheckRcpApiVersion() at radio_spinel_impl.hpp:422: RadioSpinelIncompatible

 

How I can change the RCP API version? Should I downgrade the NRF Connect SDK version for the CO-Processor sample and flash the USB dongle again? Or should I do a change for the docker image?

Parents
  • Hello,

    It seems like the RXP version is too high for your border router. Try to flash the dongle with the same sample from an earlier SDK version. Alternatively, you can try the NCP (which was removed in one of the later NCS versions. 

    Since you already have the border router up and running, I believe it would be a relatively quick check. 

    Best regards,

    Edvin

Reply
  • Hello,

    It seems like the RXP version is too high for your border router. Try to flash the dongle with the same sample from an earlier SDK version. Alternatively, you can try the NCP (which was removed in one of the later NCS versions. 

    Since you already have the border router up and running, I believe it would be a relatively quick check. 

    Best regards,

    Edvin

Children
Related