You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
Hi,
I previously managed to run the physical hardware (ESP32-S3 and ESP32-H2) on the ESP Thread Border Router. However, I am now encountering an issue getting OTBR in Linux to communicate with ot_rcp, as shown in the following running log.
It seems that the serial connection is not being established correctly at the moment, and I am continuing my troubleshooting.
Are there any features I need to enable or disable in the ot_rcp build that I may have missed? The USB is connected to J2 (UART) of the ESP32-H2-DevKitM-1.
Thank you.
donaldkoh@donaldkoh-VMware-Virtual-Platform:~$ journalctl -u otbr-agent --no-pager | tail -n 30
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Backbone interface: eth0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Running 0.3.0-thread-reference-20230710-542-g3f28d4c990c
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Thread version: 1.4.0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Thread interface: wpan0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?baudrate=460800
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Radio URL: trel://eth0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-ILS-----: Infra link selected: eth0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [INFO]-RCP_HOS-: OpenThread log level changed to 4
Feb 14 16:34:49 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:55.292 [W] P-SpinelDrive-: Wait for response timeout
Feb 14 16:34:49 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:55.292 [I] P-SpinelDrive-: co-processor self reset successfully
Feb 14 16:34:51 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:57.294 [W] P-SpinelDrive-: Wait for response timeout
Feb 14 16:34:53 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:59.296 [W] P-SpinelDrive-: Wait for response timeout
Feb 14 16:34:53 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:59.296 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
Feb 14 16:34:55 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:23:01.298 [W] P-SpinelDrive-: Wait for response timeout
Feb 14 16:34:55 donaldkoh-VMware-Virtual-Platform systemd[1]: otbr-agent.service: Main process exited, code=exited, status=1/FAILURE
Feb 14 16:34:55 donaldkoh-VMware-Virtual-Platform systemd[1]: otbr-agent.service: Failed with result 'exit-code'.
Feb 14 16:35:01 donaldkoh-VMware-Virtual-Platform systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 754.
Feb 14 16:35:01 donaldkoh-VMware-Virtual-Platform systemd[1]: Starting otbr-agent.service - OpenThread Border Router Agent...
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
OTBR Linux with esp32h2 as ot_rcp
OTBR Linux with esp32h2 as ot_rcp (IDFGH-14650)
Feb 14, 2025
Answers checklist.
General issue report
Hi,
I previously managed to run the physical hardware (ESP32-S3 and ESP32-H2) on the ESP Thread Border Router. However, I am now encountering an issue getting OTBR in Linux to communicate with ot_rcp, as shown in the following running log.
It seems that the serial connection is not being established correctly at the moment, and I am continuing my troubleshooting.
Are there any features I need to enable or disable in the ot_rcp build that I may have missed? The USB is connected to J2 (UART) of the ESP32-H2-DevKitM-1.
Thank you.
donaldkoh@donaldkoh-VMware-Virtual-Platform:~$ journalctl -u otbr-agent --no-pager | tail -n 30
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Backbone interface: eth0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Running 0.3.0-thread-reference-20230710-542-g3f28d4c990c
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Thread version: 1.4.0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Thread interface: wpan0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?baudrate=460800
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-AGENT---: Radio URL: trel://eth0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [NOTE]-ILS-----: Infra link selected: eth0
Feb 14 16:34:47 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: [INFO]-RCP_HOS-: OpenThread log level changed to 4
Feb 14 16:34:49 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:55.292 [W] P-SpinelDrive-: Wait for response timeout
Feb 14 16:34:49 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:55.292 [I] P-SpinelDrive-: co-processor self reset successfully
Feb 14 16:34:51 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:57.294 [W] P-SpinelDrive-: Wait for response timeout
Feb 14 16:34:53 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:59.296 [W] P-SpinelDrive-: Wait for response timeout
Feb 14 16:34:53 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:22:59.296 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
Feb 14 16:34:55 donaldkoh-VMware-Virtual-Platform otbr-agent[25009]: 49d.19:23:01.298 [W] P-SpinelDrive-: Wait for response timeout
Feb 14 16:34:55 donaldkoh-VMware-Virtual-Platform systemd[1]: otbr-agent.service: Main process exited, code=exited, status=1/FAILURE
Feb 14 16:34:55 donaldkoh-VMware-Virtual-Platform systemd[1]: otbr-agent.service: Failed with result 'exit-code'.
Feb 14 16:35:01 donaldkoh-VMware-Virtual-Platform systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 754.
Feb 14 16:35:01 donaldkoh-VMware-Virtual-Platform systemd[1]: Starting otbr-agent.service - OpenThread Border Router Agent...
The text was updated successfully, but these errors were encountered: