Contents

Why vehicles get software updates

Vehicles receive software updates to fix faults, close security gaps, change features and keep each vehicle on the right software and configuration.

Why it exists

A vehicle needs the right software before it leaves the factory, after a repair and throughout its service life. Engineers discover faults, attackers find weaknesses, components change and customers request new functions. Replacing hardware for every change would be expensive and often unnecessary.

Software updates let manufacturers change vehicle behavior using existing hardware. They also create responsibility: an apparently small change can affect braking, emissions, battery protection or another approved function. The update discipline connects the reason for a change to a controlled, traceable installation.

What it is

A software update changes installed software or its configuration parameters. Flashing means programming software or data into an electronic control unit’s persistent memory. An electronic control unit (ECU) is a vehicle computer.

Updates have different purposes. Installing a factory release, repairing a fault and enabling a purchased feature may use similar programming mechanisms, but need different targeting, checks and records.

Over-the-air (OTA) describes wireless delivery. A backend service may send a package through the vehicle’s telematics control unit, which provides external connectivity. Wired updates use a local connection, usually from a production or workshop tester. Both paths can ultimately program the same ECU.

Wireless delivery does not mean immediate activation. A vehicle can download a package while connected and install it later under suitable conditions.

How it works

Start with the intended vehicle state: software versions, hardware compatibility, calibration, configuration and enabled functions. Then choose a delivery path and define how to verify the result.

Use case Who triggers it Typical path Can it affect type-approved systems?
End-of-line flashing Production system following the manufacturing plan Production tester Yes. Establishes the approved software and configuration baseline; later factory changes need assessment.
Workshop flashing Technician following a repair instruction or service campaign Workshop tester Yes. A replacement controller or fault repair can change approved behavior.
Bug fixes and software recalls Manufacturer’s engineering or recall process; user or technician may start installation OTA or workshop tester Yes. Assess the affected function and required approval action.
Cybersecurity patches Manufacturer after vulnerability assessment OTA or workshop tester Yes. Security changes can also alter timing, interfaces or functional behavior.
New or paid features Manufacturer release, customer purchase or fleet request OTA; sometimes workshop tester Yes, depending on the feature. Activation can change approved functionality without replacing executable code.
Calibration and parameter updates Control engineering or service organization Production tester, workshop tester or OTA Yes. Limits and control settings can affect emissions, braking or other approved characteristics.
Maps, data and content Content provider or manufacturer; user may request download OTA or local media; sometimes workshop tester Depends on use. Entertainment content differs from data that influences an approved driving function.
Configuration and variant coding Production system, technician or authorized backend Production tester, workshop tester or OTA Yes. Selecting a variant can change which functions and settings are active.

UN Regulation No. 156 covers software updates by any path, not only OTA, within its applicable scope. It includes configuration parameter changes in its update definition. It also requires assessment of effects on type-approved systems.

An RX Software Identification Number (RXSWIN) identifies information about software relevant to a particular approval regulation. It is not a universal package version. Under UN Regulation No. 156, changing approval-relevant software requires an RXSWIN update when the change leads to an approval extension or a new approval. A package therefore needs an approval assessment, not an automatic assumption that every installation changes an RXSWIN.

End-of-line programming can be an initial installation rather than an update. It still establishes the baseline against which subsequent changes are assessed.

Calibration changes values used by an algorithm, such as torque limits. Variant coding selects settings for the vehicle’s equipment or market. Neither needs a new executable to change vehicle behavior.

Likewise, classify maps and content by their effect. Replacing music artwork is different from changing map data used by a speed-control function. A “data update” label does not settle its engineering or approval relevance.

When to use it — and when not

Use production flashing to establish a known delivery state. Use workshop programming when a repair needs hands-on work, component replacement, sensor calibration or a technician’s verification.

Use OTA when compatible vehicles can install and recover safely without workshop equipment. It suits fleet-wide fixes and feature delivery, but depends on connectivity, sufficient energy and reliable targeting. A software recall may use OTA, workshop visits or both; completing a download alone does not establish that the remedy succeeded.

Use functions on demand when the vehicle has the required hardware and the feature is validated for that configuration. Separate commercial entitlement from technical eligibility: a purchase does not prove that activation is safe or approved.

Do not use an update to conceal a hardware defect that software cannot adequately address. Do not force remote installation when recovery requires a tool or physical intervention.

Best practices

  • Define the result first. Record the intended software, calibration, configuration and feature state for each eligible vehicle.
  • Assess the whole change. Check dependencies, safety, cybersecurity and approval effects, including parameter-only changes.
  • Control every delivery path. Apply authorization, package integrity checks and traceability to production testers, workshop tools and OTA services.
  • Separate delivery from activation. Define when downloading, programming and switching to the new version may occur.
  • Plan interrupted installations. Provide a validated recovery method and enough energy to finish or reach a safe state.
  • Verify completion. Read back identifiers, run required checks and report the actual installed state to the campaign records.
  • Explain the user impact. State expected unavailability, prerequisites and any action needed after installation.

Common pitfalls

  • Treating OTA as a synonym for all software updates, leaving workshop changes outside update governance.
  • Assuming a signed package is compatible with every vehicle that can receive it.
  • Calling calibration, coding or feature activation “just data” and skipping behavior assessment.
  • Assuming every software version needs a new RXSWIN, or that no executable change means no approval impact.
  • Recording download success as installation success.
  • Closing a campaign while vehicles remain on mixed or unverified software states.

What it means for your discipline

  • Software update & OTA Core

    Defines update packages, vehicle eligibility, installation conditions and recovery paths; tracks which vehicles reached the intended software state.

  • Diagnostics & lifecycle Partial

    Implements production and workshop programming sequences, checks vehicle identity and records successful flashing and configuration.

  • HPC & application software Partial

    Delivers compatible software and calibration packages, declares dependencies and verifies behavior after installation.

  • Cybersecurity Partial

    Assesses vulnerabilities, protects update packages and authorizes which tools and services may install them.

  • Functional safety Partial

    Reviews changes to safety-related behavior and defines safe installation conditions, recovery behavior and required checks.

No direct stake: E/E architecture · Base software · Hardware & silicon · Networks & communication

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • OTA client · UCM — Installs compatible software and data packages, controls activation conditions and reports the resulting vehicle configuration.
  • Diagnostics — Supports production and workshop access to software versions, configuration and installation results.
  • Security services — Authenticates update packages and authorizes tools or services that install software or activate features.
MCU-based ECU · AUTOSAR Classic
  • Flash bootloader · secure boot — Programs executable software and calibration images during production, workshop repairs and remotely orchestrated updates.
  • Diagnostics — Provides diagnostic programming access, variant coding and routines used to verify the installed state.
  • Memory · crypto · WdgM — Persists calibration values, variant settings and software configuration across resets.