Tag

automotive-software

3 articles

A calibration engineer sits in the open driver door of a silver hatchback parked on a proving-ground slope, tuning values on a laptop that shows a calibration map, cabled to an interface box on the door sill.

Calibration and Configuration Data in ISO 26262

How ISO 26262 handles parameter data: why the software build separates configuration data from calibration data, how each value inherits its ASIL, what a parameter specification and its verification cover, and which mechanisms detect unintended changes of calibration data in the ECU.

7 minOct 12, 2026

An engineer at a desk writing an AUTOSAR-style CAN driver in C for an ECU, with a cross-compiler build finishing with zero errors and a laptop showing ECU software domains and CAN traffic.

Technical

Software in ISO 26262: A Fault With No Failure Rate

Software has no failure rate, so ISO 26262 cannot count it. What the standard asks for instead, why software is both the safety net for hardware faults and a source of its own, and why Part 6 converges on the software architecture.

7 minOct 1, 2026

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.

Technical

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 minAug 28, 2026