Skip to main content
Category

Technical

45 articles

A line of commit dots labelled as the mainline runs off the right edge. One dot is ringed in red, and a dashed line drops from it into a card holding five chips: source revision, patch list, configuration, toolchain, build recipe.

Qualifying Linux for ISO 26262: Pinning the Open-Source Element

You cannot qualify Linux. You can qualify one build of it. ISO 26262 allocates requirements to elements, and an element has to hold still. A mainline kernel does the opposite. Open source gives you more visibility than any commercial supplier will. What it does not give you is traceability from a safety requirement to the test that shows it is met. So the first work product is not a gap analysis. It is a definition: exact source revision, vendor patches, reviewed configuration, toolchain, build recipe. Hand those to an engineer who was not in the room. If they cannot arrive at your binary, or explain every difference, you do not have an element. New article on the prerequisites, and why no qualification route can be chosen before the element exists.

9 min
Plan view of a road. In the next lane an overtaking vehicle is drawn twice: a dashed grey outline where the mirror panel still shows it, and a solid red one further ahead where it actually is, with the gap between them marked.

Interior and Mirror Cameras: The Stale Frame Problem

A mirror-replacement camera rarely fails by going blank. It fails by showing you a well-formed picture of a road that has moved on. Most of the chain answers a different question. A link CRC proves the pixels arrived intact. A register readback proves the sensor is configured. A watchdog proves the imaging task is scheduled, and a task republishing its last buffer is scheduled perfectly. So teams add a frame counter, usually in the software that receives frames. That proves only that this software is running: it keeps counting while the sensor sits dark. Even minted at the sensor, a counter is metadata: it travels next to the pixels, not inside them. A stage that re-stamps on publication can attach a fresh number to old pixels, and a header-only check waves it through. Placement earns you sequence coverage. Claiming the picture is current is a bigger claim than most safety cases support. New article on what that costs in detection budget and where the ISO 21448 boundary falls.

8 min
Car bodies on a factory assembly line, a dark hatchback with its doors and bonnet open in the foreground and a row of white and blue bodies receding down the line behind it, under overhead conveyor gantries.

ASPICE and ISO 26262: What Each One Actually Grades

ASPICE rates how capable your development process is. ISO 26262 asks whether the product it produced is acceptably safe. Neither verdict substitutes for the other. Where the two read the same artifacts, where they diverge, and the safety work that has no ASPICE process behind it.

7 min
Close-up of a densely populated circuit board, with a square multi-pin integrated circuit in sharp focus among capacitors and smaller packages.

Multi-Core Safety Architectures: An ISO 26262 Overview

Multi-core automotive SoCs add shared hardware, mixed criticality, and timing interference to every safety argument. This article maps the families of multi-core safety architecture, the three interference concerns underneath them, and what actually decides which one fits.

6 min
Technical illustration showing a generic functional-safety lifecycle being adapted into the electronic architecture of a modern road vehicle.

IEC 61508 vs ISO 26262: What Automotive Engineers Need to Know

Can an element assessed at IEC 61508 SIL 3 support an ISO 26262 ASIL D safety goal? Often yes, but the label proves nothing on its own: a SIL belongs to a safety function, not to a part. Why the two risk models look alike and still cannot be converted, and what an integrity level is attached to.

9 min
A comparison table showing the differences between automotive functional safety standard ISO 26262 and machinery standards ISO 13849 and IEC 62061.

Automotive vs Machinery Functional Safety: An ISO 26262 Comparison

While automotive and machinery functional safety share common roots, their methodologies differ significantly. Explore how ISO 26262 compares to ISO 13849 and IEC 62061 in risk assessment and system architecture.

8 min
Comparison table showing aerospace functional safety standards like DO-178C and ARP4754A next to their automotive ISO 26262 equivalents for system, software, and hardware development.

Functional Safety in Aerospace vs Automotive: An ISO 26262 Guide

Discover how aerospace functional safety standards like DO-178C and ARP4754A compare to automotive ISO 26262. Learn what automotive engineers can adapt from aviation to build robust, fail-operational architectures for autonomous vehicles.

7 min
A digital automotive instrument cluster displaying a steering failure warning, illustrating HMI safety mechanisms and ISO 26262 compliance for vehicle displays.

Mastering HMI Display Safety for Automotive ISO 26262

Automotive display systems are the final line of defense during vehicle failures. Learn how to engineer robust HMI warning strategies, manage arbitration chaos, and calculate strict timing budgets to achieve ISO 26262 compliance.

7 min
Flowchart showing the Model-Based Development workflow for ISO 26262 software engineering, including modeling guidelines, Model-in-the-Loop testing, and automatic code generation.

How to Implement Model-Based Development for ISO 26262

Discover how to accelerate automotive software engineering using Model-Based Development. This guide covers essential ISO 26262 Part 6 requirements, from enforcing strict modeling guidelines to performing Model-in-the-Loop testing and automatic code generation.

8 min
Comparison table showing differences between HAZOP, FMEA, and FTA methodologies for ISO 26262 automotive functional safety analysis.

Why HAZOP is Essential for ISO 26262: Guide-Word Analysis Explained

Discover how HAZOP uses guide-word deviation analysis to uncover hidden interface hazards in automotive systems. Learn why this methodology is essential for robust ISO 26262 functional safety concepts.

9 min
Diagram illustrating a top-down Fault Tree Analysis for ISO 26262, showing Boolean logic gates connecting an ASIL D safety goal to hardware component failures in an automotive electronic system.

Mastering FTA in ISO 26262: A Deductive Approach to E/E Safety

Discover how Fault Tree Analysis exposes hidden multi-point failures in complex automotive systems. This comprehensive guide explores top-down deductive methods to ensure robust ISO 26262 compliance.

7 min
Demystifying AV Safety: Integrating ISO 26262, SOTIF, and ML

Demystifying AV Safety: Integrating ISO 26262, SOTIF, and ML

Traditional safety standards are no longer enough for autonomous vehicles. Discover how to build a unified safety architecture by integrating ISO 26262, SOTIF, and Machine Learning to handle unpredictable real-world scenarios.

8 min

Keep learning

Go from article to full guide.

Each guide is a full course with diagrams and worked examples. Open one to see what it covers.

Browse all 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
  • Vehicle domainsInterior and Mirror CamerasThe cameras that face the other way: camera monitor systems that replace mirrors, and interior cameras that watch the driver. A mirror camera rarely fails by going blank. It fails by showing you, convincingly, where things were.Expert plan pricing15 chapters
  • SoftwareISO 26262 and Automotive SPICEOEMs demand an Automotive SPICE capability level and ISO 26262 compliance in the same statement of work, and new teams treat them as two mountains to climb. This concept shows they are one mountain seen from two sides: a shared V-model, one traceability backbone and a single set of work products.Expert plan pricing12 chapters