Talon™ DSP RTOS Real-Time Operating Systems

Talon RTOS

Products

TALON 2000

Quick Links

123 Gaither Drive
Mount Laurel, NJ 08054-1701
Phone: 1-877-983-4514
FAX: 1-856-866-1100

Talon™ DSP RTOS

What is TALON DSP RTOS?

TALON RTOS is a suite of five (5) POSIX® Compliant Real Time Operating Systems that are individually optimized for each TI DSP family. This eliminates the need for understanding the underlying DSP specifics and allows the developer to concentrate on application development, reducing risk, development cycle and time to market.

TALON DSP RTOS meets the demands of sophisticated embedded DSP applications providing predictable, deterministic and hard real time behavior, unlike other OS’s such as Unix, Linux and their derivatives

TALON DSP RTOS is ready to run out-of-the-box with hardware you may already have thanks to our board support packages (BSP’s). TALON versions exist for our TAILWIND USB-based reference boards as well as many TI DSK and EVM boards and include host to target utilities for communication, file access and JTAG emulation. All BSP’s come with OS driver source code illustrating how to communicate from your application running on the DSP to another host, board or process via PCI, USB, VME, ISA and standard parallel port interfaces.

TALON Operating Systems support a wide variety of Texas Instruments DSP’s. To find out more, view the TALON Compatibility Comparison Chart.

Models

Data sheet (PDF) [download]


	Back to top Embedded System This is an embedded operating system, that is, a systems software intended to be embedded along with application programs in a target device or system. This capability is supported by the System Builder tool which allows to generate a ROM Image file with the whole application configuration and the operating system kernel to be burnt into a Read-Only Memory (ROM) device, where the software is loaded and executed at run time.

	Back to top What is POSIX? POSIX® is an IEEE Standard for Information Technology - Portable Operating System Interface. Since the beginning of the last decade, this standard has provided a stable framework for both operating system designers and application programmers. While the touch and feel of the standard is UNIX-like, the POSIX interfaces are rigorously defined, therefore ensuring predictable behavior of compliant applications. There are many benefits to using standardized operating system interfaces. Well-defined and standardized operating system services provide for design of reliable and robust application software. Application compliance to POSIX ensures smooth software portability between hardware platforms. Standard OS interfaces enhance programmers’ productivity by encouraging them to comply with proven and efficient programming practices. The availability of numerous portable utility programs allows the programmer to work in a comfortable and friendly development environment.

	Back to top Posix Compliance POSIX® is an IEEE Standard for Information Technology - Portable Operating System Interface. Since the beginning of the last decade, this standard has provided a stable framework for both operating system designers and application programmers. While the touch and feel of the standard is UNIX-like, the POSIX interfaces are rigorously defined, therefore ensuring predictable behavior of compliant applications. There are many benefits to using standardized operating system interfaces. P1003.1 - Application Program Interface [C Language] P1003.4a - Threads Extension [C Language] P1003.4b - Realtime Extensions [C Language] P1003.4c - Additional Realtime Extensions [C Language]

Posix Compiance Chart

P1003.1 - Application Program Interface [C Language]

This is the basic POSIX standard specifying operating system interfaces at process multiprogramming level. The compliance with different standard sections is listed below.

Process Primitives. The fork and exec primitives are replaced by the POSIX.1b posix_spawn primitive, because of the lack of virtual to physical address translation. Job Control signals are not supported.
Process Environment. Except for Job Control Interfaces.
Files and Directories.
Input and Output Primitives.
Device- and Class-Specific Functions.
Language-Specific Services for the C Programming Language.
System Databases. Except for Job Control interfaces.
Semaphore Synchronization.
Memory Management.
Execution Scheduling.
Clocks and Timers.
Message Passing.

P1003.4a - Threads Extension [C Language]

This standard specifies the generic thread facilities and interfaces along with the basic thread synchronization mechanism. Coverage of the POSIX Threads is complete.

Thread Management.
Mutex Primitives.
Condition Variables.
Thread-Specific Data.
Thread Priority Scheduling.
Process Control.
Reentrant Functions.
Signals.
Thread Cancellation.

P1003.4b - Realtime Extensions [C Language]

This standard includes the following facilities covered by the implementation.

Process Primitives (posix_spawn).
Timeouts for Blocking Services.
Execution Time Monitoring.
Device Control.
Interrupt Control.

P1003.4c - Additional Realtime Extensions [C Language]

This standard adds the following facilities, which are covered by the implementation.

Barrier Synchronization.
Reader-Writer Locks.
Spin Locks.
High-Resolution Sleep.

Blackhawk Talon™ RTOS Requirements & Compatibility List

RTOS	Target Family	Devices Supported	Target RAM or ROM Memory Req.		Host Computer	TI Software Tools	Microsoft Tools
			Minimum	Recommended
BH-OS-2000	TMS320C2000	TMS320C20XX TMS320C24XX	32K WORDS Program	64K WORDS Program	PC capable of running MS Windows 95, 98, ME, NT, 2000	Optimizing C Complier Assembler & Linker Tool Set.	VISUAL C/C++ V6.0 or Higher
			Data Storage depends on application	16K WORDS D-RAM (Data)		Code Composer V4.12 Windows 95, 98, NT
BH-OS-3X4X	TMS320C3X TMS3C0C4X	TMS320C3X TMS320C4X	64K WORDS	256K WORDS	PC capable of running MS Windows 95, 98, ME, NT, 2000, XP	Optimizing C Complier Assembler & Linker Tool Set.	VISUAL C/C++ V6.0 or Higher. Device Driver Development Kit (DDK) for VXD
			Data Storage depends on application.	128K WORDS D-RAM		Code Composer V4.12 Windows 95, 98, NT
BH-OS-5400	TMS320C5000	TMS320C54X	32K WORDS Program	64K WORDS Program	PC capable of running MS Windows 95, 98, ME, NT, 2000, XP	Optimizing C Complier Assembler & Linker Tool Set.	VISUAL C/C++ V6.0 or Higher
			Data Storage depends on application	16K D-RAM (Data) Advisable		Code Composer Studio v2.1 Windows 98, ME, NT, 2000, XP
				**Extended program memory addressing on 320C548 and higher not supported.
BH-OS-5500	TMS320C5000	TMS320C55X	512K BYTES Program	1MByte or more Program	PC capable of running MS Windows 95, 98, ME, NT, 2000, XP	Optimizing C Complier Assembler & Linker Tool Set.	VISUAL C/C++ V6.0 or Higher
			Data Storage depends on application.	512K Bytes (Data) Advisable		Code Composer Studio v2.1 Windows 98, ME, NT, 2000, XP
BH-OS-6000	TMS320C6000	TMS320C62XX TMS320C64XX TMS320C67XX	512K BYTES Program	1MByte or more Program	PC capable of running MS Windows 95, 98, ME, NT, 2000, XP	Optimizing C Complier Assembler & Linker Tool Set.	VISUAL C/C++ V6.0 or Higher. Device Driver Development Kit (DDK) for VXD
			Data Storage depends on application.	512K Bytes (Data) Advisable		Code Composer Studio v2.1 Windows 98, ME, NT, 2000, XP