OpenThread: Difference between revisions
(Created page with "<!-- Set release according to "release" parameter in URL and use mx93-yocto-langdale-6.1.1_1.0.1-v1.1 as default --> {{INIT_RELEASE_PARAM|mx93-yocto-langdale-6.1.1_1.0.1-v1.1}...") |
|||
Line 22: | Line 22: | ||
The OpenThread core runs on the host processor ({{#var:SOC}}) and communicates with the 802.15.4 coprocessor via OpenThread Daemon (ot-daemon) through SPI interface. Clients can connect to the ot-daemon UNIX socket and communicate using OpenThread CLI as a protocol. | The OpenThread core runs on the host processor ({{#var:SOC}}) and communicates with the 802.15.4 coprocessor via OpenThread Daemon (ot-daemon) through SPI interface. Clients can connect to the ot-daemon UNIX socket and communicate using OpenThread CLI as a protocol. | ||
= Configuring ot-daemon = | = Configuring ot-daemon = |
Revision as of 23:07, 14 September 2023
This page is using the default release mx93-yocto-langdale-6.1.1_1.0.1-v1.1.
To view this page for a specific Variscite SoM and software release, please follow these steps:
- Visit variwiki.com
- Select your SoM
- Select the software release
VAR-SOM-MX93 OpenThread Overview
VAR-SOM-MX93 SoMs ordered with the WBE option feature an IW612 based tri-radio module that supports Wi-Fi 6, Bluetooth/Bluetooth Low Energy 5.2, and 802.15.4.
The 802.15.4 radio coprocessor is managed by OpenThread. Thread is an IPv6-based networking protocol designed for low-power Internet of Things devices in an IEEE802.15.4-2015 wireless mesh network. OpenThread released by Google is an open-source implementation of Thread.
The OpenThread core runs on the host processor (mx93) and communicates with the 802.15.4 coprocessor via OpenThread Daemon (ot-daemon) through SPI interface. Clients can connect to the ot-daemon UNIX socket and communicate using OpenThread CLI as a protocol.
Configuring ot-daemon
ot-daemon is started with the following command:
ot-daemon "spinel+spi:///dev/spidev1.0?gpio-int-device=4&gpio-int-line=29&gpio-reset-device=4_&gpio-reset-line=4_&spi-mode=0&spi-speed=1000000&spi-reset-delay=500" &
This is done automatically on boot by Variscite's ot-service and the scripts in /etc/openthread on boot. The service can be managed using systemd:
systemctl <start|stop|restart|enable|disable> variscite-ot.service
For example, you can stop and disable the service:
# Stop the service systemctl stop variscite-ot # Start the service systemctl disable variscite-ot
Managing OpenThread using ot-ctl
TODO