SDK Description

Note

1. The default SDK Installation directory is: ${HOME}/ti/simplelink/ti15.4stack_linux_64_02_10_00_xx References to the ${SDK_ROOT} in this document refer to this directory location.
2. The numbering convention is: Major, Minor, Patch, BuildID The Linux Build ID is independent of the Embedded SDK Build ID and can be a different number.

Figure 101. shows the Linux SDK is divided into several directories.

Figure 101. TI 15.4-Stack 2.2.0 Linux® SDK Out-of-Box Directory Structure

Figure 101. shows the ${SDK_ROOT} directory structure under your TI 15.4-Stack 2.2.0 install directory. A high-level description of the contents in each folder follows:

• components contains the following libraries:
  • common—Simple runtime OS features, File I/O, and the stream interface
  • nv—Emulates the nonvolatile memory, as used in an embedded device
  • api—The API MAC and MT message (Msg) interface for the embedded network processor
• docs—Various documents such as the Software Developer’s Guide, Quick Start Guide, and the MAC CoProcessor Interface Guide
• example—Example applications
  • cc13xx-sbl—Flash update utility for the CC13x0
  • collector—Example application that demonstrates starting up the network, allowing network devices to join the network, collecting data from remote sensors
  • gateway—A Node.js™ based application that creates a local Web server and presents network information and sensor data through a Web application
  • npi_server2—A socket and packet interface to the embedded CoProcessor
  • google—Contains a makefile that can download, build, and install the Google protobuf compiler and the protobuf-c extension on the Linux host machine
• firmware—Prebuilt hex files for the CC13x0 MAC CoProcessor and Sensor Application
• prebuilt—Prebuilt Linux x86_v64 and BeagleBone Black (BBB) binaries for the example applications, scripts to quickly run the out-of-box example applications
• scripts—Contains makefile fragments used to compile and link example applications