UCM - Update & Configuration Manager - AUTOSAR Adaptive Platform

UCM Role

UCM is the Adaptive Platform FC responsible for receiving, verifying, and installing AUTOSAR Software Packages. It exposes a SOME/IP service consumed by the OTA client application. UCM orchestrates process stops (via EM/SM), binary replacement, and restart.

UCM Responsibility	Mechanism
Receive package	TransferStart / TransferData / TransferExit SOME/IP methods
Verify integrity	RSA/EC digital signature over package; per-file SHA-256 hashes
Install	Stop affected FG → replace binaries on filesystem → update manifests
Activate	Restart affected processes via EM
Rollback	Restore previous binary set from rollback partition or backup

Update State Machine

UCM Update States

  ┌──────┐  TransferStart   ┌─────────────┐  TransferExit  ┌────────────┐
  │ Idle │ ───────────────► │ Transferring│ ─────────────► │ Processing │
  └──────┘                  └─────────────┘                └─────┬──────┘
     ▲                                                            │ Activate()
     │ Rollback() or error                               ┌────────▼─────────┐
     │                                                   │  Activating      │
     │                                                   └────────┬─────────┘
     │                                                            │ success
     └─────────────────────────────────────────────── ◄──────────┘
                                                      Activated

Integrity Verification

JSONpackage_manifest.json

{
  "packageManifest": {
    "shortName": "SensorApp_v2",
    "version": "2.0.0",
    "targetProcessRef": "SensorApp",
    "files": [
      {
        "path": "bin/SensorApp",
        "sha256": "e3b0c44298fc1c149afb....",
        "size": 1048576
      }
    ],
    "signature": {
      "algorithm": "ECDSA-SHA256",
      "certificate": "oem_codesign.pem",
      "value": "304402..."
    }
  }
}

💡 HSM Verification

The private key used to sign packages is stored in the vehicle's Hardware Security Module (HSM). UCM uses ara::crypto to verify the signature using the corresponding public key certificate, which is validated against the OEM root CA certificate installed in the platform.

Rollback Manifest

JSONrollback_manifest.json

{
  "rollbackInfo": {
    "previousVersion": "1.0.0",
    "rollbackFiles": [
      {
        "path": "bin/SensorApp",
        "sha256": "prev_hash...",
        "backupPath": "/var/ucm/backup/SensorApp_1.0.0/bin/SensorApp"
      }
    ]
  }
}

⚠️ A/B Partition vs. Backup

The most robust rollback strategy uses A/B disk partitions (one active, one standby). UCM writes the new binary to the standby partition and switches the boot loader flag on Activate. If boot fails or PHM detects health failures post-update, UCM calls Rollback() to switch back the boot flag — no file copying needed.

Summary

UCM is the only AP-standard mechanism for software updates. Its three-phase (Transfer → Process → Activate) design with signature verification and rollback support provides the production-grade OTA infrastructure needed for vehicles in service.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.