MICROSAR COM RTE Interface Configuration Guide

Content

1 Introduction. 3

1.1 Abbreviations（ Specific terms of the document）: 3

2 APPInterface Structure. 4

2.1 RTE Concept 4

2.2 APP Route Principle. 4

3 Interface Configuration method. 5

3.1 Autosar-compliant network configuration. 5

3.1.1 Interface, ADT, IDT rules in ZCU.. 5

3.1.2 Naming rules for Port 5

3.2 How to use the script 6

3.2.1 Script usage and development process. 6

4 Generate code analysis：... 23

4.1 System signal Receiving：... 23

4.2 System signal Sending and forwarding. 23

4.3 Experience Sharing. 23

5 Summary of issues. 26

1. Introduction

This document describes the methodology of RTE Interface configuration, aiming at a fast and accurate RTE Interface configuration and improving development efficiency.In AUTOSAR software architecture, integration or application layer engineers need to use Davinci Developer tool for SWC architecture design, interface connection, runnable cycle definition, etc. and Davinci Configurator tool for BSW configuration, code generation, etc.

The purpose of this document is to introduce the interface and usage of Developer, the principle of RTE Interface and the usage of tools to help implement the functions.

1. 1. Abbreviations（ Specific terms of the document）:

SWC	Software Componet
RTE	Run-time environment
P/R Port	Provide/Receiver Port
VFB	Virtual Function Bus

1. APPInterface Structure
   1. RTE Concept

RTE is the interface implementation of VFB in AUTOSAR.

RTE provides a basic communication service that supports communication between software components and from software components to the base software module.

RTE provides configuration of component-to-ECU heterogeneous information thus standardizing RTE services.

RTE is generated specifically for each ECU.

1. 1. APP Route Principle

The current ZCU project communication signals are passed by creating an intermediate layer, adding a new SWC between ASW and BSW, creating Runable in the Inter Behavior to complete the interaction, communication signals are passed, received, signal routing, message Timeout, Callout, Counter and other signal processing work is done here.

1. Interface Configuration method
   1. Autosar-compliant network configuration

At the RTE level, the smallest unit of communication is the signal. After completing the communication BSW software configuration, you can see all the signals that have been configured in CFG by clicking DataMapping in develop

1. 1. 1. Interface, ADT, IDT rules in ZCU

Interface is the carrier of IDT ADT, but for agile development, the application layer needs the underlying unprocessed signal values, no need to add calculation methods, so the Data Type associated with the interface are Base type

1. 1. 1. Naming rules for Port

Depending on the project, there are different naming conventions, which need to be communicated with the system section in advance, in order to separate development and reduce the amount of rework.

In the ZCU project, the Signal from BSW and the