Custom Hardware

This section will explain how to adapt a Z-Stack application from the SimpleLink CC13x2 / 26x2 SDK to run on custom hardware. In general, the steps required to migrate a Z-Stack application from a development kit to a custom board are minimal and involve changing the pin configuration as well as selecting the correct RF configuration. These steps, including a bring up guide, are detailed in the subsections below.

Designing a Custom Board

Design guidelines for CC13x2 and CC26x2 boards can be found in the CC13xx/CC26xx Hardware Configuration and PCB Design Considerations app note. This app note includes RF front-end, schematic, PCB, and antenna design considerations. The report also covers crystal oscillator tuning, optimum load impedance as well as a brief explanation of the different power supply configurations.

Creating a Custom Board File

Board files are used by TI drivers to store device specific settings and I/O mapping. The board file abstraction allows one TI-drivers implementation to support many hardware implementations by just setting up new board files. Examples utilize SysConfig to generate these board files. The generated structures are placed in the ti_drivers_config.c and ti_drivers_config.h files. The SysConfig user interface can be utilized to determine pins and resources used. Information on pins and resources used is also present in both of these generated files. It is recommended to use SysConfig to generate the board files for custom hardware.

Change Device Configuration

If you need to change the device definition in your IDE, you can find instruction below.


In most cases it is not necessary to change the IDE device configuration. However, if you have been testing software on a different device than your final product will use, it can be useful. Example situations are:

Changing Device in CCS

Go to Project → Properties → General → Project → Variant and select your device.


There is a known issue in CCS where, when changing the Variant, the Target may also change. This will cause build errors. To avoid this, go to Project → Properties → General → Products and check the Target and after you change the Variant.

Changing Device in IAR

Go to Project → Options → General Options → Target and select your device.

Configuring Device Parameters for Custom Hardware

  1. Set parameters, such as the sleep clock accuracy of the 32.768-kHz crystal.
  2. Define the CCFG parameters in Device Configuration in SysConfig.


For a description of CCFG configuration parameters, see the CC13x2 CC26x2 SimpleLink Wireless MCU Technical Reference Manual.

Configuring the RF Front-End for Custom Hardware

The CC13x2 or CC26x2 supports multiple RF front end options to optimize performance or cost. Reference designs are available for multiple RF front end options to aid in decoupling and RF layout. In order to achieve optimal sensitivity, it is important to configure the Z-Stack application with the correct RF front end setting used on the custom board. An incorrectly configured RF front end may result in substantially degraded RF performance such as the inability to maintain a connection with a peer device. Configuration of the RF front end is done by SysConfig for Z-Stack projects in the RF Stacks -> Z-Stack -> Radio menu.

For information on front ends, antenna configurations and other hardware considerations, please see CC13xx/CC26xx Hardware Configuration and PCB Design Considerations.

Initial Board Bring Up

When powering up a custom board with the CC13x2 or CC26x2 for the first time, it is recommended to follow the Board Bring-Up section on CC13xx/CC26xx Hardware Configuration and PCB Design Considerations. After confirming that the board is being powered correctly by the battery or power supply and can be identified by the JTAG tool, programming the device with a minimal SW application to verify stability is also suggested.