--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/24bbf9d1-dc0d-4329-837a-987af49f89f1n%40googlegroups.com.
( LPSTK cc1352r is connected to LAUNCHXL-CC1352P via JTAG and 2 additional TX/RX wires . No battery or external power supply needed - all powered from USB).
For making flash for CC1352 without CSL
Install docker
docker pull openthread/environment:latest
docker run -it --rm openthread/environment bash
git clone github.com/.../ot-cc13x2-cc26x2.git
cd ot-cc13x2-cc26x2
git submodule update --init
cd openthread
git reset 31c7208ac87768f8fe7ad4c94d8e8b184bb0ee51
./script/bootstrap
./script/build -DTI_PLATFORM=cc1352
Then on border router I advice to compile ot-br-posix like below:
#in case you have previous compilation remove folder and clone new repo like described
rm -r ot-br-posix
git clone ---recursive https://github.com/openthread/ot-br-posix.git
git submodule update --init --recursive
then
To use OTBR in Thread 1.1 please add to third_party/openthread/CMakeLists.txt following line
BACKBONE_ROUTER=0 INFRA_IF_NAME=wlan0 ./script/setup
then
Below checks/task form website: OpenThread Border Router Build and Configuration
Configure the RCP device's serial port in otbr-agent:
Verify that all required services are enabled:
If the setup script was successful, the following services appear in the output:
Verify that the RCP is in the correct state:
ot-ctl is a command line utility provided with OTBR. It is used to communicate with the Thread PAN interface (default is wpan0) that otbr-agent is bound to in the RCP design.
If the RCP is successfully running and the node is not a member of a Thread network, the output should be similar to the below:
If the output is OpenThread daemon is not running, troubleshoot with the following:
Check the RCP status again with sudo ot-ctl state
Then you can configure your thread as described
pi@raspberrypi:~ $ sudo ot-ctl state
disabled
Done
pi@raspberrypi:~ $ sudo ot-ctl reset
pi@raspberrypi:~ $ sudo ot-ctl state
disabled
Done
pi@raspberrypi:~ $ sudo ot-ctl channel 14
Done
pi@raspberrypi:~ $ sudo ot-ctl panid 0xface
Done
pi@raspberrypi:~ $ sudo ot-ctl ifconfig up
Done
pi@raspberrypi:~ $ sudo ot-ctl thread start
Done
pi@raspberrypi:~ $ sudo ot-ctl state
leader
Done