Examples Users Guide¶
The Proprietary RF examples are split in to 2 types:
- RF Driver Examples
- EasyLink Examples
The RF driver offers very low-level API’s to run radio operation commands on the RF core and send and receive raw packets.
The EasyLink layer is an abstraction layer above the RF driver API’s for the more convenience. It uses the RF driver and executes radio operation commands. The EasyLink library was developed to be simple enough for developers to extend for their needs and should be seen as a starting point for adding an API on top of the RF driver. The EasyLink examples show how to develop an RF application on top of the EasyLink API.
RF Driver Examples¶
RF driver examples are available for the TI-RTOS kernel, but can also be used without any RTOS at all. That is possible with the NoRTOS Driver Porting Layer.
The RF Driver examples can be imported from the SDK directory:
C:/ti/simplelink_cc13x2_sdk_${VERSION}/examples/rtos/<PLATFORM>/drivers/
Carrier Wave: | Basic example for RF performance measurements and testing, written directly on top of the TI-RTOS RF driver. Set the radio into various test modes. Transmission of modulated or unmodulated signal. Easy to change radio configuration. Use radio settings exported from SmartRF Studio. |
---|---|
Echo RX/TX: | In this example you will learn how to setup the radio to do bi-directional communication. |
Listen Before Talk: | |
The Listen Before Talk (LBT) TX example illustrates how to implement a simple, proprietary LBT algorithm using the command chaining feature of the CC13x2 family. |
|
Packet Error Rate: | |
System example that showcases all available PHY configurations in one application. Multiple packets are transmitted or received and the packet error rate is calculated. The result is shown on the Display as well as a VT-100 compatible UART console. |
|
Packet RX/TX: | Shows how to send and receive packets using the RF driver. The PHY/RF settings can be modified using SmartRF Studio. Commands exported and used directly in code. Out of the box IEEE 802.15.4g GFSK 50kbps is used. Easy to change to e.g. Long Range Mode or custom PHY settings. |
Synchronized Packet RX/TX: | |
In this example you will learn how to build a time-synchronized connection between one transmitter and a receiver. This leads to the lowest possible power consumption on both sides. Time synchronization builds also the foundation for Frequency and Time Division Multiple Access, FDMA and TDMA respectively. |
|
Wake On Radio RX/TX: | |
These examples showcase the Wake-on-Radio (WoR) functionality of the CC13x2 family to significantly lower the power consumption of an RF link by duty cycling the RF core. It shows how to use the RF Driver to schedule automatic wake-ups and send messages with long preambles. |
EasyLink Examples¶
The EasyLink examples can be imported from the SDK directory:
C:/ti/simplelink_cc13x2_sdk_${VERSION}/examples/rtos/<PLATFORM>/easylink/
Only the RX, TX and listenBeforeTalk EasyLink examples are available for No-
RTOS. The others can only be used together with TI-RTOS.
EasyLink Echo Rx/TX: | |
---|---|
This example demonstrates the use of the EasyLink API in doing bi-directional communication. It will require the use of two boards, one running the rfEasyLinkEchoTx project that will originate the packets, while another board running the rfEasyLinkEchoRx project will re-transmit (echo) them back to the originator. |
|
EasyLink Listen Before Talk: | |
The EasyLink Listen Before Talk (LBT) TX example illustrates how to use the LBT capabilities of the EasyLink library. |
|
EasyLink Network Processor: | |
The EasyLink API has been exposed over an AT Command Interface such that it can be exercised by Host SW (running on a PC, MPU or MCU) or by a human using a serial terminal emulator over a UART. |
|
EasyLink RX/TX: | The EasyLink RX and TX examples show how to use the EasyLink API, how to set the frequency, and how to transmit and receive packets. One board can run the RX example while the other runs the TX example. The transmitter sends a packet every 100 ms, with a delay of 300ms between every 10th packet. The LED on the receiver board will blink for every packet received. |
Wireless Sensor Network: | |
The Wireless Sensor Network (WSN) Node and Concentrator examples illustrate how to create a very basic sensor network consisting of one or many Node device(s) and a Concentrator device. The example shows how to form one-to-many network where the Nodes send messages to the Concentrator. The Node use the Sensor Controller Engine to periodically read the value of the light sensor. Whenever the sensor value change, the main controller wakes up and sends a packet with the value to the Concentrator. The Concentrator is always waiting for incoming packet. Once a packet is received, the Concentrator sends an acknowledgement packet in return and displays the data on an LCD (if the kit has one) Additional versions of the Wireless Sensor Network example show :ref`over-the-air downloading (OAD)<sec-oad>` of new firmware images. |
Running examples in Code Composer Studio (CCS)¶
The following walks through importing and building one of the proprietary RF examples using the CCS IDE and the TI Resource Explorer.
If CCS v7 is not already installed; download and install CCS from here: https://processors.wiki.ti.com/index.php/Download_CCS.
If it is installed it is recommended that you install the available updates (Arm 16.9.0.LTS or higher is required).
Download and install the CC13x2 MCU SDK from https://www.ti.com/product/CC1352/toolssoftware#softTools.
This step is recommended, but optional as the TI Resource exploerer can download the examples from the resource explorer server. The rest of this section will assume that you have downloaded the SDK.
Open CCS, and use the menu option
View-> Resource Explorer
.Browse to the example of interest in the Resource Explorer.
Note
EasyLink examples can be found in the EasyLink folder and the RF Driver examples can be found in the TI Drivers directory.
Select the CCS or GCC compiler, we recommend using the CCS compiler, but compiling with GCC in the CCS IDE is also possible. Then select the example name and click the CCS icon in the top left to import it into your workspace.
You will notice that 2 projects have been included in the workspace:
rfEasyLinkTx_CC1352_LAUNCHXL_tirtos_ccs
tirtos_builds_CC1352_LAUNCHXL_release_ccs
As well as the example selected there is also the tirtos_builds project which is a platform and compiler specific TIRTOS build. This will only build once and is shared by all the projects for that platform and compiler in your workspace.
Build and download and debug the project by clicking on the ‘bug’. The first time it will take some time due to the TI-RTOS build.
Click run to run the example.
Running examples in IAR¶
If IAR ARM Workbench v7.80.3 or higher is not already installed, download and install IAR Workbench for ARM from http://www.iar.com .
Download and install the CC13x2 MCU SDK from https://www.ti.com/product/CC1352/toolssoftware#softTools .
Open IAR and create a new workspace with the menu option
File -> New -> Workspace
You can use this workspace for one or more examples.
Import the IAR Custom Argument Variables file with the menu option
Tools -> Configure Custom Argument Variables
. The location and file to be imported isC:/ti/simplelink_cc13x2_sdk_1_xx_xx_xx/tools/iar/SIMPLELINK_CC13XX_CC26XX_SDK.custom_argvars
.Save the Workspace with the menu option
File -> Save Workspace As...
.To enable the Custom Argument Variables for this workspace close and open the workspace with the menu options
File -> Close Workspace
andFile -> Open -> Workspace
.Select the menu option
Help -> Information Center
and select the Integrated Solutions icon:Select the Texas Instruments Example projects and then click on the example applications link.
Follow the instructions on this page to import and build the project.
When you click on one of the examples, it will ask you to place a copy of the project file in another folder. Save it in a sub-folder of your workspace. If you are going to import only one example into your workspace, you can put the project file into the same folder as the workspace file.
Download and debug the example with the menu option
Project -> Download and Debug
.
Building the examples from command line¶
All examples can be built from command line using plain makefiles in 3 steps:
- Configure the toolchain paths
- Build the kernel (only when using TI-RTOS kernel)
- Build the example
Note
To avoid problems with spaces in paths, it is recommended to use a Unix shell like Bash as command line environment instead of the native command interpreter cmd.exe in Windows.
The toolchain paths are configured in a imports.mak
in the SDK
installation root folder. Open the file in an editor and modify the toolchain
install paths lines depending on which toolchain you are going to use and
where they are installed on your system.
# The shown versions are just examples.
XDC_INSTALL_DIR ?= c:/ti/xdctools_3_50_03_33_core
CCS_ARMCOMPILER ?= c:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS
GCC_ARMCOMPILER ?= c:/ti/ccsv7/tools/compiler/gcc-arm-none-eabi-6-2017-q1-update
IAR_ARMCOMPILER ?= c:/Program Files (x86)/IAR Systems/Embedded Workbench 8.0/arm
Once that is done, the TI-RTOS kernel can be built. This step is not necessary
for No-RTOS examples. In order to build the kernel, select a specific
development board and build the release
configuration. The makefile can be
found in the folder
<SDK_INSTALL_DIR>/kernel/tirtos/builds/<BOARD>/release/<TOOLCHAIN>
.
Example:
$ cd /c/ti/simplelink_cc13x2_sdk_1_xx_xx_xx/kernel/tirtos/builds/CC1352R1_LAUNCHXL/release/gcc
$ make
Finally, the examples can be built. Navigate to the desired example and invoke make:
$ cd /c/ti/simplelink_cc13x2_sdk_1_xx_xx_xx/rtos/CC1352R1_LAUNCHXL/drivers/rfSynchronizedPacketRx/tirtos/gcc
$ make -j4
The resulting .out
file is a regular
ELF file that can be flashed to
the device or converted into a binary or an Intel Hex file for other purpose,
for instance, over-the-air download. Example for objcopy from the GNU
binutils package:
$ arm-none-eabi-objcopy -S --gap-fill 0xff -O binary rfSynchronizedPacketRx.out rfSynchronizedPacketRx.bin
$ arm-none-eabi-objcopy -S -O ihex rfSynchronizedPacketRx.out rfSynchronizedPacketRx.hex