Safety and Security requirements increase with usage of mobile connectivity in the internet of things. Via a hypervisor virtualization technology different operating systems (OS) can run in parallel partitions on a single or multicore processor to serve specific use cases, such as separation from consumer bound OS to safety bound OS types, reduction of Space, Weight and Power or the re-use of legacy code from former projects.
Partitions can host a broad variety of Guest OS, i.e. guest operating systems, run-time environments (RTE) and APIs, on top of the hypervisor and support applications of different security level, different criticality level, real-time or none real-time. This variety of Guest OS enables legacy applications (e.g. Ada or legacy RTOS) to run concurrently with new applications based on standards like POSIX® or ARINC-653 and can even be combined with embedded Linux. All these Guest OS run on the same PikeOS kernel support applications in industries like aerospace & defense, automotive & transportation, industrial automation & medical, network infrastructure, and consumer electronics.
Addressable Use Cases
- Clustering software functions
- Reduce number of ECUs
- Software separation with mixed criticality
- Addressing Safety requirements and certification
- Secure SW updates
- Secure boot process
- Security artifact handling
- Graphics performance and sharing
- Audio sharing and priority handling
Partitions & Guest OS
Complete operating systems normally don‘t require a host operating system (OS) to run on, nor can they tolerate the presence of another operating system.
On PikeOS, however, a host OS can run in user-space, in non-privileged mode.
- Embedded Linux (for example ELinOS or vanilla Linux)
- µITRON
- OSEK (AUTOSAR)
- RTEMSWindows (contact us)
- Legacy RTOS: we can provide APIs that combine your Legacy OS with other operating systems, run-time environments and APIs on top of PikeOS (contact us)
Run-time Environments high performing
Execution of run-time environments need an OS host. With PikeOS RTOS run-time environments have their own schedulers and communication processes. Therefore, run-time environments run with high performance.
- POSIX® compliant
- Certifiable POSIX® compliant
- Real-time Java
- Ada
- others (contact us for special requests)
APIs on-hand
Application programming interfaces (APIs) provide an interface used to access underlying functionality.
- ARINC 653
- PikeOS native API
- others (contact us for special requests)
Board Support Packages
To see which boards are supported please have a look at our BSP-List.