Introduction to the SimpleLink CC13x2 / 26x2 SDK

The SimpleLink CC13x2 / 26x2 SDK delivers components that enable engineers to develop applications on the Texas Instruments SimpleLink CC13x2 or CC26x2 family of wireless microcontroller (MCUs). This powerful software toolkit provides a cohesive and consistent software experience for all SimpleLink CC13x2 or CC26x2 wireless MCU users by packaging essential software components, such as a Bluetooth® Low Energy (BLE) protocol stack supporting Bluetooth 5, Thread 1.1 networking stack based on OpenThread (https://github.com/openthread/openthread), TI’s 15.4 Stack, RF-Proprietary examples, a Zigbee stack as well as the TI-RTOS kernel and TI Drivers in one easy-to-use software package along with example applications and exhaustive documentation.

The SimpleLink MCU portfolio offers a single development environment that delivers flexible hardware, software and tool options for customers developing wired and wireless applications. With 100 percent code reuse across host MCUs, Wi-Fi™, Bluetooth Low Energy, Sub-1GHz devices and more, choose the MCU or connectivity standard that fits your design. A one-time investment with the SimpleLink software development kit (SDK) allows you to reuse often, opening the door to create unlimited applications. For more information, visit www.ti.com/simplelink.

Prerequisites

The user is expected to have the following:

  • CC13x2 or CC26x2 LaunchPad
  • A computer running a supported operating system listed in the Release Notes
  • At least one of the following IDE supported by the SimpleLink CC13x2 / 26x2 SDK:
    • CCS
    • IAR for Arm
    • GNU Arm Embedded Toolchain
  • FreeRTOS (Optional - For TI Drivers projects) The SimpleLink CC13x2 / 26x2 SDK does not deliver FreeRTOS sources. User is expected to download the same from www.freertos.org if they want to use FreeRTOS with the SDK.

SDK - Download and Installation

Using the SDK Online

A quick and easy way to start working with the SDK is to use TI Resource Explorer on dev.ti.com. This online tool lets you explore the contents of the SimpleLink CC13x2 / 26x2 SDK. You can build the examples directly using the cloud version of Code Composer Studio. If you choose to use the SDK online, there is no need to download the SDK to your local computer or install any tools (other than the TI Cloud Agent for first time users).

Installing the SDK

You can also download the SimpleLink CC13x2 / 26x2 SDK from TI Resource Explorer or the software product page on TI’s website.

IDE - Download and Installation

CCS Download and Installation

This section covers the required settings for a CCS installation. The CCS toolchain contains many features beyond the scope of this document. More information and documentation can be found on the Code Composer Studio tool page.

Check the SimpleLink CC13x2 / 26x2 SDK release notes to see which CCS version to use and any required workarounds. Object code produced by CCS may differ in size and performance as compared to IAR produced object code.

  1. Download CCS

    CCS is available here: Code Composer Studio .

    Refer to the SDK release notes for the version that is compatible with this SDK.

  2. Installation Options

    During the installation, the following options are recommended:

    • We recommend that you use the default installation folder
    ../_images/ccs-install.jpg

    Figure 1. Default CCS Installation Location

    • Select SimpleLink CC13xx and CC26xx Wireless MCUs is selected. You can select additional processor support options as needed.
    ../_images/ccs-processor-support.jpg

    Figure 2. Select Processor Support

    To use a debug probe, select TI XDS Debug Probe Support and any other options you would like. The CC13x2 or CC26x2 LaunchPad uses TI XDS Debug Probe by default.

    ../_images/ccs-debugger-options.jpg

    Figure 3. CCS Debugger Options

    When the installation has completed, make sure that CC13xx/CC26xx Device Support is installed by checking for updates under Help -> Check for Updates.

  3. Discovering the SDK in CCS

    Install the SDK in the default location pointed to by the installer - c:\ti and restart CCS. CCS will automatically detect the latest install.

    You can also Install products manually by selecting Window -> Preferences -> Code Composer Studio -> Products and clicking Install and navigating to the SDK installation location.

    Code Composer Studio automatically discovers the SimpleLink CC13x2 / 26x2 SDK if it installed in its default installation directory (c:/ti). Once discovered by CCS, it defines a build environment variable named SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR which is used by all SimpleLink CC13x2 / 26x2 SDK projects.

    If a project is imported from a path other than what was specified during the SimpleLink CC13x2 / 26x2 SDK installation, the SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR variable must be redefined after the import proceeding at a project-by-project basis.

    To redefine this variable:

    1. Open the CCS project’s properties (Project -> Properties)

    2. Navigate to Resource -> Linked Resources and edit SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR and have it point to your imported root directory location.

      ../_images/redefine-ccs-linked-resources.png

      Figure 4. Redefining SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR

  4. Using a Specific TI Arm Compiler

    1. Verify Arm Compiler Tools version

      If needed, the CCS and Arm compiler versions can be verified by going to into Help -> About Code Composer Studio. Under the Installation Details button, you can determine the Arm Compiler Tools version. Please ensure this version satisfies the version requirements as stated in the release notes.

      If an update is required, refer to Installing a Specific TI Arm Compiler for the procedure to install the required TI Arm Compiler version.

    2. Install a Specific TI Arm Compiler, refer to the following steps and Figure 5.

      1. Help -> Install New Software
      2. Under the Work with: drop-down list, select Code Generation Tools Update
      3. Uncheck Show only the latest versions of available software
      4. Expand TI Compiler Update.
      5. Select the desired Arm Compiler Tools version as stated in the release notes.
      6. Press Next to complete the installation. You may have to restart CCS afterwards.
    ../_images/ti-arm-compiler-version.jpg

    Figure 5. TI Arm Compiler Version in Code Composer Studio

IAR Download and Installation

This section covers the required settings for a IAR installation. The IAR toolchain contains many features beyond the scope of this document. More information and documentation can be found at IAR.com.

Not all components in the SimpleLink CC13x2 / 26x2 SDK support IAR projects. Check the SimpleLink CC13x2 / 26x2 SDK and component release notes to check IAR support, which IAR version to use and any required workarounds. Object code produced by IAR may differ in size and performance as compared to CCS produced object code.

  1. Download IAR Download and install IAR Embedded Workbench for Arm. Please see the SDK release notes for what version of IAR the SDK supports. You can get IAR for Arm here: https://www.iar.com/iar-embedded-workbench/partners/texas-instruments/ti-wireless/

    To get IAR, choose one of the following methods:

    • Download the IAR Embedded Workbench 30-Day Evaluation Edition – This version of IAR is free, has full functionality, and includes all of the standard features. The size-limited Kickstart evaluation option is not compatible with this SDK.
    • Purchase the full-featured version of IAR Embedded Workbench – For complete BLE application development using the CC13x2 or CC26x2, TI recommends purchasing the complete version of IAR without any restrictions. You can find the information on purchasing the complete version of IAR.

    Attention

    The version required is stated in the release notes. Opening IAR project files with a previous version of IAR may cause project file corruption.

  2. Installation Options Begin Installation by selecting Install IAR Embedded Workbench® for Arm.

    ../_images/iar-install.jpg

    Figure 6. IAR Installer

    Click through the installation confirm windows and license agreement. We recommend installing to the default path

    ../_images/iar_install_dir.png

    Figure 7. Default IAR Installation Location

    Make sure to select TI XDS as one of the debug probe drivers. You may also select other drivers. The driver will be installed towards the end of the installation of IAR.

../_images/iar_install_debug_drivers.png

Figure 8. IAR Debugger Options

  1. Show Build Messages

    TI recommends showing all the build output messages for full verbosity during building. To do this, after importing a workspace, right-click in the Debug log window and select All. (see Figure 9.)

    ../_images/iar-show-build-messages.png

    Figure 9. Show All Build Messages in IAR

Get started with SysConfig

System Configuration Tool (SysConfig) is a graphical interface for configuring your SimpleLink CC13x2 / 26x2 SDK project. Configuration files, C source files and header files are generated based on the parameters configured in the SysConfig dashboard.

SysConfig can be used as a standalone tool, or as a plug-in to CCS.

Attention

SysConfig is currently in preview mode. Files and code generated by SysConfig should be thoroughly checked and reviewed.

Using Standalone SysConfig

You can find the standalone SysConfig tool on the SysConfig Standalone Installer Download Page.

Open the System Configuration Tool, and select your device, part and package, then press START.

When you have finished configuring your .syscfg file, save and generate files. Export the generated files to your project, overwriting existing files if necessary. Make any needed changes to your application for interfacing with the SysConfig-generated files.

Note

Make sure you are using a SysConfig ready example project. These are found in the examples/syscfg_preview folder in the SimpleLink CC13x2 / 26x2 SDK.

Using SysConfig with IAR Workbench

If you are using IAR, you can use SysConfig as a standalone desktop tool to generate the configuration files to be compiled and linked with your application.

These steps assume the TI Code Generation Tools are installed in the default location. The figures use the MSP432 SDK as an example, but other SimpleLink SDKs follow the same procedure.

  1. Install SysConfig as a standalone tool within the default location (C:\ti).

  2. Open IAR and follow these steps to configure it to use the correct viewer for *.syscfg files:

    1. Choose Tools > Configure Viewers from the menus, and then click New.
    2. Type .syscfg in the File name extensions field.
    3. Type $SYSCONFIG_ROOT$\nw\nw.exe $SYSCONFIG_ROOT$ --compiler iar -s $SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR$\.metadata\product.json --output $PROJ_DIR$ $FILE_PATH$ with the Command line option selected.
../_images/sysconfig_iar_1.png

Figure 10. Editing Viewer Extensions

  1. Follow these steps to import custom argument variables into IAR:

    1. Choose Tools > Configure Custom Argument Variables from the menus.
    2. Choose the Workspace or Global tab depending on how you want to apply the variables. (If you’re not sure, choose Workspace.)
    3. Click the Import button and browse to \tools\iar within your SimpleLink CC13x2 / 26x2 SDK installation. Select the *.custom_argvars file provided there and click OK.
    4. Click the Add Variable button and add SYSCONFIG_ROOT as a variable with the value c:/ti/sysconfig_x.x.xxx (where the version matches the location of your SysConfig installation, e.g. c:/ti/sysconfig_1.0.655).
../_images/sysconfig_iar_2.jpg

Figure 11. Configuring Custom Argument Variables

  1. Import an example project workspace. Make sure to take it from the syscfg_preview folder.
  2. Double click on the *.syscfg file in your project. This will open the SysConfig standalone tool. You can configure all the settings, then save your changes and switch back to the IAR view.
  3. Rebuild the project to perform the custom build step, which uses SysConfig to generate additional files.
../_images/sysconfig_iar_3.jpg

Figure 12. Building with SysConfig in IAR

Using SysConfig as a Plug-In to CCS

SysConfig requires CCS v. 8.3 or later. (Please use the version of CCS recommended for the SimpleLink CC13x2 / 26x2 SDK you are working with. You can find the recommended tool version numbers in the release notes.)

In CCS, import a SysConfig enabled project from the examples/syscfg_preview folder.

In the project folder in CCS, you will see a .syscfg file. Open this file to start the SysConfig graphical interface.

../_images/sysconfig_dashboard.png