 |
This article relies excessively on referencestoprimary sources. Please improve this article by adding secondary or tertiary sources.
Find sources: "ThreadX" – news · newspapers · books · scholar · JSTOR (November 2010) (Learn how and when to remove this message) |
| Developer | Express Logic (original) Microsoft (former) Eclipse Foundation (current) |
|---|---|
| Written in | C |
| Working state | Current |
| Source model | Open source |
| Initial release | 1997; 27 years ago (1997) |
| Latest release | 6.4.1[1] / February 28, 2024; 4 months ago (2024-02-28) |
| Repository | github |
| Marketing target | Embedded systems, IoT: including sensors, devices, edge routers, gateways |
| Update method | Re-install |
| Package manager | None |
| Platforms | ARC, ARM, Blackfin, CEVA, C6x, MIPS, NXP, PIC, PowerPC, RISC-V, RX, SH, SHARC, TI, V850, Xtensa, x86, Coldfire, others |
| Kernel type | Embedded, deterministic, real-time microkernel, picokernel |
| Default user interface | Embedded UI support (GUIX) |
| License | MIT License |
| Official website | threadx |
Eclipse ThreadX (formerly named Azure RTOS and ThreadX) is a highly deterministic, embedded real-time operating system (RTOS) programmed mostly in the language C.
ThreadX was initially developed and marketed by Express Logic of San Diego, California, United States. The author of ThreadX is William Lamie,[2] who was also the original author of the Nucleus RTOS in 1990. William Lamie was President and CEO of Express Logic.
Express Logic was purchased for an undisclosed sum by Microsoft on April 18, 2019 and renamed it to Azure RTOS.[3] 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.[4] With Eclipse Foundation as the new home, Azure RTOS was renamed to Eclipse ThreadX, or "ThreadX" in its short form.
The name ThreadX is derived from the threads that are used as the executable elements, and the letter X represents context switching, i.e., it switches threads. ThreadX provides priority-based, preemptive 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 extensive safety certifications from Technischer Überwachungsverein (TÜV, English: Technical Inspection Association) and UL (formerly Underwriters Laboratories) 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 also 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 has won high appraisal from developers and is a very popular RTOS.[5] As of 2017[update], according to marketing research firm VDC Research, the ThreadX RTOS has become one of the most popular RTOSes in the world, having been deployed in over 6.2 billion devices, including consumer electronics, medical devices, data networking applications, and SoCs.[6]
ThreadX was first introduced in 1997. ThreadX 4 was introduced in 2001. ThreadX 5 was introduced in 2005, and is the latest version as of 2020[update].
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.
Express Logic was purchased for an undisclosed sum by Microsoft on April 18, 2019.[3]
ThreadX implements a priority-based, preemptive scheduling algorithm with a proprietary feature called preemption-threshold. The latter has been shown to provide greater granularity within critical sections, reduce context switches, 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 application programming interfaces (APIs) that can signal an external event. This helps applications chain together various public objects in ThreadX such that one thread can effectively 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 ThreadX Modules component.
ThreadX RTOS components include:
FileX is the embedded file system for ThreadX. FileX supports FAT12, 16, 32, and exFAT formats. The latter extends FAT file sizes beyond 4 GB, which is especially useful for video files, and it requires license directly from Microsoft for use. FileX also offers fault tolerance and supports direct NOR and NAND flash memory media through a flash wear leveling product called LevelX.
GUIX is the embedded graphical user interface (GUI) for ThreadX. GUIX provides a 2D runtime system (environment) for embedded applications running ThreadX. GUIX 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 is the embedded TCP/IP system for ThreadX. NetX Duo supports both IPv4 and IPv6 networking along with protocols such as ARP, Auto IP, DHCP, DNS, DNS-SD, FTP, HTTP, ICMP, IGMP, mDNS, POP3, PPP, PPPoE, RARP, TFTP, SNTP, SMTP, SNMP, and TELNET. IP layer network security is provided by IPsec. TCP and UDP socket layer security is provided by TLS and DTLS, respectively. 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.[9]
USBX is the embedded Universal Serial Bus (USB) system for ThreadX. USBX supports both host and device. Host controller support includes EHCI, OHCI, and proprietary USB host controllers. USBX also supports OTG. USBX class support includes Audio, Asix, CDC/ACM, CDC/ECM, DFU, GSER, HID, PIMA, Printer, Prolific, RNDIS, and Storage.
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.[10]
As of 2017, ThreadX is packaged as part of X-Ware IoT Platform in full source code and with no runtime royalty payment.
Some high-profile products using ThreadX range from small wearable devices, to Hewlett-Packard printers, and even NASA’s Deep Impact space probe.[11]
The Raspberry Pi line of single-board computers runs ThreadX as a binary blob on the graphics processing unit (GPU). This controls initial booting, which in turn is used to boot secondary operating systems such as Linux, and continues to operate in a more privileged role even after the boot process.[12]
|
Real-time operating systems (RTOS)
| |||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Operating systems |
| ||||||||||||||||||||||||||||||||||
| Frameworks, kits |
| ||||||||||||||||||||||||||||||||||
| Developers |
| ||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||
|
| |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kernels |
| ||||||||||||||||||||||||
| Operating systems |
| ||||||||||||||||||||||||
| Frameworks, kits |
| ||||||||||||||||||||||||
| Developers |
| ||||||||||||||||||||||||
| |||||||||||||||||||||||||
