Vehicle controls with synchronized driver
By using a synchronous driver to stop the execution of the AUTOSAR driver in the vehicle control device, real-time writing of flash memory is realized, solving the problem that persistent information storage cannot be real-time in the AUTOSAR architecture, and meeting the real-time requirements of key applications such as vehicle collision records are met. , without increasing hardware costs.
Patent Information
- Application Number
- CN202111544527.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-12-16
- Filing Date
- 2021-12-16
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-12-16
AI Technical Summary
In the AUTOSAR architecture, persistent storage of information cannot be achieved in real time and cannot meet the real-time requirements of some key applications such as recording vehicle collision events.
Design a vehicle control device, use the processor to execute synchronous drivers, stop the execution of the AUTOSAR driver, directly save the flash hardware content, and allow the AUTOSAR driver to continue running during recovery, thereby real-time writing of vehicle status data to flash memory .
Real-time requirements are achieved in single-piece cost, without the need for additional external hardware components, and can quickly record important information such as status data during vehicle collisions, meeting the real-time needs of key applications.
Smart Images

Figure CN114633705B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a vehicle control device with a processor for executing a synchronous driver program to write vehicle status data in a flash memory. In particular, the present invention relates to a dedicated flash driver program for performing real-time flash memory access. Background Art
[0002] The AUTOSAR architecture (AUTOMOBILE OPEN SYSTEM ARCHITECT) is a standard for the development of software components for the automotive industry, which results from the confluence of different automobile manufacturers. AUTOSAR has the following characteristics: a) Implementation and standardization of basic functions, which have a modular structure and can be replaced by modules from third-party manufacturers. b) Scalability for different vehicle types, i.e. the implementation of scalable solutions that benefit from well-tested, high-quality standard modules. c) Possibility of redundant design, especially for safety-critical areas. d) Embedding of modules from other manufacturers. e) Maintainability during the entire product life cycle. f) Software updates and upgrades during the entire life cycle of the vehicle.
[0003] However, it has been shown that in the AUTOSAR architecture, persistent storage of information cannot be done in real time. This is because the implementation in this case is based on the first-in, first-out (FIFO) principle, in which all software components of the system are written to a queue or wait list. The software components are then processed one after the other (asynchronously), so that the exact time before they are processed cannot be determined. The worst-case analysis provides values that are outside the requirements for many applications. For example, a crash event must be saved within 10 ms. Summary of the invention
[0004] The technical problem to be solved by the present invention is to realize a vehicle control device, wherein for certain key applications, such as recording vehicle collisions, real-time and persistent storage of information can be guaranteed.
[0005] The invention is based on the idea of additionally implementing a non-AUTOSAR-compliant driver with a synchronous interface. In the case of a write command, the execution of the AUTOSAR driver is stopped, the content of the flash hardware is saved, and a new write command is directly executed. The previous state of the flash hardware is then restored and the AUTOSAR driver is allowed to continue.
[0006] With this solution, real-time requirements can be implemented in a cost-neutral manner. No additional external hardware components are required.
[0007] Similar implementations are not yet known. An alternative solution is to connect an additional external memory (eg via SPI), but this results in increased hardware costs.
[0008] According to the first aspect of the present invention, this technical problem is achieved by a vehicle control device with a processor and a flash memory, wherein the processor is designed to execute multiple processes, each of which is related to a corresponding vehicle control component; wherein the processor is designed to execute an asynchronous driver, and the asynchronous driver is designed to respond to a write request of a corresponding process among the multiple processes, write the vehicle status data of the corresponding process in the corresponding process context into the flash memory, wherein the writing to the flash memory is performed by the asynchronous driver according to a first-in-first-out (FIFO) characteristic; wherein the processor is further designed to execute a synchronous driver, and the synchronous driver is designed to respond to a write request of a predetermined process among the multiple processes, stop the execution of the asynchronous driver on the processor, and write the vehicle status data of the predetermined process into the flash memory, wherein the asynchronous driver is stopped while saving the corresponding process context, and the asynchronous driver is written to the flash memory at the time of stopping under the process context, wherein the synchronous driver is further designed to reactivate the asynchronous driver after writing the vehicle status data of the predetermined process into the flash memory and restoring the saved process context.
[0009] The technical advantage is that the synchronous driver can ensure that the vehicle status data of the predetermined process is written to the flash memory in real time. The vehicle control device can thus implement the real-time requirements in a unit cost-neutral manner without additional external hardware components.
[0010] According to an exemplary embodiment of the vehicle control device, a predetermined process among the plurality of processes is a process designed to record an abnormal state of the vehicle particularly when the vehicle crashes or an undefined state occurs in the vehicle control device.
[0011] The technical advantage is that in abnormal situations, such as in an accident or vehicle collision, important information about the vehicle state can be recorded very quickly in the flash memory without having to first wait for processing of further ongoing data storage related to the normal vehicle state.
[0012] According to an exemplary embodiment of the vehicle control device, the flash memory is a vehicle fault memory which is designed to record data relating to a fault state of a corresponding vehicle control component.
[0013] The technical advantage is that by reading the vehicle fault memory, maintenance personnel can effectively learn about the faults that occurred during the vehicle's service life, and can use this information to determine which components in the vehicle are faulty and should be inspected or replaced.
[0014] According to an exemplary embodiment of the vehicle control device, the synchronous driver is designed to write vehicle status data of a predetermined process into the flash memory in real time.
[0015] The technical advantage is that important vehicle states can be stored permanently in real time. The distinction between important and less important can be predetermined by predetermining one or more processes to be run on the processor, for example processes involving a crash module or an exception module ("Exception" module). Only these predetermined processes are run by the synchronous driver and the information of the processes is recorded in real time.
[0016] According to an exemplary embodiment of the vehicle control device, the asynchronous driver is designed to sequentially process write requests of corresponding processes among a plurality of processes according to a first-in first-out (FIFO) characteristic without guaranteeing a predetermined processing time.
[0017] The technical advantage is therefore that all other processes that do not correspond to the predetermined process(es) can also have their vehicle status data recorded in the flash memory, but not in real time. Thus, the user can decide which processes are considered critical and are executed via the synchronous driver, while all other processes are executed via the asynchronous driver. However, the user should be aware that not all processes can be run via the synchronous driver. The number of predetermined processes that are run via the synchronous driver should be significantly smaller than the number of (non-scheduled) processes that are still run via the asynchronous driver.
[0018] According to an exemplary embodiment of the vehicle control device, the saving and restoring of the corresponding process context depends on the hardware design of the processor, in particular the design of specific hardware registers of the processor.
[0019] The technical advantage is therefore that, by saving and restoring the corresponding process context, the writing of information by two drivers that access the flash memory alternately does not lead to undefined states in the flash memory. Thus, the writing into the flash memory by the asynchronous driver can be effectively interrupted and then restored in the correct process context and memory context after the writing by the synchronous driver is completed. To write into the flash memory, specific hardware registers of the processor are required, which are placed in their original state again after the writing.
[0020] According to an exemplary embodiment of the vehicle control device, a predetermined process among the plurality of processes has a dedicated interface to the synchronization driver to transmit a write request of the predetermined process to the synchronization driver.
[0021] The technical advantage is that the vehicle status data to be written into the flash memory can be efficiently transmitted via a dedicated interface to the synchronous driver. The functionality of the asynchronous driver can be retained here, so no changes to this software module are required.
[0022] According to an exemplary embodiment of the vehicle control device, the synchronous driver and the asynchronous driver are designed to run on a processor according to the automotive open system architecture AUTOSAR.
[0023] The technical advantage is therefore that real-time requirements achieved by isochronous drivers can be implemented in a simple manner in the AUTOSAR architecture without requiring additional hardware for this purpose.
[0024] According to an exemplary embodiment of the vehicle control device, the synchronization driver is implemented on the processor in a complex device driver CDD software component according to the AUTOSAR architecture and accesses hardware registers of the processor.
[0025] The technical advantage is therefore that the synchronization driver can be programmed in a user-specific manner and can be connected directly to the flash memory via the hardware registers of the processor.
[0026] According to an exemplary embodiment of the vehicle control device, an asynchronous driver is implemented on a processor in a microcontroller abstraction layer MCAL software component according to the AUTOSAR architecture.
[0027] Therefore, the technical advantage is that the asynchronous driver and the synchronous driver can work together efficiently, and the interface for stopping or restarting the asynchronous driver can be easily implemented by the synchronous driver through the existing interface between the MCAL component and the CDD component of the AUTOSAR architecture.
[0028] According to an exemplary embodiment of the vehicle control device, the flash memory is designed to permanently store vehicle status data of the individual processes.
[0029] The technical advantage is therefore that the vehicle status data are fixed in the flash memory, so that, for example, maintenance personnel can still access the vehicle status data at the next scheduled maintenance.
[0030] According to an exemplary embodiment of the vehicle control device, the synchronous driving program is designed to execute the writing of the vehicle status data of a predetermined process into the flash memory within a time interval of a maximum of 10 ms.
[0031] Therefore, the technical advantage is that the real-time requirement, for example 10 ms as mentioned above, can be met by implementing a synchronous driver.
[0032] According to an exemplary embodiment of a vehicle control device, a predetermined process is associated with a vehicle collision module, wherein the predetermined process is designed to transmit a write request to a synchronization driver in response to a collision event, wherein the write request includes data of the collision event, and the synchronization driver is designed to record the data of the collision event in a flash memory.
[0033] The technical advantage is therefore that a collision can be detected using a synchronous driver and corresponding data about the collision event can be recorded, which is not possible using an asynchronous driver based on sequential recording of events.
[0034] According to the second aspect of the present invention, this technical problem is achieved by a method for controlling write requests of multiple processes executed on a processor of a vehicle control device, wherein each process is associated with a corresponding vehicle control component, and wherein the vehicle control device has a flash memory for storing vehicle status data of each individual process, wherein the method includes the following steps: in response to a write request of a corresponding process among the multiple processes to an asynchronous driver executed on the processor, the vehicle status data of the corresponding process is written to the flash memory in the corresponding process context by the asynchronous driver, wherein the writing to the flash memory is performed by the asynchronous driver according to a first-in-first-out (FIFO) characteristic; in response to a write request of a predetermined process among the multiple processes to a synchronous driver executed on the processor, the execution of the asynchronous driver is stopped by the synchronous driver and the vehicle status data of the predetermined process is written to the flash memory by the synchronous driver, wherein the asynchronous driver is stopped while saving the corresponding process context, and the asynchronous driver writes to the flash memory at the time of stopping under the process context; and after writing the vehicle status data of the predetermined process to the flash memory, the asynchronous driver is reactivated by the synchronous driver while restoring the saved process context.
[0035] The technical advantage is that the method can ensure that the vehicle status data of a predetermined process is written to the flash memory in real time by means of a synchronous driver. The method can therefore be executed on a vehicle control device which can implement the real-time requirements in a unit-cost-neutral manner without the need for additional external hardware components.
[0036] According to a third aspect of the invention, this object is achieved by a computer program with a program code for executing the method according to the second aspect on a vehicle control device according to the first aspect.
[0037] The technical advantage is therefore that a computer program can be easily executed on the vehicle control unit, which can implement real-time requirements in a unit-cost-neutral manner without requiring additional external hardware components. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] The present invention is described in detail below based on embodiments and drawings. The drawings are:
[0039] Figure 1 A schematic diagram of a vehicle control device 100 according to the present invention is shown;
[0040] Figure 2 A schematic diagram of an AUTOSAR architecture is shown, in which an asynchronous driver 120 and a synchronous driver 130 according to an embodiment are integrated; and
[0041] Figure 3 A schematic diagram of a method for controlling write requests of multiple processes to a flash memory according to the disclosure is shown. DETAILED DESCRIPTION
[0042] In the detailed description hereinafter, reference is made to the accompanying drawings which form a part of the description, and in which specific embodiments in which the present invention may be performed are shown by way of illustration. It should be understood that other embodiments may also be used and that structural or logical changes may be made without departing from the concept of the present invention. Therefore, the detailed description hereinafter should not be considered restrictive. In addition, it should be understood that unless otherwise specifically stated, the features of the different embodiments described herein may be combined with each other.
[0043] These aspects and embodiments are described with reference to the accompanying drawings, wherein the same reference numerals generally refer to the same elements. In the description hereinafter, for the purpose of explanation, many specific details are set forth to provide a detailed understanding of one or more aspects of the present invention. However, it is apparent to those of ordinary skill in the art that one or more aspects or embodiments can be put into practice with specific details to a lesser extent. In other cases, known structures and elements are illustrated in the form of schematic diagrams to describe one or more aspects or embodiments. It should be understood that other embodiments may be used and structural or logical changes may be made without departing from the concept of the present invention.
[0044] In the description that follows, reference is made to asynchronous drivers, synchronous drivers, processes, and process contexts.
[0045] A synchronous driver is a driver that guarantees synchronization, i.e., simultaneous execution. A synchronous driver such as that used in the present disclosure ensures that memory access is performed simultaneously in response to a write request or a write requirement. For this reason, the memory is accessed at the same time as the write request arrives at the synchronous driver. However, the delay in executing the driver and performing the memory access must be considered, so a certain delay must be added here.
[0046] An asynchronous driver is a driver that does not guarantee synchronization, i.e., simultaneous execution. An asynchronous driver such as that used in the present disclosure depends on the existence of other memory requests or write requests of other processes to ensure the sequential execution of memory access. Therefore, a certain amount of time may be required before memory access can be performed. This time depends on the entire system and cannot be defined in a nutshell. For example, the write requests of all processes are processed according to a first-in, first-out (FIFO) characteristic, i.e., the write request that arrives first is processed first and the write request that arrives last is processed last. The first-in, first-out (FIFO) characteristic can be implemented using a queue.
[0047] A process as described in this disclosure is a computer program at runtime. More specifically, a process is a specific instance of a program executing within a computer system, with the aid of more information and resources allocated by the operating system for that execution.
[0048] Processes are managed by the operating system's process scheduler, which can keep a process running until it finishes or blocks, or ensure that currently running processes are interrupted after a short period of time, and can switch back and forth between different active processes to create the impression of simultaneity, even though no more than one process is being processed at any given time.
[0049] The entire information that is important for the flow and management of a process is called the process context. To manage processes, the operating system must store information about them. The data for a process within the allocated address space is called the user context. The content of the CPU registers while the process is executing is known as the hardware context. This information must be stored if a process is interrupted by another process in a multitasking environment. The system context is the information about a process that the operating system stores from its perspective, such as the process number, files opened by the process, information about the parent or child process, priority, time taken, etc.
[0050] As described in this disclosure, flash memory is a maintenance-free energy-consuming digital memory module used for non-volatile storage.
[0051] Figure 1 A schematic diagram of a vehicle control device 100 according to the present invention is shown. The vehicle control device 100 comprises a processor 101 or a microcontroller and a flash memory 140 .
[0052] The processor 101 is designed to execute a plurality of processes 111 , 112 , 113 , 114 , wherein each process is associated with a corresponding vehicle control component.
[0053] The processor 101 is also designed to execute an asynchronous driver 120, which is designed to write 121 the vehicle state data of the corresponding process into the flash memory 140 in the corresponding process context in response to the write request 115 of the corresponding process among the multiple processes 111, 112, 113, 114. The writing 121 into the flash memory 140 is performed by the asynchronous driver 120 according to the first-in-first-out (FIFO) characteristic, that is, the writing 121 is performed sequentially. The write requests are processed according to the order in which they arrive.
[0054] The processor 101 is further designed to execute a synchronous driver 130, which is designed to stop 131 the execution of the asynchronous driver 120 on the processor 101 in response to a write request 116 of a predetermined process 114 of the plurality of processes 111, 112, 113, 114, and write 132 the vehicle status data of the predetermined process 114 into the flash memory 140. When the asynchronous driver 120 is stopped 131, the corresponding process context is saved, under which the asynchronous driver 120 writes 121 into the flash memory 140 at the moment of the stop 131.
[0055] The synchronous driver 130 is also designed to reactivate the asynchronous driver 120 upon restoring the saved process context after writing 132 the vehicle state data of the predetermined process 114 into the flash memory 140 .
[0056] The predetermined process 114 among the plurality of processes 111 , 112 , 113 , 114 may be a process designed to record an abnormal state of the vehicle, for example, when the vehicle collides or when an undefined state occurs in the vehicle control device 100 .
[0057] The flash memory 140 may be a vehicle fault memory designed to record data related to a fault status of a corresponding vehicle control component.
[0058] The synchronous driver 130 may be designed to write 132 the vehicle status data of the predetermined process 114 into the flash memory 140 in real time.
[0059] The asynchronous driver 120 may be designed to sequentially process the write requests 115 of corresponding processes among the plurality of processes 111 , 112 , 113 , 114 according to a first-in, first-out characteristic without guaranteeing a predetermined processing time.
[0060] The saving and restoring of the corresponding process context may depend on the hardware design of the processor 101 , for example, on the design of a specific hardware register of the processor 101 .
[0061] A predetermined process 114 among the plurality of processes 111 , 112 , 113 , 114 may have a dedicated interface to the synchronization driver 130 to transmit a write request 116 of the predetermined process 114 to the synchronization driver 130 .
[0062] The synchronous driver 130 and the asynchronous driver 120 may be executed on the processor 101 according to the automotive open system architecture AUTOSAR 200, as described below with respect to Figure 2 Describe in more detail.
[0063] For example, the synchronization driver 130 may be implemented on the processor 101 in a complex device driver CDD software component 240 according to the AUTOSAR architecture 200 and access hardware registers of the processor 101 .
[0064] The asynchronous driver 120 may be implemented on the processor 101 in a microcontroller abstraction layer MCAL software component according to the AUTOSAR architecture 200 .
[0065] The flash memory 140 may be designed to permanently store the vehicle status data of the individual processes 111 , 112 , 113 , 114 .
[0066] The synchronous driver 130 may be designed to execute the writing 132 of the vehicle status data of the predetermined process 114 into the flash memory 140 within a time interval of up to 10 ms.
[0067] For example, the predetermined process 114 may be associated with a vehicle crash module and is designed to transmit a write request 116 to the synchronization driver 130 in response to a crash event. Here, the write request 116 may include data of the crash event. The synchronization driver 130 may be designed to record the data of the crash event in the flash memory 140.
[0068] Figure 2 2 shows a schematic diagram of an AUTOSAR architecture 200, in which an asynchronous driver 120 and a synchronous driver 130 according to an embodiment are integrated. The implementation of the asynchronous driver 120 and the synchronous driver 130 is as described above according to Figure 1 described.
[0069] The AUTOSAR architecture 200 includes complete basic software for control devices as an integrated platform for hardware-independent software applications. AUTOSAR provides an exchange format or description template for a seamless configuration process of the basic software and the integration of application software on the control device. AUTOSAR also provides interface specifications for syntax and semantics for typical automotive applications in all fields, which should be used as a standard for application software.
[0070] The AUTOSAR architecture 200 includes a hardware-independent application layer application 210 , a real-time environment RTE (“Real Time Environment”) 220 , an operating system Os 230 , a CDD (“Complex Device Driver”) layer 240 , a basic software (BSW) layer 250 , and a microcontroller abstraction layer (MCAL) 260 .
[0071] RTE 220 is a middleware layer and provides communication services for application software 210. Application software 210 communicate with each other or with services via RTE 220. The advantage of this software 220 is that functions can be grouped and relocated to other ECUs (“Electric Control Units”). In addition, functions can also be encapsulated via RTE 220 to thereby make them independent of communication technology.
[0072] The operating system AUTOSAR-OS 230 implements real-time behavior and time monitoring as well as runtime safety mechanisms. AUTOSAR-OS 230 can be extended depending on the intended use.
[0073] The role of the MCAL layer 260 is to make the application program based on the application layer 210 of the MCAL layer 260 independent of the microcontroller and thus usable on many different microcontrollers.
[0074] The CDD layer 240 is used to implement complex sensor evaluation and actuator control by using specific interrupts and / or complex microcontroller peripherals as well as external devices - such as communication transceivers or ASICs - to directly access the microcontroller to meet special functional and timing requirements. In addition, the CDD layer 240 is used to implement extended services or protocols or to encapsulate legacy functions for non-AUTOSAR systems. The synchronization driver ("DirectFI") 130 is implemented as a component of the CDD layer 240.
[0075] The basic software 250 provides the functions of the ECU (Electric Control Unit). Hardware access is performed through this layer. AUTOSAR defines a software architecture for control devices, which separates the software from the hardware of the device. AUTOSAR defines a highly automated configuration process for the software, which consists of individual functional modules, software components, and the software can be developed independently of each other and by different manufacturers, and the configuration process connects the software components into a specific project.
[0076] The MCAL layer 260 allows access to the microcontroller. Access is made through standardized interfaces. As a result, the upper modules are independent of the corresponding controller. The MCAL layer 260 allows basic microcontroller functions, such as initialization of the clock generator and CPU operating mode, control of the memory bus, interrupts, watchdog timer (WDT) and timer modules. The MCAL layer 260 also implements the basic configuration of all microcontroller connections (PORT), digital input / output (DIO), input capture unit (ICU), pulse width modulation signal output (PWM) and analog-to-digital converter (ADC), and control of internal and external flash ROM and EEPROM modules. The MCAL layer 260 also provides drivers for internal and external SPI controllers, CAN controllers, LIN controllers and FlexRay controllers. The asynchronous driver (Fis) 120 is implemented in the MCAL layer 260.
[0077] As described above, the sync driver ("DirectFl") 130 is implemented as a component of the CDD layer 240. Because one of the basic tasks of the driver 130 is to save and restore the hardware context, the software must be adapted for each platform. Currently PowerPC and Tricore are supported. The sync driver 130 can be used for functions such as "save crash event" and "save exception", which deal with the storage of vehicle status data in accident situations or abnormal situations.
[0078] The interface for writing data can be implemented as follows, for example:
[0079] Std_ReturnType DirectFls_Write(const uint32 u32TargetAddress,constuint8*pu8SourceAddressPtr,const uint8 u8Length);
[0080] Thus, a value of length u8Length (eg, 8 bits) at the address indicated by pointer pu8SourceAddressPtr may be written to the address u32TargetAddress in the flash memory.
[0081] Figure 3 A schematic diagram of a method for controlling write requests of multiple processes onto a flash memory according to the present disclosure is shown.
[0082] The method 300 is used to control write requests of multiple processes executed on a processor of a vehicle control device, as described above with respect to Figure 1 Each process is associated with a corresponding vehicle control component. The vehicle control device has a flash memory for storing vehicle status data for each individual process, as described above with respect to Figure 1 described.
[0083] The method 300 includes the following four steps:
[0084] In response to a write request from a corresponding process among multiple processes to an asynchronous driver executed on a processor, the vehicle status data of the corresponding process in the corresponding process context is written 301 into a flash memory through the asynchronous driver, wherein the writing into the flash memory is performed by the asynchronous driver according to a first-in, first-out (FIFO) characteristic.
[0085] In response to a write request from a predetermined process of the plurality of processes to a synchronous driver executing on the processor, stopping 302 execution of the asynchronous driver by the synchronous driver, and
[0086] The vehicle status data of a predetermined process are written 303 into the flash memory by the synchronous driver, wherein the corresponding process context is saved when the asynchronous driver stops, under which the asynchronous driver writes into the flash memory at the time of the stop.
[0087] After the vehicle status data of the predetermined process have been written into the flash memory, the asynchronous driver is reactivated 304 by the synchronous driver while restoring the saved process context.
[0088] These four steps correspond to the functionality of the vehicle control device 100, as described above with respect to Figure 1 The method 300 may be used in the vehicle control device 100 .
[0089] Furthermore, a computer program with a program code for executing the method 300 on the vehicle control device 100 may be provided, as described above with respect to Figure 1 described.
[0090] Reference numerals list
[0091] 100 Vehicle Control Devices
[0092] 101 Processor
[0093] 111 Process
[0094] 112 Process
[0095] 113 Process
[0096] 114 Scheduled processes, such as collisions
[0097] 120 Asynchronous Driver
[0098] 130 Synchronous Driver
[0099] 140 Flash memory
[0100] 115 Process write request
[0101] 116 Write request of scheduled process
[0102] 121 Asynchronous driver writes to flash memory
[0103] 132 Synchronous driver writes to flash memory
[0104] 131 Synchronous driver control instructions (stop, activate)
[0105] 200 AUTOSAR Architecture
[0106] 210 Application Layer
[0107] 220 RTE (Real Time Environment)
[0108] 230 OS, operating system
[0109] 240 CDD (Complex Device Driver) software component
[0110] 250 BSW (Basic Software Module) software components
[0111] 260 MCAL (Microcontroller Abstraction Layer) software component
[0112] 300 Method for controlling multiple processes on a vehicle control device
[0113] 301 Write via asynchronous driver
[0114] 302 Stopping an asynchronous driver via a synchronous driver
[0115] 303 Write via synchronous driver
[0116] 304 Reactivate asynchronous driver via synchronous driver
Claims
1. A vehicle control device (100) having a processor (101) and a flash memory (140), wherein the processor (101) is designed to execute a plurality of processes (111, 112, 113, 114), in, Each process is associated with a corresponding vehicle control component; The processor (101) is designed to execute an asynchronous driver (120), and the asynchronous driver (120) is designed to write vehicle status data of a corresponding process in a corresponding process context into the flash memory (140) in response to a write request of a corresponding process of a plurality of processes (111, 112, 113, 114), wherein the writing into the flash memory (140) is performed by the asynchronous driver (120) according to a first-in-first-out characteristic; The processor (101) is further designed to execute a synchronous driver (130), and the synchronous driver (130) is designed to stop the execution of the asynchronous driver (120) on the processor (101) in response to a write request of a predetermined process (114) of a plurality of processes (111, 112, 113, 114), and write the vehicle status data of the predetermined process (114) into the flash memory (140), wherein the corresponding process context is saved when the asynchronous driver (120) is stopped, and the asynchronous driver (120) is written into the flash memory (140) under the process context at the time of stopping, The synchronous driver (130) is further designed to reactivate the asynchronous driver (120) by restoring the saved process context after writing the vehicle status data of the predetermined process (114) into the flash memory (140).
2. The vehicle control device (100) according to claim 1, wherein a predetermined process (114) of the plurality of processes (111, 112, 113, 114) is a process designed to record an abnormal state of the vehicle, in particular when the vehicle collides or when an undefined state occurs in the vehicle control device (100).
3. The vehicle control device (100) according to claim 1 or 2, in, The flash memory (140) is a vehicle fault memory designed to record data about the fault state of a corresponding vehicle control component.
4. The vehicle control device (100) according to claim 1 or 2, in, The synchronous driving program (130) is designed to write the vehicle status data of the predetermined process (114) into the flash memory (140) in real time.
5. The vehicle control device (100) according to claim 1 or 2, in, The asynchronous driver (120) is designed to process write requests of corresponding processes of a plurality of processes (111, 112, 113, 114) in sequence according to a first-in first-out characteristic without guaranteeing a predetermined processing time.
6. The vehicle control device (100) according to claim 1 or 2, in, The saving and restoring of the corresponding process context depends on the hardware design of the processor (101), in particular, on the design of the specific hardware registers of the processor (101).
7. The vehicle control device (100) according to claim 1 or 2, in, A predetermined process (114) of the plurality of processes (111, 112, 113, 114) has a dedicated interface to the synchronization driver (130) to transmit a write request of the predetermined process (114) to the synchronization driver (130).
8. The vehicle control device (100) according to claim 1, in, The synchronous driver (130) and the asynchronous driver (120) are designed to run on the processor (101) according to the automotive open system AUTOSAR architecture (200).
9. The vehicle control device (100) according to claim 8, in, The synchronous driver (130) is implemented on the processor (101) in a complex device driver CDD software component (240) according to the AUTOSAR architecture (200) and accesses hardware registers of the processor (101).
10. The vehicle control device (100) according to claim 8 or 9, in, The asynchronous driver (120) is implemented on the processor (101) in a microcontroller abstraction layer MCAL software component (260) according to the AUTOSAR architecture (200).
11. The vehicle control device (100) according to claim 1 or 2, in, The flash memory (140) is designed to permanently store vehicle status data of the individual processes (111, 112, 113, 114).
12. The vehicle control device (100) according to claim 1 or 2, in, The synchronous driver (130) is designed to execute the writing of the vehicle status data of the predetermined process (114) into the flash memory (140) within a time interval of 10 ms at the longest.
13. The vehicle control device (100) according to claim 1 or 2, in, The predetermined process (114) is associated with a vehicle crash module, wherein the predetermined process (114) is designed to transmit the write request to the synchronization driver (130) in response to a crash event, wherein the write request includes data of the crash event, The synchronous driving program (130) is designed to record data of the collision event in the flash memory (140).
14. A method (300) for controlling write requests of a plurality of processes executed on a processor of a vehicle control device, in, Each process is associated with a corresponding vehicle control component, and the vehicle control device has a flash memory for storing vehicle status data of each individual process, wherein the method (300) comprises the following steps: In response to a write request from a corresponding process among a plurality of processes to an asynchronous driver executed on the processor, vehicle status data of the corresponding process in a corresponding process context is written (301) into a flash memory through the asynchronous driver, wherein the writing into the flash memory is performed by the asynchronous driver according to a first-in-first-out characteristic; In response to a write request from a predetermined process among a plurality of processes to a synchronous driver executed on the processor, the execution of the asynchronous driver is stopped (302) by the synchronous driver, and vehicle status data of the predetermined process is written (303) into the flash memory by the synchronous driver, wherein a corresponding process context is saved when the asynchronous driver is stopped, and the asynchronous driver is written into the flash memory under the process context at the time of stopping; and After the vehicle status data of the predetermined process have been written into the flash memory, the asynchronous driver is reactivated ( 304 ) by the synchronous driver while restoring the saved process context.
Citation Information
Patent Citations
Async. motor control for electric vehicle transmission - includes rectifier and oscillator between diesel driven alternator and async. motor
FR2448809A1
Network converting device between media oriented systems transports (MOST) for vehicle
KR1020110076161A
Vehicle data recorder
US20100070129A1
Motor control apparatus, motor drive system, and motor control method
US20190144028A1
