Directory
5.1.1 Unit unit design................................................ ............................4
5.1.2 Component module design................................................ ............ 4
5.1.5 Application layer Simulink project directory................................ .... 9
5.1.6 Simulink project configuration...................................... ............ 10
5.2.1 Convert calibration variable files........................................ ............ 12
5.2.2 Convert a2l calibration file........................................ ............ 12
6.1.1 Naming rules................................................ .............................15
7.1.7 Bootloader, underlying driver, protocol stack and model testing... 20
7.1.9 HIL test, bench and real vehicle test...................... ..... 20
New energy commercial vehicle controller application layer software development and design specifications
This specification applies to the development and design process of application layer software for new energy commercial vehicle controllers.
The software design in this specification only targets the application layer software development and design process.
The following documents are essential for the application of this specification. For dated referenced documents, only the dated edition applies to this document. For undated referenced documents, the latest version ( including all revised versions) applies to this document.
| label |
title |
Version / modification date |
| Ref.1 |
||
| Ref.2 |
3.1 Terminology
Commercial vehicle controller software
Software Architecture
Description of key terms
3.2 Abbreviations
| abbreviation |
full name |
| OEM |
Original equipment manufactureOriginal equipment manufacturer |
| ECU |
Electronic Control UnitElectronic Control Unit |
| CCD |
Complex DriversComplex Drivers |
| EGYPT |
|
In order to achieve the separation between applications and hardware modules, the automotive electronics software architecture is abstracted into four layers: from top to bottom: Application Layer, Run Time Environment (RTE), and Basic Software Layer (Basic Software, BSW) and microcontroller (Microcontroller), as shown in the figure below.
The AUTOSAR software architecture includes a completely independent application layer (Application Layer) and a hardware-related basic software layer (Basic Software, BSW), and a runtime environment (Run Time Environment) is established between the two. Separating the two creates a layered architecture. On the one hand, OEMs can focus on developing specific and competitive application layer software (located above RTE), and on the other hand, it standardizes the basic software layer (located below RTE) that OEMs do not care about. The basic software layer mainly includes four parts: microcontroller abstraction layer (MCAL), ECU abstraction layer, service layer and complex driver. The microcontroller abstraction layer includes hardware-related drivers, which can be used to access memory, communication, I/O, etc.; the ECU abstraction layer is responsible for providing a unified access interface to achieve access to communication, memory, or I/O, thereby There is no need to consider whether these resources are provided by the microprocessor or by external devices; the service layer provides various types of background services, such as network services, memory management, and bus communication services, and the operating system is located on this layer. The complex driver (CCD) layer spans between the microcontroller hardware layer and RTE. Its main task is to integrate non-standard functional modules with special purposes and cannot be configured with MCAL, and embed these functions into the AUTOSAR basic software layer. This enables the specific functional and time requirements of complex sensors and actuators to be processed. Complex drivers are closely related to microcontroller and ECU hardware. Its upper-layer program interface is specified and implemented in accordance with AUTOSAR; its lower-layer program interface is restricted by the standard interface program. Complex drivers can use specific interrupts or complex microcontroller peripherals to directly access the microcontroller to achieve evaluation of complex sensors and control of actuators, such as injection control, solenoid valve control, incremental position detection, etc. .
Since OEMs mainly focus on the development of application layer software, as long as the overall software architecture meets the layering requirements of AutoSAR, the following will focus on the writing specifications of application layer software.
In the design of application layer software, application layer software refers to the entire system software. The system software is composed of multiple module software, and the module software is composed of each unit software. The layered meaning and requirements will be explained separately below. [1]
Unit design is also called minimum subsystem design. The definition of minimum subsystem can be a subsystem with a complete and clearly defined function, such as vehicle speed calculation, pure electric power on and off, hydrogen reactor power on and off, etc. exist