Creating Open Thread Network with nRF52840 DK Board as RCP failed

[jparekh68]

Hi, 

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

Fullscreen 8664.otbr_agent_status.txt Download

● 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: 

Fullscreen otbr_agent_status_1.txt Download

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

[Charlie]

Hi Jogen,

Ok, I think I understand you better now.

1) OTBR and Android Chip Tool are initially developed for Matter developers when there was no commercial TBR(like homepod min, next hub) in the market, so developers can use them for development and test purpose. Android Chip Tool is only a sample to show how to develop your own Chip Tool on mobile phones.

2) 

jparekh68 said:

I tried above with 1. being a 'Lock" device and you mentioned that it is not possible to commission a Lock Device.

It is possible to provision a Lock Device with Android Chip Tool and you can try to control it with CLUSTER INTERACTION TOOL, but it does not provide a direct interface for Lock device like LIGHT ON/OFF &LEVEL CLUSTER. With the formal release of Matter1.0, I see less and less maintenance effort on Android Chip Tool by CSA, because developers can test on other commercial smart ecosystems now.

3)

jparekh68 said:

I am stuck at "FORM open thread networkhas failed". However, otbr-agent is successfully running on Raspberry pi.

Sorry, I misunderstood your meaning. Let's continue to debug this issue. I have tested OTBR several weeks ago, but I am not sure if there are some changes recently. Let me try the OTBR setup procedure again and I will feedback to you later.

Best regards,

Charlie 

[jparekh68]

Thanks.

Your replies 1 and 2 are bang on.

On 3) I do not know if it is worthwhile to dwell on this since Homepod Mini and Google Nest are already there in the market. 

But yes since I have started this would love to finish this for better understanding and future projects. Your webinar on matter https://webinars.nordicsemi.com/developing-matter-products-with-nrf-4 does try to explain this but its too quick to get the full grasp of the subject.

Regards.

Jogen