| Level | Environment | What Is Tested | Tools |
|---|---|---|---|
| MCAL unit test (SiL) | PC with MCU register stubs | API logic, parameter checking, DET calls | cmocka, Unity, LDRA, Parasoft |
| MCAL integration test (HiL/real HW) | Real MCU on bench or HIL | Correct register values, peripheral behaviour | Oscilloscope, logic analyser, CANoe, debugger |
| MCAL qualification test | Per AUTOSAR partner certification | Full API conformance to SWS specification | AUTOSAR MCAL Test Suite |
| System integration test | Full ECU on HIL bench | End-to-end: sensor -> MCAL -> driver -> application | HIL platform (dSPACE, NI VeriStand) |
MCAL Testing Levels
MCAL Unit Testing with Register Stubs
/* Unit test for Adc_ReadGroup() using register stubs */
/* No real hardware needed: stub ADC result registers */
#include "unity.h"
#include "Adc.h"
#include "Adc_Stub.h" /* stub: maps ADC register reads to test values */
static Adc_ValueGroupType result_buf[4];
void setUp(void)
{
Adc_Stub_Reset();
Adc_Init(&TestAdcConfig);
Adc_SetupResultBuffer(ADC_GROUP_ENGINE_SENSORS, result_buf);
}
void test_Adc_ReadGroup_ReturnsCorrectValues(void)
{
/* Arrange: set stub ADC result registers */
Adc_Stub_SetResult(ADC_CH_TPS, 2048u); /* 50% = 2.5V */
Adc_Stub_SetResult(ADC_CH_MAP, 3000u);
Adc_Stub_SetResult(ADC_CH_COOLANT, 1500u);
Adc_Stub_SetResult(ADC_CH_O2_PRE, 2200u);
/* Simulate conversion complete */
Adc_Stub_TriggerConversionComplete(ADC_GROUP_ENGINE_SENSORS);
/* Act */
Std_ReturnType ret = Adc_ReadGroup(ADC_GROUP_ENGINE_SENSORS, result_buf);
/* Assert */
TEST_ASSERT_EQUAL(E_OK, ret);
TEST_ASSERT_EQUAL_UINT16(2048u, result_buf[0]); /* TPS */
TEST_ASSERT_EQUAL_UINT16(3000u, result_buf[1]); /* MAP */
}
void test_Adc_ReadGroup_ReturnsError_WhenGroupNotStarted(void)
{
/* Group never started -- ReadGroup should fail */
Std_ReturnType ret = Adc_ReadGroup(ADC_GROUP_UNSTARTERD, result_buf);
TEST_ASSERT_EQUAL(E_NOT_OK, ret);
}ASPICE and ISO 26262 MCAL Test Requirements
| Requirement | ASPICE | ISO 26262 | MCAL Evidence |
|---|---|---|---|
| Unit test specification | SWE.4 BP3 | Part 6 Cl.9 | Test cases per MCAL function with expected register state |
| Unit test results | SWE.4 BP4 | Part 6 Cl.9 | Pass/fail report per test case; linked to test spec |
| Coverage measurement | SWE.4 BP5 | Part 6 Cl.9 | Statement/branch coverage for MCAL C code (ASIL-D: MC/DC) |
| Integration test spec | SWE.5 BP3 | Part 6 Cl.10 | Interface test cases for MCAL-to-peripheral integration |
| MCAL qualification | AUTOSAR SWS compliance | Part 8 Cl.12 | AUTOSAR MCAL Test Suite results from supplier |
Summary
MCAL testing has two distinct challenges: unit testing (exercising code paths without real hardware using register stubs) and integration testing (verifying the MCAL correctly programmes hardware registers on the actual MCU). The register stub approach enables MCAL unit tests to run in CI/CD without hardware - the stub layer intercepts all register reads/writes, allowing the test to verify that Adc_Init() wrote the correct prescaler value to the ADC clock register without needing a physical Aurix board. Integration testing on real hardware (using a logic analyser or oscilloscope to verify SPI clock polarity, CAN bit timing, PWM frequency) is still required but can be done once per MCAL version rather than on every CI run.
🔬 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.