www.gusucode.com > ecoder 案例源码程序 matlab代码 > ecoder/ModelForAUTOSARPlatformExample.m
%% Model for AUTOSAR Platform
% Different ways are available for using Simulink(R) to model AUTOSAR atomic
% software components.
%
% An AUTOSAR Support Package is needed to generating code and ARXML for an AUTOSAR atomic
% software components.
%
% Copyright 2010-2016 The MathWorks, Inc.
%% Multiple Periodic Runnables Configured for Multitasking
%
% Open the example model |rtwdemo_autosar_swc|. The model shows the
% implementation of an AUTOSAR atomic software component (ASWC). Two
% periodic runnables, |Runnable_1s| and |Runnable_2s| are modeled with
% multiple samples rates: 1 second (|In1_1s|) and 2 seconds (|In2_2s|)).
% To maximize execution efficiency, the model is configured for multitasking.
%
% The model includes an Initialize Function block, which initializes the
% integrator in |Runnable_2s| to a value of 1.
%
% To display color-coded sample rates with annotations and a legend, select
% *Display > Sample Time > Colors*.
%
% <<../rtwdemo_autosar_swc_with_legend.png>>
%
%%
% *Relevant Model Configuration Parameter Settings*
%
% * *Solver > Type* set to |Fixed-step|.
% * *Solver > Solver* set to |discrete (no continuous states)|.
% * *Solver > Fixed-step size (fundamental sample time)* set to |auto|.
% * *Solver > Treat each discrete rate as a separate task* selected.
%%
% *Scheduling*
%
% In the model window, enable sample time color-coding by selecting
% *Display > Sample Time > Colors*. The sample time legend shows the implicit
% rate grouping. Red represents the fastest discrete rate. Green represents
% the second fastest discrete rate. Yellow represents the mixture of the two
% rates.
%
% Because the model has multiple rates and the *Solver* parameter
% *Treat each discrete rate as a separate task* is selected, the model
% simulates in multitasking mode. The model handles the rate
% transition for |In2_2s| explicitly with the Rate Transition block.
%
% The Rate Transition block parameter *Ensure deterministic data transfer* is
% cleared to facilitate integration into an AUTOSAR RTE.
%
% The generated code for the model schedules subrates in the model. In this
% example, the rate for Inport block |In2_2s|, the green rate, is a subrate.
% The generated code properly transfers data between tasks that run at the
% different rates.
%%
% *Generate Code and Report*
%
% Generate code and a code generation report. The example model generates
% a report.
%
% Generated code complies with AUTOSAR so that you can schedule the code
% with the AUTOSAR run-time environment (RTE).
%%
% *Review Generated Code*
%
% In the code generation report, review the generated code.
%
% * |rtwdemo_autosar_swc.c| contains entry points for the code
% that implements the model algorithm. This file includes the rate scheduling
% code.
% * |rtwdemo_autosar_swc.h| declares model data structures and
% a public interface to the model entry points and data structures.
% * |rtwdemo_autosar_swc_private.h| contains local |define| constants
% and local data required by the model and subsystems.
% * |rtwdemo_autosar_swc_types.h| provides forward declarations for the
% real-time model data structure and the parameters data structure.
% * |rtwtypes.h| defines data types, structures, and macros that the
% generated code requires.
% * |rtwdemo_autosar_swc_component.arxml|,
% |rtwdemo_autosar_swc_datatype.arxml|,
% |rtwdemo_autosar_swc_implementation.arxml|, and
% |rtwdemo_autosar_swc_interface.arxml| contain elements and objects
% that represent AUTOSAR software components, ports, interfaces, data types,
% and packages. You import these files into the Simulink environment by using
% the AUTOSAR |arxml| importer tool.
% * |Compiler.h|, |Platform_Types.h|, |Rte_ASWC.h|, |Rte_Type.h|,
% and |Std_Types.h| contain stub implementations of AUTOSAR RTE functions.
% Use these files to test the generated code in Simulink, for example, in
% software-in-the-loop (SIL) or processor-in-the-loop (PIL) simulations of
% the component under test.
%%
% *Code Interface*
%
% Open and review the Code Interface Report. This information is captured in
% the ARXML files. The RTE generator uses the ARXML to interface the code into
% an AUTOSAR RTE.
%
% Input ports:
%
% * Require port, interface: sender-receiver of type |real-T| of 1
% dimension
% * Require port, interface: sender-receiver of type |real-T| of 1
% dimension
%
% Entry-point functions:
%
% * Initialization entry-point function, |void Runnable_Initialize(void)|.
% At startup, call this function once.
% * Output and update entry-point function, |void Runnable_1s(void)|.
% Call this function periodically at the fastest rate in the model. For this
% model, call the function every second. To achieve real-time execution, attach
% this function to a timer.
% * Output and update entry-point function, |void Runnable_2s(void)|.
% Call this function periodically at the second fastest rate in the model. For this
% model, call the function every 2 seconds. To achieve real-time execution, attach
% this function to a timer.
%
% Output ports:
%
% * Provide port, interface: sender-receiver of type |real-T| of 1
% dimension
% * Provide port, interface: sender-receiver of type |real-T| of 1
% dimension
%
%% Multiple Runnables Configured as Periodic-Rate Runnable and Asynchronous Function-Call Runnable
%
% Open the example model |rtwdemo_autosar_swc_fcncalls|. The model shows the
% implementation of an AUTOSAR atomic software component (ASWC). The model
% uses an asynchronous function-call runnable, |Runnable_Trigger|, which is
% triggerd by an external event. The model also includes
% a periodic rate-based runnable, |Runnable_1s|. The Rate Transition blocks
% represent interrunnable variables.
%
% Use this approach to model the JMAAB complex control model type beta
% architecture. In JMAAB type beta modeling, at the top level of a control
% model, you place function layers above scheduling layers.
%
% The model includes an Initialize Function block, which initializes the
% unit delay in |Runnable_1s| to a value of 0.
%
% To display color-coded sample rates with annotations and a legend, select
% *Display > Sample Time > Colors*.
%
% <<../rtwdemo_autosar_swc_fcncalls_with_legend.png>>
%
%%
% *Relevant Model Configuration Parameter Settings*
%
% * *Solver > Type* set to |Fixed-step|.
% * *Solver > Solver* set to |discrete (no continuous states)|.
% * *Solver > Fixed-step size (fundamental sample time)* set to 1.
% * *Solver > Treat each discrete rate as a separate task* cleared.
%%
% *Scheduling*
%
% In the model window, enable sample time color-coding by selecting
% *Display > Sample Time > Colors*. The sample time legend shows the implicit
% rate grouping. Red represents the discrete rate. Magenta represents
% the asynchronous function trigger. Yellow represents the mixture of two
% rates.
%
% The asynchronous trigger runnable runs at asynchronous rates
% (the *Sample time type* parameter of the function-call subsystem Trigger block
% is set to |triggered]) while the periodic rate runnable runs at the specified
% discrete rate. The generated code manages the rates by using single-tasking
% assumptions. For models with one discrete rate, the code generator does not produce
% scheduling code because there is only a single rate to execute. Use this
% technique for a single-rate application when you have one periodic runnable.
%
% The model handles transitions between the asynchronous and discrete rates of
% the interrunnables with the two Rate Transition blocks. The Rate Transition block
% parameter *Ensure deterministic data transfer* is
% cleared to facilitate integration into an AUTOSAR RTE.
%
%%
% *Generate Code and Report*
%
% Generate code and a code generation report. The example model generates
% a report.
%
% Generated code complies with AUTOSAR so that you can schedule the code
% with the AUTOSAR run-time environment (RTE).
%%
% *Review Generated Code*
%
% In the code generation report, review the generated code.
%
% * |rtwdemo_autosar_swc_fcncalls.c| contains entry points for the code
% that implements the model algorithm. This file includes the rate scheduling
% code.
% * |rtwdemo_autosar_swc_fcncalls.h| declares model data structures and
% a public interface to the model entry points and data structures.
% * |rtwdemo_autosar_swc_fcncalls_private.h| contains local |define| constants
% and local data required by the model and subsystems.
% * |rtwdemo_autosar_swc_fcncalls_types.h| provides forward declarations for the
% real-time model data structure and the parameters data structure.
% * |rtwtypes.h| defines data types, structures, and macros that the
% generated code requires.
% * |rtwdemo_autosar_swc_fcncalls_component.arxml|,
% |rtwdemo_autosar_swc_fcncalls_datatype.arxml|,
% |rtwdemo_autosar_swc_fcncalls_implementation.arxml|, and
% |rtwdemo_autosar_swc_fcncalls_interface.arxml| contain elements and objects
% that represent AUTOSAR software components, ports, interfaces, data types,
% and packages. You import these files into the Simulink environment by using
% the AUTOSAR |arxml| importer tool.
% * |Compiler.h|, |Platform_Types.h|, |Rte_ASWC.h|, |Rte_Type.h|,
% and |Std_Types.h| contain stub implementations of AUTOSAR RTE functions.
% Use these files to test the generated code in Simulink, for example, in
% software-in-the-loop (SIL) or processor-in-the-loop (PIL) simulations of
% the component under test.
%%
% *Code Interface*
%
% Open and review the Code Interface Report. This information is captured in
% the ARXML files. The RTE generator uses the ARXML to interface the code into
% an AUTOSAR RTE.
%
% Input port:
%
% * Require port, interface: sender-receiver of type |real-T| of 1
% dimension
%
% Entry-point functions:
%
% * Initialization entry-point function, |void Runnable_Initialize(void)|. At startup,
% call this function once.
% * Simulink function, |void Runnable_1s(void)|.
% Call this function periodically at the fastest rate in the model. For this
% model, call the function every second. To achieve real-time execution, attach
% this function to a timer.
% * Exported function, |void Runnable_Trigger(void)|. Call this function at
% any time from an external trigger.
%
% Output port:
%
% * Provide port, interface: sender-receiver of type |real-T| of 1
% dimension
%
%% Multiple Runnables Configured As Function-Call Subsystem and Simulink Function
% Open the example model |rtwdemo_autosar_swc_slfcns|. The model shows the
% implementation of an AUTOSAR atomic software component (ASWC). The model
% includes one periodic rate runnable, |Runnable_1s|, that uses a function-call
% subsystem, |SS1|. The model also includes a Simulink function, |readData|,
% to provide a value (|CurVal|) to clients that request it.
%
% The model includes an Initialize Function block, which initializes the
% unit delay in subsystem |RollingCounter| to a value of 0.
%
% To display color-coded sample rates with annotations and a legend, select
% *Display > Sample Time > Colors*.
%
% <<../rtwdemo_autosar_swc_slfcns_with_legend.png>>
%
% Use function-call subsystems:
%
% * When it is difficult or not possible to specify system events in a
% Simulink model.
% * To achieve complex multirate scheduling of runnables. Model each rate
% as a separate function-call subsystem.
%
%%
% *Relevant Model Configuration Parameter Settings*
%
% * *Solver > Type* set to |Fixed-step|.
% * *Solver > Solver* set to |discrete (no continuous states)|.
% * *Solver > Fixed-step size (fundamental sample time)* set to 1.
% * *Solver > Treat each discrete rate as a separate task* selected.
%%
% *Scheduling*
%
% In the model window, enable sample time color-coding by clicking
% *Display > Sample Time > Colors*. The sample time legend shows the implicit
% rate grouping. Red identifies the discrete rate. Magenta identifies
% rates inherited from exported functions, indicating their execution is
% outside the context of Simulink scheduling.
%
% Your execution framework must schedule the generated function code
% and handle data transfers between functions.
%%
% *Generate Code and Report*
%
% Generate code and a code generation report. The example model generates
% a report.
%
% The code generator:
%
% * Produces an AUTOSAR runnable for the function-call subsystem at the
% root level of the model.
% * Implements signal connections between runnables as AUTOSAR interrunable
% variables (IRVs).
%
% Generated code complies with AUTOSAR so that you can schedule the code
% with the AUTOSAR run-time environment (RTE).
%%
% *Review Generated Code*
%
% In the code generation report, review the generated code.
%
% * |rtwdemo_autosar_swc_slfcns.c| contains entry points for the code
% that implements the model algorithm. This file includes the rate scheduling
% code.
% * |rtwdemo_autosar_swc_slfcns.h| declares model data structures and
% a public interface to the model entry points and data structures.
% * |rtwdemo_autosar_swc_slfcns_private.h| contains local |define| constants
% and local data required by the model and subsystems.
% * |rtwdemo_autosar_swc_slfcns_types.h| provides forward declarations for the
% real-time model data structure and the parameters data structure.
% * |readData.c| contains code for the Simulink function.
% * |readData_private.h| contains local |define| constants and local data
% required by the function.
% * |readData.h| declares data structures and a public interface
% for calling the function.
% * |rtwtypes.h| defines data types, structures, and macros that
% the generated code requires.
% * |rtwdemo_autosar_swc_slfcns_component.arxml|,
% |rtwdemo_autosar_swc_slfcns_datatype.arxml|,
% |rtwdemo_autosar_swc_slfcns_implementation.arxml|, and
% |rtwdemo_autosar_swc_slfcns_interface.arxml| contain elements and objects
% that represent AUTOSAR software components, ports, interfaces, data types,
% and packages. You import these files into the Simulink environment by using
% the AUTOSAR |arxml| importer tool.
% * |Compiler.h|, |Platform_Types.h|, |Rte_ASWC.h|, |Rte_Type.h|,
% and |Std_Types.h| contain stub implementations of AUTOSAR RTE functions.
% Use these files to test the generated code in Simulink, for example, in
% software-in-the-loop (SIL) or processor-in-the-loop (PIL) simulations of
% the component under test.
%%
% *Code Interface*
%
% Open and review the Code Interface Report. This information is captured in
% the ARXML files. The RTE generator uses the ARXML to interface the code into
% an AUTOSAR RTE.
%
% Input ports:
%
% * Require port, interface: sender-receiver of type |uint16-T| of 1
% dimension
% * Require port, interface: sender-receiver of type |real-T| of 1
% dimension Entry-point functions:
%
% Entry-point functions:
%
% * Initialization entry-point function, |void Runnable_Init(void)|. At startup,
% call this function once.
% * Exported function, |void Runnable_1s(void)|. Call this function periodically,
% every second.
% * Simulink function, |Std_ReturnType readData(real_T Data[2])|. Call this
% function at any time.
%
% Output ports:
%
% * Provide port, interface: sender-receiver of type |uint16-T| of 1
% dimension
%
%% More About
%
% * <docid:ecoder_doccenter.autosar-component-creation>
% * <docid:ecoder_doccenter.autosar-code-generation-maad>