- Small-footprint (small as 2KB, automatic scaling)
- Fast execution (sub microsecond context switch)
- Supports all popular processors and tools (see below)
- TraceX system analysis support
- Advanced Technology:
- Preemption-Threshold™
- Event Chaining™
- Performance Metrics
- Execution Profiling
- Run-time and Static Stack Analysis
- Multicore Support (SMP and AMP)
- Downloadable Application Modules
- Memory Protection for Downloadable Application Modules
- Extensive ThreadX ecosystem
- Safety Certifications (DO-178B, FDA510(k), IEC61508, etc)
- Deployed in over 1,000,000,000 devices
- Full Source Code
- Royalty-Free
- A2P
- AMD G-Series
- ARC
- ARM/Thumb
- AVR32
- BlackFin
- CEVA-TeakLite-III
- ColdFire/68K
- Freescale i.MX Family
- Freescale Kinetis
- Hitachi H8/300H
- Leon3
- Luminary Micro’s Stellaris®
- M-CORE
- MicroBlaze
- Microchip PIC24/dsPIC
- Microchip PIC32
- MIPS
- Nios II
- Power Architecture
- Renesas RX
- Renesas SH
- Renesas V8xx
- SHARC
- StarCore
- STMicroelectronics STM32
- StrongARM
- TMS320C54x
- TMS320C6x
- Win32
- x86/x386
- XScale
- Xtensa/Diamond
TMS320C54x
ThreadX for C54x
Highlights
Complete TMS320C54x support TI Development Tool Support Reasonable pricing No Royalties Complete ANSI C source code Easy to use and powerful services Responsive Technical Support Unlimited Threads, Queues, Event Flags, Timers, Semaphores, Mutexes, Block Pools, and Byte Pools Flexible memory usage Timeout available on all thread suspension Advanced preemption-threshold technique Low-overhead Application Timers Size scales automatically Picokernel architecture for size and speed
Improve Your C54x Development
Let our extensive experience with the TI C54x family of microprocessors help your product development. ThreadX, our high-performance real-time kernel, helps improve your product's quality and its time-to-market. In addition, using ThreadX makes it easier to enhance your product in the future.
C54x Optimizations
ThreadX optimizes context switching on the C54x. When context switching occurs inside of a ThreadX service call, only the registers preserved across function calls are saved as part of the thread's context.
A similar technique is used in interrupt handling. On the front end of interrupt service routines, only the compiler's scratch registers are saved initially. The full register set is saved only if thread preemption is required.
Embedded World 2012
February 28 - March 1, 2012
Nuremberg, Germany
