LAUNCHXL-CC26X2R1: Border router beagle bone black otbr-agent service is crash

Durgaprasad kolluri

Hello Team,

Recently we trying to setup thread network with following link for border router configurations link: https://dev.ti.com/tirex/explore/node?node=ABSaAO-k3rswvnB7RdRtww__pTTHBmu__LATEST

we followed same steps in the link for installing ot-br-posix in beagle bone black. border router configured & Launch PAD CC26x2R1 board loaded with NCP_FTD program. then connected to beagle bone black using USB as shown in the link.

Form network got failed in the border router website. when i seen error in beagle bone black as shown below.

Sep 26 22:18:58 beaglebone systemd[1]: otbr-agent.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Sep 26 22:18:58 beaglebone systemd[1]: otbr-agent.service: Failed with result 'exit-code'.
Sep 26 22:19:03 beaglebone systemd[1]: otbr-agent.service: Service RestartSec=5s expired, scheduling restart.
Sep 26 22:19:03 beaglebone systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 22.
Sep 26 22:19:03 beaglebone systemd[1]: Stopped Border Router Agent.
Sep 26 22:19:03 beaglebone systemd[1]: Started Border Router Agent.
Sep 26 22:19:03 beaglebone otbr-agent[1947]: [INFO]-UTILS---: Running 0.3.0-f8b317da3-dirty
Sep 26 22:19:03 beaglebone otbr-agent[1947]: [INFO]-UTILS---: Thread version: 1.2.0
Sep 26 22:19:03 beaglebone otbr-agent[1947]: [INFO]-UTILS---: Thread interface: wpan0
Sep 26 22:19:03 beaglebone otbr-agent[1947]: [INFO]-UTILS---: Backbone interface: eth0
Sep 26 22:19:03 beaglebone otbr-agent[1947]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0
Sep 26 22:19:03 beaglebone otbr-agent[1947]: [INFO]-UTILS---: Radio URL: trel://wlan0
Sep 26 22:19:03 beaglebone otbr-agent[1947]: [INFO]-PLAT----: RCP reset: RESET_SOFTWARE
Sep 26 22:19:03 beaglebone otbr-agent[1947]: [CRIT]-PLAT----: Init() at ../../third_party/openthread/repo/src/lib/spinel/radio_spinel_impl.hpp:258: RadioSpinelIncompatible

how we can confirm whether issue in LaunchXL--cc26x2R1 or beagle bone black issue. we had checked the interface under /dev/ttyACM0 presents. i didnt get any kind of solution in the online search. am new to this setup. kindly suggest me any solution. it will be helpful.

Thanks & regards,

K. durgaprasad.

over 4 years ago

0 Toby over 4 years ago

TI__Mastermind 35070 points

Hi,

Which commit of ot-br-posix are you using?

Have you tried using the recommended git tag?
In the ot-br-posix directory, run:
git checkout thread-br-certified-20180819

Then proceed, starting from the "Build the border router".

Thanks,
Toby

0 Durgaprasad kolluri over 4 years ago in reply to Toby

Prodigy 40 points

Thank you for the info. i used "thread-br-certified-20180819". Issue was resolved. But i have other problem with thread commissioning app. its taking too long connecting to border router with commission App & password entry. Then Password authentication failed even correct password entered.

0 Toby over 4 years ago in reply to Durgaprasad kolluri

TI__Mastermind 35070 points

Thanks for the update, glad to hear your initial issue is resolved.

For your question on commissioning app, it looks like others have run into similar issues:

https://groups.google.com/g/openthread-users/c/sORdo2594aY/m/Kj0kAxipBgAJ

If you would like to use this app specifically, I recommend asking about it in that google group for openthread.

If you need to bring a device onto the network, try running the commissioner directly on the otbr.

For example, to join empty_ftd example to border router network:

on otbr: sudo wpanctl commissioner start
on otbr: sudo wpanctl commissioner joiner-add <eui64> <timeout sec> <psk>
1. eui64 : use what is shown in serial output of the empty_ftd (e.g. Device Info: [EUI64] 0x00124b000f6e6113)
2. timeout: how long to keep this entry on commissioner. 60 sec should be reasonable
3. psk: use what is shown in serial output of the empty_ftd (e.g. [PSKD] PPSSKK)
4. example of final command: sudo wpanctl commissioner joiner-add 00124b000f6e6113 60 PPSSKK
on empty_ftd: press BTN-2 to start joining

0 Durgaprasad kolluri over 4 years ago in reply to Toby

Prodigy 40 points

Thank you Toby pan for your example to connect & form the thread network.

I could able to join the door lock launchpad example to border router. How can we get & set the lock state from border router or from outside network.

Is there any example. Please provide the info.

Thanks & regards,

K. durgaprasad.

0 Toby over 4 years ago in reply to Durgaprasad kolluri

TI__Mastermind 35070 points

As a place to start, please see the "Interfacing with the Door Lock Application" here: https://dev.ti.com/tirex/explore/node?node=AHVwxNPTZ.K-PUwEaN8rHA__pTTHBmu__LATEST

This is for interacting with door_lock with cli_ftd. Same principle would apply for outside the network, you need a CoAP client to interact with the CoAP server which runs on door_lock.

Also, search "firefox" on https://dev.ti.com/tirex/explore/node?node=ABSaAO-k3rswvnB7RdRtww__pTTHBmu__LATEST.
That might be what you are looking for.

Zigbee & Thread

Zigbee & Thread forum

LAUNCHXL-CC26X2R1: Border router beagle bone black otbr-agent service is crash