World Library  
Flag as Inappropriate
Email this Article


Developer Real Time Engineers Ltd.
OS family Real-time operating systems
Working state Current
Source model Open source
Latest release 8.1.2 / September 2nd, 2014
Marketing target Embedded devices
Platforms ARM (ARM7, ARM9, Cortex-M3, Cortex-M4, Cortex-A), Atmel AVR, AVR32, HCS12, MicroBlaze, Cortus (APS1, APS3, APS3R, APS5, FPF3, FPS6, FPS8), MSP430, PIC, Renesas H8/S, SuperH, RX, x86, 8052, Coldfire, V850, 78K0R, Fujitsu MB91460 series, Fujitsu MB96340 series, Nios II, Cortex-R4, TMS570, RM4x
Kernel type Microkernel
License Modified GPL to allow commercial use
Official website .org.freertoswww

FreeRTOS is a popular[1] real-time kernel[2][3] for embedded devices, that has been ported to 34 microcontrollers. It is distributed under the GPL with an optional exception. The exception permits users' proprietary code to remain closed source while maintaining the kernel itself as open source, thereby facilitating the use of FreeRTOS in proprietary applications.[4]


  • Implementation 1
  • Key features 2
  • Supported architectures 3
  • Related projects 4
    • SafeRTOS 4.1
    • OpenRTOS 4.2
  • See also 5
  • References 6
  • External links 7


FreeRTOS is designed to be small and simple. The kernel itself consists of only three or four C files. To make the code readable, easy to port, and maintainable, it is written mostly in C, but there are a few assembly functions included where needed (mostly in architecture-specific scheduler routines).

FreeRTOS provides methods for multiple threads or tasks, mutexes, semaphores and software timers. A tick-less mode is provided for low power applications. Thread priorities are supported. In addition there are four schemes of memory allocation provided:

  • allocate only;
  • allocate and free with a very simple, fast, algorithm;
  • a more complex but fast allocate and free algorithm with memory coalescence;
  • and C library allocate and free with some mutual exclusion protection.

There are none of the more advanced features typically found in operating systems like Linux or Microsoft Windows, such as device drivers, advanced memory management, user accounts, and networking. The emphasis is on compactness and speed of execution. FreeRTOS can be thought of as a 'thread library' rather than an 'operating system', although command line interface and POSIX-like IO abstraction add-ons are available.

FreeRTOS implements multiple threads by having the host program call a thread tick method at regular short intervals. The thread tick method switches tasks depending on priority and a round-robin scheduling scheme. The usual interval is 1/1000 of a second to 1/100 of a second, via an interrupt from a hardware timer, but this interval is often changed to suit a particular application.

The download contains prepared configurations and demonstrations for every port and compiler, allowing rapid application design. The site also contains lots of documentation and RTOS tutorials (additional manuals and tutorials available for a fee starting from USD25), details of the RTOS design.

Key features

  • Very small memory footprint, low overhead, and very fast execution.
  • Tick-less option for low power applications.
  • Equally good for hobbyists who are new to OSes, and professional developers working on commercial products.
  • Scheduler can be configured for both preemptive or cooperative operation.
  • Coroutine support (Coroutine in FreeRTOS is a very simple and lightweight task that has very limited use of stack)
  • Trace support through generic trace macros. Tools such as FreeRTOS+Trace (provided by the FreeRTOS partner Percepio) can thereby record and visualize the runtime behavior of FreeRTOS-based systems. This includes task scheduling and kernel calls for semaphore and queue operations. Price point = US$1500 (purchase, 5/2014). However, no free tracer is currently available.

Supported architectures

Related projects


SafeRTOS was constructed as a complementary offering to FreeRTOS, with common functionality but with a uniquely designed safety-critical implementation. When the FreeRTOS functional model was subjected to a full HAZOP, weakness with respect to user misuse and hardware failure within the functional model and API were identified and resolved. The resulting requirements set was put through a full IEC 61508 SIL 3 development life cycle, the highest possible for a software-only component.

SafeRTOS was developed by WITTENSTEIN high integrity systems, in partnership with Real Time Engineers Ltd, primary developer of[5] the FreeRTOS project.[6] Both SafeRTOS and FreeRTOS share the same scheduling algorithm, have similar APIs, and are otherwise very similar,[7] but they were developed with differing objectives.[8] SafeRTOS was developed solely in the C language to meet requirements for certification to IEC61508.[9]

SafeRTOS is known for its ability, unique among Operating Systems, to reside solely in the on-chip memory of a microcontroller, thus enabling the pre-certification of complete Hardware and Software systems to IEC61508 or other safety or reliability operating standards.[10] When implemented in hardware memory, SafeRTOS code can only be utilized in its original configuration, so certification testing of systems using this OS need not re-test this portion of their designs during the functional safety certification process.[11]

SafeRTOS is included in the ROM of some Stellaris Microcontrollers[12] from Texas Instruments. This allows SafeRTOS to be used in commercial applications without having to purchase its source code. In this usage scenario, a simple C header file is used to map SafeRTOS API functions to their location in read-only memory. The use of read-only memory is ideal because the code it contains cannot be changed - eliminating the possibility of user error, and ensuring the code that was originally tested remains absolutely identical throughout the project lifetime. It will not need re-testing as the application code grows and evolves around it. The burden of complex kernel testing is removed as the already certified and approved certification evidence, including the test plan, code and results, can be purchased "off the shelf".


Another project related to FreeRTOS, one with identical code but different licensing, is OpenRTOS. The OpenRTOS license removes all reference to the GPL and its implications. For example: one of the conditions of using FreeRTOS in a commercial product is that the user is made aware of the use of FreeRTOS and the source code of FreeRTOS (not application) must be provided upon request. As it is a commercial product available for purchase, OpenRTOS doesn't have this licensing requirement. OpenRTOS users also have access to full technical support.[13]

See also


  1. ^ EETimes Embedded Market Study.
  2. ^ Kolesnki, Sergey (2013-12-08). "Comparing microcontroller real-time operating systems". A kernel is not an RTOS, but this can be a confusing issue because of the inappropriate naming chosen for some popular kernels, ‘freeRTOS’ for example. 
  3. ^ "Why RTOS and What Is RTOS?". Retrieved 29 August 2014. What is FreeRTOS? … The size constraints, and dedicated end application nature, rarely warrant the use of a full RTOS implementation - or indeed make the use of a full RTOS implementation possible. FreeRTOS therefore provides the core real time scheduling functionality, inter-task communication, timing and synchronisation primitives only. This means it is more accurately described as a real time kernel, or real time executive. … 
  4. ^ FreeRTOS GPL exceptions.
  5. ^ EETimes Embedded Market Study.
  6. ^ "FreeRTOS". Retrieved 8 Aug 2012. 
  7. ^ "SmartBotPaper". Retrieved 8 Aug 2012. 
  8. ^ RTOSRelationship between FreeRTOS and SAFE
  9. ^ "EETimesSafetyCritical". Retrieved 8 Aug 2012. 
  10. ^ "Embedded Systems Design Europe". Retrieved 10 Aug 2012. 
  11. ^ "Texas Instruments". Retrieved 10 Sepl 2012. 
  12. ^ TI Stellaris Product range
  13. ^ OpenRTOS

External links

  • FreeRTOS+Trace
  • FreeRTOS ecosystem products
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.