RCP failure when start simulated node

[samsung]

RCP failure when start simulated node

[wilbur-se]

Finally find the root cause from your log. The baudrate in our setting is not match with ioter. Normally the baudrate is 115200 or 460800.
After we update the baudrate to 1000000 in RCP dongle, it can works, even in VM.

Thanks for you update. It will be better if having interface to set baudrate in ioter.

[junyong-sim]

@wilbur-se
RCP dongle connection seems to have failed.
I guess it's a dongle issue or the environment issue related to VM ware.
Can you run otbr-agent in your VM environment ?

[wilbur-se]

RCP can works in Raspberry PI (Matter Test-Harness) to run OTBR. So the RCP dongle should have right firmware.
I have not test OTBR in my VM, maybe I can try it.

[wilbur-se]

I try to use docker to run ioter under ubuntu(non VM), it still have same issue.

[junyong-sim]

https://github.com/Samsung/ioter/blob/main/docs/guides/DOCKER.md
-> I think you already read this guide, but if not, please, check this guide.

Can you tell me that you can run otbr-agent with docker ?
Can you share the ioter log with log level 5 ? You can find log files under your_git_source_folder/tmp.
I don't know if it was because of permission issues, but I need to check your log to find the root cause.

[wilbur-se]

Yes, I setup ioter docker based on the guide.

I just test otbr-agent in Raspberry PI. My ubuntu in PC have not install otbr-agent.

The log is testing in ubuntu PC:
230713-1458-lightbulb-0.log
230713-1458-ioter.log

[junyong-sim]

I could not find any clues from your log. It was showing just communication errors.

This log was captured on my PC. I ran ioter with silabs dongle.
230714-1051-lightbulb-0.log

You can also get some ioter logs from /var/log/syslog.

junyong@junyong:/var/log$ cat /var/log/syslog | grep chip-all-clusters-app
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: otSysGetInstance
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: Wait for signal to initialise openthread stack !!!
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: Inside pThreadOtMainLoop
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: find empty interface [/sys/class/net/wpan0]
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: interface found [wpan0]
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: radio device found [/dev/ttyACM0]
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: radio Url found [spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000]
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: ot log level [5]
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: Running OPENTHREAD/thread-reference-20230119-484-g503e299f8; POSIX; Jun 30 2023 12:35:20
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: Thread version: 4
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: Thread interface: wpan0
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: RCP version: SL-OPENTHREAD/2.2.0.0_GitHub-91fa1f455; EFR32; Dec 21 2022 08:33:29
Jul 14 10:51:31 junyong chip-all-clusters-app-fed: otThread : gThreadId[139721349666368]
Jul 14 10:51:51 junyong chip-all-clusters-app-fed: terminate thread mainloop : exit

I hope you would find some clues through my log.

Plus, I wasn't sure, but, I guess the problem happened because the your rcp firmware is old.
I am using RCP API version 6 for my dongle. If you want, I can share my firmware with you. My silabs dongle is Silabs thunderBoardSense2.
[2023-07-14 10:51:31.531575][1967664:1967671] openthread: 59d.16:14:05.638 [D] Platform------: Received spinel frame, flg:0x2, tid:5, cmd:PROP_VALUE_IS, key:RCP_API_VERSION, version:6

[junyong-sim]

Also, you can check whether or not your dongle is attached well via dmesg.

$ sudo dmesg
...
[861009.900957] usb 3-2.2.2: new full-speed USB device number 71 using xhci_hcd
[861010.052356] usb 3-2.2.2: New USB device found, idVendor=1366, idProduct=1015, bcdDevice= 1.00
[861010.052361] usb 3-2.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[861010.052363] usb 3-2.2.2: Product: J-Link OB
[861010.052364] usb 3-2.2.2: Manufacturer: Silicon Labs
[861010.052365] usb 3-2.2.2: SerialNumber: 000440225062
[861010.073804] cdc_acm 3-2.2.2:1.0: ttyACM0: USB ACM device
[861010.074619] usb-storage 3-2.2.2:1.3: USB Mass Storage device detected
[861010.075554] scsi host0: usb-storage 3-2.2.2:1.3
[861011.085850] scsi 0:0:0:0: Direct-Access     SEGGER   MSD Volume       1.00 PQ: 0 ANSI: 4
[861011.086206] sd 0:0:0:0: Attached scsi generic sg0 type 0
[861011.086958] sd 0:0:0:0: [sda] 21829 512-byte logical blocks: (11.2 MB/10.7 MiB)
[861011.088151] sd 0:0:0:0: [sda] Write Protect is off
[861011.088154] sd 0:0:0:0: [sda] Mode Sense: 0b 00 00 08
...

[junyong-sim]

Cool !

I configured the baudrate to 1000000 so we could support nxp dongle and other dongles. junyong-sim/openthread@503e299
Please, let me know if you have the any other opinions when it comes to the baudrate.