Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

Synopsys Silver Overview

FeatureDescription
Full nameSilver / Silver SiL (formerly by Synopsys)
ArchitectureLightweight vECU runner; FMI 2.0/3.0 based; AUTOSAR BSW porting
SpeedUp to 100x faster than real-time (multi-thread support)
Python/CLIsilver-exec CLI; Python scripting via silver-python package
CoverageIntegrated gcov/bullseye coverage; ASPICE-ready reports
CI integrationDocker image available; runs headless; fast startup (< 1s)
Diff testingBuilt-in back-to-back comparison: MiL vs SiL signal diff

Silver in CI/CD Pipeline

YAMLsilver_ci.yaml
# GitLab CI: Silver SiL test stage
sil_test:
  stage: test
  image: synopsys/silver:2024.1
  script:
    # Build vECU from production source
    - silver-build \
        --source src/ \
        --stubs stubs/ \
        --config silver_config.yaml \
        --output SpeedController.fmu

    # Run test suite
    - silver-exec \
        --fmu SpeedController.fmu \
        --tests tests/silver_test_suite.yaml \
        --coverage gcov \
        --report reports/sil_report.html \
        --diff-against mil_reference/

    # Check results
    - python3 check_silver_results.py reports/sil_report.html

  artifacts:
    paths:
      - reports/sil_report.html
      - reports/coverage_report.html
    when: always
    expire_in: 90 days

FMU-Based vECU Export

Pythonsilver_check_results.py
"""Parse Silver SiL report and enforce quality gates."""
import sys
import xml.etree.ElementTree as ET

def check_silver_report(report_path: str) -> bool:
    tree = ET.parse(report_path)
    root = tree.getroot()

    # Check test pass rate
    total  = int(root.find(".//TestSummary/Total").text)
    passed = int(root.find(".//TestSummary/Passed").text)
    failed = int(root.find(".//TestSummary/Failed").text)

    if failed > 0:
        print(f"FAIL: {failed}/{total} tests failed")
        return False

    # Check coverage thresholds
    branch_cov = float(
        root.find(".//Coverage/Branch/Percentage").text)
    mcdc_cov   = float(
        root.find(".//Coverage/MCDC/Percentage").text)

    if branch_cov < 100.0:
        print(f"FAIL: Branch coverage {branch_cov:.1f}% < 100%")
        return False
    if mcdc_cov < 90.0:
        print(f"FAIL: MC/DC coverage {mcdc_cov:.1f}% < 90%")
        return False

    # Check MiL vs SiL diff
    max_diff = float(root.find(".//BackToBack/MaxDiff").text)
    if max_diff > 1e-4:
        print(f"FAIL: MiL/SiL max diff {max_diff:.6f} > 1e-4")
        return False

    print(f"PASS: {passed}/{total} tests, branch={branch_cov:.1f}%, "
          f"mcdc={mcdc_cov:.1f}%, max_diff={max_diff:.2e}")
    return True

if __name__ == "__main__":
    ok = check_silver_report(sys.argv[1])
    sys.exit(0 if ok else 1)

Summary

Synopsys Silver is positioned as the CI-friendly alternative to dSPACE VEOS: faster startup, lighter Docker image, and simpler CLI make it easier to integrate into GitLab/Jenkins pipelines where dozens of parallel SiL jobs run simultaneously. The FMU (Functional Mock-up Unit) export format is key to portability -- an FMU built from the Silver build system runs on any FMI-compliant simulation platform, making it exchangeable between OEM and supplier without proprietary tool dependencies. The built-in back-to-back diff comparison (MiL vs SiL) eliminates the need for separate comparison scripts in CI: Silver computes the maximum signal difference automatically and includes it in the test report, ready for the ISO 26262 evidence package.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousVirtual ECU with dSPACE VEOSNext →Back-to-Back Testing: MiL vs SiL