• State Not Answered
  • Replies 5 replies
  • Subscribers 87 subscribers
  • Views 270 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 357209
Options

openthread coprocessor sample from sdk v3.2.1 doesn't work for me with openthread border router

Jan_Erik

The openthread coprocessor sample in sdk v2.8.0 and v3.1.0 work for me with the openthread border router but not the sample in sdk v3.2.1

I followed the instructions for buiding the openthread border router and the coprocessor as described here:  https://docs.nordicsemi.com/bundle/ncs-3.2.1/page/nrf/protocols/thread/tools.html

~/src/ot-br-posix$ git branch
* (HEAD detached at fbde28a0)
  main
  
otbr-agent --version
0.3.0-thread-reference-20230710-394-gfbde28a0

When trying to run the openthread border router with the coprocessor built with sdk v3.2.1  I get the following:

systemctl status otbr-agent
● otbr-agent.service - LSB: thread border agent
     Loaded: loaded (/etc/init.d/otbr-agent; generated)
    Drop-In: /run/systemd/system/service.d
             └─zzz-lxc-service.conf
     Active: active (running) since Wed 2026-02-11 21:49:36 UTC; 26s ago
 Invocation: ad8db29b4ee2431d92a5f5ef84622c67
       Docs: man:systemd-sysv-generator(8)
    Process: 359 ExecStart=/etc/init.d/otbr-agent start (code=exited, status=0/SUCCESS)
      Tasks: 1 (limit: 19037)
     Memory: 776K (peak: 1.9M)
        CPU: 23ms
     CGroup: /system.slice/otbr-agent.service
             └─365 /usr/sbin/otbr-agent -I wpan0 -B eth0 "spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000" trel://eth0

Feb 11 21:49:36 otbr otbr-agent[365]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000
Feb 11 21:49:36 otbr otbr-agent[365]: [NOTE]-AGENT---: Radio URL: trel://eth0
Feb 11 21:49:36 otbr otbr-agent[365]: [NOTE]-ILS-----: Infra link selected: eth0
Feb 11 21:49:36 otbr otbr-agent[365]: [INFO]-RCP_HOS-: OpenThread log level changed to 4
Feb 11 21:49:49 otbr otbr-agent[365]: 49d.17:36:28.060 [W] P-SpinelDrive-: Wait for response timeout
Feb 11 21:49:49 otbr otbr-agent[365]: 49d.17:36:28.060 [I] P-SpinelDrive-: co-processor self reset successfully
Feb 11 21:49:51 otbr otbr-agent[365]: 49d.17:36:30.062 [W] P-SpinelDrive-: Wait for response timeout
Feb 11 21:49:53 otbr otbr-agent[365]: 49d.17:36:32.065 [W] P-SpinelDrive-: Wait for response timeout
Feb 11 21:49:53 otbr otbr-agent[365]: 49d.17:36:32.065 [C] Platform------: Init() at spinel_driver.cpp:82: Failure
Feb 11 21:49:55 otbr otbr-agent[365]: 49d.17:36:34.067 [W] P-SpinelDrive-: Wait for response timeout


Running the same deployment of the border router with a coprocessor built with sdk v2.8.0 works fine:

systemctl status otbr-agent
● otbr-agent.service - LSB: thread border agent
     Loaded: loaded (/etc/init.d/otbr-agent; generated)
    Drop-In: /run/systemd/system/service.d
             └─zzz-lxc-service.conf
     Active: active (running) since Wed 2026-02-11 21:54:37 UTC; 6s ago
 Invocation: e0a3f2992eb749b6ba02affa242c2b47
       Docs: man:systemd-sysv-generator(8)
    Process: 393 ExecStart=/etc/init.d/otbr-agent start (code=exited, status=0/SUCCESS)
      Tasks: 1 (limit: 19037)
     Memory: 1M (peak: 2.1M)
        CPU: 48ms
     CGroup: /system.slice/otbr-agent.service
             └─399 /usr/sbin/otbr-agent -I wpan0 -B eth0 "spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000" trel://eth0

Feb 11 21:54:38 otbr otbr-agent[399]: 00:00:00.680 [I] P-Netif-------: ADD [M] ff03::fc (already subscribed, ignored)
Feb 11 21:54:38 otbr otbr-agent[399]: 00:00:00.680 [I] P-Netif-------: ADD [M] ff03::1 (already subscribed, ignored)
Feb 11 21:54:38 otbr otbr-agent[399]: 00:00:00.680 [I] P-Netif-------: ADD [M] ff02::16 (already subscribed, ignored)
Feb 11 21:54:38 otbr otbr-agent[399]: 00:00:00.680 [I] P-Netif-------: ADD [M] ff02::2 (rejected)
Feb 11 21:54:38 otbr otbr-agent[399]: [INFO]-MDNS----: Successfully registered service OpenThread BorderRouter #26D8._meshcop._udp
Feb 11 21:54:38 otbr otbr-agent[399]: [INFO]-BA------: Result of publish meshcop service OpenThread BorderRouter #26D8._meshcop._udp.l>
Feb 11 21:54:42 otbr otbr-agent[399]: 00:00:04.720 [I] Mle-----------: Send Link Request (ff02:0:0:0:0:0:0:2)
Feb 11 21:54:42 otbr otbr-agent[399]: 00:00:04.727 [I] MeshForwarder-: Sent IPv6 UDP msg, len:82, chksum:ef27, ecn:no, to:0xffff, sec:>
Feb 11 21:54:42 otbr otbr-agent[399]: 00:00:04.727 [I] MeshForwarder-:     src:[fe80:0:0:0:bc00:b575:1961:26d8]:19788
Feb 11 21:54:42 otbr otbr-agent[399]: 00:00:04.727 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788


Please advise.

Thanks,
Jan Erik

Parents
  • 0

    I just want to let everybody know that I ran into exactly the same issue.

    I wanted to rebuild my OpenThread border router setup using a Raspberry Pi 3B and a nRF52840 USB Dongle.

    I went directly for the OpenThread coprocessor sample from v3.2.1, but this failed in the way described here.

    I googled for the problem and came to this ticket. I switched to the OpenThread coprocessor sample from v3.1.0 and it worked out-of-the-box.

    Regards!

Reply
  • 0

    I just want to let everybody know that I ran into exactly the same issue.

    I wanted to rebuild my OpenThread border router setup using a Raspberry Pi 3B and a nRF52840 USB Dongle.

    I went directly for the OpenThread coprocessor sample from v3.2.1, but this failed in the way described here.

    I googled for the problem and came to this ticket. I switched to the OpenThread coprocessor sample from v3.1.0 and it worked out-of-the-box.

    Regards!

Children
No Data
Related
Terms of service