• documentation
main content

composition and ecu software simulation -凯发k8网页登录

model and simulate autosar compositions and ecu software

when you develop multiple autosar software component models that are interconnected and work together, you can combine them in an autosar composition model for simulation. a composition is an autosar software component that aggregates related groups of software components. compositions support component scaling and help to manage complexity in a design.

to create a simulink® representation of an autosar composition, take one of these actions:

  • import an autosar xml (arxml) description of a composition (classic platform).

  • create a model and use model blocks to reference and connect autosar component models.

alternatively, if you have system composer™ software, you can create an autosar architecture model and use software composition blocks to model autosar compositions. for more information, see software architecture modeling.

when you simulate a composition model, you simulate the combined behavior of the aggregated autosar components.

for the autosar classic platform, autosar blockset provides basic software (bsw) blocks, which allow you to model software component calls to bsw services that run in the autosar run-time environment. bsw services include nvram manager (nvm), diagnostic event manager (dem), and function inhibition manager (fim). in the run-time environment, autosar software components typically access bsw services using client-server or sender-receiver communication.

to simulate autosar components that call bsw services, you create a containing composition model and add preconfigured bsw service component blocks. the blocks provide reference implementations of bsw services.

if you have simulink design verifier™, you can perform verification on the autosar component models.

blocks

call autosar function inhibition manager (fim) service interface controlfunctionavailable
inject an event failure to test recovery
override an event to simulate and verify behavior
call autosar diagnostic event manager (dem) service interface eventavailable
call autosar diagnostic event manager (dem) service interface diagnosticinfo
call autosar diagnostic event manager (dem) service interface diagnosticmonitor
call autosar diagnostic event manager (dem) service interface operationcycle
configure autosar diagnostic services and runtime environment (rte) for emulation
call autosar function inhibition manager (fim) service interface functioninhibition
call autosar nvram manager (nvm) service interface nvmadmin
call autosar nvram manager (nvm) service interface nvmservice
configure autosar nvram services and runtime environment (rte) for emulation

functions

create simulink representation of autosar arxml software composition
update autosar model with arxml changes

topics


  • develop and assemble reusable autosar software components into autosar compositions.


  • create simulink® model from xml description of autosar software composition.


  • import autosar software composition and its contained components and compositions.


  • combine autosar software components in a composition model for simulation.


  • develop autosar components by implementing behavior algorithms, simulating components and compositions, and generating component code.


  • model communication between an autosar software component and autosar basic software (bsw) services.


  • implement component calls to diagnostic event manager (dem) service with preconfigured autosar basic software blocks.


  • implement component calls to function inhibition manager (fim) service with preconfigured autosar basic software blocks.


  • implement component calls to nvram manager (nvm) service with preconfigured autosar basic software blocks.


  • for system-level simulation of autosar basic software caller blocks, use reference implementations of basic software services.

  • simulate autosar basic software services and run-time environment

    simulate autosar component calls to basic software memory and diagnostic services by using reference implementations.


  • simulate autosar component calls to basic software function inhibition and related services by using reference implementations.


  • this example shows how to simulate and verify the behavior of autosar components modeled in simulink® that contain calls into the autosar diagnostic event manager (dem).

网站地图