This topic describes how you use Embedded Coder® software to configure a Simulink® representation of an AUTOSAR application for model-based design, and subsequently generate AUTOSAR-compliant code from the model.
Two typical workflows are
The round-trip workflow, in which you import AUTOSAR software components created by an AUTOSAR authoring tool (AAT) into the Simulink model-based design environment, and later export XML descriptions and C code for merging back into the AAT environment.
The Simulink originated, or bottom-up, workflow, in which you take a model-based design that originated in Simulink, configure and evolve it for AUTOSAR code generation, and export XML descriptions and C code for use in the AUTOSAR environment.
This diagram shows the round-trip workflow.
In the round-trip workflow, you perform the following tasks:
Import previously specified AUTOSAR software components, including definitions of calibration parameters, into Simulink. See:
Import AUTOSAR Software Component (Embedded Coder)
Model AUTOSAR Calibration Parameters and Lookup Tables (Embedded Coder)
Develop the model using Simulink model-based design. This process includes configuring AUTOSAR elements, mapping Simulink model elements to AUTOSAR component elements, and validating the AUTOSAR interface. See:
Model AUTOSAR Software Components (Embedded Coder)
AUTOSAR Interface Configuration (Embedded Coder)
Configure AUTOSAR Sender-Receiver Communication (Embedded Coder)
Configure AUTOSAR Runnables and Events (Embedded Coder)
Configure AUTOSAR Variants in Ports and Runnables (Embedded Coder)
Configure AUTOSAR Data for Measurement and Calibration (Embedded Coder)
Export the AUTOSAR component from Simulink, generating XML description files and C code files. See:
Export AUTOSAR Software Component (Embedded Coder)
Generate AUTOSAR-Compliant C Code and Export ARXML Descriptions (Embedded Coder)
You can also verify your generated code in a simulation. See Verify AUTOSAR C Code with SIL and PIL (Embedded Coder).
Merge generated code and description files with other systems using an AUTOSAR authoring tool.
You can use the authoring tool to export specifications, which
can be imported back into Simulink. If there are AUTOSAR software
component changes in the arxml
code, you can update
the model to reflect the changes. See Import AUTOSAR Software Component Updates (Embedded Coder).
In the Simulink originated (bottom-up) workflow, you perform the same tasks as with the round-trip workflow, except that rather than importing AUTOSAR software components from an AAT (step 1), you start with a Simulink model-based design and use Simulink to create a customized AUTOSAR component. See Create AUTOSAR Software Component in Simulink (Embedded Coder). Subsequent tasks in the workflow are as listed above.