| Component | Detail |
|---|---|
| ECU | Aurix TC397 with PBL + SBL + Application; programming session accessible via CAN or DoIP |
| Images | sbl_v1.2.bin, app_v3.3.bin, cal_v2.0.bin — from CI build artefacts |
| Tool | Python script using udsoncan; or Delphi/CANoe CAPL sequence |
| Target time | Full reprogramming (SBL + App + Cal) in < 90s over CAN 500kbit/s; < 10s over DoIP 100Mbit |
Lab Setup
Complete Reprogramming Automation Script
#!/usr/bin/env python3
# Full ECU reprogramming sequence: SBL → App → Cal
import udsoncan, time
from udsoncan.client import Client
def full_reprogramming(client, sbl_path: str, app_path: str, cal_path: str):
print("=== ECU Reprogramming Sequence ===")
# Pre-conditions
speed = read_did_uint16(client, 0xF40D)
assert speed == 0, f"PRE-COND FAIL: vehicle moving at {speed} km/h"
vbat = read_did_uint16(client, 0xFD01) / 1000.0
assert 11.5 <= vbat <= 14.5, f"PRE-COND FAIL: battery {vbat}V"
print(f"Pre-conditions: speed=0 km/h, battery={vbat}V — OK")
# Session transition
client.change_session(udsoncan.services.DiagnosticSessionControl.Session.extendedDiagnosticSession)
client.communication_control(0x03, 0x01) # disable non-diag CAN TX
security_access(client, level=1)
client.change_session(udsoncan.services.DiagnosticSessionControl.Session.programmingSession)
security_access(client, level=2)
print("Session established, security unlocked")
# Download and activate SBL
download_sbl(client, sbl_path)
print("SBL active")
# Flash application block
erase_and_program(client, 0x80080000, 0x780000, app_path)
print("Application programmed")
# Flash calibration block
erase_and_program(client, 0x80800000, 0x800000, cal_path)
print("Calibration programmed")
# Check dependencies
resp = client.routine_control(0x01, 0xFF01, b'')
assert resp.positive, "Dependency check FAILED"
print("Dependency check passed")
# ECU reset
client.ecu_reset(0x03) # hard reset
time.sleep(5)
print("ECU reset complete")
# Post-flash verification
client.change_session(udsoncan.services.DiagnosticSessionControl.Session.extendedDiagnosticSession)
sw_version = read_did_bytes(client, 0xF189)
print(f"New SW version: {sw_version.hex()}")
print("=== Reprogramming COMPLETE ===" )Post-Flash Verification Checks
#!/usr/bin/env python3
# Post-flash verification: confirm ECU is running new firmware correctly
import udsoncan
from udsoncan.client import Client
def verify_after_reprogramming(client, expected_sw_version: str):
client.change_session(udsoncan.services.DiagnosticSessionControl.Session.extendedDiagnosticSession)
checks = []
# 1. SW version matches expected
resp = client.read_data_by_identifier(0xF189)
sw_ver = resp.service_data.values[0xF189].hex()
checks.append(("PASS" if sw_ver == expected_sw_version else "FAIL",
f"SW version: {sw_ver} (expected {expected_sw_version})"))
# 2. No programming-related DTCs
resp = client.get_dtc_by_status_mask(0x08) # confirmed
prog_dtcs = [d for d in resp.service_data.dtcs
if (d.id >> 16) & 0xFF == 0x70] # U-code network/prog DTCs
checks.append(("PASS" if not prog_dtcs else "FAIL",
f"Programming DTCs: {len(prog_dtcs)} (expected 0)"))
# 3. ECU responds to standard DID read (application running)
resp = client.read_data_by_identifier(0xF190) # VIN
checks.append(("PASS" if resp.positive else "FAIL", "VIN readable (application active)"))
for status, desc in checks:
print(f"[{status}] {desc}")
return all(c[0] == "PASS" for c in checks)Summary
The full reprogramming script demonstrates the production-grade sequence: pre-conditions → session transition → SBL download → block-by-block erase/program → dependency check → reset → verification. The three most common causes of field bricking: missing TesterPresent causing S3 timeout mid-programming (automate 0x3E 0x80 every 2s), voltage brownout during erase (check pre-condition and monitor during programming), and wrong SBL version (validate SBL signature against known-good hash before download). Post-flash verification is mandatory in production — a bricked ECU that passed programming but fails post-verification is caught before vehicle delivery.
🔬 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.