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 tool chain (see Section 2.4). TI-RTOS is provided with full source code and requires no up-front or runtime license fees.
www.ti.com 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 MSP43x are as follows. Table 1–1.
How Can I Find Example Projects? 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.
The following code generation tool (compilers and linkers) used to build the TI-RTOS libraries and to perform testing. More recent versions are expected to be compatible. • Texas Instruments: MSP430 CodeGen Tools 4.4.2 (for MSP430) • Texas Instruments: ARM CodeGen Tools 5.2.4 (for MSP432) •...
(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 —...
Page 9
— 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 • MSPWare — Documents in <tirtos_install>/products/MSPWare_##/doc —...
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.)
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.
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 tool chain.
Chapter 3 SPRUHU4D—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 Creating Example Projects Using the Resource Explorer in CCS . . Creating Examples with IAR Embedded Workbench.
Creating Example Projects Using the Resource Explorer in CCS 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 TI-RTOS and its components and have all the settings needed for your device. Follow these steps: 1.
Page 15
www.ti.com Creating Example Projects Using the Resource Explorer in CCS 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.
Creating Example Projects Using the Resource Explorer in CCS www.ti.com 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. (If you want to use a simulator instead of a hardware connection, double-click the *.ccxml file in the targetConfigs folder of the project to open the Target Configuration File editor.
www.ti.com Creating Example Projects Using the Resource Explorer in CCS 3.1.2 Creating Examples to Build via a Command Line TI-RTOS has a command-line utility called that generates example projects along with the examplesgen makefiles needed to build the examples for all supported tool chains—TI and IAR. The files are created in a location you specify on the command line.
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. 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.
www.ti.com MSP430 MSP-EXP430F5529LP Settings and Resources MSP430 MSP-EXP430F5529LP Settings and Resources The MSP-EXP430F5529LP board contains an MSP430 MSP430F5529 device. MSP-EXP430F5529LP connections: Micro-B USB for power, emulation, UART examples, and USB examples Rev 1.4+ required for all booster-packs Board_BUTTON1 Board_BUTTON0 (MSP_EXP430F5529LP_S2) (MSP_EXP430F5529LP_S1) Board_LED0 Board_LED1...
MSP430 MSP-EXP430F5529LP Settings and Resources www.ti.com Resources Used: The following list shows which MSP_EXP430F5529LP resources are used by TI-RTOS applications on that platform. TI-RTOS examples control which peripherals (and which ports) are used. • TI-RTOS Kernel (SYS/BIOS). Uses the first general-purpose timer available and that timer's associated interrupts.
www.ti.com MSP430 MSP-EXP430FR5969LP Settings and Resources MSP430 MSP-EXP430FR5969LP Settings and Resources The MSP-EXP430FR5969LP board contains an MSP430FR5969 device. This device has an FRAM memory unit. MSP-EXP430FR5969LP connections: Micro-B USB for power, emulation, and UART examples Rev 1.4+ required for all booster-packs Board_BUTTON0 Board_BUTTON1...
Page 22
MSP430 MSP-EXP430FR5969LP Settings and Resources www.ti.com Jumper settings: • Set RXD << and TXD >> to provide UART communications via the onboard USB debugger. If you use a BoosterPack with this board (Section 3.8), the BoosterPack fits over J4 and J5. SPI Loopback example pin connections: The SPI loopback example is not supported on the MSP_EXP430FR5969LP.
www.ti.com MSP430 MSP-EXP430FR6989LP Settings and Resources MSP430 MSP-EXP430FR6989LP Settings and Resources The MSP-EXP430FR6989LP board contains an MSP430FR6989 device. This device has an FRAM memory unit. MSP-EXP430FR6989LP connections: Micro-B USB for power, emulation, and UART examples Segmented LCD Board_BUTTON0 Board_BUTTON1 (MSP_EXP430FR6989_S1) (MSP_EXP430FR6989_S2) Board_LED0 Board_LED1...
Page 24
MSP430 MSP-EXP430FR6989LP Settings and Resources www.ti.com Jumper settings: • Set RXD << and TXD >> to provide UART communications via the onboard USB debugger. If you use a BoosterPack with this board (Section 3.8), the BoosterPack fits over J1 through J4. SPI Loopback example pin connections: The SPI loopback example is not supported on the MSP_EXP430FR6989LP.
www.ti.com MSP432 MSP-EXP432P401RLP Settings and Resources MSP432 MSP-EXP432P401RLP Settings and Resources The MSP-EXP432P401RLP board contains an MSP432P401R device. MSP-EXP432P401RLP connections: Micro-B USB for power, emulation, and UART examples Board_BUTTON1 (MSP_EXP432P401RLP_S2) Board_BUTTON0 (MSP_EXP432P401RLP_S1) Board_LED1 (MSP_EXP432P401RLP_LED_RED) Board_LED0 Board_LED2 (MSP_EXP432P401RLP_LED_GREEN) (MSP_EXP432P401RLP_LED1) Board_LED3 (MSP_EXP432P401RLP_LED_BLUE) SPRUHU4D—February 2016 Examples for TI-RTOS Submit Documentation Feedback...
Page 26
MSP432 MSP-EXP432P401RLP Settings and Resources www.ti.com Jumper settings: • Set RXD << and TXD >> to provide UART communications via the onboard USB debugger. • If you use a BoosterPack with this board (Section 3.8), the BoosterPack fits over J1 and J5. SPI Loopback example pin connections: When wiring for SPI loopback, pins on a single board are wired to other pins on the same board.
www.ti.com BoosterPacks 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.8.1 SD Card BoosterPack microSD BoosterPack 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.
BoosterPacks www.ti.com 3.8.4 CC3100 BoosterPacks The TI CC3100 is a self-contained wireless network processor that simplifies the implementation of Internet connectivity. TI’s SimpleLink Wi-Fi solution minimizes the software requirements of the host microcontroller (MCU) and is thus the ideal solution for embedded applications using any low-cost and low-power MCU.
BoosterPacks www.ti.com 3.8.5 RF430CL330 NFC Transponder Module The I C RF430CL330 Load example uses the I C driver to communicate with a RF430CL330 NFC transponder module. This board may be used with the MSP-EXP430F5529LP, MSP-EXP430FR5969LP, MSP-EXP430FR6989LP, and MSP-EXP432P401RLP. A Wireless Connectivity Adaptor board is also required in order to use the NFC Transponder Module with a LaunchPad board.
www.ti.com Installing USB Drivers for the USB Device Examples Installing USB Drivers for the USB Device Examples The USB examples build upon the examples provided with MSPWare. Because the examples mimic the same functionality, you can use the same drivers delivered with standalone installations of MSPWare. USB drivers for MSP430 are located in each example's folder.
Page 32
Installing USB Drivers for the USB Device Examples www.ti.com 5. Select the Device Manager category in the left pane. 6. In the center pane, select the unknown driver that you are trying to install. For example, the device shown here is for the USB CDC driver. 7.
Chapter 4 SPRUHU4D—February 2016 Configuring TI-RTOS This chapter describes how to configure TI-RTOS and its components for use by your application. Topic Page Starting the Configuration Tool ......Configuring TI-RTOS Drivers .
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 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.
www.ti.com Configuring TI-RTOS Drivers 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.
Configuring Components of TI-RTOS www.ti.com Other SystemSupport implementations are provided with XDCtools. • 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);...
Index SPRUHU4D—February 2016 Index App Center 11 GPIO driver 7 Available Products list 35 resources used 20, 22, 24, 26 BoosterPacks 27 HID device 8 RF430CL330 30 SD Card 27 TMP006 27 I2C driver 7 installation CCS 11 directory 11 creating a project 6, 14 instrumentation 5 installation 11...
Page 38
www.ti.com non-instrumented libraries 35 target configuration file 16 TMP006 BoosterPack 27 TPL0401EVM board 30 Power driver 7 products directory 5 PWM driver 8 UART driver 8 resources used 20, 22, 24, 26 UIA 5 other documentation 9 USB Descriptor Tool 20 USB driver readme.txt file 18 resources used 20...
Page 39
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.