Special Features of the ARXML Import

ASCET can import ARXML files from several AUTOSAR versions; see this AUTOSAR format overview. For the import to work, you must specify the correct package for platform implementation types in the Platform Types field of the Interfaces\Import node in the ASCET options window.

• The importer analyzes all AR-Packages to gather information about primitive data types, mode declaration groups, record types, Parameter interfaces, Sender-Receiver and NVData interfaces, Client-Server interfaces, software component types, compu_methods, interrunnable variables, ports, runnable entities, Operation Invoked events, Mode Switch events, and Timing events. This information is used to create the ASCET counterparts of the AUTOSAR elements.

  Other AUTOSAR elements are currently not supported; they are ignored during import.

• The AUTOSAR name space is mapped to a folder structure in ASCET.

  For example: An AUTOSAR element named /BaseSystem/DataTypes/VoltBatt is placed, in ASCET, in a top-level folder BaseSystem, sub-folder DataTypes; the item name is VoltBatt.

• AUTOSAR COMPU-METHODs are mapped as follows:

  COMPU-METHOD category	ASCET object
  TEXTTABLE	enumeration
  IDENTICAL	Identity formula
  LINEAR	linear formula
  RATFUNC	Moebius formula (if possible)

  Other categories of COMPU-METHODs are not supported.

• The primitive AUTOSAR types INTEGER-TYPE, REAL-TYPE, BOOLEAN-TYPE and OPAQUE-TYPE are mapped to suitable implementation types (see also Implementation Types) in the default project of the software component.
• AUTOSAR mode declaration groups are mapped to ASCETmode groups.
• AUTOSAR record types are mapped to ASCETrecords. All elements and implementation information are preserved.

• AUTOSAR Sender-Receiver and NVData interfaces are mapped to ASCETSenderReceiver interfaces and NVData interfaces.

  ASCET supports only elements with the IS-QUEUED attribute set to false. If this attribute is set to true, a warning "not yet supported" is issued.

  All attributes from the SW-DATA-DEF-PROPS section of an element are currently ignored, since there are no adequate properties in ASCET.

• AUTOSAR Client-Server interfaces are mapped to ASCETClientServer interfaces. Operation prototypes are mapped to public methods with method arguments.

  For all POSSIBLE-ERRORS defined in the interface, an enumeration type is created in ASCET (in the same folder as the ClientServer interface). The name of the enumeration is set to <name of CS-Interface>_AppError.

• AUTOSAR Parameter interfaces are mapped to ASCETcalibration interfaces. All child elements with implementation information are converted accordingly.

• An AUTOSAR software component is mapped to an ASCET SWC. In detail, this means the following:

  • For each Provided port prototype, a Pport is created in the SWC.

    If the port is of type Client-Server interface, a public diagram named <port name>_<interface name> is created, too. Within this diagram, runnable entities with suitable signatures are created for each operation.

  • For each Required port prototype, an Rport is created in the SWC.

  • For each runnable, the attributes CAN-BE-INVOKED-CONCURRENTLY and MINIMUM-START-INTERVAL are converted to appropriate settings in the Settings tab of the runnable's signature editor.

    The implementation of the runnable is set as follows:

    Inline	deactivated
    Use FPU	activated
    Memory Location	Default
    Memory Segment	Automatic
    Symbol	derived from the SYMBOL attribute in the AUTOSAR runnable definition

  • For each TIMING-EVENT, MODE-SWITCH-EVENT, and OPERATION-INVOKED-EVENT, a corresponding event is created in the SWC.

See also

Importing from ARXML or A2L Files

Using the AUTOSAR to ASCET Converter

Import Options

Importing Folders and Database/Workspace Items

Project Editor – Implementation Types

Software Component Editors – Ports and Interfaces

AUTOSAR Interfaces – SenderReceiver and NVData Interfaces

AUTOSAR Interfaces – ClientServer Interfaces

AUTOSAR Interfaces – Calibration Interfaces