1

From Simulink to AUTOSAR Code

김종헌 부장
Senior Application Engineer
MathWorks Korea

© 2017 The MathWorks, Inc.

2
Agenda
 Introduction to AUTOSAR Standards
– Simulink approach to AUTOSAR

 AUTOSAR design workflows

 Bottom Up
 Top Down
 Round trip
– Overview:
 Modeling AUTOSAR Components / Attributes
 Components, Runnables and Events
 Modeling styles

3
 2.0
90 files
Components specification

2.1
120 files
Body and Interior Electronics APIs…

3.0
125 files
APIs for Powertrain, Chassis…

3.1
129 files
DCM, DEM Revisions...

3.2
136 files
Added safety concepts…

AUTOSAR Releases RTE Enhancements...

4.0
183 files
Complexity of Classic AUTOSAR is growing

Variant Handling for

4.1

Application Interfaces...
198 files

Efficient NV Data
Handling via RTE…
4.2
227 files

Crypto Interface,
www.autosar.org

V2X support……..
238 files

4
4.3……….
AUTOSAR Adoption

5
6
What is AUTOSAR?

AUTOSAR® (AUTomotive Open System ARchitecture) is an open and

standardized automotive software architecture

Application Layer

RTE

ECU Abstraction Layer Complex

Services
Layer Basic Software Device
Drivers

Microcontroller Abstraction Layer

ECU Hardware

www.autosar.org 7
AUTOSAR Vision

Non AUTOSAR AUTOSAR

Application Software
Application Software

Basic SW
Basic SW

Hardware Hardware

AUTOSAR Slogan-

“Cooperate on Standards – compete on implementation”

www.autosar.org 8
AUTOSAR Members
11 Development
9 Core Partners
Members

88 Associate Members
57 Premium Member 17 Attendees

General Generic Standard Tools and Semi-

OEM Tier 1 Software Services conductors

www.autosar.org 9
 AUTOSAR Support from Embedded Coder and Simulink
Authoring Tools
Software Architecture Definition

Application Layer Behavior

AUTOSAR Software AUTOSAR Software ………. AUTOSAR Software Modeling
Component 1 Component 2 Component n & Code
Generation

Run Time Environment (RTE)

Modeling and
Simulation
Basic Software

BSW Configuration
ECU Abstraction Layer
& RTE Generation Complex Device
Services Layer
Basic Software Drivers
Basic SW Providers

Microcontroller Abstraction Layer

ECU Hardware
10
 Simulink Approach to AUTOSAR
No separate
Available via web
Simulink and Embedded Coder AUTOSAR
download + AUTOSAR Support package for Embedded Coder Blockset needed

C Code and
ARXML
Import Export

Code-generation
through Mapping

11
 Supported AUTOSAR Design Workflows

Top-Down Workflow SW-C

Description

Export ARXML Import/Update

AUTOSAR
SW-C
SIL/PIL Test

Embedded
Coder
Simulink

SW-C
Description

AUTOSAR
SW-C
Import/Update Export ARXML Bottom-Up Workflow

Round-Trip Workflow 12
Modeling AUTOSAR Communication

 Ports in a AUTOSAR software component allow for

communication

 Categories of ports based on direction

– Require port
– Provide port

 Each port can have either of the following Interfaces

13
Runnable Entities

 Each AUTOSAR SW-C is composed by one or more runnables/runnable

entities

AUTOSAR SW-C

Receiver Sender
Port Runnable 1 Port

Server
Client Runnable 2 Port
Port

Function
Callers
14
Supported Events for a Runnable
Each Runnable should have at least one event attached

 TimingEvent - Periodically scheduled Runnables

 DataReceivedEvent - Trigger the runnable when data is received

 ModeSwitchEvent - Triggered onEntry, onExit, or onTransition

 OperationInvokedEvent - Client-server type event

 InitEvent - designate an AUTOSAR runnable as an initialization

runnable, and then map an initialization function to the runnable.

 DataReceiveErrorEvent - when the communication layer reports

an error in data reception by the receiver component

 ExternalTriggerOccuredEvent – used to activate a runnable in an

SWC as result of an explicit trigger by a runnable entity of some
other SWC
15
 Mapping Simulink to AUTOSAR
Application Layer

AUTOSAR
Software
AUTOSAR
Software … AUTOSAR
Software
SW-C Component 1 Component 2 Component n
Description

AUTOSAR
SW-C
1
AR: Port Virtual Functional Bus (VFB)

AR: Interface

AR: Data Element 1

AR: Data Element 2

AR: Data Element 3

16
Example Mapping to a Receiver Port
Add a New Simulink Port Add a New Data Element to the Interface

Validate AUTOSAR to Simulink Mapping Map Simulink Port to AUTOSAR Port

17
Using MATLAB for automating common tasks

%% Setup AUTOSAR Configuration programmatically

model = ‘Average_VehicleSpeed_Calculation';

% Modify AUTOSAR Properties

autosarProps = autosar.api.getAUTOSARProperties(model);
set(autosarProps, 'Input', 'IsService', true);
set(autosarProps, 'XmlOptions', 'ArxmlFilePackaging','SingleFile');

% Modify Simulink Mapping to AUTOSAR

slMap = autosar.api.getSimulinkMapping(model);
mapInport(slMap, 'Input' , 'Input', 'Input' , 'ExplicitReceive');
mapOutport(slMap, 'Output' , 'Output', 'Output' , 'ExplicitSend');

18
 Modeling Multiple Entry-Point Functions

For the multi-runnable modeling

pattern, each input port that
represents a runnable trigger
event will need to have the
check box for Output function
call checked as part of the
inport properties.

This allows for function triggers

from a test harness model to be
passed across a model
reference boundary.

>> rtwdemo_autosar_multirunnables 19
Model AUTOSAR Components
Application Layer

AUTOSAR
Software … AUTOSAR
Software
Component 1 Component n

Virtual Functional Bus (VFB)

Periodic rate-based Periodic and Asynchronous

Multi-rate and Asynchronous

20
Bottom-Up Workflow (Starting from Simulink)
AUTOSAR Authoring Tool

Import
SWC Description

Export SWC Description/

Generate SWC C code

AUTOSAR design
(Meta-model)

21
Launch AUTOSAR Configuration

 The method for Configuring AUTOSAR Properties is

– selecting the Code Menu and then selecting C/C++ Code
– Configure Model as an AUTOSAR Component. (This will bring up a dialog screen as shown.)

Configure AUTOSAR Interface (User Dialog)

>> rtwdemo_autosar_counter
22
 Simulink-AUTOSAR Mapping Editor
View / Edit AUTOSAR Properties and Simulink Mappings

The Green Check mark is

to Validate the AUTOSAR
Configuration.

The blue Circle arrow is to

refresh the Simulink
elements.

The AUTOSAR Interface

Configuration is split
between two areas: With the accordion control set to Simulink-AUTOSAR Mapping,
Simulink-AUTOSAR configure AUTOSAR Mapping of Simulink:
Mapping and AUTOSAR  Inports
Properties. See this  Outports
accordion based UI control  Entry Point Functions
at the bottom left corner of
the dialog screen  Data Transfers (IRV – InterRunnable Varialbes)

23
Editing AUTOSAR Properties View / Edit AUTOSAR Properties and Simulink Mappings

With the accordion control set to AUTOSAR Properties, the user can configure
AUTOSAR elements / attributes such as:

 Add / Remove / Edit AUTOSAR Entities such as Components / Ports and

Interfaces
 Configure ARXML options such as modular or single file generated on
export or build; package paths; allow or not allow implementation types.

24
Mapping Inports to AUTOSAR Receiver Ports

Here is an example of mapping a

Simulink Inport to a AUTOSAR Port
Data Element. In this case, you can
see the Simulink Inport called Input
is mapped to the AR:Port of Input.
The actual selection of the
AR:Element is a bit hidden in this
view. Notice that the
AR:DataAccessMode is also
available for the user to select from
this dialog.

25
Map Outports to AUTOSAR Sender Ports

Here is an example of mapping a

Simulink Inport to a AUTOSAR Port
Data Element. In this case, you can
see the Simulink Inport called Input
is mapped to the AR:Port of Input.
The actual selection of the
AR:Element is a bit hidden in this
view. Notice that the
AR:DataAccessMode is also
available for the user to select from
this dialog.

26
Map Entry Point Functions for a Model

Here is an example of mapping a Simulink Function Entry Point to

an AUTOSAR Runnable. Note: The Initialze Function most likely
will get mapped to the Runnable_Step (In this example). This
Initialize Function is for blocks within the Software Component that
need initialization such as 1/z blocks. This is not the same as user
initialization of signals or varaibles.
27
Generate Code
Build model into AUTOSAR compl
aint Code (Control B or build Icon
show to the left).

 Generates both C Code & AUT

OSAR Software Component de
scription files (ARXML files).

 Code uses RTE APIs to access

AUTOSAR Ports such as Se
nder Receiver ports or Client /
Server Ports as needed.

28
Select AUTOSAR Target

 The mechanism for selecting an AUTOSAR target is similar to selecting an

ERT target
– via the Simulink Configuration Parameters menu, Code Generation Tab , System target file.

29
Overview of Generated ARXML

 Generated ARXML contains

– Component and Internal Behavior

– Datatypes
– Implementation information
 Lists all generated source code and ARXML files
– Interfaces
– Other entities

30
AUTOSAR Schema Versions

 Seamless support for AUTOSAR Releases

– Import detects AUTOSAR 2.x – 4.x release from
arxml file
– User selects AUTOSAR release from
configuration set options for code generation and
arxml export
MATLAB Release AUTOSAR Release
R2015b, R2016a/b, R2017a 2.1, 3.0, 3.1, 3.2 (Rev 3.2.2), 4.0, 4.1, 4.2 (Rev 4.2.1, 4.2.2)
R2014b, R2015a 2.1, 3.0, 3.1, 3.2, 4.0, 4.1 (Rev 4.1.1)
R2012a/b, R2013a/b, R2014a 2.1, 3.0, 3.1, 3.2, 4.0 (Rev 4.0.2)

R2011b 2.0, 2.1, 3.0, 3.1, 3.2

R2010a/b, R2011a 2.0, 2.1, 3.0, 3.1
R2009a/b 2.0, 2.1, 3.0
R2008a/b 2.0, 2.1

31
MISRA C:2012 for AUTOSAR target

 100% Compliance with MISRA C:2012 Mandatory and Required rules

32
33
Verification with Software- and Processor-In-The-Loop (PIL)

 Support for SIL/PIL with AUTOSAR target

 Profile code and measure execution time on target
 Develop a custom PIL target for AUTOSAR using the toolchain build
approach

34
Top-Down Workflow (Starting from SWC Description)
AUTOSAR Authoring Tool

Export Merge
SWC Description SWC Description

Import Export SWC Description/

SWC Description Generate SWC C code

Model Based
Design

35
Top Down Workflow
AUTOSAR Authoring Tool Top Down Workflow
Starts with Authoring Tool, then user
exports ARXML files from Authoring tool.

User can then either import the ARXML

files into a new Simulink Skeleton model
or Update an existing Simulink Model.
ARXML FIles

Update existing Simulink model

Import as new Simulink model

OR

36
 Importing ARXML Files
%Import ARXML Files Top Down Workflow
importerObj = arxml.importer('rtwdemo_autosar_multirunnables.arxml') Commands to create a skeleton
model with no internal behavior
%Create new model with interfaces setup in the skeleton model (no
model = importerObj.createComponentAsModel('/pkg/swc/ASWC'); runnables)

Note: After running the

arxml.importer command, here
is the package that is needed for
the second command of create
Component as Model

37
 Import with Internal Behavior

Top Down Workflow

Commands to create a skeleton model with internal behavior
setup in the skeleton model (create with runnables)
38
Updating Existing Models from ARXML
V1.arxml Updated to V2.arxml

39
 Update Existing Models from ARXML

Top Down Workflow

Commands to update an existing Simulink model
that already has an AUTOSAR configuration.

Notice that a report was created such that the

user can understand what has changed in the
model.

40
41
http://www.mathworks.com/hardware-support/autosar.html 42
43
Thank You!

44