[AUTOSAR II appl overview]

1 AppL form

• Application software components SWC

• AutoSAR Interface Ports And connectors Connector

• Runnable entities Runnable

2 SWC

2.1 SWC Communication for

SWC The communication between them is carried out outside the application software layer , We call it virtual function bus （VFB）.
The bus is a combination of on-chip and off chip communication , It is called virtual function bus , It is actually divided into two parts ：

1. In the film is through RTE signal communication . The previous chapter said , One SWC You can think of it as one .c file , that c How to communicate between files —— Global variables .

2. Off chip communication through off chip bus （ It's usually on cars CAN Bus）

The symbol in the above figure refers to AutoSAR Interface (Ports), The blue connecting line between them is called a connector (Connector).

2.3 SWC The distribution of

We put the above 7 individual SWC Assigned to two ECU in （ In fact, it's also done in cars ）. Turn the lamp switch 、 Put the dimming controller and the left and right dome lights into one ECU It is controlled by a chip on the top of the car ; Put the left and right door switches and the door switch logic unit into the dedicated door ECU In chip control .
Two ECU That is, two controllers , The door controller at the front of the car body and the dome light controller at the top of the car body .ECU Inside SWC It's through RTE Management to communicate ; And cross ECU The communication of is through the external bus （ It's usually CAN, That is, the car body is connected with ECU Of CAN Twisted pair harness ）.
thus , Unify the functions of the whole ceiling lamp , And deployed to all parts of the car body ECU To perform .

2.4 SWC The type of

2.4.1 Atomic SWC（Atomic SWC）

Atomic SWC（Atomic SWC）： seeing the name of a thing one thinks of its function , It can't be divided any more SWC.

We will SWC As atom , that runnable Is one of the electrons 、 Protons and neutrons , They are inseparable from atoms . So it will SWC As the smallest unit ,runnable Is one of the functions . Every SWC The functions of are basically used to implement specific algorithms .

2.4.2 Set level SWC（Composition SWC）

There is indivisible SWC, There must be divisible SWC. therefore AutoSAR It also stipulates a kind of set level SWC（Composition SWC）. They can be divided into smaller ones Atomic SWC.

We can integrate functions that are similar or need to be integrated into a convenient place to watch SWC（ in the future Atomic SWC Are abbreviated to SWC） Using a compositon
SWC Include . such , It's convenient SWC classified

This will AppL In the form of a folder , The relationship of file mapping will also change ：

• Be careful ：
  stay Vector Of DaVinci In fact, it will not generate Composition Folder , In order to make it easier for everyone to understand . Actually Composition It's just a concept , It is used to facilitate classification and sorting on the configuration tool , It looks pleasant

2.4.3 special SWC

actually , It is not just the application layer that needs to add code SWC. stay BSW in ,IO Hardware abstraction layer （IoHwAb,BSW The chapter will talk about ） And complex drivers （Cdd) You need to add code manually , These two places can also be regarded as SWC, stay DaVinci Developer Can be used as SWC Configure and add runnable The operations such as . therefore , We regard it as special SWC To look at

3 Ports type

Ports yes SWC and SWC Interface （Interface） Communication with , perhaps SWC adopt RTE and BSW Interface （Interface） Communication with .

Ports It is mainly divided into 5 Types , Listed in the figure below ：

Which can be classified as ：R-Ports、P-Ports and PR-Ports. It is worth noting that , there PR-Ports Only in AutoSAR4 It defines .
Or it can be divided into ：Send/Receiver（S/R） Interface and Client/Server（C/S） Interface .
and S/R The interface is used to transmit data ;C/S Interfaces are used to perform operations .

3.1.1 S/R Interface

• effect ： To transmit data . adopt RTE To transmit data , And through RTE Manage data transmission , Avoid data problems （ For example, an error may occur when calling the same data at the same time ）
• An interface can contain multiple data , Similar to transmission through structures
• Basic data types can be transferred （int,float etc. ） And complex data types （record,array etc. ）

To be more specific , For example, call the receiving interface ：

Rte_Read_<Port>_<Data>()
// there xx Refers to the transmitted data content , such as DoorOpen Namely ：
SWC_DoorOpen = Rte_Read_Door_DoorOpen();

3.1.2 C/S Interface

• effect ： Provide operation . Namely Server Provide functions for Client call
• It can be synchronous and asynchronous . Synchronization is a direct call , It is equivalent to inserting the function directly into the context to run ; Asynchronous words need to wait , It is equivalent to letting the function run in another thread , Return after running , The original context is still running
• One interface can provide multiple operations , An interface can contain many functions
• ECU Internal and cross ECU You can call , Span ECU Also through the external bus

To be more specific , For example, call the client interface ：

Rte_Call_<Port>_<Function>()
// there xx Refers to the called function , For example, call State() Namely ：
Rte_Call_Door_State();

4 Runnables Runnable entities

Runnable Namely SWC The function in , And in the AutoSAR The architecture is being DaVinci When the software is generated ,Runnable It's a null function , You need to add code manually to achieve its actual function .

Runnable Can be triggered , For example, triggered by a timer 、 Triggered by operation call or received data .

• Runnable Is the need to OS Medium Task As a carrier .

runnable Is the function , But again c There is only one function in the file, which is useless , This function must be called to work , There must be tasks in the operating system to execute this function .