ThreadX

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
Eclipse ThreadX
File:Eclipse ThreadX logo.png
DeveloperExpress Logic (original)
Microsoft (former)
Eclipse (current)
Written inC
Working stateCurrent
Source modelOpen source
Initial release1997; 29 years ago (1997)
Latest release6.4.1[1] / February 28, 2024; 2 years ago (2024-02-28)
Repositorygithub.com/eclipse-threadx/threadx/
Marketing targetEmbedded systems, IoT
Update methodRe-install
Package managerNone
Supported platformsARC, ARM, Blackfin, CEVA, C6x, MIPS, NXP, PIC, PowerPC, RISC-V, RX, SH, SHARC, TI, V850, Xtensa, x86, Coldfire, others
Kernel typeEmbedded, deterministic, real-time microkernel, picokernel
Default
user interface
Embedded UI support (GUIX)
LicenseMIT License (as of 2023)
Official websitethreadx.io

ThreadX is an embedded real-time operating system (RTOS) programmed mostly in the C language. It was originally released in 1997 as ThreadX when Express Logic first developed it, later it was renamed to Azure RTOS (2019) after Express Logic was purchased by Microsoft,[2] then most recently it was renamed again to Eclipse ThreadX (2023), or "ThreadX" in its short form, after it transitioned to free open source model under the stewardship of the Eclipse Foundation.[3]

History

[edit | edit source]

In 1997, ThreadX was first released and marketed by Express Logic of San Diego, California, United States. It was developed by William Lamie,[4] who was also the original author of Nucleus and PX5 RTOS, and was president and CEO of Express Logic. ThreadX version 4 was introduced in 2001, version 5 was introduced in 2005, and then version 6 was introduced in 2020 (the latest major version). FileX – the embedded file system for ThreadX was introduced in 1999. NetX – the embedded TCP/IP networking stack for ThreadX was introduced in 2002. USBX – the embedded USB support for ThreadX was introduced in 2004. ThreadX SMP for SMP multi-core environments was introduced in 2009. ThreadX Modules was introduced in 2011. ThreadX achieved safety certifications for: TÜV IEC 61508 in 2013, and UL 60730 in 2014. GUIX – the embedded UI for ThreadX was introduced in 2014.

On April 18, 2019, Microsoft purchased Express Logic for an undisclosed sum and it was renamed to Azure RTOS.[2]

On November 21, 2023, Microsoft announced Azure RTOS would be transitioning to an open source model under the stewardship of the Eclipse Foundation, and making the project available under the permissive MIT License.[3] With Eclipse Foundation as the new home, Azure RTOS was renamed to Eclipse ThreadX, or "ThreadX" in its short form.

Overview

[edit | edit source]

The name ThreadX refers to the threads used as the executable elements, with X representing context switching.

ThreadX provides priority-based, pre-emptive scheduling, fast interrupt response, memory management, interthread communication, mutual exclusion, event notification, and thread synchronization features. Major distinguishing technology characteristics of ThreadX include preemption-threshold, priority inheritance, efficient timer management, fast software timers, picokernel design, event-chaining, and small size: minimal size on an ARM architecture processor is about 2 KB.

ThreadX supports multi-core processor environments via either asymmetric multiprocessing (AMP) or symmetric multiprocessing (SMP). Application thread isolation with memory management unit (MMU) or memory protection unit (MPU) memory protection is available with ThreadX Modules.

ThreadX has safety certifications from TÜV, UL and is Motor Industry Software Reliability Association MISRA C compliant.

ThreadX is the foundation of Express Logic's X-Ware Internet of things (IoT) platform, which includes embedded file system support (FileX), embedded UI support (GUIX), embedded Internet protocol suite (TCP/IP), and cloud connectivity (NetX/NetX Duo), and Universal Serial Bus (USB) support (USBX). ThreadX is liked by developers and is a popular RTOS.[5]

As of 2017, ThreadX RTOS become one of the most popular RTOSs in the world, deployed in over 6.2 billion devices, including consumer electronics, medical devices, data networking applications, and SoCs.[6]

Technology

[edit | edit source]

ThreadX implements a priority-based, pre-emptive scheduling algorithm with a proprietary feature called preemption-threshold. The threshold provides greater granularity within critical sections, reduces context switching, and has been the subject of academic research on guaranteeing scheduling.[7]

ThreadX provides a unique construct called event chaining,[8] where the application can register a callback function on all APIs that can signal an external event. This helps applications chain together various public objects in ThreadX allowing one thread to block on multiple objects.

ThreadX also provides counting semaphores, mutexes with optional priority inheritance, event flags, message queues, software timers, fixed-sized block memory, and variable-sized block memory. All APIs in ThreadX that block on resources also have an optional timeout.

ThreadX offers multi-core processor support via either AMP or SMP. Application code isolation is available through the ThreadX Modules component.

Safety certification

[edit | edit source]

ThreadX (and FileX and NetX Duo) have been precertified by SGS-TÜV Saar to the following safety standards: IEC 61508 SIL 4, IEC 62304 Class C, ISO 26262 ASIL D, and EN 50128 SW-SIL 4.

ThreadX (and FileX and NetX Duo) have been precertified by UL to the following safety standards: UL/IEC 60730, UL/IEC 60335, UL 1998

ThreadX has also been certified to DO-178 standards by various military and aerospace companies. It is supported by popular Transport Layer Security (SSL/TLS) libraries such as wolfSSL.[9]

Packaging

[edit | edit source]

As of 2017, ThreadX is packaged as part of X-Ware IoT Platform in full source code and with no runtime royalty payment.

Major components

[edit | edit source]

The major ThreadX components are:

ThreadX

[edit | edit source]

ThreadX is the real-time operating system (RTOS).

FileX & LevelX

[edit | edit source]

FileX is an optional file system for ThreadX. It supports FAT12, FAT16, FAT32, and exFAT file systems. The latter extends FAT file sizes beyond 4 GB, which is useful for large video files.

It also offers fault tolerance and supports direct NOR and NAND flash memory media through an optional flash wear leveling product called LevelX.

GUIX is an optional graphical user interface (GUI) for ThreadX. It provides a 2D computer graphics system that supports multiple display devices with a variety of screen resolutions and color depths. Many predefined graphical widgets are available. A Windows WYSIWYG host tool called GUIX Studio automatically generates C code for GUIX to execute at runtime.

NetX Duo

[edit | edit source]

NetX Duo is an optional TCP/IP network system for ThreadX. It supports both IPv4 and IPv6 networking with IPsec network security. TCP and UDP socket layers are provided by TLS / DTLS. Optional protocols include ARP, Auto IP, DHCP, DNS, DNS-SD, FTP, HTTP, ICMP, IGMP, mDNS, POP3, PPP, PPPoE, RARP, TFTP, SNTP, SMTP, SNMP, and Telnet. IoT Cloud protocol support includes CoAP, MQTT, and LWM2M. NetX Duo also supports Thread and 6LoWPAN. In 2017, ThreadX and NetX Duo became a Thread Certified Product.[10]

USBX is an optional Universal Serial Bus (USB) system for ThreadX. It supports both host/device/on-the-go (OTG). Host controller support includes EHCI, OHCI, and proprietary USB host controllers.

It supports these USB Device Classes: Audio, Asix, CDC/ACM, CDC/ECM, DFU, GSER, HID, PIMA, Printer, Prolific, RNDIS, and Storage.

TraceX

[edit | edit source]

TraceX is an optional host software that provides a graphical view of ThreadX RTOS events. It requires Windows XP or later.

Supported ports

[edit | edit source]

Products using ThreadX

[edit | edit source]

Some examples of products that use ThreadX:

See also

[edit | edit source]

Lua error in mw.title.lua at line 392: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal').

References

[edit | edit source]
  1. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  2. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  3. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  4. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  5. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  6. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  7. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  8. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  9. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  10. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  11. ^ a b c d e f g h Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  12. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  13. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  14. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  15. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  16. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).

Further reading

[edit | edit source]
ThreadX documentation
RTOS comparison
[edit | edit source]
Official
STM32