Automotive OEMs are developing AUTOSAR-based electronic systems to cope with the increasingly complex software in today's cars. AUTOSAR simplifies the development process and makes the ECU software reusable. Since the advent of AUTOSAR in 2004, this innovative cutting-edge technology has been tested in many research projects; now, AUTOSAR is beginning to enter the real implementation phase through productized ECUs. AUTOSAR software represents the current state of the art and continues to evolve through continuous version updates.
This article refers to the address: http://
The automotive industry is facing a new era. The increasing number of complex car functions has made the development of automotive electronics more and more complicated. The complexity of the ECU development process is exacerbated by the customer's functional and individual requirements for the product, as well as the increased demand for such non-functional requirements. Cars, especially premium luxury cars, have more than 1,000 software features, several in-car bus networks, and more than 70 ECUs. Due to the diversity of hardware platforms in the automotive electronics field, ECU software development relies heavily on hardware and system configuration. Changes to the relevant constraints each time will result in rewriting the program or modifying the software.
To reduce the complexity of ECU software development, AUTOSAR development members provide a proven software architecture as the basis for developing reusable applications. AUTOSAR, an open system architecture standard, is developed by automotive OEMs, component suppliers and companies in the software, semiconductor and electronics industries worldwide. AUTOSAR allows users to avoid the growing development costs associated with adopting proprietary solutions.
AUTOSAR divides the electronic architecture into layers and modules. While defining interfaces, AUTOSAR also defines software components and hardware platform standards that are easy to exchange. The AUTOSAR development members not only provide specifications for the underlying software modules, but also provide methods for developing distributed system applications. This approach begins with model-based software and distributed system descriptions, with automatic code generation and repeatable testing. This approach simplifies the use of the toolchain.
Three years after the launch of AUTOSAR, AUTOSAR development members released version 2.1 in 2007. At this point, the development of AUTOSAR has reached a stable stage. Several different development projects have tested the practicality of AUTOSAR. In the commercial field, the "AUTOSAR Evaluation System" has been completed. Now, AUTOSAR is ready to enter the product ECU.
In order to achieve the goal of AUTOSAR, which is to achieve separation between the application and the base module, automotive electronics are abstracted into several layers. The connection to the actual microcontroller, the physical basis, is abstracted into the microcontroller abstraction layer used to map the functions and peripheral interfaces of the microcontroller. The microcontroller abstraction layer defines the memory interface, the I/O driver interface, and the communication connection interface, as well as emulating functions that the microcontroller cannot provide. The second layer is a layer of abstraction ECU (ECU Abstraction Layer). This layer provides peripherals drivers for the ECU based on the ECU-related hardware. The third layer is the Services Layer. This layer provides a variety of services such as network services, memory management, network communications, and operating systems. The service layer is largely independent of the hardware system. The fourth layer of RTE truly separates the application from the underlying software. The RTE handles application integration and data exchange between the application and the underlying software modules. The existence of RTE is the foundation for real application reuse. Because RTE pre-defines the relevant interfaces, developers can develop application software without knowing the hardware and apply it to any AUTOSAR-compliant ECU.
Virtual function bus (Virtual Functional Bus) forming a base configuration of these layers. Through this virtual bus, all automotive electronic communication components can be abstracted while using pre-defined ports; for virtual function buses, there is no difference between ECU internal communication and external bus communication. This difference will not be reflected until the system layout and the specific functions of the ECU are finalized. The software components themselves are not concerned with this distinction, so we can develop software components in a separate situation. The software component is divided into a number of executable units, ie running entities. When a specified event occurs, a corresponding running entity is triggered. Such an event may be a new sensor signal or a periodic timing. The formal description of the electronic system from the perspective of the virtual function bus ultimately defines the interface to the relevant software components. Therefore, the development of application software can be independent of the specific ECU.
RTE provides access to I/O, memory, and other basic services. With a model-based description, RTEs can be tailored to specific ECUs to accommodate different needs and save resources.
method
While defining the ECU software architecture, the AUTOSAR standard also defines the method of developing an AUTOSAR system. Compliance with a proven development process is an important prerequisite for developing software. The deficiencies in the requirements list are discovered early in development, and the reuse of software components simplifies the development process and makes the entire system more reliable. However, this approach also allows for a degree of freedom: for example, the user can decide whether to use a top-down or bottom-up development process.
The purpose of AUTOSAR is to provide common support for software development processes through tools. Mature tools are used for structured implementation and corresponding management of requirements, while establishing corresponding configurations.
The first step involves a formal description of three main aspects: software (software components), ECU (ECU resources), and system constraints. A suitable editing tool for creating a complete system description
The system configuration serves as the basis for the ECU configuration, and the user can use the configuration tool to generate the underlying software components based on the ECU configuration. At the end of the development process, there are several generation tools that can be used to generate RTE and basic software. All design and configuration data during development is saved in a uniform file format. To this end, AUTOSAR defines an XML-based file format. On the one hand, a unified file format guarantees the versatility of the development process; on the other hand, it simplifies the seamless integration between development tools.
transplant
AUTOSAR's software architecture is not a single module, it contains a large number of interfaces to define complete standard modules. This makes the migration of AUTOSAR very easy, even between projects; it is also possible to use both standard AUTOSAR modules and proprietary software modules within a single project.
In order to achieve such a migration, the existing software architecture and the AUTOSAR architecture must first be compared. By analyzing overlapping functions and integration options, it is decided which modules can be retained and which modules should be replaced by standard software modules.
Therefore, it is a very wise choice to introduce a separation layer between the application and the underlying software. One possible approach is to prepare the application and AUTOSAR software components early in the migration process and integrate them through RTE. Under RTE, a dedicated modification layer is used to provide an interface to existing underlying software, as shown in Figure 3.
If some of the existing base software needs to be replaced by the AUTOSAR base software, the focus is on using a unified tool. Vector provides the right tools for configuring proprietary software modules. The non-AUTOSAR module can be gradually replaced by the AUTOSAR module, thus avoiding the risk of overthrowing the entire architecture or the enormous workload of rewriting the module.
prospect
The release of AUTOSAR 3.0 marks the further improvement of the AUTOSAR standard. Companies involved in standards development are committed to continuing efforts to achieve the goals of AUTOSAR. The various ideas currently introduced will be implemented in the future version 4.0 of AUTOSAR.
Tool vendors have also come up with some ideas related to AUTOSAR. Vector's AUTOSAR development team is working to make AUTOSAR-based ECU development easier and easier. A typical example is the test tool for the AUTOSAR application component running on a PC. This tool can also be used as a simulation environment for an AUTOSAR-compliant ECU. This makes it easier to test the implementation code of the AUTOSAR software component on a PC. Widely used standardized tools (such as Vector's CANoe) can be used for test implementation, visual testing, and generating test reports. Vector supports the entire development process with a full suite of AUTOSAR basic software components and a common design and development tool chain
Vector's AUTOSAR solution has been validated in several projects, along with proven products that are compliant with AUTOSAR 2.0 and 2.1 (AUTO 3.0-compliant products will be available in the second quarter of 2008).
to sum up
AUTOSAR is becoming a reality. Many OEMs plan to use AUTOSAR in their next models. Vector provides a complete solution for AUTOSAR, including AUTOSAR software components and development tools. This not only supports pure AUTOSAR system development, but also supports the gradual migration of existing systems to AUTOSAR.
24V Frequency Transformer,110V 60Hz To 220V 50Hz Transformer,Oil-Filled Electric Transformer,Electric Transformer Price
IHUA INDUSTRIES CO.,LTD. , https://www.ihua-sensor.com