This directory contains the platform drivers necessary to run OpenThread on the Texas Instruments CC13XX_CC26XX family of Connected MCUs. These drivers use the TI SimpleLink™ SDK for the RTOS enabled platform drivers. The example applications are built with FreeRTOS to enable an environment for the standard device drivers to operate.
The following is the currently supported Thread roles for compatible TI devices. This list may be updated as the Thread stack is updated or new devices are added.
| Device | RCP | MTD | FTD |
|---|---|---|---|
| CC2652R | x | ||
| CC2652RB | x | ||
| CC2652P | x | ||
| CC2652RSIP | x | ||
| CC2652PSIP | x | ||
| CC2652R7 | x | x | x |
| CC2652P7 | x | x | x |
| CC2674R10 | x | x | x |
| CC2674P10 | x | x | x |
The documentation hosted in the docs folder is sorted by alphabetical order. After reading the rest of the README document, it is recommended to read the documentation in the following order:
Start with ti-openthread-release-notes for important information about versioning, known issues, and more.
- ti-openthread-release-notes
Optional, if migration is needed, locate the thread-migration-guide folder and reference:
- thread-migration
- thread-cc2674-migration
Then navigate to the thread-users-guide folder and read in the following order:
- ti-openthread-overview
- ti-openthread-thread-protocol
- ti-openthread-product-certification
- ti-openthread-example-apps
- ti-openthread-application-development
- ti-openthread-ncp-interface
- ti-openthread-borderrouter-setup-guide
Conclude by opening the thread-syscfg folder and refer to the getting-started guide and sysconfig-board as needed.
In a Bash terminal, follow these instructions to install the GNU toolchain and other dependencies.
$ cd <path-to-ot-ti>
$ git submodule update --init
$ ./script/bootstrapIn a Bash terminal, follow these instructions to build the cc13xx_cc26xx examples. The <simplelink_board> is a
reference development kit available on ti.com.
$ cd <path-to-ot-ti>
$ ./script/build <simplelink_board>Attention: The above statement is only true when you have already run the bootstrap script.
If the build completed successfully, the elf files may be found in <path-to-ot-ti>/build/bin/. These files do not
have any file extension.
Loading the built image onto a LaunchPad is supported through two methods; UniFlash and Code Composer Studio (CCS). UniFlash can be used to load the image. Code Composer Studio can be used to load the image and debug the source code.
Programming with CCS will allow for a full debug environment within the IDE. This is accomplished by creating a target connection to the XDS110 debugger and starting a project-less debug session. The CCS IDE will attempt to find the source files on the local machine based on the debug information embedded within the ELF. CCS may prompt you to find the source code if the image was built on another machine or the source code is located in a different location than what is recorded within the ELF.
Download and install Code Composer Studio.
First open CCS and create a new workspace.
Create a target connection (sometimes called the CCXML) for your target SoC and debugger as described in the Manual Method section of the CCS User's Guide.
Next initiate a project-less debug session as described in the Manual Launch section of the CCS User's Guide.
CCS should switch to the debug view described in the After Launch section of the User's Guide. The
SoC core will likely be disconnected and symbols will not be loaded. Connect to the core as described in the Debug
View section of the User's Guide. Once the core is connected, use the Load button on the toolbar to
load the ELF image.
Note that the default configuration of the CCXML uses 2-wire cJTAG instead of the full 4-wire JTAG connection to match the default jumper configuration of the LaunchPad.
Uniflash is Texas Instrument's uniform programming tool for embedded processors. This will allow you to erase, flash, and inspect the SoC without setting up a debugging environment.
Download and install UniFlash.
First open UniFlash. Debug probes connected to the computer will usually be displayed under the Detected Devices due to
the automatic device detection feature. If your device does not show up in this view it my be disconnected, or you may
have to create a New Configuration. If you already have a CCXML for your SoC and debug connection you can use that in
the section at the bottom. Once your device is selected, click the Start button within the section to launch the
session.
Select the ELF image to load on the device with the Browse button. Make sure to deselect the binary check-box,
Uniflash assumes a file without an extension is a binary file and not an elf. Click the Load Image button to load the
executable image onto the device. You should be able to see the log output over the XDS110 User UART.
Note that programming the device through JTAG sets the Halt-in-Boot flag and may cause issues when performing a software reset. This flag can be reset by power-cycling the LaunchPad.
By default the terminal output will be sent to the Application/User UART. This can be found in Windows in the Device
Manager or in Linux as the /dev/ttyACM0 device. Open a terminal emulator to that port to see the output with the
following options:
| Parameter | Value |
|---|---|
| Speed (baud) | 115200 |
| Data bits | 8 |
| Stop bits | 1 |
| Parity | None |
| Flow control | None |
- Open terminal to the com port associated with the User UART.
- Type
helpfor list of commands. - See OpenThread CLI Reference README.md to learn more.
Low power mode can be enabled/disabled by going to examples/apps/cli/cli_uart.cpp and changing the defines listed below.
- TIOP_POWER_MEASUREMENT: disable UART/peripherals and automatically start thread device upon boot up.
- TIOP_POWER_SED: will enable features to make device a sleepy end device (SED) and enter deep sleep mode.
- TIOP_POWER_SSED: will enable features to make device a synchronous sleepy end device (SSED).
The Thread network data/features can be modified by changing the defined value/variables listed below:
- TIOP_POWER_PANID
- TIOP_POWER_CH
- TIOP_POWER_POLL_PERIOD
- TIOP_POWER_CSL_PERIOD
- networkKeyVal
For technical support, please consider creating a post on TI's E2E forum. Additionally, we welcome any feedback.
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, Texas Instruments or The Thread Group.
OpenThread support is available on GitHub:
- Bugs and feature requests pertaining to OpenThread on CC13x2/CC26x2 family — submit a ticket to the E2E forum
- OpenThread bugs and feature requests — submit to the OpenThread Issue Tracker
- Community Discussion - ask questions, share ideas, and engage with other community members
