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

Lab Scope: C++17 Adaptive AUTOSAR SWC

TaskDetail
SWC implementationTemperature sensor SWC using class + RAII + ara::core::Result
Error handlingReplace E_NOT_OK pattern with ara::core::Result throughout
TestingUnit test with Catch2; mock ADC hardware via dependency injection

Exercise 1: Temperature Sensor SWC

C++temperature_swc.cpp
#include "ara/core/result.h"
#include "ara/core/optional.h"
#include 
#include 

// Pure abstract interface: allows mocking in unit tests
class IAdcDriver {
public:
    virtual ~IAdcDriver() = default;
    virtual ara::core::Result Read(uint8_t channel) const noexcept = 0;
};

class TemperatureSensor {
public:
    // Dependency injection: inject ADC driver (real or mock)
    explicit TemperatureSensor(const IAdcDriver &adc, uint8_t channel) noexcept
        : m_adc(adc), m_channel(channel) {}

    // Returns celsius in Q4.12 fixed-point, or error
    ara::core::Result ReadTemperatureCelsius() const noexcept
    {
        auto raw_result = m_adc.Read(m_channel);
        if (!raw_result.HasValue()) {
            return ara::core::Result::FromError(raw_result.Error());
        }

        // Convert ADC raw to millivolts: raw * 3300 / 4095
        const uint32_t mv = (static_cast(raw_result.Value()) * 3300u) / 4095u;

        // LM35 transfer function: 10 mV/°C, offset 0°C at 0V
        // Celsius = mV / 10 — Q4.12: multiply by 4096/10 = 409.6 ≈ use *4096 / 10
        const int16_t celsius_q412 = static_cast((mv * 4096u) / 10000u);

        // Range check: -40°C to +150°C in Q4.12
        constexpr int16_t TEMP_MIN_Q412 = static_cast(-40 * 4096 / 10);
        constexpr int16_t TEMP_MAX_Q412 = static_cast(150 * 4096 / 10);
        if (celsius_q412 < TEMP_MIN_Q412 || celsius_q412 > TEMP_MAX_Q412) {
            return ara::core::Result::FromError(kSensorOutOfRange);
        }
        return celsius_q412;
    }

private:
    const IAdcDriver &m_adc;
    uint8_t m_channel;
};

Summary

Dependency injection (passing the ADC driver as a reference to the constructor) enables unit testing without hardware: the test provides a mock ADC that returns known values, and the TemperatureSensor SWC is tested in isolation from hardware. ara::core::Result as the return type propagates errors without exceptions: the caller is forced to handle both value and error paths explicitly. This pattern is characteristic of production Adaptive AUTOSAR code and is also applicable to Classic platform C++ application SWCs that need exception-free error handling.

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

← PreviousC++14/17 Features for Adaptive AUTOSARNext →Debugger Usage: Breakpoints & Watchpoints