configure autosar scheduling and simulation -凯发k8网页登录

simulate basic software service calls

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 architecture, composition, or test harness model and add preconfigured bsw service component blocks. the blocks provide reference implementations of bsw service operations.

if the components in your architecture model use bsw caller blocks, make sure that the architecture model contains bsw service implementations. for more information, see and simulate autosar basic software services and run-time environment.

for an example of using bsw blocks in an autosar architecture model, see .

connect a test harness

after you develop an architecture model, you can connect it to a test harness model that provides meaningful input values and plant model elements. for example, consider the architecture model autosar_tpc_composition from example . the model has three require (input) ports and one provide (output) port.

here is a test harness model for simulating the architecture model autosar_tpc_composition. the test harness contains a plant model with a pedal input block and signals that correspond with the architecture model require and provide ports. this model was adapted from example model autosar_tpc_system.

to connect the architecture model to the test harness:

to view and run the completed test harness model, open example model autosar_tpc_system. (to open the model in a local working folder, use openexample('autosar_tpc_system').)

schedule component runnables

for autosar classic platform software components that contain multiple runnables, the autosar timing extensions specification defines execution order constraints. these constraints specify the execution order of runnable entities within a component. you can view and manipulate the constraints at the component level or, in autosar architecture models, at the virtual function bus (vfb) level.

in architecture models, you can:

to schedule and specify the execution order of autosar component runnables, use the schedule editor. from a standalone component model or an architecture model, you can:

the schedule editor supports multiple modeling styles, including rate-based and export-function modeling. for more information, see and . for autosar component model examples, see .

in an autosar architecture model, to open the schedule editor, open the modeling tab and select design tools > schedule editor. the editor displays every runnable in every component in the composition hierarchy. here is the execution order view when you open the schedule editor from the example architecture model autosar_tpc_composition. use the editor controls to modify the execution order of the runnables.

exporting a composition from an autosar architecture model exports vfb-level execution order constraints into the file modelname_timing.arxml. the arxml module aggregates timing information from the entire composition hierarchy. this arxml code shows the execution order constraint exported for the runnables in autosar_tpc_composition, based on the schedule editor configuration.

  tpc_composition
  
    <execution-order-constraint uuid="...">
      eoc
      
        /components/tpc_composition
      
      
        
          pedalsensor_pedalsensor_step
          
            
              /components/sensors/pedalsensor
            
          
          
            /components/pedalsensor/pedalsensor_ib/pedalsensor_step
          
          
            
              /timing/tpc_composition/eoc/tps_primary_throttlesensor1_step
            
          
        
        
          tps_primary_throttlesensor1_step
          ...
        
        
          tps_secondary_throttlesensor2_step
        ...
        
        
          monitor_throttlesensormonitor_step
          ...
        
        
          ctrl_controller_step
          ...
        
        
          actuator_actuator_step
          
            
              /components/tpc_composition/actuator
            
          
          
            /components/actuator/actuator_ib/actuator_step
          
        
      
    
  
  
    /components/tpc_composition