Master'sAutonomous, ADAS & Software-Defined Vehicle Applications open

Master’s in RTOS and Hypervisor Engineering in Automotive — Partitioning, Isolation and Mixed Criticality

Online master's programme of 1,900 hours in automotive RTOS and hypervisor engineering, structured in 12 modules covering real-time theory, RTOS on microcontrollers and application processors, automotive hypervisors, spatial and temporal partitioning and isolation, mixed criticality, secure boot and functional safety under ISO 26262, AUTOSAR Classic Platform and IEC 61508, with an assigned technical tutor.

Duration1900 h
ModeOnline
LanguageEnglish
Start datesSet by the faculty
AwardSEIUM Institute diploma
Virtual lab · try it before you enrol

Take the controls.

Run a real engineering trade-off from this field. Move the sliders, watch the model react in real time and beat the challenge.

SIM · LIVE ●
Learning outcomes

What you will be able to do

01

Apply real-time scheduling theory.

02

Configure RTOS on microcontrollers and application processors.

03

Deploy hypervisors on automotive platforms.

04

Ensure spatial and temporal isolation between partitions.

05

Design mixed-criticality systems.

06

Apply functional safety requirements to base software.

07

Develop a complete RTOS and hypervisor project.

Profile

Who it's for

  • Embedded operating systems engineers working with AUTOSAR OS, QNX or Linux.
  • Virtualisation engineers consolidating ECUs with hypervisors.
  • Real-time software engineers responsible for timing and scheduling analysis.
  • Platform architects defining partitioning and mixed-criticality strategies.
  • Software functional safety engineers working on base software.
  • BSP integration engineers bringing up automotive boards.
  • Engineering or science graduates aiming to enter the automotive sector.
Standards & tools

What you'll work with

  • ISO 26262 (functional safety of road vehicles)
  • AUTOSAR Classic Platform (standard architecture for automotive ECUs)
  • IEC 61508 (functional safety of E/E/PE systems)
  • ISO/SAE 21434 (road vehicle cybersecurity engineering)
  • ISO 17356-3 (OSEK/VDX operating system)
  • IEEE 1003.1 (POSIX operating system interface)
  • ARINC 653 (partitioning for avionics application software)
  • MISRA C:2012 (coding guidelines for safety-critical C)
  • QNX Neutrino
  • Xen Project
  • FreeRTOS
  • Zephyr
  • Lauterbach TRACE32
Syllabus

12 modules · 1900 h

  1. 1.1Requirements of automotive embedded software
  2. 1.2Real-time operating systems
  3. 1.3General-purpose operating systems
  4. 1.4Mixed criticality in vehicles
  5. 1.5OSEK and AUTOSAR OS
  6. 1.6QNX, VxWorks and Zephyr
  7. 1.7Automotive Linux
  8. 1.8Hypervisors in the vehicle
  9. 1.9Trends in ECU consolidation
  10. 1.10Case study: OS map of a vehicle
  1. 2.1Periodic and sporadic tasks
  2. 2.2Fixed-priority scheduling
  3. 2.3Rate monotonic and deadline monotonic
  4. 2.4Earliest Deadline First scheduling
  5. 2.5Response-time analysis
  6. 2.6Priority inversion
  7. 2.7Priority inheritance protocols
  8. 2.8Worst-case execution time (WCET) analysis
  9. 2.9Partitioned and global multi-core scheduling
  10. 2.10Lab: RTA of a task set
  1. 3.1AUTOSAR OS architecture
  2. 3.2Tasks and interrupts
  3. 3.3Resources and alarms
  4. 3.4Memory protection
  5. 3.5Timing protection of tasks
  6. 3.6Multi-core in AUTOSAR OS
  7. 3.7FreeRTOS and SAFERTOS
  8. 3.8Zephyr RTOS in automotive
  9. 3.9RTOS configuration
  10. 3.10Practical exercise: AUTOSAR OS configuration
  1. 4.1QNX Neutrino architecture
  2. 4.2Microkernel and message passing
  3. 4.3Adaptive partitioning in QNX
  4. 4.4Linux with the PREEMPT_RT patch
  5. 4.5Interrupt latencies
  6. 4.6RTOS certification
  7. 4.7Real-time POSIX
  8. 4.8Drivers and services
  9. 4.9RTOS comparison
  10. 4.10Workshop: latency measurement with cyclictest
  1. 5.1Type 1 and type 2 hypervisors
  2. 5.2Hardware-assisted virtualisation
  3. 5.3Xen and QNX Hypervisor
  4. 5.4Lightweight hypervisors and separation kernels
  5. 5.5Static resource partitioning
  6. 5.6Device virtualisation
  7. 5.7VirtIO paravirtualised devices
  8. 5.8Inter-VM communication
  9. 5.9Virtualisation performance and overhead
  10. 5.10Lab: Xen on an ARM board
  1. 6.1Spatial memory partitioning
  2. 6.2Temporal resource partitioning
  3. 6.3MMU and MPU
  4. 6.4SMMU for peripherals
  5. 6.5Cache isolation
  6. 6.6Memory interference
  7. 6.7Cache colouring and cache partitioning
  8. 6.8Bandwidth control
  9. 6.9Isolation assessment
  10. 6.10Practical exercise: cache colouring in Xen
  1. 7.1Mixed-criticality models
  2. 7.2Freedom from interference
  3. 7.3Coexistence of ASILs
  4. 7.4Consolidation architectures
  5. 7.5Fault management between partitions
  6. 7.6Boot and start-up order
  7. 7.7Cross-partition monitoring
  8. 7.8Standards applicable to mixed criticality
  9. 7.9Cockpit use cases
  10. 7.10Case study: cockpit with Android and an RTOS
  1. 8.1Secure boot and root of trust
  2. 8.2Chain of trust
  3. 8.3Fast system boot
  4. 8.4Key management
  5. 8.5TrustZone and TEE
  6. 8.6Secure update of base software
  7. 8.7Memory protection
  8. 8.8Security isolation
  9. 8.9Hypervisor cybersecurity
  10. 8.10Workshop: secure boot on ARM
  1. 9.1ISO 26262 part 6
  2. 9.2Requirements for certified operating systems
  3. 9.3Operating system safety manual
  4. 9.4Software qualification
  5. 9.5Dependency analysis
  6. 9.6Execution timing monitoring
  7. 9.7Internal and external watchdogs
  8. 9.8Software FMEA
  9. 9.9Certification evidence
  10. 9.10Lab: freedom from interference analysis
  1. 10.1System tracing
  2. 10.2Debugging with Lauterbach tools
  3. 10.3Timing analysis
  4. 10.4Synchronised multi-core debugging
  5. 10.5Profiling of tasks and interrupts
  6. 10.6Event logging
  7. 10.7Deadlock detection
  8. 10.8Stress testing
  9. 10.9Failure analysis
  10. 10.10Practical exercise: tracing with Tracealyzer
  1. 11.1BSP integration
  2. 11.2Middleware integration
  3. 11.3Real-time testing
  4. 11.4Isolation testing
  5. 11.5HIL testing of the consolidated system
  6. 11.6Continuous integration of base software
  7. 11.7Configuration management
  8. 11.8Integration documentation
  9. 11.9Long-term maintenance
  10. 11.10Workshop: RTOS test pipeline
  1. 12.1Definition of the system
  2. 12.2Selection of RTOS and hypervisor
  3. 12.3Partitioning design
  4. 12.4System configuration
  5. 12.5Real-time analysis
  6. 12.6Safety analysis
  7. 12.7Integration and stress testing
  8. 12.8Conclusions and future work
  9. 12.9Thesis report
  10. 12.10Master's Thesis: defence before a panel
Methodology, software & labs

How you'll learn

Training is 100% online on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. There are no fixed timetables: you progress at your own pace within the intake, so the programme can be combined with work.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is QNX Neutrino, Xen Project, FreeRTOS, Zephyr and Lauterbach TRACE32, in free, academic or evaluation versions. Exercises are based on real procedures for measuring real-time latencies, analysing interference between partitions and HIL testing of consolidated systems. Assessment is continuous by module, plus the final Master's Thesis.

Standards covered: ISO 26262, AUTOSAR Classic Platform, IEC 61508, ISO/SAE 21434, ISO 17356-3 (OSEK/VDX OS), IEEE 1003.1 (POSIX), ARINC 653, MISRA C:2012.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of ISO 26262, AUTOSAR Classic Platform and IEC 61508 applied to real cases, not as a theoretical annex.
Industry software:QNX Neutrino, Xen Project, FreeRTOS, Zephyr and Lauterbach TRACE32, in free, academic or evaluation versions.
Master's Thesis with defence:A complete RTOS and hypervisor project, from system definition and partitioning design to configuration, real-time and safety analysis and integration and stress testing, defended before a panel.
Flexible format:100% online, no fixed timetables, compatible with full-time work.
Capstone project

Build it end to end

Your final project follows the real engineering workflow, step by step, reviewed by your tutor.

Define the system
Describe the consolidated ECU, its functions and their criticality levels.
Select RTOS and hypervisor
Justify the choice of RTOS and hypervisor for each partition.
Design the partitioning
Define spatial and temporal partitioning and configure the system.
Analyse timing and safety
Carry out real-time response-time analysis and freedom from interference analysis.
Master's Thesis
Run integration and stress tests on the consolidated system and draw conclusions, defended before a panel.
Career opportunities

Where this takes you

Embedded Operating Systems EngineerVirtualisation EngineerReal-Time Software EngineerPlatform ArchitectSoftware Functional Safety EngineerBSP Integration Engineer
Admissions & scholarships

Requirements

  • A university degree in engineering, science or architecture, or equivalent demonstrable professional experience.
  • An internet connection and a computer capable of running the programme's software.
  • English sufficient to read technical standards.

Ready to start?

Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.

FAQ

Frequently asked questions

The programme totals 1,900 hours over 12–14 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.

You work with QNX Neutrino, Xen Project, FreeRTOS, Zephyr and Lauterbach TRACE32, using free, academic or evaluation versions. Your tutor indicates the free alternative wherever one exists.

A SEIUM Institute diploma, awarded on passing the continuous assessment and the Master's Thesis. It is SEIUM's own qualification, not an official state degree; its recognition depends on the programme completed and the regulations of each country.

Yes. Modules passed in a course or postgraduate diploma in the same area are recognised in the higher programme. Ask about the recognition policy when you enrol.

A university degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the programme's software and English sufficient to read technical standards.

Start dates are set by SEIUM's faculty for each intake. Our admissions team will confirm the next available date when you apply.

Master’s in RTOS and Hypervisor Engineering in Automotive — Partitioning, Isolation and Mixed CriticalityEnrol
Scroll to Top
SEIUM – Institute of Advanced Engineering
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.