6.2.5.3. Architecture-ARXMLRteCommunication

Add dependencies implemented via AUTOSAR classic RTE

Required inputs: RFG

This rule is intended for projects developed according to AUTOSAR classic methodology.See option arxml_name to select the ARXML import.

This script finds communication realized via RTE (most prominently Sender/Receiver or Client/Server) by inspecting the ARXML model. The communication end-points (calls to RTE functions) are identified in the base_view. Artificial communication dependencies are then added to the source code representation in the communication_view.

This makes the communication among application SWCs visible, especially for an architecture check.

Possible Messages

This rule has no predefined messages.

Options

• This rule shares the following common options: exclude_messages_in_system_headers, excludes, includes, justification_checker, post_processing, provider, severity

• The following places define options that affect this rule: Analysis-GlobalOptions

advanced

Advanced settings. Typically these should not be changed.

 

advanced.map_from_rfg_instead_of_ir : bool = False

Do not require an IR file to be present in the project. Instead, compute the source mapping directly from the RFG. This can be useful for debugging if IR is not available. Setting this to true may negatively impact execution time and parallelization.

 

arxml_name

arxml_name : str = 'default'

Name of the ARXML import. This shall be configured in an instance of the rule Frameworks-AutosarArxml to refer to a specific set of ARXML files.

 

base_view_name

base_view_name : str = 'Code Facts'

Name of the base view containing the program dependencies, generated by rule Architecture-Dependencies. Typically this should be either Code Facts, or Declaration Facts, or a view copied from one of those. This view shall contain the runnable entities as Routine nodes and invocations of Rte functions as Macro_Invocation or Call edges.

 

communication_view_name

communication_view_name : str | None = None

Optionally, name of a separate view to generate new dependencies into. If set to None, new dependencies will be added directly into the base_view. If this option designates an existing view, new dependencies will be added without clearing the view.

 

export_warnings

export_warnings : bool = True

Export output messages to the analysis database.

 

loglevel

loglevel : LogLevel = 'WARNING'

Logging mode. WARNING only outputs errors and warnings, INFO additionally prints info messages, DEBUG additionally outputs info and debug messages.

 

Option Types

These types are used by options listed above:

LogLevel

An enumeration.

 

• WARNING

• INFO

• DEBUG