Figure 1. AUTOSAR software architecture. While some AUTOSAR projects that our team works on involve a set of SW-C that runs on top of the RTE, others require more direct access to the ECU microcontroller via a complex device driver (CDD) operating under the RTE. · Hence there was a need to develop Complex Device Divers (CDD) for the Powertrain ECU. In a nutshell, our customer’s EV (Electric Vehicle) team was confronted with the following challenges. Design and development of the Complex Device Drivers (CDD) for the specific devices. Configuration of the interface between CDDs and the AUTOSAR application . A Complex Driver is a software entity not standardized by AUTOSAR that can access or be accessed via AUTOSAR Interfaces and/or Basic Software Modules APIs. According to the document [3] Layered Software Architecture, a CDD is a specific module located in the Complex Drivers Layer of the Basic SoftWare which interacts.
Complex drivers are software modules that are not defined by AUTOSAR. The main purpose of complex drivers is to add support for complex sensors or actuators. They may also be used to extend or enhance the AUTOSAR standard in various ways e.g. encapsulating legacy functionality. The complex drivers may have three different interface categories. Abstract: The Complex Device Driver is a loosely coupled container, where specific software implementations can be placed. The only requirement to the software parts is that the interface to the AUTOSAR system has to be implemented according to the AUTOSAR port and interface specifications. The purpose of the Complex Device Drivers is to fulfill the special functional and timing requirements for handling complex sensors and actuators. The Complex Device Driver is a loosely coupled container, where specific software implementations can be placed. The only requirement to the software parts is that the interface to the AUTOSAR system has to be implemented according to the AUTOSAR port and interface specifications.
Software), is now continued with AUTOSAR (Automotive. Open System Architecture) which will In addition, non-standardized complex drivers need to be. Complex device driver-AUTOSAR part views views. . 8. Dislike. Share. Save. Venkatesh Mane. Venkatesh Mane. 8 Dec The word AUTOSAR and the AUTOSAR logo are registered trademarks. Page 3. Complex Driver design and integration guideline. AUTOSAR CP Release
0コメント