AutoSar CP Learning Summary

Table of Contents of Series Articles

C++ skills series
Linux communication architecture series
C++ high-performance optimized programming series
in-depth understanding of software architecture design series
advanced C++ concurrent thread programming
design pattern series

Looking forward to your attention! ! !

现在的一切都是为将来的梦想编织翅膀，让梦想在现实中展翅高飞。
Now everything is for the future of dream weaving wings, let the dream fly in reality.

1. AutoSar CP learning resources

1.1 AutoSar official website documentation

Address: https://www.autosar.org

1.2 AutoSar CP open source source code

Address: https://github.com/openAUTOSAR/classic-platform/

1.3 Software and hardware tools

1.4 Underlying hardware knowledge

1.5 Communication protocol and working language

2. Introduction to AutoSar CP

2.1 Automotive software

2.2 AutoSar architecture

AUTOSAR defines a set of common technical methods for the development process of automotive electronic software systems , namely the AUTOSAR methodology. This methodology describes the design steps from system configuration to ECU executable code generation, and can help developers master the development process to lead and promote the development process of systems that comply with AUTOSAR standards.

3. Make a simple DEMO of the vehicle controller

3.1 Brief structural block diagram of VCU

3.2 Workflow

4. Communication under AutoSAR architecture

4.1 CAN communication

CAN, which stands for "Controller Area Network", is a multi-master serial communication bus and is one of the most widely used field buses in the world.

4.2 LIN communication

LIN bus is a low-cost serial communication bus defined for automotive distributed electronic systems. It is a supplement to other automotive multi-channel networks such as Controller Area Network (CAN) and is suitable for network bandwidth and performance. Or applications that do not have excessive requirements for fault tolerance. The LIN bus is based on the SCI (UART) data format and adopts a single master controller/multiple slave device mode, which is a special case of UART.

4.3 ETH Communication

AutoSAR's implementation of OSI model

5. Network management

The meaning of network management:
There are multiple ECU control units in the automotive system. These ECU control units are not isolated, but work together. The process by which the automotive electronic system configures, manages and coordinates all ECUs through the vehicle network is called network management.

The purpose of network management:
to enable the ECU nodes in the network to sleep and wake up in an orderly manner. Sleeping when there is no need for communication and waking up when communication is needed can save the power of the car battery.

Network management state machine:
Network management state machine switching:

Network management messages:

6. J1939 Agreement

6. THERE

ECUM state machine:

ECUM state scheduling:
ECU startup method:

7. Storage stack

Memory stack data transfer process

NVM data synchronization mechanism

FEE module and FEE mechanism

8. XCP

9. Diagnosis

UDS
UDS mainly provides unified diagnostic functions for vehicle-mounted electronic control units and adopts a universal automotive diagnostic protocol constrained by ISO 14229. Can be implemented on different automotive buses such as CAN, LIN, Flexray, Ethernet and K-line.

Diagnostic data transfer process

10. Mode configuration

11. ASW layer

The work content of the ASW layer

12. System description

System mapping

13. RTE is the implementation of VFB

RTE’s workflow and work content

14. The necessity of OS

OS

design a minimal AutoSar OS

RTA OS installation and composition

15. Introduction to MCAL and driver classification

MCAL configuration method and process

16. Integration and compilation

Typical project file integration tree

startup process

Reset_Handler