| Mode | How It Works | Best For |
|---|---|---|
| Simulink SiL (Top Model) | Ctrl+B generates code; model runs compiled code in Simulink | Quick back-to-back MiL vs SiL comparison |
| Simulink SiL (Model Reference) | Specific Model Block runs as compiled code; rest is Simulink | Component SiL; test one ECU component at a time |
| Standalone SiL binary | Compiled .so/.dll loaded by external test harness (pytest/C++) | CI/CD integration; non-MATLAB test environments |
| AUTOSAR SiL (VEOS/Silver) | Full AUTOSAR stack compiled for host; OS task scheduling simulated | Full ECU SiL with RTE and BSW |
SiL Execution Modes
Embedded Coder SiL Configuration
% Configure Embedded Coder SiL mode for SpeedController
model = "SpeedController";
% Method 1: Top-model SiL (simplest)
set_param(model, "SimulationMode", "software-in-the-loop (sil)");
% sim() will now compile and run generated code
% Method 2: Model Reference SiL (for component testing)
% In parent model, set the Model block to SiL mode:
set_param("VehicleEMS/SpeedController_Ref",
"SimulationMode", "Software-in-the-loop (SIL)");
% Verify SiL compilation succeeds before running tests
[~, buildInfo] = slbuild(model, "ModelReferenceCoderTarget");
fprintf("SiL binary: %s\n", buildInfo.BuildDirectory);
% Run SiL simulation
set_param(model, "SimulationMode", "software-in-the-loop (sil)");
sil_out = sim(model, 20.0);
% SiL automatically logs code coverage (via gcov)
% View: Coverage Reports in Code Generation ReportStandalone SiL Wrapper
/* Standalone SiL wrapper: exposes step function via C API */
#include "SpeedController.h"
#include "SpeedController_private.h"
/* Global state (matches Embedded Coder rtModel structure) */
static RT_MODEL_SpeedController_T SpeedController_M_;
static RT_MODEL_SpeedController_T *const SpeedController_M
= &SpeedController_M_;
/* Test API: exposed via shared library */
void SiL_Init(void) {
SpeedController_initialize();
}
void SiL_SetSpeedRef(float value) {
SpeedController_U.SpeedRef = value;
}
void SiL_SetVehicleSpeed(float value) {
SpeedController_U.VehicleSpeed = value;
}
void SiL_Step(void) {
SpeedController_step();
}
float SiL_GetPedalRequest(void) {
return SpeedController_Y.PedalRequest;
}
uint8_t SiL_GetFaultActive(void) {
return (uint8_t)SpeedController_Y.FaultActive;
}Summary
The standalone SiL binary approach is the most CI/CD-friendly SiL execution mode because it removes the MATLAB dependency from the test execution step. The test runner (pytest, Jenkins, GitLab CI) loads the compiled shared library directly, drives inputs via the C API, and reads outputs -- no MATLAB license required on the CI server. This is important in practice: automotive CI pipelines run tests on multiple agents simultaneously, and floating-point MATLAB licenses are expensive. The compiled SiL binary only requires a C runtime and a license for the application code itself, enabling scaling test execution to many parallel agents without license costs.
🔬 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.