SWRA843 January   2026 CC1310

 

  1.   1
  2.   Summary
  3. 1How to port a product design from CC1310 to CC1311
    1. 1.1 Hardware porting
    2. 1.2 Software porting
      1. 1.2.1 System Configuration (SysConfig)
      2. 1.2.2 Port TI-RTOS to TI-RTOS 7
      3. 1.2.3 Peripheral driver code porting
        1. 1.2.3.1 Port PIN driver to GPIO driver
        2. 1.2.3.2 Port UART driver to UART2 driver
  4. 2How to use the CC1311/CC110L combination to implement a multi-function system at 915MHz/433MHz/345MHz
    1. 2.1 Solution overview
    2. 2.2 RF topology design recommendations and BOM
    3. 2.3 Layout design
      1. 2.3.1 CC1311 section
      2. 2.3.2 CC110L section
    4. 2.4 Test results
  5. 3Reference links

Port TI-RTOS to TI-RTOS 7

The software engineering for both CC1310 and CC1311 relies on the TI-RTOS real-time operating system. The TI-RTOS version has been upgraded since CC1311 SDK 5.30 version. Currently, TI-RTOS 7 is used on CC1311 and the original TI-RTOS on CC1310., without a version number.

Compared to TI-RTOS, TI-RTOS 7 introduces the following key upgrades:

  • TI-RTOS 7 generates the configuration code through SysConfig
  • TI-RTOS 7 improves compilation speed by removing its dependency on the XDSTools tool for compilation
  • TI-RTOS 7 consumes less flash and RAM
  • TI-RTOS 7 enhances the debug experience by directly entering kernel functions for single-step debugging

More detailed updates can be found at the following links:

[FAQ] Why use TI-RTOS7? - Sub-1 GHz forum - Sub-1 GHz - TI E2E support forums

The biggest difference for users upgrading from CC1310 is that the related configuration of TI-RTOS 7 is generated by SysConfig, replacing the previous cfg configuration file. SysConfig is covered already in section 2.2.1. Detailed TI-RTOS migration steps are also available in the CC1311 SDK:

TI-RTOS to TI-RTOS7 Migration

In addition to this, some RTOS-related APIs have changed in the routine. The CC1311 adds a layer of DPL (Driver Porting Layer) for compatibility with different RTOS operating systems and uses the DPL API in routines instead of the original TI-RTOS API. Thus, you should be aware of the following API changes when porting:

  • The Clock Module API, including the Clock_Struct structure and Clock_getTicks() etc., should be replaced with ClockP_Struct and ClockP_getTicks();
  • The API in util_timer.c, such as Timer_start(), Timer_stop(), and so on, should be replaced with UtilTimer_start(), UtilTimer_stop(), and so on.

For a detailed description of the DPL API, refer to the Driver Porting Layer section of SimpleLink MCU SDK Driver API Reference document.