OTBR cannot connect to slae.sh cc2652 stick #6
Description
Hi,
I have slaesh's CC2652 stick and flashed the 2025.3.1 RCP firmware from this repo (CC2652RB_ot_rcp_2025_3_1.zip). I used the cc2538-bsl tool to flash it:
./cc2538_bsl.py -p /dev/ttyUSB0 -evw CC2652RB_ot_rcp_2025_3_1.hex
And this works fine.
However when trying to link this with OTBR, I get a timeout:
% docker run --name=otbr --rm -it --device=/dev/ttyUSB0 -e 'OT_RCP_DEVICE=spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800' --privileged openthread/border-router
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service otbr-agent: starting
Configuring OpenThread firewall...
Configuring OpenThread NAT64...
Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-7729fd3
[NOTE]-AGENT---: Thread version: 1.4.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800
[NOTE]-AGENT---: Radio URL: trel://wlan0
[NOTE]-ILS-----: Infra link selected: wlan0
[INFO]-RCP_HOS-: OpenThread log level changed to 5
49d.21:53:27.785 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:0, cmd:RESET
49d.21:53:27.785 [D] P-SpinelDrive-: Waiting response: key=0
49d.21:53:29.786 [W] P-SpinelDrive-: Wait for response timeout
49d.21:53:29.786 [I] P-SpinelDrive-: co-processor self reset successfully
49d.21:53:29.786 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.21:53:29.786 [D] P-SpinelDrive-: Waiting response: key=1
49d.21:53:31.788 [W] P-SpinelDrive-: Wait for response timeout
49d.21:53:31.788 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.21:53:31.788 [D] P-SpinelDrive-: Waiting response: key=1
49d.21:53:33.790 [W] P-SpinelDrive-: Wait for response timeout
49d.21:53:33.790 [C] Platform------: Init() at spinel_driver.cpp:87: Failure
49d.21:53:33.790 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.21:53:33.790 [D] P-SpinelDrive-: Waiting response: key=1
49d.21:53:35.792 [W] P-SpinelDrive-: Wait for response timeout
otbr-agent exited with code 1 (by signal 0).
Chain OT_FORWARD_INGRESS (0 references)
target prot opt source destination
DROP all -- anywhere anywhere PKTTYPE = unicast
DROP all -- anywhere anywhere match-set otbr-ingress-deny-src src
ACCEPT all -- anywhere anywhere match-set otbr-ingress-allow-dst dst
DROP all -- anywhere anywhere PKTTYPE = unicast
ACCEPT all -- anywhere anywhere
otbr-ingress-deny-src
otbr-ingress-deny-src-swap
otbr-ingress-allow-dst
otbr-ingress-allow-dst-swap
OpenThread firewall rules removed.
s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died
s6-rc: warning: unable to start service otbr-agent: command exited 1
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
My goal is to eventually run this with HomeAssistant, but to debug this issue I ran OTBR locally using docker as above. The stick is new, I did not have a previous working state with OTBR.
Am I doing something wrong? How can I troubleshoot this? I've read about some similar timeouts from other users recently, so it could be connected to an OTBR update, but I am unsure how to even try an older version of that.