AUTOSAR Code Generation (arxml + code) - Model-Based Development

AUTOSAR Code Generation with Embedded Coder

AUTOSAR Code Generation Outputs

  Simulink Model (SpeedController.slx)
  + AUTOSAR Configuration (in model or .sldd)
      |
  slbuild with autosar.tlc
      |
      +-- SpeedController.c     -- runnable implementations
      +-- SpeedController.h     -- internal types
      +-- SpeedController_ARXML/
          +-- SpeedController_swc.arxml   -- SWC description
          +-- SpeedController_ifc.arxml   -- interfaces
          +-- SpeedController_int.arxml   -- internals

  The ARXML is imported into the AUTOSAR tool chain
  (EB tresos, Vector DaVinci, SystemDesk) to configure
  OS task mapping, COM signal routing, NvM block allocation.

Runnable and Port Configuration

MATLABautosar_mapping.m

% Configure AUTOSAR mapping for SpeedController model
arObj = autosar.api.getAUTOSARProperties(model);

% Map inports to AUTOSAR receiver ports
addPort(arObj, "Receiver", "SpeedRef_Port");
mapInport(arObj, "SpeedRef",      "SpeedRef_Port", "SpeedRef_DE");
mapInport(arObj, "VehicleSpeed",  "VehicleSpeed_Port", "VehicleSpeed_DE");

% Map outports to AUTOSAR sender ports
addPort(arObj, "Sender", "PedalRequest_Port");
mapOutport(arObj, "PedalRequest", "PedalRequest_Port", "PedalRequest_DE");

% Map Function-Call Subsystem to Runnable
mapRunnable(arObj, "SpeedControl_10ms", "SpeedControl_10ms_Runnable");
setRunnable(arObj, "SpeedControl_10ms_Runnable", ...
    "MinStartInterval", 0.01);  % 10ms minimum period

% Map calibration parameters to AUTOSAR CalibrationComponent
addCalPrm(arObj, "Kp", "SpeedController_Cal");

% Generate code and ARXML
slbuild(model);
% Outputs: SpeedController.c + SpeedController_ARXML/*.arxml

AUTOSAR Integration Workflow

Step	Activity	Tool
1	Build AUTOSAR SWC model in Simulink with autosar.tlc	Embedded Coder
2	Import generated ARXML into AUTOSAR toolchain	EB tresos / DaVinci
3	Map SWC ports to COM signals (CanIf PDUs)	EB tresos ECU Extract
4	Map Runnables to OS Tasks	EB tresos OS configuration
5	Generate OS, RTE, Com from AUTOSAR configuration	EB tresos Generate
6	Compile all generated code + hand-written MCAL integration	GCC/TASKING/HighTec
7	Flash and verify on HIL or real ECU	CANoe, CANape, Debugger

Summary

AUTOSAR code generation with Embedded Coder produces both the C implementation and the ARXML description simultaneously - this is the key advantage over hand-coding the AUTOSAR SWC: the ARXML is always consistent with the implementation because both are generated from the same model. In hand-coded projects, the ARXML description (maintained separately in the AUTOSAR tool) frequently drifts from the actual implementation, causing integration failures. With MBD, if the model builds, the ARXML and C code are guaranteed to match. The most common AUTOSAR code generation issue is port interface mismatch: the data element type in the model (e.g., single) must match the data element type defined in the system-level ARXML exactly, or the RTE generator will produce type-mismatch compilation errors.

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