• State Verified Answer
  • Replies 5 replies
  • Subscribers 75 subscribers
  • Views 1880 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 300672
Options

Installing OTBR manually (Raspberry Pi) instructions fail

jahess

In

    https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.2.0/nrf/ug_thread_tools.html#installing-otbr-manually-raspberry-pi

bulding the "compatible" version 0895ad5 with:

INFRA_IF_NAME=eth0 ./script/setup

fails with:

+ sudo systemctl enable otbr-firewall
otbr-firewall.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable otbr-firewall
+ sudo systemctl start otbr-firewall
Job for otbr-firewall.service failed because the control process exited with error code.
See "systemctl status otbr-firewall.service" and "journalctl -xe" for details.
+ die 'Failed to start firewall service!'
+ echo ' *** ERROR:  Failed to start firewall service!'
 *** ERROR:  Failed to start firewall service!
+ exit 1

Since 0895ad5 was explicitly suggested in the nordic link above, what now?

For more background, see:

https://github.com/openthread/ot-br-posix/issues/1687

 
Parents Reply
  • +1 in reply to AHaug

    I've been using Pi 3 with the old raspios image specified in the OT codelab.  With some reboots... I think it is working now.

    Biggest problem as I see it is examples asking for specific versions of different operating systems -- OTBR will work only with  old raspio, and chip-tool will only work with ubuntu running on a rasperrypi 64 bit.

    Still working on getting the OTBR to work with matter.

Children
  • 0 in reply to jahess

    Hi,

    jahess said:
    I've been using Pi 3 with the old raspios image specified in the OT codelab.

    We're still not seeing any issues with RPi v3 and/or v4 with either  the master branch (git clone github.com/.../ot-br-posix.git --depth 1 ) or the verified and tested branch mentioned in the Open Thread OTBR guide (git checkout 0895ad5). 8095ad5 is the one we've tested the OTBR up against with our samples, which is why this is mentioned in the documentation. 

    jahess said:
    Still working on getting the OTBR to work with matter.

    If you're still working on getting the OTBR to work with Matter and if you've not already seen this resource, I suggest you have a look at https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_matter_gs_testing_thread_one_otbr.html. If you've already seen it, feel free to ask questions that might lead you to getting everything up and running

    jahess said:
    OTBR will work only with  old raspio, and chip-tool will only work with ubuntu running on a rasperrypi 64 bit.

    Some of the requirements according to the above mentioned guide is

    One of the following:

    • 1x PC with Ubuntu (20.04 or newer)
    • 1x Raspberry Pi Model 3B+ or newer with Ubuntu (20.04 or newer) instead of Raspbian OS

    So you will have to use Ubuntu 20.04 or newer to get it to work with chip tool.

    Let me know you have additional questions related to this case or if we can close this case

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Thank you for the additional link.

    The build finishes and status of system daemons appear acceptable.  After a while CHIP actions result in errors with a brtr-3.  I've no idea where the -3 is coming from -- the pi running OTBR has a name of brtr.  In OpenThread sites, I've not yet stumbled opon useful howto's of how to debug issues with OTBR, SRP, diagnose network issues, and etc.  IE, what to do and what to check when the build "recipes" appear to work but the result doesn't.

    Thank you for re-verifying.  I will suggest a reply as an answer and accept.

Related
Terms of service