This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2652R7: OpenThread Border Router (ot-br-posix) fails to build on BeagleBoneBlack-RevC

Part Number: CC2652R7
Other Parts Discussed in Thread: CC2652RB,

Summary:
I get a error while attempting to build the OpenThread Border Router (branch thread-br-certified-20180819). Any tips on how to proceed? Thank you in advance!

Details:
I have a new BeagleBoneBlack-RevC (bbb) board that I am booting Debian 10.3 from an 8GB SDCard. The bbb is connected to Ethernet, and connect to the wall power supply. I have ssh’ed in from my LapTop to issue the following commands.

$ sudo /opt/scripts/tools/grow_partition.sh    [Once, after booting 1st time from SDCard]
$ sudo shutdown -r now
$ sudo update-initramfs -u   [Once, after 1st boot following grow_partition.sh operation]
$ sudo shutdown -r now

$ cat /etc/debian_version
10.3
$ echo $SHELL
/bin/bash
$ pwd
/home/debian
$ git clone --depth 1 --branch thread-br-certified-20180819 github.com/.../ot-br-posix.git

$ cd ot-br-posix
$ ./script/bootstrap 2>&1 | tee ot_bootstrap.log         [This succeeds]
$ sudo shutdown -r now

$ INFRA_IF_NAME=eth0 ./script/setup 2>&1 | tee ot_setup.log     [This fails, see below…]
$ tail -15 ot_setup.log
Making all in common
make[3]: Nothing to be done for 'all'.
Making all in utils
make[3]: Nothing to be done for 'all'.
Making all in agent
  CXX      libotbr_agent_la-ncp_wpantund.lo
ncp_wpantund.cpp: In constructor ‘ot::BorderRouter::Ncp::ControllerWpantund::ControllerWpantund(const char*)’:
ncp_wpantund.cpp:238:12: error: ‘char* strncpy(char*, const char*, size_t)’ specified bound 16 equals destination size [-Werror=stringop-truncation]
     strncpy(mInterfaceName, aInterfaceName, sizeof(mInterfaceName));
     ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
make[3]: *** [Makefile:716: libotbr_agent_la-ncp_wpantund.lo] Error 1
make[2]: *** [Makefile:444: all-recursive] Error 1
make[1]: *** [Makefile:570: all-recursive] Error 1
make: *** [Makefile:496: all] Error 2

Thanks in advance,

Steve K.

  • Thank you Toby. Still not quite right. As recommended in the post you referred me too — in order to resolve the 1st compile error — I changed ./src/agent/ncp_wpantund.cpp line 238.
     …this line…
         strncpy(mInterfaceName, aInterfaceName, sizeof(mInterfaceName));
     …changed to this instead…
         strncpy(mInterfaceName, aInterfaceName, sizeof(mInterfaceName)-1); /* note the “-1” */

    But that just got me a bit further and I hit a similar compile error in another file (./src/agent/mdns_avahi.cpp line 571 and line 572). I made the “-1” edit to each of those offending lines. But I don’t have confidence that the ot-br-posix tree was built correctly as it finished up with this:

    $ INFRA_IF_NAME=eth0 ./script/setup 2>&1 | tee setup.log
    $ tail -10 setup.log
    make[3]: Nothing to be done for 'install-exec-am'.
    make[3]: Nothing to be done for 'install-data-am'.
    Making install in tools
    make[3]: Nothing to be done for 'install-exec-am'.
    make[3]: Nothing to be done for 'install-data-am'.
    make[3]: Nothing to be done for 'install-exec-am'.
    Failed to enable unit: File /etc/systemd/system/wpantund.service already exists.
    enabled
    enabled
    enabled

    And attempting the following commands on the BeagleBoneBlack gives suspicious results. These command for example:

    $ sudo ot-ctl state
    sudo: ot-ctl: command not found

    $ sudo service mdns status
    Unit mdns.service could not be found.

    $ sudo service otbr-agent status
    ● otbr-agent.service - Border Router Agent
       Loaded: loaded (/etc/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
       Active: inactive (dead)
    Jul 07 22:50:18 beaglebone otbr-agent[1898]: lookup_dbus_name_from_interface: error: The name com.nestlabs.WPANTunnelDriver was not provided by any .service
    Jul 07 22:50:18 beaglebone otbr-agent[1898]: otbr-agent[1898]: NCP failed to find the interface!
    Jul 07 22:50:18 beaglebone otbr-agent[1898]: NCP failed to find the interface!
    Jul 07 22:50:18 beaglebone otbr-agent[1898]: otbr-agent[1898]: NCP failed to initialize!
    Jul 07 22:50:18 beaglebone otbr-agent[1898]: otbr-agent[1898]: Failed to create border route agent instance: -1!
    Jul 07 22:50:18 beaglebone otbr-agent[1898]: NCP failed to initialize!
    Jul 07 22:50:18 beaglebone otbr-agent[1898]: Failed to create border route agent instance: -1!
    Jul 07 22:50:19 beaglebone systemd[1]: otbr-agent.service: Main process exited, code=exited, status=1/FAILURE
    Jul 07 22:50:19 beaglebone systemd[1]: otbr-agent.service: Failed with result 'exit-code'.
    Jul 07 22:50:21 beaglebone systemd[1]: Stopped Border Router Agent.

    $ sudo service otbr-web status
    ● otbr-web.service - Border Router Web
       Loaded: loaded (/etc/systemd/system/otbr-web.service; enabled; vendor preset: enabled)
       Active: inactive (dead)
    Jul 07 22:47:00 beaglebone otbr-web[850]: otWeb[850]: destination is NULL; error: (null)
    Jul 07 22:47:00 beaglebone otbr-web[850]: otWeb[850]: message is NULL
    Jul 07 22:47:00 beaglebone otWeb[850]: reply is NULL; error: The name com.nestlabs.WPANTunnelDriver was not provided by any .service files
    Jul 07 22:47:00 beaglebone otWeb[850]: reply error: The name com.nestlabs.WPANTunnelDriver was not provided by any .service files
    Jul 07 22:47:00 beaglebone otWeb[850]: destination is NULL; error: (null)
    Jul 07 22:47:00 beaglebone otWeb[850]: message is NULL
    Jul 07 22:50:21 beaglebone systemd[1]: Stopping Border Router Web...
    Jul 07 22:50:21 beaglebone systemd[1]: otbr-web.service: Main process exited, code=killed, status=15/TERM
    Jul 07 22:50:21 beaglebone systemd[1]: otbr-web.service: Succeeded.
    Jul 07 22:50:21 beaglebone systemd[1]: Stopped Border Router Web.

    Uggggg, I could really use some more help. I've got a lot of time already wrapped up in my attempts to build the OpenThread Border Router for the BeagleBoneBlack-RevC; and I'm still not there. I get the impression that the online recipe may have gone stale in recent years and may be due for an update. Thoughts?

    Regards,

    Steve K.

  • Try to remove -Werror parameter in Makefile to build again.

  • Hi YiKai, I notice there are a few Makefiles. But maybe it's just the ./src/agent/Makefile I should edit. I'll try it.

    $ pwd
    /home/debian/ot-br-posix

    $ find . -name "Makefile" -exec grep -l -i -e "-Werror" {} \;

    ./Makefile
    ./tools/Makefile
    ./._build/wpantund/third_party/pt/Makefile
    ./doc/Makefile
    ./include/Makefile
    ./tests/unit/Makefile
    ./tests/meshcop/Makefile
    ./tests/Makefile
    ./tests/mdns/Makefile
    ./src/Makefile
    ./src/common/Makefile
    ./src/agent/Makefile         <--- the pertinent one ??? Will try...
    ./src/web/Makefile
    ./src/utils/Makefile
    ./third_party/angular-material/Makefile
    ./third_party/mbedtls/Makefile
    ./third_party/angular/Makefile
    ./third_party/libcoap/Makefile
    ./third_party/wpantund/Makefile
    ./third_party/Makefile
    ./third_party/Simple-web-server/Makefile
    ./third_party/mdl/Makefile

  • Are you talking about this online guide? https://dev.ti.com/tirex/explore/node?node=AP0oXq54dgMJ4g-gwa3-rw__BSEc4rl__LATEST

    We plan to update this in next few weeks, since we will have RCP in the 6.20 SDK.

    Do you have a CC2652R1 launchpad?
    If yes, I'd recommend following the guide here, specifically for the "Thread Border Router" (you can ignore the other components): https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1082428/faq-cc2652r7-matter----getting-started-guide 

  • Hi YiKai and Toby, I did remove the -Werror from the ./src/agent/Makefile and it did allow the build to complete without first editing the two source files, yet I get the same suspicious results as I posted earlier. And “Yes”, I do have a two CC2652RB LaunchPads and one CC2652R1 LaunchPad, but not the CC2652R7 you asked about. I will assume that I can attempt your suggestion with one of the LaunchPads I do have. If that is a bad idea please let me know.

    Thanks!

    Steve K.

  • Do you still have questions?

  • Hi YiKai, I am still trying to get a working OTBR but will try the latest suggestion from Toby to use the https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1082428/faq-cc2652r7-matter----getting-started-guide

    I'll reply back with how that goes as so far I've been following the directions (without success) from the following two guides:

    https://openthread.io/codelabs/openthread-border-router#1
    https://dev.ti.com/tirex/explore/node?node=AP0oXq54dgMJ4g-gwa3-rw__BSEc4rl__LATEST 

    Regards,

    Steve K.

  • OK. Let us know if you still have issues.

  • Summary:

    Toby and YiKai, the new OTBR instructions that you [Toby] pointed me at make reference to an attached “rcp_CC26X2R1_LAUNCHXL_tirtos_ticlang.out” and that link does not resolve. Also, as it turns out I don’t have a CC2652R1, but rather I have CC2652RB and CC2652R7 LaunchPads. Nevertheless, I was able to switch to the [newly] recommended OTBR git version and do a build that showed some progress. However as you can see in the details below it looks like I’m running into an incompatibility with the NCP I have attached to the BeagleBoneBlack. It is a CC2652RB Launchpad running a NCP I built from the TI simplelink_cc13xx_cc26xx_sdk_5_40_00_40. I suspect the [newly] recommended OTBR (and that I just built) might need a different version of NCP (or possibly an RCP). Can you look below an let me know if there is a “next steps” you could suggest? Thanks in advance.

    Details:

    I confirmed that I am using the recommended Linux version:
    Linux Version:
    bone-debian-10.3-iot-armhf-2020-04-06-4gb.img

    I switched over to the [newly] recommended OTBR git version:
    $ cd $HOME
    $ rm -rf ot-br-posix
    $ git checkout 84b7b2fda3005a6b8eb83262884ecf78d2a82b21
    $ ./script/bootstrap 2>&1 | tee bootstrap.log
    $ INFRA_IF_NAME=eth0 ./script/setup 2>&1 | tee setup.log

    $ sudo shutdown -r now

    $ which ot-ctl
    /usr/sbin/ot-ctl

    $ sudo ot-ctl state
    connect session failed: No such file or directory

    $ sudo service mdns status
    ● mdns.service
       Loaded: loaded (/etc/init.d/mdns; generated)
       Active: active (running) since Fri 2022-07-08 02:47:03 UTC; 51s ago
         Docs: man:systemd-sysv-generator(8)
      Process: 1129 ExecStart=/etc/init.d/mdns start (code=exited, status=0/SUCCESS)
        Tasks: 1 (limit: 1026)
       Memory: 832.0K
       CGroup: /system.slice/mdns.service
               └─1131 /usr/sbin/mdnsd
    Jul 08 02:47:03 beaglebone systemd[1]: Starting mdns.service...
    Jul 08 02:47:03 beaglebone mdns[1129]: Starting Apple Darwin Multicast DNS / DNS Service Discovery daemon: mdnsd.
    Jul 08 02:47:03 beaglebone mDNSResponder[1131]: mDNSResponder (Engineering Build) (Jul  8 2022 01:56:02) starting
    Jul 08 02:47:03 beaglebone systemd[1]: Started mdns.service.
    Jul 08 02:47:03 beaglebone mDNSResponder[1131]: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)

    $ sudo service otbr-web status
    ● otbr-web.service - Border Router Web
       Loaded: loaded (/etc/systemd/system/otbr-web.service; enabled; vendor preset: enabled)
       Active: active (running) since Fri 2022-07-08 02:46:55 UTC; 1min 8s ago
     Main PID: 915 (otbr-web)
        Tasks: 1 (limit: 1026)
       Memory: 1.0M
       CGroup: /system.slice/otbr-web.service
               └─915 /usr/sbin/otbr-web
    Jul 08 02:46:55 beaglebone systemd[1]: Started Border Router Web.
    Jul 08 02:46:56 beaglebone otbr-web[915]: otbr-web[915]: [INFO]-WEB-----: Running 0.3.0-84b7b2fda3
    Jul 08 02:46:56 beaglebone otbr-web[915]: otbr-web[915]: [INFO]-WEB-----: Border router web started on wpan0
    Jul 08 02:46:56 beaglebone otbr-web[915]: otbr-web[915]: [ERR ]-WEB-----: OpenThread daemon is not running.
    Jul 08 02:46:56 beaglebone otbr-web[915]: [INFO]-WEB-----: Running 0.3.0-84b7b2fda3
    Jul 08 02:46:56 beaglebone otbr-web[915]: [INFO]-WEB-----: Border router web started on wpan0
    Jul 08 02:46:56 beaglebone otbr-web[915]: [ERR ]-WEB-----: OpenThread daemon is not running.

    $ sudo service otbr-agent status
    ● otbr-agent.service - Border Router Agent
       Loaded: loaded (/etc/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
       Active: activating (auto-restart) (Result: exit-code) since Fri 2022-07-08 02:48:11 UTC; 4s ago
      Process: 1801 ExecStart=/usr/sbin/otbr-agent $OTBR_AGENT_OPTS (code=exited, status=6)
     Main PID: 1801 (code=exited, status=6)
    debian@beaglebone:~$

    $ tail -15 /var/log/syslog
    Jul  8 03:00:14 beaglebone otbr-agent[1923]: [INFO]-UTILS---: Running 0.3.0-84b7b2fda3
    Jul  8 03:00:14 beaglebone otbr-agent[1923]: [INFO]-UTILS---: Thread version: 1.2.0
    Jul  8 03:00:14 beaglebone otbr-agent[1923]: [INFO]-UTILS---: Thread interface: wpan0
    Jul  8 03:00:14 beaglebone otbr-agent[1923]: [INFO]-UTILS---: Backbone interface: eth0
    Jul  8 03:00:14 beaglebone otbr-agent[1923]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0
    Jul  8 03:00:14 beaglebone otbr-agent[1923]: [INFO]-UTILS---: Radio URL: trel://eth0
    Jul  8 03:00:14 beaglebone wpantund[1516]: wpantund[1516]: [-NCP-]: NCP was reset (RESET_SOFTWARE, 114)
    Jul  8 03:00:14 beaglebone wpantund[1516]: wpantund[1516]: State change: "offline" -> "uninitialized"
    Jul  8 03:00:14 beaglebone wpantund[1516]: [-NCP-]: NCP was reset (RESET_SOFTWARE, 114)
    Jul  8 03:00:14 beaglebone wpantund[1516]: State change: "offline" -> "uninitialized"
    Jul  8 03:00:14 beaglebone otbr-agent[1923]: 49d.17:16:28.988 [W] Platform------: Unexpected Spinel transaction message: 2
    Jul  8 03:00:14 beaglebone otbr-agent[1923]: 49d.17:16:28.988 [W] Platform------: Error processing response: Drop
    Jul  8 03:00:16 beaglebone otbr-agent[1923]: 49d.17:16:30.789 [C] Platform------: BSD TCP function() at radio_spinel_impl.hpp:2226: RadioSpinelNoResponse
    Jul  8 03:00:16 beaglebone systemd[1]: otbr-agent.service: Main process exited, code=exited, status=6/NOTCONFIGURED
    Jul  8 03:00:16 beaglebone systemd[1]: otbr-agent.service: Failed with result 'exit-code'.

    Regards,

    Steve K.

  • Right, for this border router build, we need to use RCP.

    Good to know you have CC2652RB, I had shared an RCP image for this here: https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1102043/lp-cc2652rb-openthread-rcp-firmware-needed/4083971#4083971

  • Hi Toby,

    I sure appreciate the quick responses. Yes, I flashed the CC2652RB *.out you provided and I do indeed get different results; but probably still not quite right. I just rebooted the BeagleBoneBlack installed with the git version 84b7b2fda3005a6b8eb83262884ecf78d2a82b21 of OTBR (on Linux bone-debian-10.3-iot-armhf-2020-04-06-4gb.img ) with the RCP CC2652RB, and I get the following new results. Does this trigger anything for you? I think we are getting closer. Thanks again.

    $ sudo shutdown -r now

    $ which ot-ctl
    /usr/sbin/ot-ctl

    $ sudo ot-ctl state
    connect session failed: No such file or directory

    $ tail -15 /var/log/syslog
    Jul  8 03:46:30 beaglebone systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 11.
    Jul  8 03:46:30 beaglebone systemd[1]: Stopped Border Router Agent.
    Jul  8 03:46:30 beaglebone systemd[1]: Started Border Router Agent.
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: [INFO]-UTILS---: Running 0.3.0-84b7b2fda3
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: [INFO]-UTILS---: Thread version: 1.2.0
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: [INFO]-UTILS---: Thread interface: wpan0
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: [INFO]-UTILS---: Backbone interface: eth0
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: [INFO]-UTILS---: Radio URL: trel://eth0
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: 49d.17:04:11.076 [I] Platform------: RCP reset: RESET_POWER_ON
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: 49d.17:04:11.094 [N] Platform------: RCP API Version: 5
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: 49d.17:04:11.098 [I] Platform------: Backbone interface is configured to eth0 (4)
    Jul  8 03:46:30 beaglebone otbr-agent[1787]: 49d.17:04:11.099 [C] Platform------: platformConfigureTunDevice() at netif.cpp:1463: Device or resource busy
    Jul  8 03:46:30 beaglebone systemd[1]: otbr-agent.service: Main process exited, code=exited, status=5/NOTINSTALLED
    Jul  8 03:46:30 beaglebone systemd[1]: otbr-agent.service: Failed with result 'exit-code'.

    $ sudo ot-ctl reset
    connect session failed: No such file or directory

    $ tail -15 /var/log/syslog
    Jul  8 03:57:36 beaglebone systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 138.
    Jul  8 03:57:36 beaglebone systemd[1]: Stopped Border Router Agent.
    Jul  8 03:57:36 beaglebone systemd[1]: Started Border Router Agent.
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: [INFO]-UTILS---: Running 0.3.0-84b7b2fda3
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: [INFO]-UTILS---: Thread version: 1.2.0
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: [INFO]-UTILS---: Thread interface: wpan0
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: [INFO]-UTILS---: Backbone interface: eth0
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: [INFO]-UTILS---: Radio URL: trel://eth0
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: 49d.17:15:17.826 [I] Platform------: RCP reset: RESET_POWER_ON
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: 49d.17:15:17.845 [N] Platform------: RCP API Version: 5
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: 49d.17:15:17.848 [I] Platform------: Backbone interface is configured to eth0 (4)
    Jul  8 03:57:37 beaglebone otbr-agent[1948]: 49d.17:15:17.849 [C] Platform------: platformConfigureTunDevice() at netif.cpp:1463: Device or resource busy
    Jul  8 03:57:37 beaglebone systemd[1]: otbr-agent.service: Main process exited, code=exited, status=5/NOTINSTALLED
    Jul  8 03:57:37 beaglebone systemd[1]: otbr-agent.service: Failed with result 'exit-code'.

    $ sudo service otbr-agent status
    ● otbr-agent.service - Border Router Agent
       Loaded: loaded (/etc/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
       Active: activating (auto-restart) (Result: exit-code) since Fri 2022-07-08 03:53:51 UTC; 2s ago
      Process: 1881 ExecStart=/usr/sbin/otbr-agent $OTBR_AGENT_OPTS (code=exited, status=5)
     Main PID: 1881 (code=exited, status=5)

    $ sudo service otbr-web status
    ● otbr-web.service - Border Router Web
       Loaded: loaded (/etc/systemd/system/otbr-web.service; enabled; vendor preset: enabled)
       Active: active (running) since Fri 2022-07-08 03:45:27 UTC; 8min ago
     Main PID: 905 (otbr-web)
        Tasks: 1 (limit: 1026)
       Memory: 1.0M
       CGroup: /system.slice/otbr-web.service
               └─905 /usr/sbin/otbr-web
    Jul 08 03:45:27 beaglebone systemd[1]: Started Border Router Web.
    Jul 08 03:45:27 beaglebone otbr-web[905]: otbr-web[905]: [INFO]-WEB-----: Running 0.3.0-84b7b2fda3
    Jul 08 03:45:27 beaglebone otbr-web[905]: otbr-web[905]: [INFO]-WEB-----: Border router web started on wpan0
    Jul 08 03:45:27 beaglebone otbr-web[905]: otbr-web[905]: [ERR ]-WEB-----: OpenThread daemon is not running.
    Jul 08 03:45:27 beaglebone otbr-web[905]: [INFO]-WEB-----: Running 0.3.0-84b7b2fda3
    Jul 08 03:45:27 beaglebone otbr-web[905]: [INFO]-WEB-----: Border router web started on wpan0
    Jul 08 03:45:27 beaglebone otbr-web[905]: [ERR ]-WEB-----: OpenThread daemon is not running.

    $ sudo service mdns status
    ● mdns.service
       Loaded: loaded (/etc/init.d/mdns; generated)
       Active: active (running) since Fri 2022-07-08 03:45:35 UTC; 8min ago
         Docs: man:systemd-sysv-generator(8)
      Process: 1122 ExecStart=/etc/init.d/mdns start (code=exited, status=0/SUCCESS)
        Tasks: 1 (limit: 1026)
       Memory: 840.0K
       CGroup: /system.slice/mdns.service
               └─1124 /usr/sbin/mdnsd
    Jul 08 03:45:35 beaglebone systemd[1]: Starting mdns.service...
    Jul 08 03:45:35 beaglebone mdns[1122]: Starting Apple Darwin Multicast DNS / DNS Service Discovery daemon: mdnsd.
    Jul 08 03:45:35 beaglebone mDNSResponder[1124]: mDNSResponder (Engineering Build) (Jul  8 2022 01:56:02) starting
    Jul 08 03:45:35 beaglebone systemd[1]: Started mdns.service.
    Jul 08 03:45:35 beaglebone mDNSResponder[1124]: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)

    Regards,
    Steve K.

  • Thanks for update.

    I'd recommend one of these options:

    1. https://github.com/openthread/ot-br-posix/issues/741
    2. sudo service otbr-agent restart
    3. power cycle the whole system (BBB)
  • Hi Toby,

    Oh my, I think that might have done the trick. The ‘sudo ip link del wpan0’. See details below. Maybe give me a chance to fiddle a bit more today (and attempt to Join some other devices, etc) and then if all looks good I”ll close this as resolved. I think the following looks very encouraging:

    $ sudo shutdown -r now
    $ sudo ip link del wpan0
    $ sudo ot-ctl state
    disabled
    Done

    Browse to the BeageBone OTBR internal Web page and Form a network with all default settings:


    $ sudo ot-ctl state
    leader
    Done

    $ ifconfig (Note that wpan0 now listed after FORMing the OT network)
    eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC>  mtu 1500
            inet 192.168.0.15  netmask 255.255.255.0  broadcast 192.168.0.255
            inet6 ::6633:dbff:fe34:44b7  prefixlen 64  scopeid 0x0<global>
            inet6 fd23:a956:a530:4db9:6633:dbff:fe34:44b7  prefixlen 64  scopeid 0x0<global>
            inet6 fe80::6633:dbff:fe34:44b7  prefixlen 64  scopeid 0x20<link>
            ether 64:33:db:34:44:b7  txqueuelen 1000  (Ethernet)
            RX packets 2989  bytes 328916 (321.2 KiB)
            RX errors 0  dropped 243  overruns 0  frame 0
            TX packets 2968  bytes 2065384 (1.9 MiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
            device interrupt 55  

    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 1000  (Local Loopback)
            RX packets 367  bytes 25669 (25.0 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 367  bytes 25669 (25.0 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    nat64: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
            inet 192.168.255.1  netmask 255.255.255.255  destination 192.168.255.1
            inet6 fe80::5313:e093:57c6:d6c9  prefixlen 64  scopeid 0x20<link>
            inet6 fdaa:bb:1::2  prefixlen 128  scopeid 0x0<global>
            unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 4  bytes 304 (304.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
            inet 192.168.7.2  netmask 255.255.255.0  broadcast 192.168.7.255
            ether 64:33:db:34:44:b9  txqueuelen 1000  (Ethernet)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    usb1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
            inet 192.168.6.2  netmask 255.255.255.0  broadcast 192.168.6.255
            ether 64:33:db:34:44:bd  txqueuelen 1000  (Ethernet)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    wpan0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1280
            inet6 fdcf:63:5fae:4ed1:0:ff:fe00:fc38  prefixlen 64  scopeid 0x0<global>
            inet6 fd11:22::9238:fb81:6a8:b2bd  prefixlen 64  scopeid 0x0<global>
            inet6 fdcf:63:5fae:4ed1:b968:fa17:ae5b:97ab  prefixlen 64  scopeid 0x0<global>
            inet6 fdcf:63:5fae:4ed1:0:ff:fe00:fc10  prefixlen 64  scopeid 0x0<global>
            inet6 fdcf:63:5fae:4ed1:0:ff:fe00:b800  prefixlen 64  scopeid 0x0<global>
            inet6 fdcf:63:5fae:4ed1:0:ff:fe00:fc11  prefixlen 64  scopeid 0x0<global>
            inet6 fdcf:63:5fae:4ed1:0:ff:fe00:fc00  prefixlen 64  scopeid 0x0<global>
            inet6 fe80::dcae:c7ff:f34e:6c47  prefixlen 64  scopeid 0x20<link>
            unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 1  overruns 0  frame 0
            TX packets 8  bytes 1508 (1.4 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    Regards,
    Steve K.

  • This looks good to me too!

    Look forward to hearing your next results.

  • HI Toby and YiKai, well I’m going to close out this e2e forum thread as “resolved”. I sure appreciate all the timely help. This afternoon I was able to use a CC2652R7 running the TI CLI-FTD demo application and I “joined” this device to OpenThread network formed by the OTBR (Border Router) running on my BeagleBoneBlack. I was able to ping between the CLI-FTD and the OTBR. Each has an ipv6 address reachable to the other. Also, I was able to ping the CLI-FTD from my Laptop which resides on the ethernet/wifi side of the border router. This is all very cool. I think I’m at a spot that I can proceed with my product development. Again, thank you.

    Regards,
    Steve K.