Texas Instruments | TI-RTOS 2.16 for CC32xx SimpleLink Wireless MCUs (Rev. F) | User Guides | Texas Instruments TI-RTOS 2.16 for CC32xx SimpleLink Wireless MCUs (Rev. F) User guides

Texas Instruments TI-RTOS 2.16 for CC32xx SimpleLink Wireless MCUs (Rev. F) User guides
TI-RTOS 2.16 for CC32xx SimpleLink™
Wireless MCUs
Getting Started Guide
Literature Number: SPRUHU8F
February 2016
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1
About TI-RTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 What is TI-RTOS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 What are the TI-RTOS Components?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 How Can I Find Example Projects? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 What Compilers and Targets are Supported? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 What Boards and Devices Have TI-RTOS Driver Examples? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 What Drivers Does TI-RTOS Include? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
4
5
6
7
7
7
8
2
Installing TI-RTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Installing Code Composer Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Installing TI-RTOS in Code Composer Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Installing TI-RTOS for Use in IAR Embedded Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Installing TI-RTOS as a Standalone Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
10
11
11
12
12
3
Examples for TI-RTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Creating Example Projects Using the Resource Explorer in CCS . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Creating an Empty TI-RTOS Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 Creating Examples to Build via a Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Creating Examples with IAR Embedded Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Driver Examples: Readme Files and Common Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 CC3200 SimpleLink LaunchPad Settings and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 BoosterPacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1 SD Card BoosterPack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2 TMP006 I2C Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3 CC3200 BoosterPacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 <Board>.c File and PinMux Tool Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 Using Driverlib in ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
14
16
17
18
18
19
20
20
21
21
22
24
4
Configuring TI-RTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Starting the Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Configuring TI-RTOS Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Configuring System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Configuring Components of TI-RTOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
27
28
28
29
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
SPRUHU8F—February 2016
Submit Documentation Feedback
Contents
2
Preface
SPRUHU8F—February 2016
Read This First
About This Manual
This manual describes TI-RTOS for SimpleLink™ Wireless MCUs. The version number as of the
publication of this manual is v2.16.
Notational Conventions
This document uses the following conventions:
•
Program listings, program examples, and interactive displays are shown in a special typeface.
Examples use a bold version of the special typeface for emphasis.
Here is a sample program listing:
#include <xdc/runtime/System.h>
int main(void)
{
System_printf("Hello World!\n");
return (0);
}
•
Square brackets ( [ and ] ) identify an optional parameter. If you use an optional parameter, you
specify the information within the brackets. Unless the square brackets are in a bold typeface, do not
enter the brackets themselves.
Trademarks
Registered trademarks of Texas Instruments include Stellaris and StellarisWare.
Trademarks of Texas Instruments include: the Texas Instruments logo, Texas Instruments, TI, TI.COM,
C2000, C5000, C6000, Code Composer, Code Composer Studio, Concerto, controlSUITE, DSP/BIOS,
MSP430, MSP430Ware, MSP432, SimpleLink, Sitara, SPOX, TI-RTOS, Tiva, TivaWare, TMS320,
TMS320C5000, TMS320C6000, and TMS320C2000.
ARM is a registered trademark, and Cortex is a trademark of ARM Limited.
Windows is a registered trademark of Microsoft Corporation.
Linux is a registered trademark of Linus Torvalds.
IAR Systems and IAR Embedded Workbench are registered trademarks of IAR Systems AB.
All other brand or product names are trademarks or registered trademarks of their respective companies
or organizations.
February 15, 2016
SPRUHU8F—February 2016
Submit Documentation Feedback
Read This First
3
Chapter 1
SPRUHU8F—February 2016
About TI-RTOS
This chapter provides an overview of TI-RTOS for SimpleLink™ Wireless MCUs.
Topic
1.1
Page
1.1
What is TI-RTOS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2
What are the TI-RTOS Components? . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3
How Can I Find Example Projects? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4
What Compilers and Targets are Supported? . . . . . . . . . . . . . . . . . . . 7
1.5
What Boards and Devices Have TI-RTOS Driver Examples? . . . . . . . 7
1.6
What Drivers Does TI-RTOS Include? . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.7
For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
What is TI-RTOS?
TI-RTOS is a scalable, one-stop embedded tools ecosystem for TI devices. It
scales from a real-time multitasking kernel (SYS/BIOS) to a complete RTOS
solution including additional middleware components and device drivers. By
providing essential system software components that are pre-tested and preintegrated, TI-RTOS enables you to focus on creating your application.
TI-RTOS is not installed automatically as part of the Code Composer Studio v6.x
installation. You can install TI-RTOS from the CCS App Center (choose View >
CCS App Center in CCS). Choose the version of TI-RTOS for your device family.
If you use devices in multiple families, you can install multiple TI-RTOS versions. See Section 2.3 for
details.
If you do not use CCS, you can download and install TI-RTOS as a standalone product (see Section 2.5).
In addition to the Texas Instruments Code Generation Tools, TI-RTOS includes support for the IAR and
GNU tool chains (see Section 2.4).
TI-RTOS is provided with full source code and requires no up-front or runtime license fees.
SPRUHU8F—February 2016
Submit Documentation Feedback
About TI-RTOS
4
www.ti.com
1.2
What are the TI-RTOS Components?
What are the TI-RTOS Components?
TI-RTOS contains its own source files, pre-compiled libraries (both instrumented and non-instrumented),
and examples. Additionally, TI-RTOS contains a number of components within its "products"
subdirectory. The components of TI-RTOS for SimpleLink Wireless MCUs are as follows.
Table 1–1. TI-RTOS Components
TI-RTOS Component
Name
Documentation Location
TI-RTOS
TI-RTOS examples
Chapter 3 of this Getting Started Guide
TI-RTOS Kernel
SYS/BIOS
SYS/BIOS (TI-RTOS Kernel) User’s Guide -- SPRUEX3
TI-RTOS Drivers & Board Support Drivers and CC3200
SDK's driverlib
TI-RTOS User's Guide -- SPRUHD4
TI-RTOS Instrumentation
UIA
System Analyzer User’s Guide -- SPRUH43
TI-RTOS Network Services
Network Services
<tirtos_install>/products/ns_<version>/docs/
NS_Users_Guide.html
TI-RTOS File System
FatFS
TI-RTOS User's Guide -- SPRUHD4
The components in the "products" subdirectory are:
•
TI-RTOS Kernel — SYS/BIOS. SYS/BIOS is a scalable real-time kernel. It is designed to be used
by applications that require real-time scheduling and synchronization or real-time instrumentation. It
provides preemptive multi-threading, hardware abstraction, real-time analysis, and configuration
tools. SYS/BIOS is designed to minimize memory and CPU requirements on the target.
•
TI-RTOS Drivers and Board Support. TI-RTOS includes drivers for a number of peripherals. These
drivers are thread-safe for use with the TI-RTOS Kernel. The drivers have a common framework, so
using multiple drivers in your application is easy. Both instrumented and non-instrumented versions
of the drivers are provided. Board support files to configure the drivers is provided for several targets.
•
TI-RTOS Instrumentation — UIA. The Unified Instrumentation Architecture (UIA) provides target
content that aids in the creation and gathering of instrumentation data (for example, Log data).
•
TI-RTOS Network Services. The Network Services component provides application layer network
protocols, such as an HTTP Client and an SNTP Client.
•
SimpleLink CC3200 Driverlib is a subset of the SimpleLink Wi-Fi CC3200 Software Development
Kit (SDK) needed to use the drivers with CC3200. The Wi-Fi functionality is not included in this
driverlib subset; to use Wi-Fi, download and install the SimpleLink Wi-Fi CC3200 Software
Development Kit (SDK). You can download this SDK at http://www.ti.com/tool/cc3200sdk. For
details about using the Wi-Fi examples in the SDK, see the TI-RTOS CC3200Wireless wiki page.
•
XDCtools. This core component provides the underlying tooling for configuring and building TIRTOS and its components. XDCtools is installed as part of CCS v6.x. If you install TI-RTOS outside
CCS, a compatible version of XDCtools is installed automatically. XDCtools is installed in a directory
at the same level as TI-RTOS, not in the "products" directory of the TI-RTOS installation.
SPRUHU8F—February 2016
Submit Documentation Feedback
About TI-RTOS
5
How Can I Find Example Projects?
1.3
www.ti.com
How Can I Find Example Projects?
TI-RTOS and its components provide numerous examples that you can import using the Resource
Explorer in Code Composer Studio (CCS). These examples use TI-RTOS and its components and have
all the settings needed for your device. Expand the tree in the Resource Explorer to see the examples
that are available for your device.Resource Explorer provides TI-RTOS examples for both the TI and
GNU tool chains.
•
•
•
Driver Examples are TI-RTOS driver examples.
Instrumentation Examples are UIA examples.
Kernel Examples are the SYS/BIOS examples.
Follow the steps in Section 3.1 to import, build, and run these examples.
6
About TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
1.4
What Compilers and Targets are Supported?
What Compilers and Targets are Supported?
The following code generation tool (compilers and linkers) versions are supported. The versions listed
are recommended because they were used to build the TI-RTOS libraries and to perform testing. More
recent versions are expected to be compatible.
•
•
•
Texas Instruments: ARM CodeGen Tools v5.2.2
GCC: gcc-arm-none-eabi-4_8-2014q3
IAR Workbench for ARM: 7.40.3
The configuration uses a "target" specification during the build. This specification is sometimes called the
"RTSC target." The targets supported are:
•
1.5
CC3xxx
— ti.targets.arm.elf.M4
— iar.targets.arm.M4
— gnu.targets.arm.M4
What Boards and Devices Have TI-RTOS Driver Examples?
Currently, TI-RTOS provides driver examples for the following board:
Family
Device on Board
Board
ARM
CC3200
CC3200 LaunchPad
(called CC3200_LAUNCHXL in TI-RTOS code)
Examples are provided specifically for the supported boards, but libraries are provided for each of these
device families, so that you can port the examples to similar boards. Porting information for TI-RTOS is
provided on the Texas Instruments Wiki.
1.6
What Drivers Does TI-RTOS Include?
TI-RTOS includes drivers for the following peripherals. These drivers are in the
<install_dir>/products/tidrivers_<version>/packages/ti/drivers directory. TI-RTOS
examples show how to use these drivers. Note that all of these drivers are built on top of the driverlib from
the CC3200 SDK.
The TI-RTOS installation installed drivers for multiple device families. The following list indicates which
drivers can be use with CC32xx targets:
•
•
Camera. APIs to retrieve data transferrer by a camera sensor.
•
•
•
I2C. API set intended to be used directly by the application or middleware.
•
PWM. API set intended to be used directly by the application or middleware to generate Pulse Width
Modulated signals.
•
SPI. API set intended to be used directly by the application or middleware to communicate with the
Serial Peripheral Interface (SPI) bus. SPI is sometimes called SSI (Synchronous Serial Interface).
GPIO. API set intended to be used directly by the application or middleware to manage the GPIO
interrupts, pins, and ports.
I2S. API set for support of Inter-IC Sound interface standard.
Power. Power management framework. See the TI-RTOS Power Management User’s Guide
(SPRUI18).
SPRUHU8F—February 2016
Submit Documentation Feedback
About TI-RTOS
7
For More Information
1.7
www.ti.com
•
SDSPI. Driver for SD cards using a SPI (SSI) bus. This driver is used by the FatFS and not intended
to be called directly by the application.
•
•
UART. API set intended to be used directly by the application to communicate with the UART.
Watchdog. API set intended to be used directly by the application or middleware to manage the
watchdog timer.
For More Information
To see release notes for a component, go to the subdirectory for that component within the TI-RTOS
products directory. For example,
C:\ti\tirtos_simplelink_2_##_##_##\products\bios_6_40_##_## contains release notes for
SYS/BIOS.
To see user guide PDFs and other documentation for a component, go to the "docs" subdirectory within
the directory that contains the release notes.
To learn more about TI-RTOS and its components, refer to the following documentation:
•
TI-RTOS
— TI-RTOS User’s Guide (SPRUHD4)
— In the TI-RTOS Release Notes, follow the Documentation Overview link. In the Documentation
Overview page, choose the TI-RTOS Drivers Runtime APIs (doxygen) item.
— TI-RTOS on the Texas Instruments Wiki
— TI-RTOS forum on TI’s E2E Community
— TI-RTOS Porting Guide
— Embedded Software Download Page
•
Code Composer Studio (CCS)
— CCS online help
— CCSv6 on the Texas Instruments Wiki
— Code Composer forum on TI’s E2E Community
•
SYS/BIOS
— SYS/BIOS User’s Guide (SPRUEX3)
— SYS/BIOS API and configuration reference. In the TI-RTOS Release Notes, follow the
Documentation Overview link. In the Documentation Overview page, choose the TI-RTOS
Kernel Runtime APIs and Configuration (cdoc) item.
— SYS/BIOS on the Texas Instruments Wiki
— TI-RTOS forum on TI’s E2E Community
— SYS/BIOS 6.x Product Folder
•
XDCtools
— SYS/BIOS User’s Guide (SPRUEX3)
— XDCtools online reference. Open from CCS help or run <xdc_install>/docs/xdctools.chm.
— RTSC-Pedia Wiki
— TI-RTOS forum on TI’s E2E Community
8
About TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
•
For More Information
UIA
— System Analyzer User’s Guide (SPRUH43)
— UIA API and configuration reference. In the TI-RTOS Release Notes, follow the Documentation
Overview link. In the Documentation Overview page, choose the TI-RTOS Instrumentation
Runtime APIs and Configuration (cdoc) item.
— System Analyzer on the Texas Instruments Wiki
•
FatFS API
— Open source documentation
— TI-RTOS User’s Guide (SPRUHD4)
•
General microcontroller information
— Microcontrollers forum on TI’s E2E Community
•
SimpleLink resources
— SimpleLink WiFi Overview
— CC3100 Boosterpack
— CC3100 WiFi SDK
— CC31xx/CC32xx Main Wiki Page
— CC31xx & CC32xx E2E Forum
— CC3200 LaunchPad
— CC3200 WiFi SDK
— SimpleLink Wi-Fi CC3200 Audio BoosterPack
— Camera BoosterPack for SimpleLink Wi-Fi CC3200 LaunchPad
— SimpleLink WiFi Radio Tool
— CC3200 Programmer’s Guide (SWRU369)
— CC3200 Technical Reference Manual (SWRU367)
•
I2C
— Specification
SPRUHU8F—February 2016
Submit Documentation Feedback
About TI-RTOS
9
Chapter 2
SPRUHU8F—February 2016
Installing TI-RTOS
This chapter covers the steps to install TI-RTOS within Code Composer Studio or as a standalone
software product.
Topic
2.1
Page
2.1
System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2
Installing Code Composer Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3
Installing TI-RTOS in Code Composer Studio . . . . . . . . . . . . . . . . . . 11
2.4
Installing TI-RTOS for Use in IAR Embedded Workbench. . . . . . . . . 12
2.5
Installing TI-RTOS as a Standalone Product . . . . . . . . . . . . . . . . . . . 12
System Requirements
The Microsoft Windows version of TI-RTOS can be installed on systems running Windows 8, Windows 7,
Windows Vista, or Windows XP (SP2 or SP3).
The Linux version of TI-RTOS can be installed on systems that are running Linux RedHat v4 and higher
or Ubuntu v10.04 and higher.
Separate versions of TI-RTOS are available for various Texas Instruments device families.
In order to install TI-RTOS, you must have at least 1 GB of free disk space. (If you have not yet installed
Code Composer Studio, you will also need at least 4 GB of disk space for that installation.)
SPRUHU8F—February 2016
Submit Documentation Feedback
Installing TI-RTOS
10
www.ti.com
2.2
Installing Code Composer Studio
Installing Code Composer Studio
TI-RTOS is used in conjunction with Code Composer Studio 6.1 or higher. (TI-RTOS can also be used
with the IAR Embedded Workbench IDE. See page 12 for more information.) CCS is available for
Microsoft Windows and Linux.
For Windows installations, we recommend that you install CCS in the default installation directory of
c:\ti. If you install in c:\Program Files (or c:\Program Files (x86) with Windows 7), you are likely to run
into problems related to Windows security permissions.
Note:
Do not install CCS in a location that contains any spaces in the full path. For example,
CCS should not be installed in c:\Program Files. Makefiles may not function correctly
with directory paths that include spaces.
To install CCS 6.x, go to the "Download CCS" page on the Texas Instruments wiki and follow a link to
download the software for your license type. For multi-user licenses, see the CCS product page.
Run the installer, and answer the prompts as appropriate.
2.3
Installing TI-RTOS in Code Composer Studio
TI-RTOS is not installed automatically as part of the Code Composer Studio v6.x
installation. Instead, you can install it through the CCS App Center as described
in this section, for use in IAR Workbench as described in Section 2.4, or as a
standalone product as described in Section 2.5.
Follow these steps to install TI-RTOS in CCS:
1. Run CCS v6.1 or higher.
2. Choose View > CCS App Center in CCS.
3. Select the version of TI-RTOS for your device family. If you use devices from multiple families, you
can select multiple TI-RTOS versions.
4. Click the Install Software button near the top of the App Center view.
5. Answer the prompts as necessary to complete the TI-RTOS installation.
6. Restart CCS in order for TI-RTOS and its components to be available.
SPRUHU8F—February 2016
Submit Documentation Feedback
Installing TI-RTOS
11
Installing TI-RTOS for Use in IAR Embedded Workbench
2.4
www.ti.com
Installing TI-RTOS for Use in IAR Embedded Workbench
You can install TI-RTOS for use with IAR Embedded Workbench as follows:
1. Install IAR Embedded Workbench for Texas Instruments ARM devices. See Section 1.4 for the
supported versions of IAR Workbench.
2. Download the Windows installer for TI-RTOS for SimpleLink. For example,
tirtos_setupwin32_simplelink_2_##_##_##.exe.
3. Run the downloaded file to install the full TI-RTOS product. You can install TI-RTOS in a standalone
directory. Installing in a directory path that contains spaces, such as C:\Program Files (x86), is
not supported.
Note: TI-RTOS installs the core functionality of the XDCtools component if you have not already
installed the necessary version as part of a CCS installation. TI-RTOS places XDCtools in a separate
directory at the same level where you install TI-RTOS. For example, if the TI-RTOS installation
directory is C:\ti\tirtos_simplelink_2_##_##_##, the XDCtools directory will be
C:\ti\xdctools_3_31_##_##_core.
Follow the instructions in Section 3.1.2 to complete the installation of the TI-RTOS examples. See
Section 3.2 to build the examples with the IAR compiler and to load and run the examples with IAR
Embedded Workbench.
2.5
Installing TI-RTOS as a Standalone Product
If you do not use Code Composer Studio, you can install TI-RTOS as a standalone product. In addition
to compiling and linking with the Texas Instruments Code Generation Tools, TI-RTOS includes support
for the IAR and GNU tool chains (GNU is supported for CC3xxx only).
1. Download the Windows or Linux installer for TI-RTOS for the device family you use. For example,
tirtos_setupwin32_simplelink_2_##_##_##.exe or
tirtos_setuplinux_simplelink_2_##_##_##.bin.
2. Run the downloaded file to install TI-RTOS. You can install TI-RTOS in a standalone directory.
Installing in a directory path that contains spaces, such as C:\Program Files (x86), is not
supported.
Note: TI-RTOS installs the core functionality of the XDCtools component if you have not already
installed the necessary version as part of a CCS installation. TI-RTOS places XDCtools in a separate
directory at the same level where you install TI-RTOS. For example, if the TI-RTOS installation
directory is located in C:\ti\tirtos_simplelink_2_##_##_##, the XDCtools directory will be in
C:\ti\xdctools_3_31_##_##_core.
Follow the instructions in Section 3.1.2 to complete the installation of the TI-RTOS examples.
12
Installing TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
Chapter 3
SPRUHU8E—February 2016
Examples for TI-RTOS
TI-RTOS comes with a number of examples that illustrate on how to use the individual components. This
chapter explains how to create and use these examples.
Topic
Page
3.1
Creating Example Projects Using the Resource Explorer in CCS . . 14
3.2
Creating Examples with IAR Embedded Workbench . . . . . . . . . . . . . 18
3.3
Driver Examples: Readme Files and Common Features . . . . . . . . . . 18
3.4
CC3200 SimpleLink LaunchPad Settings and Resources . . . . . . . . . 19
3.5
BoosterPacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6
<Board>.c File and PinMux Tool Integration. . . . . . . . . . . . . . . . . . . . 22
3.7
Using Driverlib in ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
SPRUHU8F—February 2016
Submit Documentation Feedback
Examples for TI-RTOS
13
Creating Example Projects Using the Resource Explorer in CCS
3.1
www.ti.com
Creating Example Projects Using the Resource Explorer in CCS
You can use the Resource Explorer
in Code Composer Studio (CCS) to
create example projects that use TIRTOS and its components and have
all the settings needed for your
device. Follow these steps:
1. Open CCS. If you do not see the
Resource Explorer, make sure
you are in the CCS Edit
perspective and choose View >
Resource Explorer (Examples)
from the menus.
2. Type the name or part of the
name of your device in the enter
search keyword field to hide all
the examples that don’t apply to
your device. Or, type "Driver
Examples" to find driver
examples.
3. Expand the tree until you see the
examples for your device. Any
Driver Examples listed are TIRTOS driver examples. Any
Instrumentation Examples listed are UIA examples. The Kernel Examples are the TI-RTOS
Kernel (SYS/BIOS) examples. Resource Explorer provides TI-RTOS examples for both the TI and
GNU tool chains.
4. Select the example you want to create. A description of the selected example is shown to the right
of the example list.
5. Click the Step 1 link in the right pane of the Resource Explorer to Import the example project into
CCS. This adds a new project to your Project Explorer view. Once you have completed a step for a
particular example and device, a green checkmark will be shown next to that step.
Note: CCS will not allow two projects with the same name in a workspace. If you want to import both
TI and GNU projects for the same board and example in the same workspace, you would need to
rename the first project you import before importing the second version.
14
Examples for TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
Creating Example Projects Using the Resource Explorer in CCS
6. The project created will have a name with the format <example_name>_<board>. You can expand
the project to see the source code, configuration, and other files in the project.
7. The page shown when you select an example in the Resource Explorer provides additional links to
perform common actions with that example. Use the Step 2 link when you are ready to build the
project. If you want to change any build options, right click on the project and select Properties from
the context menu. For example, you can change compiler, linker, and RTSC (XDCtools) options.
8. Use the Step 3 link to change the connection used to communicate with the board. The current
setting is shown in the Resource Explorer page for the selected example.
SPRUHU8F—February 2016
Submit Documentation Feedback
Examples for TI-RTOS
15
Creating Example Projects Using the Resource Explorer in CCS
www.ti.com
9. You will see the Debugger Configuration dialog. Choose an emulator. For CC32xx SimpleLink
devices, choose the Stellaris In-Circuit Debug Interface.
10. Use the Step 4 link to launch a debug session for the project and switch to the CCS Debug
Perspective.
3.1.1
Creating an Empty TI-RTOS Project
TI-RTOS provides blank projects you can use as a starting point for creating your own projects that utilize
TI-RTOS. Both "Empty" and "Empty (Minimal)" versions are provided. The "Empty" version enables more
kernel features and debug capabilities at the cost of large footprint. The "Empty (Minimal)" version
disables various kernel features and debug capabilities to minimize the footprint. See the "Memory Usage
with TI-RTOS" chapter in the TI-RTOS User’s Guide (SPRUHD4) for details about techniques used to
minimize the footprint.
Empty TI-RTOS driver projects can be created with the Resource Explorer (see Section 3.1).
After you create the example, the files in the empty project example include:
•
•
•
Key C files: empty.c, <board>.c/.h
Key configuration files: empty.cfg
Linker command file: <board>.cmd
Add to the example as needed to implement your application.
16
Examples for TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
3.1.2
Creating Example Projects Using the Resource Explorer in CCS
Creating Examples to Build via a Command Line
TI-RTOS has a command-line utility called examplesgen that generates example projects along with the
makefiles needed to build the examples for all supported tool chains—TI and IAR and GNU. The files are
created in a location you specify on the command line. The tirtos.mak file in the top level directory of
your TI-RTOS installation can be used to run examplesgen.
Note:
If you installed TI-RTOS using the standalone installer (Section 2.5 or Section 2.4), this
step is not necessary because pre-generated examples are included as part of the
installation for all supported boards and tool chains. The provided examples are
located in the TIRTOS_INSTALL_DIR\tirtos_simplelink_2_##_##_##_examples
directory. Pre-generated examples are not provided if you installed TI-RTOS through
the CCS App Center.
You only need to perform these steps once:
1. If you installed TI-RTOS in a location other than the default location of C:\ti, edit the tirtos.mak file
in the TI-RTOS installation directory. Modify the following variables as needed to make them point to
the correct locations.
— DEFAULT_INSTALL_DIR: Full path to the location where TI tools are installed.
— IAR_COMPILER_INSTALL_DIR: Full path to the IAR code generation tools installation.
— GCC_INSTALLATION_DIR: Full path to the GCC code generation tools installation.
— TIRTOS_INSTALL_DIR: Full path to the TI-RTOS installation.
— XDCTOOLS_INSTALL_DIR: Full path to the XDCtools installation.
2. If you plan to use TI-RTOS with IAR, set the IAR_BUILD variable in the tirtos.mak file to true.
IAR_BUILD ?= true
3. If you plan to use TI-RTOS with GCC, set the GCC_BUILD variable in the tirtos.mak file to true.
GCC_BUILD ?= true
4. Open a command line window, and use the following commands to run the examplesgen utility. (If
you installed TI-RTOS in a protected directory, you should run the command window as the
administrator.)
> cd <tirtos_install>
> ..\xdctools_3_31_##_##_core\gmake -f tirtos.mak examplesgen DEST="YOURPATH"
For the destination path, use a UNIX-style path. That is, use forward slashes (/) instead of
backslashes (\). For example, DEST="C:/myfiles".
The output from this command is a tirtos_simplelink_2_##_##_##_examples directory tree
containing folders for the supported boards. Each board folder contains folders for all the examples
available for that board.
Examples for TI and IAR and GNU are generated for boards supported by TI-RTOS. Each board directory
contains a makedefs file that can be modified to specify other installation paths or compiler/linker options
and a makefile that can be used to build all the examples for that board. Each example directory has its
own makefile that can be used to build that example specifically.
SPRUHU8F—February 2016
Submit Documentation Feedback
Examples for TI-RTOS
17
Creating Examples with IAR Embedded Workbench
3.2
www.ti.com
Creating Examples with IAR Embedded Workbench
For information about using TI-RTOS examples with IAR Embedded Workbench, see the wiki page on
Creating TI-RTOS Applications in IAR Embedded Workbench on the Texas Instruments wiki.
3.3
Driver Examples: Readme Files and Common Features
Details about the driver examples are provided in the readme files in the example projects. There is a
separate <example_name>_readme file for each of the examples. These files are added to your CCS
project when you use the Resource Explorer to create a project. You can open the
<example_name>_readme file within CCS. The <example_name>_readme files contain the following
types of information:
•
•
•
Actions performed by functions in the example.
Hardware-specific descriptions of buttons, LEDs, etc…
Which external components are (or may be) needed to run with particular examples.
There are several TI-RTOS example categories. The Empty and Empty (Minimal) projects are configured
to make TI-RTOS available but do not contain specific code that uses TI-RTOS. The Demo examples use
several peripherals working together. The remaining examples show how to use a specific peripheral.
The Driver Examples share the following features:
•
Most TI-RTOS driver examples use the SysMin System Support module. See the readme files in the
individual example projects for details.
•
The empty, demo, and most UART examples use the ti.uia.sysbios.LoggingSetup module with stop
mode data collection. The UART Console example uses run-time data collection during Idle thread
processing. For more details on data collection, see Chapter 2 of the TI-RTOS User’s Guide
(SPRUHD4).
•
Driver Examples for a particular target all have the same <board>.c and <board>.h files. These files
perform board-specific configuration of the drivers provided by TI-RTOS. For more details, see
Chapter 4 of the TI-RTOS User’s Guide (SPRUHD4).
The sections that follow list settings required to run the TI-RTOS examples on the supported boards.
They also list the hardware resources that TI-RTOS and its dependent components use by default. Some
of these resources offer flexible options, whereas others are fixed in the current design or
implementation.
18
Examples for TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
3.4
CC3200 SimpleLink LaunchPad Settings and Resources
CC3200 SimpleLink LaunchPad Settings and Resources
The CC3200 SimpleLink LaunchPad contains a CC3200 device.
Micro-B USB for
power, emulation,
UART examples
TMP006 I2C
Temperature
Sensor
Set jumpers J6 and J7 to
“Flash” to route UART0
to the emulator.
Close jumpers J2
and J3 to connect
the TMP006 to the
I2C0 bus.
Board_LED0
(CC3200_LAUNCHXL_LED_D7)
Board_LED1
(CC3200_LAUNCHXL_LED_D6)
Board_LED2
(CC3200_LAUNCHXL_LED_D5)
Board_BUTTON1
(CC3200_LAUNCHXL_SW3)
Board_BUTTON0
(CC3200_LAUNCHXL_SW2)
The Micro-B connector on the CC3200 LaunchPad can be used for power, debugger emulation, and
UART communications.
Jumper Settings:
•
•
To use the TMP006 I2C temperature sensor, close jumpers J2 and J3.
To use the UART connected to the emulator, move jumpers J6 and J7 into the "flash" (2-3) position.
Switch Settings:
•
SW2: Some examples use PIN 15 as a GPIO input.
SPRUHU8F—February 2016
Submit Documentation Feedback
Examples for TI-RTOS
19
BoosterPacks
•
www.ti.com
SW3: Some examples use PIN 04 as a GPIO input.
Resources Used:
•
TI-RTOS Kernel (SYS/BIOS). Uses the Cortex M4’s SYSTICK timer and that timer's associated
interrupts. The TI-RTOS Kernel manages the Interrupt Vector Table.
•
TI-RTOS.
— GPIOs. The GPIO driver uses 3 output pins for the onboard LEDs and 2 input pins for switches
SW2 (PIN 15) and SW3 (PIN 04).
— I2C. The I2C driver is configured on I2CA0 to support various BoosterPacks or onboard
peripherals.
— PWM. The PWM driver uses the onboard LEDs D5 (PIN 02) and D6 (PIN 01). While these pins
coincide with GPIO driver pins, they are configured for the PWM driver for the PWM examples.
The GPIO driver APIs should not be used.
— SD Card. Uses FatFs and the SDSPI driver on GSPI without interrupts to read and write to files.
— Serial. The UART driver uses UARTA0, which is attached to the FTDI USB chip to facilitate serial
communications.
— SPI. The SPI driver uses GSPI for Board_SPI0 and LSPI for Board_SPI1.
— Watchdog. The Watchdog example uses the Watchdog Timer and its associated interrupt.
3.5
BoosterPacks
Several BoosterPack boards are used with the TI-RTOS examples. This section described those boards
and provides any special notes about installing the board.
3.5.1
SD Card BoosterPack
A microSD BoosterPack or SD Card BoosterPack should be used with examples that require an SD Card
reader on target boards that do not include an SD Card reader. This board may be used with the CC3200.
The figure below shows the jumper needed on the microSD BoosterPack to make it pin-compatible with
the SD Card BoosterPack.
J5: Position 2
20
Examples for TI-RTOS
J6: Open
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
BoosterPacks
TMP006 I2C Sensor
3.5.2
While other boards require an additional TMP006 BoosterPack to run the I2CTMP006 example, the
CC3200_LAUNCHXL board already has a TMP006 temperature sensor on the board. Simply close
jumpers J2 and J3 on the LaunchPad to connect the TMP006 sensor to the I2C bus. Refer the picture in
Section 3.4 to see where these jumpers are located on the C3200 board.
3.5.3
CC3200 BoosterPacks
The BoosterPacks add functionality to your SimpleLink board to support examples that require additional
peripherals. The following BoosterPacks are supported for the CC3200.
•
Audio BoosterPack for SimpleLink Wi-Fi CC3200. Use with the TI-RTOS I2S Echo example,
which uses the I2S driver to echo back the audio received from the microphone over the speaker.
See the user’s guide for this BoosterPack (SWRU383) for details.
SPRUHU8F—February 2016
Submit Documentation Feedback
Examples for TI-RTOS
21
<Board>.c File and PinMux Tool Integration
•
3.6
www.ti.com
Camera BoosterPack for SimpleLink Wi-Fi CC3200 LaunchPad. Use with the Camera example
provided in the SimpleLink Wi-Fi CC3200 Software Development Kit (SDK).
<Board>.c File and PinMux Tool Integration
For every board supported in each TI-RTOS product, there
are three common files that are used in all the driver
examples.
22
•
Board.h. This is a small shim file that allows example
code (for example, uartecho.c) to be used on different
boards in different TI-RTOS products.
•
<Board>.c/.h files. For example, CC3200_LP.c and
CC3200_LP.h in this picture. These files are specific to a
board. The same files are used for all driver examples for
that board.
Examples for TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
<Board>.c File and PinMux Tool Integration
For CC32xx, the TI PinMux Tool was used to generate the
pinmux code for the TI-RTOS examples. You can install the TI
PinMux Tool from the CCS App Center.
For example, the pin_mux_config.h and
uartecho_pin_mux_config.c files were generated by the TI
PinMux Tool based on the uartecho.pinmux project. The
generated pin_mux_config.c file was renamed to
uartecho_pin_mux_config.c so that the pinmux project and
generated files for each driver example are uniquely named.
The <Board>.c file accommodates the use of the PinMux
Tool. For example, the Board_initGeneral() function for the
CC3200 is as follows, where the PinMuxConfig() function is in
the generated uartecho_pin_mux_config.c file).
void CC3200_LAUNCHXL_initGeneral(void)
{
PinMuxConfig();
}
The pinxmux code is removed from the peripheral initialization function. For example in the
CC3200_LAUNCHXL_initI2C function makes only the driver initialization call:
void CC3200_LAUNCHXL_initI2C(void)
{
I2C_init();
}
When peripherals are added or removed, the driver configuration structures in the <Board>.c/.h files must
be manually changed. For example if an additional I2C is added, the following structures in
CC3200_LAUNCHXL.c must be manually updated (as well as the enums in the CC3200_LAUNCHXL.h
file):
I2CCC3200_Object i2cCC3200Objects[ CC3200_LAUNCHXL_I2CCOUNT ];
/* I2C configuration structure */
const I2CCC3200_HWAttrs i2cCC3200HWAttrs[ CC3200_LAUNCHXL_I2CCOUNT ] = {
{ I2CA0_BASE, INT_I2CA0 }
};
const I2C_Config I2C_config[] = {
{ &I2CCC3200_fxnTable, &i2cCC3200Objects[0], &i2cCC3200HWAttrs[0] },
{ NULL, NULL, NULL }
};
Please refer to Section 5.2, "Driver Framework" in the TI-RTOS User’s Guide for details on managing
these structures.
SPRUHU8F—February 2016
Submit Documentation Feedback
Examples for TI-RTOS
23
Using Driverlib in ROM
www.ti.com
Note that a #if directive in the <Board>.c file is used to include or exclude initialization code. For example
#if TI_DRIVERS_I2C_INCLUDED
#include <ti/drivers/I2C.h>
#include <ti/drivers/i2c/I2CCC3200.h>
#include <driverlib/i2c.h>
I2CCC3200_Object i2cCC3200Objects[CC3200_LAUNCHXL_I2CCOUNT];
...
void CC3200_LAUNCHXL_initI2C(void)
{
I2C_init();
}
#endif /* TI_DRIVERS_I2C_INCLUDED */
The #defines are generated and set to 1 when a driver is included by the .cfg file. It is set to 0 when the
driver is not included in the .cfg file.
3.7
Using Driverlib in ROM
The ROM on the CC3200 rev 1.33 includes a version of driverlib. By default, TI-RTOS drivers (such as
UART and SDSPI) and examples do not use this ROM version of driverlib. Instead they link with driverlib
functions in the <tirtos_install_dir>/products/CC3200_driverlib_<version>/driverlib
library. However, both the TI-RTOS drivers and examples call MAP_xyz driverlib functions with the same
names and calling syntax as those in ROM. They can thus be rebuilt to use the ROM functions (as
described in the rest of this section).
To use the driverlib functions in ROM, you will need to define TARGET_IS_CC3200 and rebuild both the
TI-RTOS driver libraries and the application. Follow these steps to perform the necessary builds:
1. Edit the <tirtos_install_dir>\tirtos.bld file and add TARGET_IS_CC3200 into the ccOpts
definition as follows:
var ccOpts = {
"ti.targets.arm.elf.M4" : " -ms -g --gcc --define=ccs -DTARGET_IS_CC3200 ",
"iar.targets.arm.M4"
: " -Dewarm –DIAR -DTARGET_IS_CC3200 ",
"gnu.targets.arm.M4"
: " -g -D gcc -DTARGET_IS_CC3200 ",
};
2. Rebuild the driver libraries as explained in the “Rebuilding TI-RTOS” chapter in the TI-RTOS User
Guide (SPRUHD4). For example:
% ..\<xdctools>\gmake –f tirtos.mak drivers
3. Define TARGET_IS_CC3200 for builds of the application project.
24
Examples for TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
Using Driverlib in ROM
In CCS or IAR you can modifying the project properties to add the predefined symbol. For example
for project that uses a TI compiler within CCS, you can choose Project > Properties from the menus
and go to the Build > ARM Compiler > Advanced Options > Predefined Symbols category to add
TARGET_IS_CC3200 to the list of Pre-defined names.
If you are not using an IDE, add TARGET_IS_CC3200 to the makedefs file in the generated
command-line examples. For example, this command line for the TI compiler includes the symbol
definition (in bold).
CFLAGS = -mv7M4 --code_state=16 --abi=eabi -me -DPART_CC3200 -g
--display_error_number --diag_warning=255 --diag_wrap=off -DTARGET_IS_CC3200
-Dccs -DCCWARE -I$(CCWARE_INSTALLATION_DIR) -I$(CCWARE_INSTALLATION_DIR)/inc
-I$(CCWARE_INSTALLATION_DIR)/driverlib
4. Rebuild your application.
SPRUHU8F—February 2016
Submit Documentation Feedback
Examples for TI-RTOS
25
Chapter 4
SPRUHU8F—February 2016
Configuring TI-RTOS
This chapter describes how to configure TI-RTOS and its components for use by your application.
Topic
Page
4.1
Starting the Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2
Configuring TI-RTOS Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.3
Configuring Components of TI-RTOS . . . . . . . . . . . . . . . . . . . . . . . . . 29
SPRUHU8F—February 2016
Submit Documentation Feedback
Configuring TI-RTOS
26
www.ti.com
4.1
Starting the Configuration Tool
Starting the Configuration Tool
Note:
The graphical configuration tool is not available within IAR Embedded Workbench. If
you are using IAR, edit the project’s *.cfg file within IAR as a text-based source file. See
the Texas Instruments Wiki for more about using IAR with TI-RTOS.
This section shows how to open the Graphical Configuration Tool (XGCONF) to view the System
Overview. For details on using XGCONF, see Chapter 2 of the SYS/BIOS User’s Guide (SPRUEX3).
To use CCS to open the graphical tool for editing configuration files (XGCONF), follow these steps:
1. Make sure you are in the CCS Edit perspective of CCS. If you
are not in that perspective, click the CCS Edit icon to switch back.
2. Double-click on the *.cfg configuration file for a TI-RTOS
example project in the Project Explorer tree. (See Section 3.1 if
you need to create an example project.) While XGCONF is
opening, the CCS status bar shows that the configuration is
being processed and validated.
3. When XGCONF opens, you see the Welcome sheet for TI-RTOS if you are using a Driver example.
(If this is the configuration file for a Kernel example or an Instrumentation example, the Welcome
sheet for SYS/BIOS opens first, instead.) The Welcome sheet provides links to documentation
resources.
4. Click the System Overview link to see a diagram of the components available through TI-RTOS.
(SYS/BIOS modules are shown if you are using a Kernel example or an Instrumentation example.)
A green check mark indicates the modules that are being used by the application.
SPRUHU8F—February 2016
Submit Documentation Feedback
Configuring TI-RTOS
27
Configuring TI-RTOS Drivers
www.ti.com
5. You also see a list of Available Products in a pane on the left of the
CCS window. This list allows you to select the TIRTOS module
and any configurable modules in the products TI-RTOS provides.
6. Click a blue box in the System Overview to go to the configuration
page for a module.
Note: If the configuration is shown in a text editor instead of XGCONF,
close the text editor window. Then, right-click on the *.cfg file and
choose Open With > XGCONF. If you are comfortable editing
configuration scripts with a text editor, you can do that. However, you
should not have the file open in both types of editor at the same time.
4.2
Configuring TI-RTOS Drivers
In the System Overview display for the TIRTOS module, click on the
TI-RTOS Drivers block.
You can choose to use either the instrumented or non-instrumented driver libraries when linking with TIRTOS. The instrumented libraries process Log events while the non-instrumented libraries do not. See
the section on "Using Instrumented or Non-Instrumented Libraries" in the TI-RTOS User’s Guide
(SPRUHD4) for more information. This setting affects all the TI-RTOS drivers listed in Section 1.6
together.
All of the TI-RTOS drivers are available to your application without being separately enabled. To reduce
code size, only the driver code that your application needs to use will be compiled into your application.
4.2.1
Configuring System Support
The SysCallback module lets you configure the functions that handle System output—for example,
System_printf() and System_abort(). This module handles transmissions to System output only; it does
not handle responses received. See the chapter on "TI-RTOS Utilities" in the TI-RTOS User’s Guide
(SPRUHD4) for more about the SysCallback module.
28
Configuring TI-RTOS
SPRUHU8F—February 2016
Submit Documentation Feedback
www.ti.com
Configuring Components of TI-RTOS
Other SystemSupport implementations are provided with XDCtools.
4.3
•
SysMin stores System_printf() strings in an internal buffer in RAM. SysMin requires RAM, so it not
ideal for devices with minimal RAM.
•
SysStd writes System_printf() strings to STDOUT (the CCS Console window). By default, SysStd
allows System_printf() to be called from Tasks only (not Swis or hardware interrupts); it can be
modified to allow calls from Swis and Hwis, but this impacts real-time performance.
Configuring Components of TI-RTOS
For information about configuring individual sub-components of TI-RTOS, see the documentation for that
component. Chapter 2 of the SYS/BIOS User’s Guide (SPRUEX3) provides details about XGCONF.
Within XGCONF, you can see the full file path to the version of the component being used by hovering
your mouse cursor over a component in the "Other Products" list in the Available Products area.
SPRUHU8F—February 2016
Submit Documentation Feedback
Configuring TI-RTOS
29
Index
SPRUHU8F—February 2016
Index
A
resources used
App Center 11
Available Products list 28
20
I
I2C driver 7
I2S driver 7
installation
CCS 11
directory 11
instrumentation 5
instrumented libraries
B
BoosterPacks 20
SD Card 20
28
C
K
Camera driver 7
CC3200 LaunchPad 7
CCS
creating a project 6, 14
installation 11
other documentation 8
CCS App Center 4, 11
components 5
Concerto
other documentation 9
configuration 26
graphical editor 27
kernel examples 6
L
LEDs
managed by GPIO driver
LoggingSetup module 18
7
N
D
non-instrumented libraries
disk space 10
documentation 8
P
Power driver 7
products directory 5
PWM driver 7
E
Empty Project example
empty.c file 16
examples 13
16
R
readme.txt file 18
Resource Explorer 6, 14
F
FatFs API, documentation
forum 8
9
G
GPIO driver
28
7
SPRUHU8F—February 2016
Submit Documentation Feedback
S
SD Card BoosterPack 20
SDSPI driver 8
SimpleLink SDK 5
SPI driver 7
30
www.ti.com
SYS/BIOS 5
other documentation 8
SysCallback module, configuration 28
SysMin module 18
System Overview configuration 27
system requirements 10
W
Watchdog driver
wiki 8
8
X
U
UART driver 8
UIA 5
other documentation
9
SPRUHU8F—February 2016
Submit Documentation Feedback
XDCtools 5
other documentation 8
XGCONF
configuring other components
starting 27
29
Index
31
IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and
other changes to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service
per JESD48, latest issue. Buyers should obtain the latest relevant information before placing orders and should verify that such
information is current and complete. All semiconductor products (also referred to herein as “components”) are sold subject to TI’s
terms and conditions of sale supplied at the time of order acknowledgment.
TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty
in TI’s terms and conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent
TI deems necessary to support this warranty. Except where mandated by applicable law, testing of all parameters of each
component is not necessarily performed.
TI assumes no liability for applications assistance or the design of Buyers’ products. Buyers are responsible for their products
and applications using TI components. To minimize the risks associated with Buyers’ products and applications, Buyers should
provide adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask
work right, or other intellectual property right relating to any combination, machine, or process in which TI components or services
are used. Information published by TI regarding third-party products or services does not constitute a license to use such products
or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the
patents or other intellectual property of the third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without
alteration and is accompanied by all associated warranties, conditions, limitations, and notices. TI is not responsible or liable for
such altered documentation. Information of third parties may be subject to additional restrictions.
Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or
service voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive
business practice. TI is not responsible or liable for any such statements.
Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements concerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or support that may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and
implement safeguards which anticipate dangerous consequences of failures, monitor failures and their consequences, lessen
the likelihood of failures that might cause harm and take appropriate remedial actions. Buyer will fully indemnify TI and its
representatives against any damages arising out of the use of any TI components in safety-critical applications.
In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TI’s
goal is to help enable customers to design and create their own end-product solutions that meet applicable functional safety
standards and requirements. Nonetheless, such components are subject to these terms.
No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of
the parties have executed a special agreement specifically governing such use.
Only those TI components which TI has specifically designated as military grade or “enhanced plastic” are designed and intended
for use in military/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use
of TI components which have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for
compliance with all legal and regulatory requirements in connection with such use.
TI has specifically designated certain components as meeting ISO/TS16949 requirements, mainly for automotive use. In any case
of use of non-designated products, TI will not be responsible for any failure to meet ISO/TS16949.
Products
Applications
Audio
www.ti.com/audio
Automotive and Transportation
www.ti.com/automotive
Amplifiers
Data Converters
amplifier.ti.com
dataconverter.ti.com
Communications and Telecom
Computers and Peripherals
www.ti.com/communications
www.ti.com/computers
DLP® Products
DSP
www.dlp.com
dsp.ti.com
Consumer Electronics
Energy and Lighting
www.ti.com/consumer-apps
www.ti.com/energy
Clocks and Timers
Interface
www.ti.com/clocks
interface.ti.com
Industrial
Medical
www.ti.com/industrial
www.ti.com/medical
Logic
Power Mgmt
logic.ti.com
power.ti.com
Security
Space, Avionics and Defense
www.ti.com/security
www.ti.com/space-avionics-defense
Microcontrollers
RFID
microcontroller.ti.com
www.ti-rfid.com
Video & Imaging
www.ti.com/video
OMAP Mobile Processors www.ti.com/omap
TI E2E Community
Wireless Connectivity
www.ti.com/wirelessconnectivity
e2e.ti.com
Mailing Address: Texas Instruments, Post Office Box 655303 Dallas, Texas 75265
Copyright © 2016, Texas Instruments Incorporated
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising