Author Classic AUTOSAR SWCs in Simulink

Use this skill to create, extend, repair, and validate one Classic AUTOSAR Application Software Component (SWC). Keep the work focused on the component model, its AUTOSAR mappings, and its generated component artifacts.

When to Use

Use this skill for a Classic AUTOSAR SWC when the work involves:

• Creating or extending an AUTOSAR-mapped Simulink component model.
• Configuring runnables, generated symbols, timing events, init behavior, or sender-receiver data access.
• Mapping root ports, client-server operations, BSW service calls, or inter-runnable variables (IRVs).
• Repairing an existing component mapping without losing its intended interfaces, events, or customizations.
• Importing or updating a component model from changed ARXML.
• Checking generated component ARXML or C code for requested interfaces, symbols, events, or memory placement.

When Not to Use

• Do not use this skill for Adaptive AUTOSAR, ara::com, service discovery, SOME/IP, or Adaptive service interfaces.
• Do not use this skill for non-AUTOSAR code-interface configuration, including coder.mapping.* storage classes and code mappings or Embedded Coder dictionary Data/Service Interface setup. Use simulink-configure-code-interfaces for those tasks.
• Do not use this skill to author an AUTOSAR composition, a System Composer model, or an architecture-level interface topology.
• Do not use this skill for generic Simulink editing that has no Classic AUTOSAR SWC mapping or code-generation concern.

Start With the Current Component

Answer a request for an API pattern or a modeling decision directly when it does not require a model change. For a model change, inspect the supplied component before modifying it: