| Deliverable | Contents | Standard |
|---|---|---|
| Tool classification | TI, TD, TCL for MATLAB+Simulink+Embedded Coder | ISO 26262-8 Cl.11 |
| Intended use statement | Exactly which tool features are used, for which ASIL | ISO 26262-8 Cl.11.4.7 |
| Validation test plan | Test cases verifying tool functions used in project | ISO 26262-8 Cl.11.4.8 |
| Validation test results | Executed results + PASS/FAIL for each test | ISO 26262-8 Cl.11.4.9 |
| Operational constraints | Configuration freeze, version lock, environment | ISO 26262-8 Cl.11.4.10 |
| Qualification report | Consolidated document linking all above | ISO 26262-8 Cl.11.4 |
Lab: Assembling a Tool Qualification Package
Exercise 1: TCL Determination Worksheet
% Tool Qualification Level determination for Embedded Coder
% Tool: MathWorks Embedded Coder R2024b
% Intended use: generate ASIL-D compliant C code from MATLAB/Simulink
% models for ARM Cortex-M7 target
% Step 1: Determine Tool Impact (TI)
% Q: Could a malfunction of Embedded Coder introduce faults
% into the safety-relevant software without being detected?
% A: YES -- a code generator bug could produce wrong C code
% TI = TI3
% Step 2: Determine Tool Error Detection (TD)
% Detection methods:
% D1: Back-to-back MiL/SiL comparison (catches most gen errors)
% D2: Static analysis (Polyspace) of generated code
% D3: HiL testing of generated code on real ECU
% Assessment: D1+D2+D3 = medium-high confidence => TD2
% Step 3: TCL = f(TI3, TD2) = TCL2
%
% TCL2 requires:
% - Tool qualification report
% - Validation tests for functions used
% - Increased confidence through usage experience
% (MathWorks TQP covers most of this)
fprintf("Tool: Embedded Coder R2024b\n");
fprintf("TI: TI3 (can introduce faults)\n");
fprintf("TD: TD2 (MiL/SiL + static analysis)\n");
fprintf("TCL: TCL2\n");
fprintf("Qualification: Tool qualification report required\n");Exercise 2: Validation Test Plan
% Validation test plan for Embedded Coder (project-specific)
% Focus: functions used in SpeedController ASIL-D model
% TVT-EC-001: Gain block code generation
% Purpose: verify single-precision gain generates correct C code
% Model: Gain block K=10.0, input=single, output=single
% Expected code: y = 10.0F * u;
% Verification: parse generated .c file; compare output
% TVT-EC-002: Discrete integrator code generation
% Purpose: verify Unit Delay generates z^-1 behaviour
% Model: Discrete-Time Integrator Ts=0.01, initial=0
% Expected: accumulates input*Ts each step
% Verification: MiL/SiL comparison; verify identical output
% TVT-EC-003: Saturation block clamps at limits
% Purpose: verify overflow protection generates correct code
% Model: Saturation(-100, 100) on int16 signal
% Expected: clamps at -100 and +100 exactly
% Verification: run above-limit input; check output = limit
% TVT-EC-004: Stateflow state entry action
% Purpose: verify entry action executes exactly once on state entry
% Model: 2-state chart; entry: counter++
% Expected: counter increments exactly once per state entry
% Verification: SiL simulation; count increments
fprintf("Validation test plan: 4 critical functions covered\n");
fprintf("Execute tests and record PASS/FAIL in TQP report\n");Summary
The Tool Qualification Package lab demonstrates that tool qualification is not as daunting as it first appears. The core work is: determine TCL (one worksheet, 30 minutes), write validation tests for the specific tool functions used in the project (not for every tool feature - only those actually used), run the tests, and document the results. For Embedded Coder at TCL2, the MathWorks TQP pre-written package covers the structural requirements, and the project-specific validation tests (TVT-EC-001 through TVT-EC-004 above) are a small, targeted set. The total effort for a well-organised team using the MathWorks TQP is 2-5 person-days, not the 2-5 person-months that teams without an established process sometimes estimate.
🔬 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.