FreeRTOS

FreeRTOS
Developer Real Time Engineers Ltd.
OS family Real-time operating systems
Working state Current
Source model Source available
Latest release 10.0.1 / December 20th, 2017
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 MIT[1]
Official website www.freertos.org

FreeRTOS is a real-time operating system kernel[2][3][4] for embedded devices that has been ported to 35 microcontroller platforms. It is distributed under the MIT License.

Implementation

FreeRTOS is designed to be small and simple. The kernel itself consists of only three 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. FreeRTOS applications can be completely statically allocated. Alternatively RTOS objects can be dynamically allocated with five 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;
  • an alternative to the more complex scheme that includes memory coalescence that allows a heap to be broken across multiple memory areas.
  • 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 I/O 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 FreeRTOS.org site also contains a lot of documentation and RTOS tutorials (additional manuals and tutorials are available for a fee), as well as details of the RTOS design.

Key features

  • Book and reference manuals.
  • Small memory footprint, low overhead, and fast execution.
  • Tick-less option for low power applications.
  • Intended for both hobbyists and professional developers working on commercial products.
  • Scheduler can be configured for both preemptive or cooperative operation.
  • Coroutine support (coroutines in FreeRTOS are simple and lightweight tasks with limited use of the call stack)
  • Trace support through generic trace macros. Tools such as Tracealyzer by 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. Tracealyzer a freemium pricing strategy, offering a feature-limited free version.

Supported architectures

SafeRTOS

SafeRTOS was constructed as a complementary offering to FreeRTOS, with common functionality but with an 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[2] of the FreeRTOS project.[5] Both SafeRTOS and FreeRTOS share the same scheduling algorithm, have similar APIs, and are otherwise very similar,[6] but they were developed with differing objectives.[7] SafeRTOS was developed solely in the C language to meet requirements for certification to IEC61508.[8]

SafeRTOS is known for its ability to reside solely in the on-chip read only memory of a microcontroller for standards compliance.[9] 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.[10]

SafeRTOS is included in the ROM of some Stellaris Microcontrollers[11] 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".

See also

References

  1. ↑ "FreeRTOS open source licensing". 2017-12-22.
  2. 1 2 "2011 Embedded Market Study". EE Times. Archived from the original on 2012-04-02.
  3. ↑ Kolesnik, 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.
  4. ↑ "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. …
  5. ↑ "FreeRTOS". Retrieved 8 Aug 2012.
  6. ↑ "SmartBotPaper" (PDF). Archived from the original (PDF) on 2012-07-04. Retrieved 8 Aug 2012.
  7. ↑ Relationship between FreeRTOS and SAFERTOS
  8. ↑ "EETimesSafetyCritical". Retrieved 8 Aug 2012.
  9. ↑ "Embedded Systems Design Europe". Retrieved 10 Aug 2012.
  10. ↑ "Texas Instruments" (PDF). Retrieved 10 Sep 2012.
  11. ↑ TI Stellaris Product range
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.