Creating Open Thread Network with nRF52840 DK Board as RCP failed

Hi, 

1. otbr-agent service is successfully running on raspberrypi. See below.

● otbr-agent.service - OpenThread Border Router Agent
     Loaded: loaded (/lib/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Tue 2023-01-31 22:58:12 GMT; 3s ago
    Process: 1469 ExecStartPre=service mdns start (code=exited, status=0/SUCCESS)
    Process: 1475 ExecStart=/usr/sbin/otbr-agent $OTBR_AGENT_OPTS (code=exited, status=2)
   Main PID: 1475 (code=exited, status=2)
        CPU: 73ms
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-7/7 (END)


2. RCP Firmware successfully flashed on nRF52840 DK Board. See below:

3. We are not able to figure out next steps from the Documentation. Our objective is to form a Thread Network and run example "Lock" using Android Chiptool.

4. Our RCP Board(nRF52840 DK) is now connected to Raspberrypi and status check is as below: 

pi@raspberrypi:~ $ cd ot-br-posix
pi@raspberrypi:~/ot-br-posix $ sudo service otbr-agent status
● otbr-agent.service - OpenThread Border Router Agent
     Loaded: loaded (/lib/systemd/system/otbr-agent.service; enabled; vendor pr>
     Active: active (running) since Thu 2023-02-02 23:38:43 GMT; 5s ago
    Process: 1462 ExecStartPre=service mdns start (code=exited, status=0/SUCCES>
   Main PID: 1468 (otbr-agent)
      Tasks: 1 (limit: 4915)
        CPU: 72ms
     CGroup: /system.slice/otbr-agent.service
             └─1468 /usr/sbin/otbr-agent -I wpan0 -B eth0 spinel+hdlc+uart:///d>

Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Backbone interfa>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Running 0.3.0-08>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Thread version: >
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Thread interface>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Radio URL: spine>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Radio URL: trel:>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-ILS-----: Infra link selec>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [INFO]-NCP-----: OpenThread log l>
Feb 02 23:38:45 raspberrypi otbr-agent[1468]: 49d.17:06:14.146 [W] Platform---->
Feb 02 23:38:45 raspberrypi otbr-agent[1468]: 49d.17:06:14.146 [C] Platform---->
lines 1-20/20 (END)...skipping...
● otbr-agent.service - OpenThread Border Router Agent
     Loaded: loaded (/lib/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2023-02-02 23:38:43 GMT; 5s ago
    Process: 1462 ExecStartPre=service mdns start (code=exited, status=0/SUCCESS)
   Main PID: 1468 (otbr-agent)
      Tasks: 1 (limit: 4915)
        CPU: 72ms
     CGroup: /system.slice/otbr-agent.service
             └─1468 /usr/sbin/otbr-agent -I wpan0 -B eth0 spinel+hdlc+uart:///dev/ttyACM0 trel://eth0

 

5. I also refer to your webinar of October 15, 2021 https://webinars.nordicsemi.com/developing-matter-products-with-nrf-4. Video duration 21:50 to 23:07

FORM Open Thread network is failed.

Please help us resolve the issue. We know if once Open Thread Network is formed,  Android Chiptool will automatically identify the "Lock" device which is flashed on the other nRF52840 DK Board.

Regards.

Jogen

Parents
  • Hi Jogen,

    I can recreate your issue with the default RCP build using the nRF52840DK uart port, but the build with the nRF52840 USB port will work.

    Here is the build command for the USB port and firmware. Please test it.

    west build --build-dir c:\NCS\v2.2.0\nrf\samples\openthread\coprocessor\build_nrf52840dk c:\NCS\v2.2.0\nrf\samples\openthread\coprocessor --pristine --board nrf52840dk_nrf52840 -- -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DCONF_FILE:STRING="c:/NCS/v2.2.0/nrf/samples/openthread/coprocessor/prj.conf" -DOVERLAY_CONFIG:STRING="c:/NCS/v2.2.0/nrf/samples/openthread/coprocessor/overlay-usb.conf" -DDTC_OVERLAY_FILE:STRING="c:/NCS/v2.2.0/nrf/samples/openthread/coprocessor/usb.overlay"

    nrf52840DK_RCP_usb.hex

    I will report to our development team for further investigation.

    Best regards,

    Charlie

Reply
  • Hi Jogen,

    I can recreate your issue with the default RCP build using the nRF52840DK uart port, but the build with the nRF52840 USB port will work.

    Here is the build command for the USB port and firmware. Please test it.

    west build --build-dir c:\NCS\v2.2.0\nrf\samples\openthread\coprocessor\build_nrf52840dk c:\NCS\v2.2.0\nrf\samples\openthread\coprocessor --pristine --board nrf52840dk_nrf52840 -- -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DCONF_FILE:STRING="c:/NCS/v2.2.0/nrf/samples/openthread/coprocessor/prj.conf" -DOVERLAY_CONFIG:STRING="c:/NCS/v2.2.0/nrf/samples/openthread/coprocessor/overlay-usb.conf" -DDTC_OVERLAY_FILE:STRING="c:/NCS/v2.2.0/nrf/samples/openthread/coprocessor/usb.overlay"

    nrf52840DK_RCP_usb.hex

    I will report to our development team for further investigation.

    Best regards,

    Charlie

Children
No Data
Related