|OS family||Real-time operating systems|
|Source model||Open source|
|Latest release||2.21.01.08 / February 2018|
|Marketing target||Embedded systems|
|Platforms||TMS320 DSPs, ARM, MSP430|
TI-RTOS is an embedded tools ecosystem created and offered by Texas Instruments (TI) for use in a wide range of their embedded system processors. It includes a real-time operating system (RTOS) component named TI-RTOS Kernel (formerly named SYS/BIOS, which evolved from DSP/BIOS) along with added components that support device drivers, networking connectivity stacks, power management, file systems, instrumentation, and inter-processor communications like DSP/BIOS Link. It is free and open-source software, released under one of the BSD licenses.
TI-RTOS can be used within TI's Code Composer Studio integrated development environment (IDE), IAR Systems' IAR Embedded Workbench, and the GNU Compiler Collection (GCC). Separate versions of TI-RTOS are provided to support TI's MSP43x (including MSP432), SimpleLink Wireless MCU, Sitara, Tiva C, C2000, and C6000 lines of embedded devices.
TI-RTOS provides a wide range of system services to an embedded application such as preemptive multitasking, memory management and real-time analysis. TI-RTOS can be used in a wide variety of different microprocessors, with very different processing and memory constraints, so it was designed to be highly configurable. It is supported by popular Secure Sockets Layer (SSL) and Transport Layer Security (TLS) libraries such as wolfSSL.
The roots of TI-RTOS were originally developed by Spectron Microsystems (a subsidiary of Dialogic Corporation) as the first RTOS developed specifically for digital signal processors and was named SPOX. Spectron eventually also developed a second product named BIOSuite that included a light-weight real-time kernel and various associated tools that allow configuring and real-time analysis.
Spectron Microsystems was eventually acquired by Texas Instruments and the SPOX and BIOSuite products were merged into one microkernel product named DSP/BIOS. The DSP/BIOS RTOS product underwent significant changes to its application programming interface (API) in version 6.0. With the release of version 6.3 in August 2010, DSP/BIOS was renamed SYS/BIOS to reflect its support for microcontrollers beyond DSPs. With the release of version 6.40 in April 2014, SYS/BIOS was renamed TI-RTOS Kernel and made a tightly-integrated component of the TI-RTOS product suite.
TI-RTOS 1.00 was released initially in July 2012. for TI's microprocessors The 2.00 release of TI-RTOS in April 2014 completed the renaming process and integrated the TI-RTOS Kernel and other components under one software umbrella.
TI-RTOS consists of these components, some of which are unavailable for all embedded target families:
Most of the TI-RTOS components are released under the BSD License. Any user can rebuild the kernel using the included source code.
The TI-RTOS Kernel is made up of a number of discrete components, called modules. Each module can provide services via an API and is individually configurable. For example, system semaphores are provided by a module named ti.sysbios.knl.Semaphore. A developer can choose whether this module is included in the runtime image or optimized out. If included, the user can configure various aspects of the Semaphore module, and instances of semaphores to be created on system start up. The module also provides an API so that semaphores can be created, posted, pended, and deleted as an embedded program runs.
TI-RTOS Kernel provides support for several different types of threads in an embedded system.
TI-RTOS Kernel provides tooling to set up an embedded system's memory map and allow memory buffers to be allocated and deallocated while the system runs. The type of memory manager used during runtime is configurable so that memory fragmentation can be minimized as needed.
TI-RTOS Kernel provides modules that allow it to provide information about how the system is executing. This includes how different threads are loading the CPU over time, and logging events as they occur in both the system application and within the TI-RTOS Kernel. Also, the Code Composer Studio IDE can take this logged data and graphically display it for analysis.