[AUTOSAR five methodology]

1. Simple and necessary concepts

1.1 The name in the supply chain

abbreviation	OEM	TIER1	TIER2
Chinese name	Agent factory （ Vehicle factory ）	First tier supplier	Secondary supplier
Example	Mercedes 、 BMW 、 Audi, etc （ Mainly do the assembly work of the whole vehicle ）	mainland 、 Bosch et al （ Mainly for OEM supply ECU、 Sheet metal parts, etc ）	Ying Feiling 、NXP etc. （ Mainly for TIER1 Supply parts , such as ECU The chip on the 、MOS Tubes and circuit boards ）

1.2 What is methodology ？

Construction conforms to AutoSAR Architecturally ECU Detailed workflow of software

Methodology mainly stipulates the following contents ：

• Specific workflow ： from OEM Start designing automotive electronic architecture , To each TIER1 Complete each ECU The whole process of software design , In a moment we will cover
• Specific exchange documents ： OEM and TIER1 Between 、TIER1 Inside AutoSAR Between the bottom layer and the application layer and MCAL And BSW File interaction is required between . But we can't use word To exchange this information , such as OEM Want to tell TIER1 The vehicle's CAN What is the content of the message . Use word Words ,OEM Editing takes time and effort ,TIER1 Reading is also laborious ; therefore AutoSAR A new file format is specified ：.arxml, This format is based on .xml file , add AutoSAR Abbreviation ar became arxml. The advantage of using it is that DaVinci Wait for the software to automatically generate . For example, the whole vehicle factory has designed the whole vehicle with a set of software CAN Communication matrix , Direct export .arxml, Then send it to TIER1;TIER1 stay Davinci Open in , All the contents are clear at a glance , And will automatically CAN、CAN IF、PUDR When the module is configured .（ Is it convenient ！ But now many manufacturers still use DBC file , It's almost the same , however AutoSAR It is recommended to use arxml file ）
• Specific tool chains ： accord with AutoSAR The tool chain , Like DaVinci、ETAS such , I won't repeat this

2. Workflow

2.1 Normal process

1. OEM Through some software, the communication matrix of the whole vehicle is designed , And export DBC、FIBEX or LDF file
2. OEM Send these files to TIER1
3. TIER1 If there is DaVinci Such software , You can import it and configure it automatically Communication Most of the functions

2.2 AutoSAR technological process

1. List requirements ：OEM What is needed to design the whole vehicle ECU、 What functions are needed 、 What do you want SWC, List it first in this step . It is still the previous example of controlling the roof lamp ：OEM You need two ECU（ Car door ECU And roof lights ECU）、 need 7 individual SWC.
2. Allocate demand ：OEM List all SWC Assign to each ECU in .（ Here you can see the door ECU And roof lights ECU There is communication between , Here is transmitted through the bus , Therefore, the information of communication matrix is also included here
3. Give the demand to TIER1 Realization ：OEM Will all ECU The needs of （ Communication matrix 、 What is needed SWC This information ） Generate corresponding arxml file , hand TIER1.（ Every arxml Only this ECU What you need , For example, the door ECU To get the arxml There will be no actuator in SWC The content of ）
4. TIER1 After getting the demand ： Import to DaVinci in , Then it is automatically configured AppL layer ,Communication That's the content of . And then SWC Fill in the specific implementation code , Configure other necessary contents , Just like the