Jump to content

FreeRTOS: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
m Added link to the ESP32 Wikipedia page.
add x86 os category
 
(24 intermediate revisions by 21 users not shown)
Line 1: Line 1:
{{Short description|Real-time operating system}}
{{Infobox OS
{{Infobox OS
| name = FreeRTOS
| name = FreeRTOS
Line 4: Line 5:
| screenshot =
| screenshot =
| caption =
| caption =
| developer = Real Time Engineers Ltd.
| developer = [[Amazon Web Services]]
| family = [[Real-time operating system]]s
| family = [[Real-time operating system]]s
| working state = Current
| working state = Current
| source model = [[Open-source software|Open source]]
| source model = [[Open-source software|Open source]]
| released = {{Start date and age|2003}}
| released = {{Start date and age|2003}}
| latest release version = 10.4.3<ref>{{cite web|title=www.freertos.org/History.txt|url=https://www.freertos.org/History.txt|date=2020-12-14}}</ref>
| latest release version = 11.1.0<ref>{{cite web|title=FreeFTOS Github Releases|website=[[GitHub]] |url=https://github.com/FreeRTOS/FreeRTOS-Kernel/releases/tag/V11.1.0|date=2024-04-22}}</ref>
| latest release date = {{Start date and age|2020|12|14}}
| latest release date = {{Start date and age|2024|04|22}}
| marketing target = [[Embedded system]]s
| marketing target = [[Embedded system]]s
| programmed in = [[C (programming language)|C]]
| programmed in = [[C (programming language)|C]]
Line 17: Line 18:
| update model = <!-- APT, Windows Update, etc. -->
| update model = <!-- APT, Windows Update, etc. -->
| package manager =
| package manager =
| supported platforms = [[ARM architecture|ARM]] (ARM7, ARM9, [[ARM Cortex-M3|Cortex-M3]], [[ARM Cortex-M4|-M4]], [[ARM Cortex-M7|-M7]], [[ARM Cortex-A8|-A]], [[ARM Cortex-R|-R4]]), [[Atmel AVR]], [[AVR32]], [[HCS12]], [[MicroBlaze]], Cortus (APS1, APS3, APS3R, APS5, FPF3, FPS6, FPS8), [[MSP430]], [[PIC microcontroller|PIC]], [[Renesas Technology|Renesas]] [[H8 Family|H8/S]], [[SuperH]], RX, [[x86]], [[Intel 8051#Related processors|8052]], [[Freescale ColdFire|Coldfire]], [[V850]], 78K0R, Fujitsu series MB91460, MB96340, [[Nios II]], TMS570, RM4x, [[ESP32|Espressif ESP32]], [[RISC-V]]
| supported platforms = [[ARM architecture|ARM]] (ARM7, ARM9, [[ARM Cortex-M3|Cortex-M3]], [[ARM Cortex-M4|-M4]], [[ARM Cortex-M7|-M7]], [[ARM Cortex-A8|-A]], [[ARM Cortex-R|-R4]]), [[Atmel AVR]], [[AVR32]], [[HCS12]], [[MicroBlaze]], Cortus (APS1, APS3, APS3R, APS5, FPF3, FPS6, FPS8), [[MSP430]], [[PIC microcontroller|PIC]], [[Renesas Technology|Renesas]] [[H8 Family|H8/S]], [[SuperH]], RX, [[x86]], [[Intel 8051#Related processors|8052]], [[Freescale ColdFire|Coldfire]], [[V850]], 78K0R, Fujitsu series MB91460, MB96340, [[Nios II]], TMS570, RM4x, [[ESP32|Espressif ESP32]], [[RISC-V]] (e.g. [[SHAKTI (microprocessor)|SHAKTI]])
| kernel type = [[Microkernel]] [[Real-time operating system|RTOS]]
| kernel type = [[Real-time operating system|Real-Time]] [[Microkernel]]
| ui =
| ui =
| license = [[MIT License|MIT]]<ref>{{cite web |title=FreeRTOS open source licensing |url=https://www.freertos.org/a00114.html |date=2017-12-22}}</ref>
| license = [[MIT License|MIT]]<ref>{{cite web |title=FreeRTOS open source licensing |url=https://www.freertos.org/a00114.html |date=2017-12-22}}</ref>
Line 24: Line 25:
}}
}}


'''FreeRTOS''' is a [[real-time operating system]] [[Kernel (operating system)|kernel]]<ref name=EETimes2012>{{cite web|title=2011 Embedded Market Study|url=http://www.eetimes.com/electrical-engineers/education-training/webinars/4214387/2011-Embedded-Market-Study|publisher=EE Times|archive-url=https://web.archive.org/web/20120402223224/http://www.eetimes.com/electrical-engineers/education-training/webinars/4214387/2011-Embedded-Market-Study|archive-date=2012-04-02}}</ref><ref>{{cite web|last1=Kolesnik|first1=Sergey|title=Comparing microcontroller real-time operating systems|url=http://www.embedded.com/design/operating-systems/4425751/Comparing-microcontroller-real-time-operating-systems|date=2013-12-08|quote=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.}}</ref><ref>{{cite web|title=Why RTOS and What Is RTOS?|url=http://www.freertos.org/about-RTOS.html|access-date=29 August 2014|quote=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 functions, inter-task communication, timing, and synchronisation primitives only. This means it is more accurately described as a real time kernel, or real time executive. …}}</ref> for [[embedded device]]s that has been ported to 35 [[microcontroller]] platforms. It is distributed under the [[MIT License]].
'''FreeRTOS''' is a [[real-time operating system]] [[Kernel (operating system)|kernel]]<ref name=EETimes2012>{{cite web|title=2011 Embedded Market Study|url=http://www.eetimes.com/electrical-engineers/education-training/webinars/4214387/2011-Embedded-Market-Study|publisher=EE Times|archive-url=https://web.archive.org/web/20120402223224/http://www.eetimes.com/electrical-engineers/education-training/webinars/4214387/2011-Embedded-Market-Study|archive-date=2012-04-02}}</ref><ref>{{cite web|last1=Kolesnik|first1=Sergey|title=Comparing microcontroller real-time operating systems|url=http://www.embedded.com/design/operating-systems/4425751/Comparing-microcontroller-real-time-operating-systems|date=2013-12-08|quote=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.}}</ref><ref>{{cite web|title=Why RTOS and What Is RTOS?|url=http://www.freertos.org/about-RTOS.html|access-date=29 August 2014|quote=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 computing|real-time]] scheduling functions, inter-task communication, timing, and synchronisation primitives only. This means it is more accurately described as a real time kernel, or real time executive. …}}</ref> for [[embedded device]]s that has been ported to 40 [[microcontroller]] platforms. It is distributed under the [[MIT License]].


== History ==
== History ==
The FreeRTOS kernel was originally developed by Richard Barry around 2003, and was later developed and maintained by Barry's company, Real Time Engineers Ltd. In 2017, the firm passed stewardship of the FreeRTOS project to [[Amazon Web Services]] (AWS). Barry continues to work on FreeRTOS as part of an AWS team.<ref>{{Cite web|url=http://www.openrtos.net/RTOS.html|title=RTOS - Free professionally developed and robust real time operating system for small embedded systems development}}</ref>
The FreeRTOS kernel was originally developed by Richard Barry around 2003, and was later developed and maintained by Barry's company, Real Time Engineers Ltd. In 2017, the firm passed stewardship of the FreeRTOS project to [[Amazon Web Services]] (AWS). Barry continues to work on FreeRTOS as part of an AWS team.<ref>{{Cite web|url=http://www.openrtos.net/RTOS.html|title=RTOS - Free professionally developed and robust real time operating system for small embedded systems development}}</ref> With the transition to Amazon control, subsequent releases of the project also switched licensing from GPL version 2 (with special exceptions for static linking to proprietary code outside the FreeRTOS kernel itself) to MIT.<ref>{{Cite web|url=https://github.com/FreeRTOS/FreeRTOS/commit/cfc268814a94a4deb8ddc8322b63ccae270a8669#diff-5cc7ddfa7e630dfb9a53b0da00eaa0233c6ce2adc6a94ff5285ab8913882c81a|title=Update to MIT licensed FreeRTOS V10.0.0}}</ref>


==Implementation==
==Implementation==
FreeRTOS is designed to be small and simple. It is mostly written in the [[C (programming language)|C programming language]] to make it easy to port and maintain. It also comprises a few [[assembly language]] functions where needed, mostly in architecture-specific scheduler routines.
FreeRTOS is designed to be small and simple. It is mostly written in the [[C (programming language)|C programming language]] to make it easy to port and maintain. It also comprises a few [[assembly language]] functions where needed, mostly in architecture-specific scheduler routines.


=== Process management ===
FreeRTOS provides methods for multiple [[Thread (computing)|threads]] or [[Task (computing)|tasks]], [[mutex]]es, [[Semaphore (programming)|semaphores]] and [[software timer]]s. A [[Tickless kernel|tickless]] mode is provided for low power applications. Thread priorities are supported. FreeRTOS applications can be statically allocated, but objects can also be dynamically allocated with five schemes of [[memory management]] (allocation):
FreeRTOS provides methods for multiple [[Thread (computing)|threads]] or [[Task (computing)|tasks]], [[mutex]]es, [[Semaphore (programming)|semaphores]] and [[software timer]]s. A [[Tickless kernel|tickless]] mode is provided for low power applications. Thread priorities are supported. FreeRTOS applications can be statically allocated, but objects can also be dynamically allocated with five schemes of [[memory management]] (allocation):
* allocate only;
* allocate only;
Line 38: Line 40:
* an alternative to the more complex scheme that includes memory coalescence that allows a heap to be broken across multiple memory areas.
* 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.
* and C library allocate and free with some mutual exclusion protection.
RTOS typically does not have the more advanced features that are typically found in [[operating system]]s like [[Linux]] and [[Microsoft Windows]], such as [[device driver]]s, advanced memory management, user accounts. 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 [[input/output]] (I/O) abstraction are available.
RTOSes typically do not have the more advanced features that are found in [[operating system]]s like [[Linux]] and [[Microsoft Windows]], such as [[device driver]]s, advanced memory management, and user accounts. 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 [[input/output]] (I/O) abstraction 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 to 10 milliseconds (1/1000 to 1/100 of a second), via an interrupt from a hardware timer, but this interval is often changed to suit a given application.
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 to 10 milliseconds ({{frac|1|1000}} to {{frac|1|100}} of a second) via an interrupt from a hardware timer, but this interval is often changed to suit a given application.


The software distribution contains prepared configurations and demonstrations for every port and compiler, allowing rapid application design. The project website provides documentation and RTOS tutorials, and details of the RTOS design.
The software distribution contains prepared configurations and demonstrations for every port and compiler, allowing rapid application design. The project website provides documentation and RTOS tutorials, and details of the RTOS design.
Line 138: Line 140:
** STR7
** STR7
* [[Texas Instruments]]
* [[Texas Instruments]]
** C2000 series (TMS320F28x)
** [[MSP430]]
** [[MSP430]]
** Stellaris
** Stellaris
Line 148: Line 151:
== Derivations ==
== Derivations ==
=== Amazon FreeRTOS ===
=== Amazon FreeRTOS ===
[[Amazon (company)|Amazon]] provides an extension of FreeRTOS, referred to as ''a:FreeRTOS''. This is FreeRTOS with libraries for [[Internet of things]] (IoT) support, specifically for [[Amazon Web Services]]. Since version 10.0.0 in 2017, Amazon has taken stewardship of the FreeRTOS code, including any updates to the original kernel.<ref>{{cite web |title=Amazon FreeRTOS |url=https://aws.amazon.com/freertos/ |publisher=Amazon |access-date=28 November 2018}}</ref><ref>{{cite web |title=FAQ: Amazon FreeRTOS |url=https://www.freertos.org/FAQ_Amazon.html |publisher=FreeRTOS |access-date=28 November 2018}}</ref><ref>{{cite web |title=Amazon FreeRTOS is a new OS for IoT |url=https://techcrunch.com/2017/11/29/amazon-freertos-is-a-new-operating-system-for-microcontroller-based-iot-devices/ |publisher=TechCrunch |access-date=4 December 2018}}</ref>
[[Amazon (company)|Amazon]] provides a now deprecated extension of FreeRTOS, this is FreeRTOS with libraries for [[Internet of things]] (IoT) support, specifically for [[Amazon Web Services]]. Since version 10.0.0 in 2017, Amazon has taken stewardship of the FreeRTOS code, including any updates to the original kernel.<ref>{{cite web |title=Amazon FreeRTOS |url=https://aws.amazon.com/freertos/ |publisher=Amazon |access-date=28 November 2018}}</ref><ref>{{cite web |title=FAQ: Amazon FreeRTOS |url=https://www.freertos.org/FAQ_Amazon.html |publisher=FreeRTOS |access-date=28 November 2018}}</ref><ref>{{cite web |title=Amazon FreeRTOS is a new OS for IoT |date=29 November 2017 |url=https://techcrunch.com/2017/11/29/amazon-freertos-is-a-new-operating-system-for-microcontroller-based-iot-devices/ |publisher=TechCrunch |access-date=4 December 2018}}</ref>


=== SAFERTOS ===
=== SAFERTOS ===
Line 155: Line 158:
SAFERTOS was developed by Wittenstein High Integrity Systems, in partnership with Real Time Engineers Ltd, primary developer<ref name=EETimes2012/> of the FreeRTOS project.<ref name=FreeRTOS>{{cite web|url=http://www.freertos.org/|title=FreeRTOS|access-date=8 Aug 2012}}</ref> Both SAFERTOS and FreeRTOS share the same scheduling algorithm, have similar application programming interfaces ([[API]]s), and are otherwise very similar,<ref name=SmartBotPaper>{{cite web|url=http://www.ece.stevens-tech.edu/~ymeng/publications/IROS08_SMARbot_meng.pdf|title=SmartBotPaper|access-date=8 Aug 2012|url-status=dead|archive-url=https://web.archive.org/web/20120704013911/http://www.ece.stevens-tech.edu/~ymeng/publications/IROS08_SMARbot_meng.pdf|archive-date=2012-07-04}}</ref> but they were developed with differing objectives.<ref name="freertos_a">[http://www.freertos.org/FreeRTOS-Plus/Safety_Critical_Certified/SafeRTOS.shtml Relationship between FreeRTOS and SAFE'''RTOS''']</ref> SAFERTOS was developed solely in the [[C language]] to meet requirements for certification to IEC61508.<ref name=EETimesSafetyCritical>{{cite web|url=http://www.eetimes.com/design/embedded/4007228/How-to-verify-your-compiler-for-use-in-IEC-61508-safety-critical-applications|title=EETimesSafetyCritical|access-date=8 Aug 2012}}</ref>
SAFERTOS was developed by Wittenstein High Integrity Systems, in partnership with Real Time Engineers Ltd, primary developer<ref name=EETimes2012/> of the FreeRTOS project.<ref name=FreeRTOS>{{cite web|url=http://www.freertos.org/|title=FreeRTOS|access-date=8 Aug 2012}}</ref> Both SAFERTOS and FreeRTOS share the same scheduling algorithm, have similar application programming interfaces ([[API]]s), and are otherwise very similar,<ref name=SmartBotPaper>{{cite web|url=http://www.ece.stevens-tech.edu/~ymeng/publications/IROS08_SMARbot_meng.pdf|title=SmartBotPaper|access-date=8 Aug 2012|url-status=dead|archive-url=https://web.archive.org/web/20120704013911/http://www.ece.stevens-tech.edu/~ymeng/publications/IROS08_SMARbot_meng.pdf|archive-date=2012-07-04}}</ref> but they were developed with differing objectives.<ref name="freertos_a">[http://www.freertos.org/FreeRTOS-Plus/Safety_Critical_Certified/SafeRTOS.shtml Relationship between FreeRTOS and SAFE'''RTOS''']</ref> SAFERTOS was developed solely in the [[C language]] to meet requirements for certification to IEC61508.<ref name=EETimesSafetyCritical>{{cite web|url=http://www.eetimes.com/design/embedded/4007228/How-to-verify-your-compiler-for-use-in-IEC-61508-safety-critical-applications|title=EETimesSafetyCritical|access-date=8 Aug 2012}}</ref>


SAFERTOS can reside solely in the on-chip [[read-only memory]] (ROM) of a microcontroller for standards compliance.<ref name=EmbeddedSystemsDesign>{{cite web|url=http://www.nxtbook.com/nxtbooks/cmp/esd-europe0607/index.php?startpage=32|title=Embedded Systems Design Europe|access-date=10 Aug 2012}}</ref> When implemented in hardware memory, SAFERTOS code can only be used in its original, certified configuration. This means certifying a system needs no retesting of the kernel portion of a design.<ref name="TexasInstruments">{{cite web|url=http://www.ti.com/lit/wp/spry180/spry180.pdf|title=Texas Instruments|access-date=10 Sep 2012|archive-url=https://web.archive.org/web/20130704175730/http://www.ti.com/lit/wp/spry180/spry180.pdf|archive-date=4 July 2013|url-status=dead}}</ref> SAFERTOS is included in the ROM of some Stellaris Microcontrollers<ref name="TI Stellaris Product range">[http://www.ti.com/lsds/ti/microcontroller/arm_stellaris/overview.page TI Stellaris Product range]</ref> from Texas Instruments. SAFERTOS source code does not need to be separately purchased. In this usage scenario, a C header file is used to map SAFERTOS API functions to their location in read-only memory.
SAFERTOS can reside solely in the on-chip [[read-only memory]] (ROM) of a microcontroller for standards compliance.<ref name=EmbeddedSystemsDesign>{{cite web|url=http://www.nxtbook.com/nxtbooks/cmp/esd-europe0607/index.php?startpage=32|title=Embedded Systems Design Europe|access-date=10 Aug 2012|archive-date=23 October 2012|archive-url=https://web.archive.org/web/20121023125706/http://www.nxtbook.com/nxtbooks/cmp/esd-europe0607/index.php?startpage=32|url-status=dead}}</ref> When implemented in hardware memory, SAFERTOS code can only be used in its original, certified configuration. This means certifying a system needs no retesting of the kernel portion of a design.<ref name="TexasInstruments">{{cite web|url=http://www.ti.com/lit/wp/spry180/spry180.pdf|title=Texas Instruments|access-date=10 Sep 2012|archive-url=https://web.archive.org/web/20130704175730/http://www.ti.com/lit/wp/spry180/spry180.pdf|archive-date=4 July 2013|url-status=dead}}</ref> SAFERTOS is included in the ROM of some Stellaris Microcontrollers<ref name="TI Stellaris Product range">[http://www.ti.com/lsds/ti/microcontroller/arm_stellaris/overview.page TI Stellaris Product range]</ref> from Texas Instruments. SAFERTOS source code does not need to be separately purchased. In this usage scenario, a C header file is used to map SAFERTOS API functions to their location in read-only memory.


=== OPENRTOS ===
=== OPENRTOS ===
OPENRTOS is a commercially-licensed version of Amazon FreeRTOS, sold by WITTENSTEIN High Integrity Systems. This product provides support and allows companies to use the Amazon FreeRTOS kernel and libraries without the a:FreeRTOS MIT license.<ref>{{cite web |title=OPENRTOS |url=https://www.highintegritysystems.com/openrtos/ |publisher=High Integrity Systems |access-date=28 November 2018}}</ref><ref>{{cite web |title=FreeRTOS open source licensing |url=https://www.freertos.org/a00114.html#commercial |publisher=FreeRTOS |access-date=28 November 2018}}</ref>
OPENRTOS is a commercially licensed version of Amazon FreeRTOS, sold by Wittenstein High Integrity Systems. This product provides support and allows companies to use the Amazon FreeRTOS kernel and libraries without the a:FreeRTOS MIT license.<ref>{{cite web |title=OPENRTOS |url=https://www.highintegritysystems.com/openrtos/ |publisher=High Integrity Systems |access-date=28 November 2018}}</ref><ref>{{cite web |title=FreeRTOS open source licensing |url=https://www.freertos.org/a00114.html#commercial |publisher=FreeRTOS |access-date=28 November 2018}}</ref>


== See also ==
== See also ==
Line 174: Line 177:
{{Microkernel}}
{{Microkernel}}


[[Category:Amazon Web Services]]
[[Category:ARM operating systems]]
[[Category:ARM operating systems]]
[[Category:Embedded operating systems]]
[[Category:Embedded operating systems]]
Line 180: Line 184:
[[Category:Microkernels]]
[[Category:Microkernels]]
[[Category:Real-time operating systems]]
[[Category:Real-time operating systems]]
[[Category:Amazon Web Services]]
[[Category:X86 operating systems]]

Latest revision as of 13:14, 20 October 2024

FreeRTOS
DeveloperAmazon Web Services
Written inC
OS familyReal-time operating systems
Working stateCurrent
Source modelOpen source
Initial release2003; 21 years ago (2003)
Latest release11.1.0[1] / April 22, 2024; 7 months ago (2024-04-22)
Repository
Marketing targetEmbedded systems
Available inEnglish
PlatformsARM (ARM7, ARM9, Cortex-M3, -M4, -M7, -A, -R4), 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 series MB91460, MB96340, Nios II, TMS570, RM4x, Espressif ESP32, RISC-V (e.g. SHAKTI)
Kernel typeReal-Time Microkernel
LicenseMIT[2]
Official websitewww.freertos.org

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

History

[edit]

The FreeRTOS kernel was originally developed by Richard Barry around 2003, and was later developed and maintained by Barry's company, Real Time Engineers Ltd. In 2017, the firm passed stewardship of the FreeRTOS project to Amazon Web Services (AWS). Barry continues to work on FreeRTOS as part of an AWS team.[6] With the transition to Amazon control, subsequent releases of the project also switched licensing from GPL version 2 (with special exceptions for static linking to proprietary code outside the FreeRTOS kernel itself) to MIT.[7]

Implementation

[edit]

FreeRTOS is designed to be small and simple. It is mostly written in the C programming language to make it easy to port and maintain. It also comprises a few assembly language functions where needed, mostly in architecture-specific scheduler routines.

Process management

[edit]

FreeRTOS provides methods for multiple threads or tasks, mutexes, semaphores and software timers. A tickless mode is provided for low power applications. Thread priorities are supported. FreeRTOS applications can be statically allocated, but objects can also be dynamically allocated with five schemes of memory management (allocation):

  • 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.

RTOSes typically do not have the more advanced features that are found in operating systems like Linux and Microsoft Windows, such as device drivers, advanced memory management, and user accounts. 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 input/output (I/O) abstraction 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 to 10 milliseconds (1⁄1000 to 1⁄100 of a second) via an interrupt from a hardware timer, but this interval is often changed to suit a given application.

The software distribution contains prepared configurations and demonstrations for every port and compiler, allowing rapid application design. The project website provides documentation and RTOS tutorials, and details of the RTOS design.

Key features

[edit]
  • Book and reference manuals.
  • Small memory size, 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 multitasking.
  • 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, a commercial tool by FreeRTOS partner Percepio, can thereby record and visualize the runtime behavior of FreeRTOS-based systems for debugging and verification. This includes task scheduling and kernel calls for semaphore and queue operations.

Supported architectures

[edit]

Derivations

[edit]

Amazon FreeRTOS

[edit]

Amazon provides a now deprecated extension of FreeRTOS, this is FreeRTOS with libraries for Internet of things (IoT) support, specifically for Amazon Web Services. Since version 10.0.0 in 2017, Amazon has taken stewardship of the FreeRTOS code, including any updates to the original kernel.[9][10][11]

SAFERTOS

[edit]

SAFERTOS was developed as a complementary version of FreeRTOS, with common functions, but designed for safety-critical implementation. FreeRTOS was subject to hazard and operability study (HAZOP), and weaknesses were identified and resolved. The result was put through a full IEC 61508 SIL 3 development lifecycle, the highest level for a software-only component.

SAFERTOS was developed by Wittenstein High Integrity Systems, in partnership with Real Time Engineers Ltd, primary developer[3] of the FreeRTOS project.[12] Both SAFERTOS and FreeRTOS share the same scheduling algorithm, have similar application programming interfaces (APIs), and are otherwise very similar,[13] but they were developed with differing objectives.[14] SAFERTOS was developed solely in the C language to meet requirements for certification to IEC61508.[15]

SAFERTOS can reside solely in the on-chip read-only memory (ROM) of a microcontroller for standards compliance.[16] When implemented in hardware memory, SAFERTOS code can only be used in its original, certified configuration. This means certifying a system needs no retesting of the kernel portion of a design.[17] SAFERTOS is included in the ROM of some Stellaris Microcontrollers[18] from Texas Instruments. SAFERTOS source code does not need to be separately purchased. In this usage scenario, a C header file is used to map SAFERTOS API functions to their location in read-only memory.

OPENRTOS

[edit]

OPENRTOS is a commercially licensed version of Amazon FreeRTOS, sold by Wittenstein High Integrity Systems. This product provides support and allows companies to use the Amazon FreeRTOS kernel and libraries without the a:FreeRTOS MIT license.[19][20]

See also

[edit]

References

[edit]
  1. ^ "FreeFTOS Github Releases". GitHub. 2024-04-22.
  2. ^ "FreeRTOS open source licensing". 2017-12-22.
  3. ^ a b "2011 Embedded Market Study". EE Times. Archived from the original on 2012-04-02.
  4. ^ 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.
  5. ^ "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 functions, inter-task communication, timing, and synchronisation primitives only. This means it is more accurately described as a real time kernel, or real time executive. …
  6. ^ "RTOS - Free professionally developed and robust real time operating system for small embedded systems development".
  7. ^ "Update to MIT licensed FreeRTOS V10.0.0".
  8. ^ "Using FreeRTOS on RISC-V Microcontrollers". FreeRTOS. Retrieved 11 September 2019.
  9. ^ "Amazon FreeRTOS". Amazon. Retrieved 28 November 2018.
  10. ^ "FAQ: Amazon FreeRTOS". FreeRTOS. Retrieved 28 November 2018.
  11. ^ "Amazon FreeRTOS is a new OS for IoT". TechCrunch. 29 November 2017. Retrieved 4 December 2018.
  12. ^ "FreeRTOS". Retrieved 8 Aug 2012.
  13. ^ "SmartBotPaper" (PDF). Archived from the original (PDF) on 2012-07-04. Retrieved 8 Aug 2012.
  14. ^ Relationship between FreeRTOS and SAFERTOS
  15. ^ "EETimesSafetyCritical". Retrieved 8 Aug 2012.
  16. ^ "Embedded Systems Design Europe". Archived from the original on 23 October 2012. Retrieved 10 Aug 2012.
  17. ^ "Texas Instruments" (PDF). Archived from the original (PDF) on 4 July 2013. Retrieved 10 Sep 2012.
  18. ^ TI Stellaris Product range
  19. ^ "OPENRTOS". High Integrity Systems. Retrieved 28 November 2018.
  20. ^ "FreeRTOS open source licensing". FreeRTOS. Retrieved 28 November 2018.
[edit]
Wikimedia Commons has media related to FreeRTOS.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=FreeRTOS&oldid=1252238010"