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

Tool Confidence Level (TCL) Determination

TCLConditionQualification Needed?Action
TCL1Tool output not used in safety item (TI1), OR tool failure immediately detectableNoDocument classification justification
TCL2TI2 + TD1 (failure has limited impact or detectable)Yes — operational experience sufficientDocument usage history; no missed failures on similar projects
TCL3TI2 + TD2 or TD3 (failure could cause undetected safety violation)Yes — full qualification with validation suiteVendor TQK, or in-house validation, or increased confidence from use
Pythontcl_determination.py
#!/usr/bin/env python3
# Tool Confidence Level determination per ISO 26262 Part 8.11

def determine_tcl(tool_name, ti_level, td_level) -> str:
    """
    TI (Tool Impact): TI1=tool output not integrated in safety; TI2=tool output IS in safety item
    TD (Tool Error Detection): TD1=immediately detectable; TD2=not easily detectable; TD3=not detectable
    """
    if ti_level == 1:
        tcl = "TCL1"
    elif ti_level == 2 and td_level == 1:
        tcl = "TCL2"
    elif ti_level == 2 and td_level in [2, 3]:
        tcl = "TCL3"
    else:
        tcl = "Invalid"

    qualification_actions = {
        "TCL1": "No qualification needed. Document TI1 classification.",
        "TCL2": "Qualification by use: document tool usage history with zero safety failures.",
        "TCL3": "Full qualification required: vendor TQK or in-house validation suite.",
    }
    return tcl, qualification_actions.get(tcl, "")

tools = [
    ("IAR Compiler v9.30", 2, 3),    # TI2 (generates binary), TD3 (errors not detectable)
    ("Polyspace Bug Finder", 2, 2),  # TI2 (missed bugs affect safety), TD2 (false negative hard to detect)
    ("TESSY Unit Tester", 2, 2),     # TI2 (missed test = unverified req), TD2
    ("Git (version control)", 1, 1), # TI1 (no safety output), TD1
    ("Wireshark", 1, 1),             # TI1 (analysis only), TD1
]

for tool, ti, td in tools:
    tcl, action = determine_tcl(tool, ti, td)
    print(f"{tool}: TI{ti}, TD{td} → {tcl}")
    print(f"  Action: {action}")
    print()

TD × TI → TCL Matrix

TCL Determination Matrix (ISO 26262-8 Table 4)
              TI1            TI2
              (not in        (output in
              safety item)   safety item)
  TD1         TCL1           TCL2
  (immediate  No qual        Operational
  detection)  needed         use evidence

  TD2         TCL1           TCL3
  (not easily No qual        Full
  detected)   needed         qualification

  TD3         TCL1           TCL3
  (not        No qual        Full
  detectable) needed         qualification

  Key insight: Compiler always TI2 (generates binary) + TD3 (errors not detectable by inspection)
  → Compiler is always TCL3 → full qualification required

TCL3 Qualification Methods

MethodEvidence RequiredWhen to Use
Vendor Tool Qualification Kit (TQK)Run TQK test suite on project tool version; pass/fail record; vendor declarationBest for commercial tools with available TQKs (IAR, GreenHills, Polyspace, TESSY)
Operational Use EvidenceDocument projects where tool was used; tool version; no safety failures observed; comparable use contextWhen TQK unavailable; tool version unchanged from prior qualified version
In-house Validation SuiteWrite test suite against tool specification; run against tool; pass/fail recordFor custom tools or tools with no vendor TQK
Shellrun_tool_qualification.sh
#!/bin/bash
# Run IAR Compiler qualification kit (TQK) per ISO 26262
TOOL_VERSION="IAR_EWARM_9.30.1"
COMPILER_PATH="/opt/iar/ewarm_9.30/bin/iccarm"

# Step 1: Verify tool version matches qualified version
ACTUAL_VERSION=$($COMPILER_PATH --version | grep -oP 'V[0-9]+\.[0-9]+\.[0-9]+')
if [ "$ACTUAL_VERSION" != "V9.30.1" ]; then
    echo "FAIL: Tool version mismatch. Qualified V9.30.1, installed $ACTUAL_VERSION"
    exit 1
fi

# Step 2: Run TQK test suite (provided by IAR)
cd /opt/iar/tqk_iso26262/
./run_qualification_tests.sh --compiler "$COMPILER_PATH"     --output "qualification_results_${TOOL_VERSION}.html"

# Step 3: Check pass/fail
if grep -q "FAIL" qualification_results_${TOOL_VERSION}.html; then
    echo "FAIL: Qualification test failures found. Review report."
    exit 1
fi

echo "PASS: All TQK tests passed for $TOOL_VERSION"
cp qualification_results_${TOOL_VERSION}.html dms/tool_qualification/ 

Toolchain Management and CI Version Lock

PracticeImplementationCompliance Benefit
Docker container with pinned tool versionsDockerfile: FROM tools_base:iar_9.30.1_polyspace_2025aCI always uses qualified tool version; no accidental upgrade
Tool version in SVVPSVVP section 3: lists all tools + versions + qualification statusAuditor can verify CI build used SVVP-specified tools
Tool upgrade CRUpgrading any TCL2/3 tool requires CR + re-qualification planPrevents unqualified tool introduction mid-project
Build artefact verificationJenkins records Docker image hash in build logTraceability from delivered binary to exact tool versions used

Summary

Tool qualification is a systematic process, not a paperwork exercise. The TCL determination matrix is objective: compilers and code generators are always TCL3 (TI2 + TD3); get vendor TQKs for them before the project starts. Running TQKs takes hours; discovering mid-project that a tool is unqualified and has no TQK available takes weeks to remediate. Docker containers with pinned tool versions enforce tool discipline automatically in CI, eliminating the accidental-upgrade failure mode.

🔬 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.

← PreviousEvidence Management & Audit TrailsNext →Supplier Compliance Management