Skip to main content
Concept guide · AUTOSAR + ISO 26262 · 12 chapters

AUTOSAR Functional Safety

Learn which AUTOSAR Classic and Adaptive mechanisms answer which interference channel of ISO 26262, what a qualified stack still leaves to the integrator, and how the evidence reaches the safety case.

Chapters
12
Chapters
Platforms: Classic and Adaptive
2
Platforms: Classic and Adaptive
Interference channels
3
Interference channels
Worked integration example
1
Worked integration example
The short version

Quick answers

How does AUTOSAR support functional safety in ISO 26262?
AUTOSAR is a toolbox of specified safety mechanisms, not a certificate. The Classic and Adaptive platforms provide standardized mechanisms that answer the three interference channels of ISO 26262-6: memory partitioning through MPU-backed OS-Applications, timing protection through execution budgets and arrival frames, program-flow supervision through the Watchdog Manager, and end-to-end communication protection through the E2E profiles. The AUTOSAR specifications themselves are quality-managed documents: only a qualified vendor implementation, integrated with its assumptions of use verified, can carry safety claims into a project. Understanding which mechanism owns which fault is the core skill of AUTOSAR safety engineering.
Is AUTOSAR ASIL D certified?
No. An AUTOSAR specification cannot be ASIL anything, because a specification is a document, not a product. The specifications are developed under quality management, and safety claims attach only to a specific vendor implementation that was developed or qualified according to ISO 26262. Even then, the vendor ships a safety manual full of assumptions of use, and every one of those assumptions must be verified in your integration before the claim holds. "We use a qualified stack, so it is safe" hides exactly this gap.
Why this course · ISO 26262, Part 6

Why it pays for itself

Map mechanisms to interference channels

Point at any AUTOSAR safety mechanism (MPU partitions, OS timing budgets, Watchdog Manager, E2E protection) and name which fault, on which of the three interference channels, it detects or contains.

Choose a mixed-ASIL strategy

Compare the three practical patterns for QM and ASIL software on one ECU (full MPU barriers, defensive ASIL islands, or a qualified silent stack) and pick one you can defend.

Make the FTTI arithmetic close

The worked lane-keeping example builds a fault tolerant time interval budget across two platforms and traces every slice of it to a configured parameter and a measurement.

After the course

What you’ll be able to do

Map mechanisms to interference channels

Name which AUTOSAR mechanism detects or contains which memory, timing or communication fault, and where its coverage ends.

Choose a mixed-ASIL pattern

Pick and defend a partitioning strategy for QM and ASIL software sharing one ECU.

Configure meaningful supervision

Set up Watchdog Manager supervision and E2E protection so that they detect the faults your safety concept relies on.

Work across both platforms

Decide per function between Classic and Adaptive and keep supervision intact across the boundary.

Assemble integration evidence

Verify vendor assumptions of use and connect platform evidence to your own safety case.

The curriculum · 12 chapters

Chapter by chapter

  1. 01

    Why AUTOSAR Meets ISO 26262

    Separate what the AUTOSAR platform contributes to a safety project from what it leaves to you, and find the safety-related corner of the specification set.

    • What AUTOSAR is
    • What the platform gives
    • What it does not give
  2. 02

    The Classic Platform Through a Safety Lens

    Read the layered Classic architecture as a safety engineer: three interference channels, the mechanism family answering each, and why the mechanisms are stacked.

    • Layered architecture
    • Three channels, three families
    • Defense in depth
  3. 03

    Mixed-ASIL Integration Strategies

    Compare the partitioning patterns used in practice to host QM and ASIL software on one ECU, including the awkward role of shared basic software.

    • The coexistence problem
    • Three partitioning patterns
    • Basic software serves everyone
  4. 04

    Memory Protection & OS Partitioning

    Follow OS-Applications, a partitioned memory map and a blocked write through the MPU, then see what memory partitioning leaves uncovered.

    • OS-Applications
    • Partitioned memory map
    • Service protection
  5. 05

    Timing Protection & Execution Integrity

    See how a shared core loses time, how execution budgets bound the loss, why a bound is not a deadline guarantee, and what multi-core adds.

    • Execution budgets
    • Bound versus deadline
    • Multi-core interference paths
  6. 06

    The Watchdog Manager

    Learn why a timer-serviced watchdog proves little, and how alive, deadline and logical supervision escalate a bad cycle toward a hardware reset.

    • Three supervision functions
    • Escalation to reset
    • Meaningful supervision
  7. 07

    End-to-End Communication Protection

    Work through the black-channel idea, which E2E ingredient catches which communication fault, the profile family and the work the receiver must do.

    • The black channel
    • The profile family
    • Receiver responsibilities
  8. 08

    Complex Device Drivers & Integration Risk Areas

    Treat the complex device driver as the sanctioned shortcut it is, see why assessors open it first, and check the other integration gaps.

    • The CDD shortcut
    • Assessor focus
    • Integrator gap list
  9. 09

    The Adaptive Platform

    Understand why Classic could not stretch to high-performance computers, which Adaptive functional clusters matter for safety, and how dynamic behavior is contained.

    • Safety-relevant clusters
    • New enforcers
    • Taming the dynamics
  10. 10

    Classic vs Adaptive

    Compare the two platforms on safety terms, choose per function, and combine them with a supervision chain that crosses the platform boundary.

    • Platform comparison
    • Choosing per function
    • Cross-platform supervision
  11. 11

    Safety Case & Qualification

    Trace the evidence supply chain from stack vendor to integrator, read assumptions of use as part of the product, and plan tool confidence for generated code.

    • Evidence supply chain
    • Assumptions of use
    • Generated code
  12. 12

    Worked Example & Pitfalls

    Follow a lane-keeping steering-torque path from an Adaptive computer to a Classic ECU, make its timing budget close, and review how mechanisms get defeated.

    • Lane keeping scenario
    • Closing the timing budget
    • Defeated mechanisms

Read all 12 chapters with Expert.

Start with a free account: the complete Functional Safety Concept guide and 5 practice exams a month, then upgrade when you need this guide.

Expert plan pricing
Interactive figures

Not just text: the visual toolkit

Classic Platform layer stack

An interactive view of the Classic layers showing where each safety mechanism sits.

Detection latency ladder

The defense-in-depth detectors placed on one latency axis, from hardware checks to supervision.

Supervision function explorer

Alive, deadline and logical supervision side by side, each with the fault it is built to see.

E2E bit-flip lab

Protect a message at the sender, corrupt it in transit and watch the receiver checks respond.

MPU versus MMU

How the same pointer resolves under a Classic MPU and under an Adaptive MMU address space.

Worked Example

Lane Keeping Across Two Platforms

The final chapter follows one steering-torque request from an Adaptive high-performance computer to a Classic actuator ECU and assigns every threat on that path to a mechanism.

  • The scenario and the safety goal behind the steering-torque request
  • Each threat on the path paired with the mechanism that owns it
  • A timing budget that must close against the fault tolerant time interval
  • The ways these mechanisms are commonly defeated in real integrations
Lane keeping threat map
Path: Adaptive lane-keeping application to Classic steering ECU

Unlock in course

Built for

Who this guide is for

  • Integrators putting QM and ASIL software on the same ECU
  • BSW engineers configuring the OS, Watchdog Manager, or E2E protection
  • Safety engineers verifying vendor safety manuals and assumptions of use
  • Architects weighing Classic versus Adaptive for a high-performance computer

Frequently Asked Questions

Common questions about AUTOSAR Functional Safety

End-to-end (E2E) protection guards safety-relevant communication against a seven-fault model: corruption, repetition, loss, delay, insertion, masquerade, and wrong sequence. It combines four ingredients (a CRC, a sequence counter, a data ID, and receiver-side timeout supervision) packaged into standardized profiles sized for different buses and payloads. Data IDs also have to be managed consistently across the network, otherwise masquerade detection is weakened.
Classic targets deeply embedded control ECUs: a statically configured OS with MPU-backed OS-Applications, scalability classes SC1 to SC4, and the Watchdog Manager for supervision. Adaptive targets high-performance computers: a POSIX-based, C++ platform where processes in MMU address spaces replace MPU partitions, Platform Health Management takes over the Watchdog Manager role, and Execution and State Management drive recovery and degradation. The mechanisms translate rather than disappear: E2E rides ara::com, so the black-channel argument survives the jump from signals to services.
The guide runs 12 chapters covering both platforms, the three interference channels and their mechanisms, mixed-ASIL integration patterns, complex device drivers, and the safety case and qualification evidence. It closes with a worked example in which a lane-keeping function on an Adaptive computer sends steering torque to a Classic ECU, with each threat on that path assigned to one owning mechanism. A free account starts you off, and the Pro and Expert plans unlock more of the library.

Start the course today

A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov and RBD simulators, and 5 practice exams per month. The Pro and Expert plans unlock more of the 93-guide library. No credit card required.

Continue with

Where this topic leads next.

Browse all 93 guides
  • SoftwareLinux and Open-Source SafetyBuilding an ISO 26262 safety case for software nobody developed for you: pin down the exact kernel as an element, choose between qualification, proven-in-use and ISO PAS 8926, and guard Linux with external safety mechanisms.Expert plan pricing13 chapters
  • SoftwareSW Critical Path & Dependent Failure AnalysisLearn how to identify safety-critical software execution paths and prioritize verification effort where it matters most. Covers control flow analysis, dependent failure analysis (DFA), and strategic placement of safety mechanisms.Expert plan pricing7 chapters
  • Safety analysesSafety AnalysesLearn how HARA, FMEA, FTA, STPA, DFA, and HAZOP complement each other across the ISO 26262 lifecycle. Covers method selection criteria, analysis sequencing, and a guide to choosing the right technique for each risk.Expert plan pricing12 chapters