Li Cao
097aa4f65d
Background: In an early stage of developing a new product, developers may want to verify the Thread related hardware functionality, for example, send, receive, etc. However if the product uses the posix <-> RCP mode, it's hard to verify it before the posix daemon can run on the host. cli-ftd and cli-mtd could be an alternative. However, if the product uses the posix <-> RCP mode, the space of the 802.15.4 radio chip will be very small. For example, nRF52811 doesn't have enough space to flash cli-ftd or cli-mtd firmware. So this PR creates a new firmware ot-cli-radio which has very limited functionality for verifying the hardware. Basically, the ot-cli-radio consists of openthread-radio and libopenthread-cli-radio.a. It supports very few cli commands. The most important command is diag. Currently, there are: diag, help, reset, version. Currently, the diag commands have different implementation on RCP: - For commands like diag start, the process function (Diags::ProcessStart) is first called on host. Then host sends an SPI frame to the RCP and Diags::ProcessStart (different implementation) is called again on RCP. - For commands like diag send, Diags::ProcessSend is first called on host. Then host sends an SPI frame to the RCP, directly calling send API. And there is no Diags::ProcessSend implemented on RCP. Let's call the implementation of Diags::Process* currently on host as native diag commands. When we run ot-cli-radio, we should use the native diag commands because it won't interact with a posix daemon and it processes the diag commands through the whole process. So this PR adds a new option OPENTHREAD_CONFIG_DIAG_NATIVE_CMDS_ON_RCP to control whether to use the native diag implementation on RCP. When we use a normal RCP, the option should be disabled. While when use ot-cli-radio, the option should be enabled.
What is OpenThread?
OpenThread released by Google is... 
...an open-source implementation of the Thread networking protocol. Google Nest has released OpenThread to make the technology used in Nest products more broadly available to developers to accelerate the development of products for the connected home.
...OS and platform agnostic, with a narrow platform abstraction layer and a small memory footprint, making it highly portable. It supports both system-on-chip (SoC) and network co-processor (NCP) designs.
...a Thread Certified Component, implementing all features defined in the Thread 1.1.1 specification, including all Thread networking layers (IPv6, 6LoWPAN, IEEE 802.15.4 with MAC security, Mesh Link Establishment, Mesh Routing) and device roles, as well as Border Router support.
More information about Thread can be found at threadgroup.org. Thread is a registered trademark of the Thread Group, Inc.
Who supports OpenThread?
Getting started
All end-user documentation and guides are located at openthread.io. If you're looking to do things like...
- Learn more about OpenThread features and enhancements
- Use OpenThread in your products
- Learn how to build and configure a Thread network
- Port OpenThread to a new platform
- Build an application on top of OpenThread
- Certify a product using OpenThread
...then openthread.io is the place for you.
Note: For users in China, end-user documentation is available at openthread.google.cn.
If you're interested in contributing to OpenThread, read on.
Contributing
We would love for you to contribute to OpenThread and help make it even better than it is today! See our Contributing Guidelines for more information.
Contributors are required to abide by our Code of Conduct and Coding Conventions and Style Guide.
Versioning
OpenThread follows the Semantic Versioning guidelines for release cycle transparency and to maintain backwards compatibility. OpenThread's versioning is independent of the Thread protocol specification version but will clearly indicate which version of the specification it currently supports.
License
OpenThread is released under the BSD 3-Clause license. See the LICENSE file for more information.
Please only use the OpenThread name and marks when accurately referencing this software distribution. Do not use the marks in a way that suggests you are endorsed by or otherwise affiliated with Nest, Google, or The Thread Group.
Need help?
There are numerous avenues for OpenThread support:
- Bugs and feature requests — submit to the Issue Tracker
- Stack Overflow — post questions using the
openthreadtag - Google Groups — discussion and announcements at openthread-users
The openthread-users Google Group is the recommended place for users to discuss OpenThread and interact directly with the OpenThread team.