Search

CN-116755366-B - Driving platform system for vehicle-mounted electronic control unit and construction method thereof

CN116755366BCN 116755366 BCN116755366 BCN 116755366BCN-116755366-B

Abstract

The present disclosure relates to a drive platform system for a vehicle-mounted electronic control unit and a method of constructing the same. A driver platform system for an on-board electronic control unit, the driver platform system comprising, in order from bottom to top, a microcontroller abstraction layer configured to provide an underlying driver of the driver platform system, the microcontroller abstraction layer having unique direct access to registers and peripherals of a microcontroller of the on-board electronic control unit, a complex device driver layer configured to access complex device drivers, a base software layer configured to provide system level services, and an internal interface layer configured to provide data interactions between the base software layer and an application layer external to the driver platform system.

Inventors

  • LIU JUN
  • MAO JIAJIAO

Assignees

  • 上海纳恩汽车技术股份有限公司

Dates

Publication Date
20260505
Application Date
20230606

Claims (13)

  1. 1. A drive platform system for an on-board electronic control unit, the drive platform system comprising, in order from bottom to top: A microcontroller abstraction layer configured to provide an underlying drive of the drive platform system, the microcontroller abstraction layer uniquely having direct access to registers and peripherals of a microcontroller of the on-board electronic control unit; A complex device driver layer configured to access complex device drivers; A base software layer configured to provide system level services, and An internal interface layer configured to provide data interaction between the base software layer and an application layer external to the drive platform system, Wherein the microcontroller abstraction layer is configured to abstract features of a plurality of different microcontrollers that do not include a controller of an electronic control unit of the vehicle and provide a unified interface to be compatible with the plurality of different microcontrollers.
  2. 2. The drive platform system of claim 1, wherein a first module in the base software layer is not data interactable with a first module in the application layer without the internal interface layer.
  3. 3. The drive platform system of claim 1, wherein the internal interface layer is further configured to provide data interaction between modules of the application layer, Wherein a second module in the application layer is not capable of data interaction with a third module in the application layer without via the internal interface layer.
  4. 4. The drive platform system of claim 1, wherein the microcontroller abstraction layer comprises a digital input output drive module, the base software layer comprises a sensor module, the application layer comprises an application module, and wherein: The digital input output driver module of the microcontroller abstraction layer is configured to obtain an input signal and transmit the input signal to the sensor module of the base software layer in response to control at an application device associated with the application module of the application layer; The sensor module is configured to receive the input signal from the digital input output drive module and transmit the input signal to the internal interface layer, and The internal interface layer is configured to transmit the input signal to the application module of the application layer.
  5. 5. The drive platform system of claim 4, wherein the base software layer further comprises an executor module, the complex device driver layer comprises a complex device driver high-side driver module, and wherein: The application module of the application layer is configured to convert the input signal into an output signal and transmit the output signal to the internal interface layer; the internal interface layer is configured to invoke the executor module of the base software layer to execute the output signal; the executor module of the base software layer is configured to invoke the complex device driver high-side driver module of the complex device driver layer in response to being invoked by the internal interface layer; The complex device driver high-side driver module of the complex device driver layer being configured to adjust the output signal to an adjusted output signal suitable for execution by the application device in response to being invoked by the executor module, and invoke the digital input output driver module of the microcontroller abstraction layer to execute the adjusted output signal, and The digital input output drive module of the microcontroller abstraction layer is configured to drive the application device to perform an operation corresponding to the control in accordance with the adjusted output signal.
  6. 6. The drive platform system of claim 1, wherein the base software layer comprises a sensor module and an actuator module, wherein: The sensor module is designed with a functional service interface, a fault diagnosis interface, and a hard-wired input service interface, the hard-wired input service interface of the sensor module is encapsulated by the functional service interface and the fault diagnosis interface of the sensor module to provide a sensor abstraction interface, and The actuator module is designed with a functional service interface, a fault diagnosis interface, a hard-wired input service interface, and a hard-wired output service interface, which are encapsulated by the functional service interface and the fault diagnosis interface of the actuator module to provide an actuator abstract interface.
  7. 7. The drive platform system of claim 1, wherein the drive platform system comprises a first type of module and a second type of module, the configuration parameters of each of the first type of module being non-configurable, one or more of the configuration parameters of each of the second type of module being configurable and the remaining configuration parameters being non-configurable.
  8. 8. The drive platform system of claim 1, wherein the internal interface layer comprises a piled interface for testing modules in the application layer regardless of whether one or more of the microcontroller abstraction layer, the complex device driver layer, and the base software layer are present and what configuration, if any.
  9. 9. The drive platform system of claim 1, wherein the microcontroller abstraction layer comprises a microcontroller interface, a port interface, a digital input output interface, a universal timer interface, an interrupt service routine interface, an electrically erasable programmable interface, and a controller area network interface, and the base software layer comprises a system base chip interface, a high-side drive interface, a non-volatile memory interface, an operating system interface, a sensor interface, an actuator interface, and a controller area network networking interface.
  10. 10. The drive platform system according to claim 9, further comprising one or more of: The system comprises a watchdog interface, an input capturing unit interface, a pulse width modulation interface, an analog-to-digital conversion interface, a serial peripheral interface and a local internet interface in the microcontroller abstract layer, wherein the watchdog interface, the radio frequency interface, the analog-to-digital conversion manager interface, the serial peripheral interface manager interface and the electronic control unit manager interface in the basic software layer.
  11. 11. An on-board electronic control unit comprising a drive platform system according to any one of claims 1 to 10 and an application layer external to the drive platform system.
  12. 12. A vehicle comprising an on-board electronic control unit according to claim 11.
  13. 13. A method of building a drive platform system for an on-board electronic control unit, comprising: Providing a microcontroller abstraction layer to provide a bottom level driver of the driver platform system, the microcontroller abstraction layer uniquely having direct access to registers and peripherals of a microcontroller of the on-board electronic control unit; Providing a complex device driver layer for accessing complex device drivers; Providing a base software layer for providing system level services, and An internal interface layer is provided for providing data interaction between the base software layer and an application layer external to the drive platform system, Wherein features of a plurality of different microcontrollers, which do not include a controller of an electronic control unit of the vehicle, are abstracted by the microcontroller abstraction layer and a unified interface is provided to be compatible with the plurality of different microcontrollers.

Description

Driving platform system for vehicle-mounted electronic control unit and construction method thereof Technical Field The present disclosure relates generally to the field of vehicle technology, and more particularly to a drive platform system for an on-board electronic control unit and a method of constructing the same, as well as to an on-board electronic control unit comprising such a drive platform system and a vehicle comprising such an on-board electronic control unit. Background Thanks to the continued development of units in vehicles that implement electronic control functions (also known as on-board electronic control units), vehicles are becoming increasingly automated and intelligent. In order to cope with challenges brought by the acceleration of upgrading and updating of vehicles, shortening of marketing period and the like, a large number of vehicle-mounted electronic control units are currently designed by adopting an automobile open system architecture (Automotive open system architecture, AUTOSAR), and the bottom software architecture unifies interface standards and layered architecture for different spare and accessory parts suppliers, thereby being beneficial to the exchange and updating of automobile embedded software and providing a better solution for managing complex software. An underlying software architecture such as AUTOSAR has a complete set of frameworks that cover the business requirements of part of the chip, all of the hardware, all of the underlying software logic, and all of the application layers. Such a large and full framework results in a very large number of parameters that need to be configured. For example, the underlying software configuration parameters of an automotive central electronic control unit (Electronic control unit, ECU) developed with AUTOSAR can be tens of thousands. However, for those lightweight vehicle-mounted electronic control units that perform simpler functions (e.g., a window controller for controlling the lifting of a window, a lamp controller for controlling the turning on and off of a lamp, a wiper controller for controlling a wiper switch, etc., typically only one or a few functions), they are often implemented with a much cheaper controller than an ECU, and on-chip resources of such controllers cannot meet the application requirements of AUTOSAR. Therefore, such lightweight vehicle-mounted electronic control units cannot be quickly developed by means of the existing underlying software architecture such as AUTOSAR, and still follow the traditional software development mode. Disclosure of Invention According to a first aspect of the present disclosure, there is provided a drive platform system for an on-board electronic control unit, the drive platform system comprising, in order from bottom to top, a microcontroller abstraction layer configured to provide an underlying drive of the drive platform system, the microcontroller abstraction layer having unique direct access to registers and peripherals of a microcontroller of the on-board electronic control unit, a complex device driver layer configured to access complex device drives, a base software layer configured to provide system level services, and an internal interface layer configured to provide data interaction between the base software layer and an application layer external to the drive platform system. In some embodiments, a first module in the base software layer may not interact with a first module in the application layer via the internal interface layer. In some embodiments, the internal interface layer is further configured to provide data interaction between modules of the application layer, wherein a second module in the application layer may not interact with a third module in the application layer via the internal interface layer. In some embodiments, the microcontroller abstraction layer includes a digital input output driver module, the base software layer includes a sensor module, the application layer includes an application module, and wherein the digital input output driver module of the microcontroller abstraction layer is configured to obtain an input signal and transmit the input signal to the sensor module of the base software layer in response to control at an application device associated with the application module of the application layer, the sensor module is configured to receive the input signal from the digital input output driver module and transmit the input signal to the internal interface layer, and the internal interface layer is configured to transmit the input signal to the application module of the application layer. In some embodiments, the base software layer further comprises an executor module, the complex device driver layer comprising a complex device driver high-side driver module, and wherein the application module of the application layer is configured to convert the input signal into an output signal and transmit the output signal to the i