SafeRTOS
This article, SafeRTOS, has recently been created via the Articles for creation process. Please check to see if the reviewer has accidentally left this template after accepting the draft and take appropriate action as necessary.
Reviewer tools: Inform author |
This article, SafeRTOS, has recently been created via the Articles for creation process. Please check to see if the reviewer has accidentally left this template after accepting the draft and take appropriate action as necessary.
Reviewer tools: Inform author |
Developer | WITTENSTEIN high integrity systems |
---|---|
OS family | Real-time operating systems |
Working state | Current |
Source model | Open source |
Marketing target | Embedded devices |
Platforms | Same as FreeRTOS |
Kernel type | Microkernel |
License | Proprietary |
Official website | http://www.highintegritysystems.com/rtos/safertos/ |
SAFERTOS is an embedded real-time, deterministic operating system specially designed for critical applications. It is available pre-certified according to key standards in markets including Industrial and Medical. First certified by TÜV SÜD in 2007, SAFERTOS was developed in compliance with IEC61508 SIL3.[1] [2] [3]
Implementation
SAFERTOS is a complementary offering to FreeRTOS, with common functionality but designed for safety critical applications.[4]
The development of SAFERTOS involved subjecting the FreeRTOS functional model to a full HAZOPS, where weaknesses within the functional model and API were identified and resolved, resulting in a set of Safety Requirements. The Functional and Safety requirements sets that define SAFERTOS were then put through a full IEC 61508 SIL 3 development life cycle, the highest possible for a software only component.
SAFERTOS is licensed as a SAFERTOS variant, where a variant is defined according to the selected micro-processor and tool chain. The API and the core SAFERTOS design and code is common between all SAFERTOS variants; the remaining port layer is adapted to support the selected micro-processor. Each SAFERTOS variant is subjected to the full IEC 61508 compliant development life cycle.
Design Assurance Pack
SAFERTOS is supplied with a Design Assurance Pack (DAP) which contains every design artefact produced during the full development life cycle, from development and safety life cycle plans, requirements specifications and design documents, to HAZOPS, the source code, all verification and validation documents and relating evidence. The full test harness, with user and safety manuals are also supplied.[5]
The Design Assurance Pack supports the product certification process.
Key features
- IEC 61508-3 SIL3 certified.
- Supports domain adaptations of IEC 61508-3.
- IEC 62304 Class C compliant.[6]
- Full Design Assurance Pack
Supported architectures
Same as FreeRTOS.
See also
References
External links
Category:Real-time operating systems
Category:Embedded operating systems
Category:Microkernel-based operating systems
References
This article, SafeRTOS, has recently been created via the Articles for creation process. Please check to see if the reviewer has accidentally left this template after accepting the draft and take appropriate action as necessary.
Reviewer tools: Inform author |
Subject of my article is SafeRTOS
Developer | WITTENSTEIN high integrity systems |
---|---|
OS family | Real-time operating systems |
Working state | Current |
Source model | Open source |
Marketing target | Embedded devices |
Platforms | Same as FreeRTOS |
Kernel type | Microkernel |
License | Proprietary |
Official website | http://www.highintegritysystems.com/rtos/safertos/ |
SAFERTOS is an embedded real-time, deterministic operating system specially designed for critical applications. It is available pre-certified according to key standards in markets including Industrial and Medical. First certified by TÜV SÜD in 2007, SAFERTOS was developed in compliance with IEC61508 SIL3.[1] [2] [3]
Implementation
SAFERTOS is a complementary offering to FreeRTOS, with common functionality but designed for safety critical applications.[4]
The development of SAFERTOS involved subjecting the FreeRTOS functional model to a full HAZOPS, where weaknesses within the functional model and API were identified and resolved, resulting in a set of Safety Requirements. The Functional and Safety requirements sets that define SAFERTOS were then put through a full IEC 61508 SIL 3 development life cycle, the highest possible for a software only component.
SAFERTOS is licensed as a SAFERTOS variant, where a variant is defined according to the selected micro-processor and tool chain. The API and the core SAFERTOS design and code is common between all SAFERTOS variants; the remaining port layer is adapted to support the selected micro-processor. Each SAFERTOS variant is subjected to the full IEC 61508 compliant development life cycle.
Design Assurance Pack
SAFERTOS is supplied with a Design Assurance Pack (DAP) which contains every design artefact produced during the full development life cycle, from development and safety life cycle plans, requirements specifications and design documents, to HAZOPS, the source code, all verification and validation documents and relating evidence. The full test harness, with user and safety manuals are also supplied.[5]
The Design Assurance Pack supports the product certification process.
Key features
- IEC 61508-3 SIL3 certified.
- Supports domain adaptations of IEC 61508-3.
- IEC 62304 Class C compliant.[6]
- Full Design Assurance Pack
Supported architectures
Same as FreeRTOS.
See also
References
- ^ Cite error: The named reference
highintegritysystems
was invoked but never defined (see the help page). - ^ Cite error: The named reference
freertos
was invoked but never defined (see the help page). - ^ Cite error: The named reference
eetimes
was invoked but never defined (see the help page). - ^ Cite error: The named reference
freertos_a
was invoked but never defined (see the help page). - ^ Cite error: The named reference
highintegritysystems_a
was invoked but never defined (see the help page). - ^ Cite error: The named reference
eetimes_a
was invoked but never defined (see the help page).
External links