This is the GA release of TI-RTOS . This version of TI-RTOS requires CCS 6.0, IAR 5.60.1 (MSP430) or 6.70.2 (ARM). For CC3200 users, IAR 7.20.1 is required.
The TI-RTOS delivers components that enable engineers to develop applications on Texas Instruments micro-controller devices. The product is comprised of multiple software components and examples of how to use these components together.Product | Kernel (SYS/BIOS) | Instrumentation (UIA) | Wired Networking (NDK) | Wireless
Networking |
IPC | Drivers (refer to the product's Getting Started Guide for more details) | *Ware |
TI-RTOS for C2000 | Included | Included | Included (M3-only) | Included (M3-only) | included | Included (M3-only) | Included (MWare) |
TI-RTOS for C6000 | Included | Included | Included | Not included | Included | Not included | Not included |
TI-RTOS for MSP430 | Included | Included | Not included | Included | Not included | Included | Included (MSP430) |
TI-RTOS for Sitara | Included | Included | Included | Not included | Not included | Not included | Not included |
TI-RTOS for TivaC | Included | Included | Included | Included | Not included | Included | Included (TivaWare) |
TI-RTOS for SimpleLink™ Wireless MCUs | Included | Included | Not included | Included | Not included | Included | Included (cc3200-driverlib) |
The following documentation is available:
ID | Headline |
SDOCM00112133 | TI-RTOS installer needs to handle case in which XDCTools does not include JRE |
SDOCM00108224 | Project template description has a misspelled word |
This release requires the following other software components and tools versions to successfully function:
Product | Supported Targets | Compiler Toolchains | Compiler Versions |
TI-RTOS for C2000 | ti.targets.arm.elf.M3 ti.targets.C28_float ti.targets.C28_large |
Texas Instruments | 5.1.5
(M3) 6.2.5 (C28) |
TI-RTOS for C6000 | ti.targets.elf.C66 ti.targets.elf.C66_big_endian ti.targets.elf.C674 |
Texas Instruments | 7.4.7 |
TI-RTOS for MSP430 | ti.targets.msp430.elf.MSP430X iar.targets.msp430.MSP430X_small |
Texas Instruments | 4.3.1 |
IAR for MSP430 | 5.60.1 | ||
TI-RTOS for Sitara | ti.targets.arm.elf.A8Fnv gnu.targets.arm.A8F gnu.targets.arm.A9F |
Texas Instruments | 5.1.5 |
GCC (in CCS 6) | gcc-arm-none-eabi-4_7-2013q3 | ||
TI-RTOS for TivaC | ti.targets.arm.elf.M4F iar.targets.arm.M4F gnu.targets.arm.M4F |
Texas Instruments | 5.1.5 |
GCC (in CCS 6) | gcc-arm-none-eabi-4_7-2013q3 | ||
IAR for ARM | 6.70.1 | ||
TI-RTOS for SimpleLink™ Wireless MCUs | ti.targets.arm.elf.M4 iar.targets.arm.M4 gnu.targets.arm.M4 |
Texas Instruments | 5.1.5 |
GCC (in CCS 6) | gcc-arm-none-eabi-4_7-2013q3 | ||
IAR for ARM | 6.70.1 |
ID | Headline |
Bug 431821 | add explicit (Void) to parameter for implmentation of SysCallback_abort() and ready() (IAR warning) |
SDOCM00112186 | Making a debug build for the drivers is not obvious |
SDOCM00111765 | USBMSCHFatFs service priority is fixed as a default of 15. |
SDOCM00108264 | UIA hello and stairstep examples do not build for some MSP430 devices |
SDOCM00108100 | Remove #ifdef MSP430F5529 and MSP430FR5969 from ENV.h |
SDOCM00108042 | TI-RTOS driver APIs need a calling context table |
SDOCM00107416 | TI-RTOS Kernel GNU examples (EK-TM4C1294XL) on Linux are missing the tm4c1294ncpdt.lds linker file |
SDOCM00107367 | TI-RTOS projects imported to IAR Workbench use the default linker files |
SDOCM00107366 | Grlibdemo on MSP430FR5969LP not working for IAR |
SDOCM00107337 | BIOS and UIA examples will not link with default MSP430FR5969 linker file. |
SDOCM00107336 | GPIO's ROV module does work on the TM4C1294 because of a missing entry in the gel file. |
SDOCM00107319 | makedef's XDCTOOLS_JAVA_HOME default is bad in supplied examples for stand-alone installer |
SDOCM00107296 | UARTMon IAR warning in MSP430FR5969 |
SDOCM00107295 | UART write callback function called twice for a single byte sent |
SDOCM00107276 | ROV for GPIO exception if opened before Board_initGeneral() is called |
SDOCM00107260 | ROV view for GPIO doesn't work for MSP430 |
SDOCM00106479 | I2C_transfer() fails to unblock with a bad I2C address on Tiva C devices |
SDOCM00106264 | UART driver doesn't handle RX FIFO overruns. |
SDOCM00106124 | Editor has problems identifying used code sections in CCS. |
SDOCM00105778 | MSP430 UART logging to System Analyzer does not work |
SDOCM00105762 | TI Resource Explorer can't distinguish between boards of the same device or same boards with different toolchains |
SDOCM00105761 | CC3000 Wi-Fi examples not working with GCC |
SDOCM00105006 | Build warnings for IAR when doing a top-level build |
SDOCM00104686 | UART in Stellaris launchpad not working above 9600 baud when used with windows apps that use rxtxSerial.dll driver |
SDOCM00104253 | MSP430 Launchpad ez-FET UART emulation issue at buadrate > 28.8kbps |
SDOCM00103637 | MSP430 UART[USCIA] LibType_Instrumented is not recommended at baudrates > 9600 |
SDOCM00102563 | WiFi driver should not create Hwi instance |
SDOCM00101155 | Intermittent spin lock in USB library's USBHCDPipeRead() for LM4F232 |
SDOCM00100865 | TI-RTOS drivers should have top-level enable and disable APIs |
SDOCM00100864 | Multithreaded CC3000 Host Driver does not work properly |
SDOCM00100494 | SPI driver was not tested in Slave Open Drain mode |
SDOCM00099858 | Stellaris launchpad doesn't detect a USB disconnect event |
SDOCM00099460 | ping flood causes Concerto board to stop receiving interrupts |
SDOCM00098063 | UART driver needs to support DMA |
SDOCM00097626 | Giving Priorities to Hwis from TI-RTOS Drivers |
SDOCM00094053 | TI-RTOS sub-products (e.g. UIA, IPC) are not linked into CCS Help |
SDOCM00093967 | TI-RTOS Windows install will fail if installed in multiple or single directory that contains more than 38 characters in path |
SDOCM00093268 | Add parity and error checking for UART driver |
SDOCM00088931 | I2C Needs a Timeout feature |
SDOCM00088081 | SD Card driver lacks CRC support |
All releases have 4 digits (M.mm.pp.bb). This includes GA and pre-releases (engineering, EA, beta, etc.). Pre-releases are denoted with a suffix (e.g. 1.01.00.15_eng or 1.01.00.21-beta).
This product's version follows a version format, M.mm.pp.bb, where M is a single digit Major number, mm is 2 digit minor number, pp is a 2 digit patch number, and b is an unrestricted set of digits used as an incrementing build counter.
To support multiple side-by-side installations of the product, the product version is encoded inEK-TM4C1294XL the top level directory, ex. tirtos_1_00_01_11.
Subsequent releases of patch upgrades will be identified by the patch number, ex. TI-RTOS 1.00.00.68 with directory tirtos_1_00_01_70. Typically, these patches only include critical bug fixes.
Please note that version numbers and compatibility keys are NOT the same. For an explanation of compatibility keys, please refer to the 'Upgrade and Compatibility Information' section.
For technical support, please refer to the Texas Instruments E2E BIOS Support Forum http://e2e.ti.com/support/embedded/tirtos/default.aspx or other forums in http://e2e.ti.com/ as needed.
Last updated: August 01, 2014