Vehicle chassis power domain controller reset control method and device and vehicle
By classifying reset faults in the vehicle chassis power domain controller and executing differentiated initialization procedures, the problem of excessively long initialization time after a reset fault is solved, thereby improving vehicle safety and reliability.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CONTEMPORARY AMPEREX INTELLIGENCE TECHNOLOGY (SHANGHAI) LTD
- Filing Date
- 2024-10-30
- Publication Date
- 2026-05-01
AI Technical Summary
The vehicle chassis power domain controller takes a long time to initialize after resetting a fault, which increases the risk of safety accidents during high-speed driving.
By classifying the reset faults of the vehicle chassis power domain controller, a differentiated initialization process is adopted to perform corresponding initialization operations for different types of faults, including first reset faults and second reset faults, each corresponding to a different initialization process.
It effectively reduces the initialization time of the vehicle chassis power domain controller, reduces the safety risks caused by reset failures, and improves the safety and reliability of the vehicle.
Smart Images
Figure CN121947534A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle control technology, and more specifically, to a vehicle chassis power domain controller reset control method, device, and vehicle. Background Technology
[0002] In related technologies, when a vehicle chassis power domain controller experiences a reset fault, it will execute the same reset and initialization process. After the reset, it will initialize all registers, running programs, hardware, etc. of the controller, resulting in a long initialization time (e.g., about 500ms). If the vehicle is traveling at high speed, the excessively long initialization time will increase the risk of safety accidents. Summary of the Invention
[0003] This application proposes a vehicle chassis power domain controller reset control method, device, and vehicle to solve the problems of long reset and initialization processes in related technologies, which can easily lead to safety accidents.
[0004] In a first aspect, this application provides a method for resetting a vehicle chassis power domain controller, the method comprising:
[0005] The vehicle chassis power domain controller was found to have experienced a first reset fault.
[0006] The first reset procedure is executed to initialize the running program and hardware corresponding to the first reset fault.
[0007] The reset control method provided in this application, after determining that the vehicle chassis power domain controller has a first reset fault, executes a first reset procedure to initialize the running program and hardware corresponding to the first reset fault. This can effectively reduce the initialization time after the vehicle chassis power domain controller has a first reset fault and is reset, reduce the safety risk after the vehicle chassis power domain controller has a reset fault, and improve the safety and reliability of the vehicle.
[0008] According to one embodiment of this application, determining that the vehicle chassis power domain controller has experienced a first reset fault includes:
[0009] Read the soft reset flag from memory;
[0010] If the soft reset flag is valid, it is determined that the vehicle chassis power domain controller has experienced a first reset fault.
[0011] In the above technical solution, the fault type of the vehicle chassis power domain controller can be determined by reading the soft reset flag in the memory. Different solutions can be adopted according to different reset fault types, and differentiated initialization processes can be executed. This can effectively reduce the initialization time of the vehicle chassis power domain controller caused by some reset faults, thereby improving the safety and reliability of the vehicle.
[0012] According to one embodiment of this application, the method further includes:
[0013] After the vehicle chassis power domain controller is initialized, a reset fault detection is performed on the vehicle chassis power domain controller.
[0014] If a reset fault is detected in the vehicle chassis power domain controller, the type of the reset fault is determined;
[0015] The soft reset flag is processed according to the type of reset fault.
[0016] In the above technical solution, by detecting reset faults in the vehicle chassis power domain controller, and processing the soft reset flag according to the type of reset fault, the reset faults of the vehicle chassis power domain controller can be classified, which facilitates the subsequent execution of differentiated initialization processes. This effectively reduces the initialization time of the vehicle chassis power domain controller caused by some reset faults, thereby improving the safety and reliability of the vehicle.
[0017] According to one embodiment of this application, determining the type of reset fault when a reset fault is detected in the vehicle chassis power domain controller includes:
[0018] If the output level of each functional module of the vehicle chassis power domain controller does not meet the preset requirements or cannot receive the level, it is determined that the vehicle chassis power domain controller has a reset fault.
[0019] Obtain the fault code corresponding to the reset fault, and determine the type of the reset fault based on the fault code.
[0020] In the above technical solution, when the output level of each functional module does not meet the preset requirements or the level cannot be received, it is determined that the vehicle chassis power domain controller has a reset fault. By obtaining the fault code corresponding to the reset fault, the type of reset fault can be determined. The vehicle chassis power domain controller can be detected and the type of reset fault can be determined in a timely manner. A differentiated initialization process can be executed, which can effectively reduce the initialization time of the vehicle chassis power domain controller caused by some reset faults, and improve the safety and reliability of the vehicle.
[0021] According to one embodiment of this application, processing the soft reset flag based on the type of the reset fault includes:
[0022] In the case that the type of reset fault is a first reset fault, the soft reset flag in the memory is set to valid;
[0023] In the case that the type of reset fault is a second reset fault, the soft reset flag in the memory is set to invalid.
[0024] In the above technical solution, the soft reset flag in the memory is set to valid or invalid according to the type of reset fault, which is either the first reset fault or the second reset fault. This allows the reset faults of the vehicle chassis power domain controller to be classified, which facilitates the subsequent execution of differentiated initialization processes.
[0025] According to one embodiment of this application, the method further includes:
[0026] If the soft reset flag is invalid, it is determined that a second reset fault has occurred in the vehicle chassis power domain controller;
[0027] A second reset procedure is executed to initialize all operating programs and hardware of the vehicle chassis power domain controller.
[0028] In the above technical solution, when the soft reset flag is invalid, it is determined that the vehicle chassis power domain controller has a second reset fault. The second reset process is executed to initialize all the operating programs and hardware of the vehicle chassis power domain controller, thereby reducing potential risks and improving the safety and reliability of the vehicle.
[0029] According to one embodiment of this application, the first reset fault includes at least one of the following: MCU bus communication fault, MCU memory management unit fault, operating system running error, and watchdog program flow monitoring abnormality.
[0030] The second reset fault is any reset fault other than the first reset fault.
[0031] In the above technical solution, the reset faults of the vehicle chassis power domain controller are classified into first reset faults and second reset faults. Different solutions can be adopted according to different reset fault types, and differentiated initialization processes can be executed. This can effectively reduce the initialization time of the vehicle chassis power domain controller caused by some reset faults, thereby improving the safety and reliability of the vehicle.
[0032] According to one embodiment of this application, the method further includes:
[0033] After the first or second reset procedure is completed, a reset fault detection is performed on the vehicle chassis power domain controller.
[0034] In the above technical solution, the reset faults of the vehicle chassis power domain controller are classified into first reset faults and second reset faults. After determining that the vehicle chassis power domain controller has a first reset fault, the first reset procedure is executed to initialize the corresponding running program and hardware. Different solutions can be adopted according to different reset fault types, and differentiated initialization procedures can be executed. After the first or second reset procedure is completed, the vehicle chassis power domain controller is detected for reset faults in real time. Potential faults can be detected in a timely manner, which can effectively reduce the initialization time after the vehicle chassis power domain controller has a first reset fault and is reset, reduce the safety risks after the vehicle chassis power domain controller has a reset fault, and improve the safety and reliability of the vehicle.
[0035] Secondly, this application provides a vehicle chassis power domain controller reset control device, the device comprising:
[0036] The fault determination unit is used to determine if a first reset fault has occurred in the vehicle chassis power domain controller.
[0037] The execution unit is used to execute the first reset procedure to initialize the running program and hardware corresponding to the first reset fault.
[0038] In the above technical solution, after determining that the vehicle chassis power domain controller has a first reset fault, the first reset procedure is executed to initialize the running program and hardware corresponding to the first reset fault. This can effectively reduce the initialization time after the vehicle chassis power domain controller has a first reset fault and is reset, reduce the safety risk after the vehicle chassis power domain controller has a reset fault, and improve the safety and reliability of the vehicle.
[0039] Thirdly, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle chassis power domain controller reset control method as described in the first aspect above.
[0040] Fourthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle chassis power domain controller reset control method as described in the first aspect above.
[0041] Fifthly, this application provides a vehicle, including: a vehicle chassis power domain controller, the vehicle chassis power domain controller including a vehicle chassis power domain controller reset control device as described in the second aspect above.
[0042] In a sixth aspect, this application provides a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the vehicle chassis power domain controller reset control method as described in the first aspect.
[0043] In a seventh aspect, this application provides a computer program product, including a computer program that, when executed by a processor, implements the vehicle chassis power domain controller reset control method as described in the first aspect above.
[0044] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description
[0045] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0046] Figure 1 This is one of the flowcharts illustrating a vehicle chassis power domain controller reset control method provided in some embodiments of this application;
[0047] Figure 2 This is a second schematic flowchart illustrating the vehicle chassis power domain controller reset control method provided in some embodiments of this application.
[0048] Figure 3 Schematic diagram of the structure of the vehicle chassis power domain controller reset control device provided in some embodiments of this application;
[0049] Figure 4 The diagram shows the structure of an electronic device provided in some embodiments of this application. Detailed Implementation
[0050] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0051] Unless otherwise defined, all technical and scientific terms used in this application have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used in the description of this application is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms "comprising" and "having," and any variations thereof, in the description, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the description, claims, or accompanying drawings of this application are used to distinguish different objects, not to describe a specific order or hierarchy.
[0052] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.
[0053] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.
[0054] In this application, "multiple" refers to two or more (including two), and similarly, "multiple groups" refers to two or more (including two), and "multiple pieces" refers to two or more (including two).
[0055] The vehicle chassis power domain controller reset control method provided in this application embodiment can be executed by an electronic device or a functional module or functional entity in an electronic device that can implement the vehicle chassis power domain controller reset control method. The electronic device mentioned in this application embodiment includes, but is not limited to, the vehicle chassis power domain controller.
[0056] In modern automotive electronic control systems, the Chassis Domain Controller (CDC) is a component responsible for managing and coordinating the power output and performance of various parts of the vehicle chassis. By receiving and processing signals from other parts of the vehicle, it controls the engine, transmission, suspension system, and other components to ensure vehicle stability and safety. It coordinates and manages the various power systems of the vehicle chassis, ensuring stability and safety under various driving conditions. However, when this critical component experiences a reset failure, the performance of the entire vehicle may be affected. In such cases, the Chassis Domain Controller automatically triggers a series of preset reset and initialization procedures to ensure the system can resume normal operation.
[0057] In related technologies, when a vehicle chassis power domain controller experiences a reset fault, the controller immediately initiates a reset process, which includes resetting all internal registers, stopping the currently running program, and checking and configuring the hardware devices so that the controller can restart in the best condition after the reset. However, the initialization process takes a relatively long time, approximately 500 milliseconds.
[0058] For example, when a vehicle is speeding on a highway at 100 kilometers per hour, if the chassis power domain controller suddenly resets and begins the initialization process, the driver may lose control of some key functions of the vehicle for a short period of time. The vehicle's stability control system, traction control system, and braking system may temporarily fail, increasing the possibility of safety accidents.
[0059] To address the aforementioned problems, embodiments of this application provide a vehicle chassis power domain controller reset control method. The following, in conjunction with the accompanying drawings, provides a detailed description of the vehicle chassis power domain controller reset control method, device, and vehicle provided in this application through specific embodiments and application scenarios.
[0060] Figure 1 This is one of the flowcharts illustrating the vehicle chassis power domain controller reset control method provided in some embodiments of this application, such as... Figure 1 As shown, the vehicle chassis power domain controller reset control method includes steps 110 and 120.
[0061] Step 110: Determine that the vehicle chassis power domain controller has experienced a first reset fault;
[0062] It should be noted that the vehicle chassis dynamics domain controller is an integrated electronic control unit in the automotive electronic architecture, used to manage various functions related to the vehicle chassis, such as integrated control, data processing, and stability control. The integrated control includes brake control, suspension adjustment, and powertrain control.
[0063] In one embodiment of this application, the first reset fault includes at least one of the following: MCU bus communication failure, MCU memory management unit failure, operating system runtime error, and watchdog program flow monitoring abnormality;
[0064] The second reset fault is any reset fault other than the first reset fault.
[0065] It is easy to understand that during the driving process, the vehicle chassis power domain controller may experience a first reset fault and a second reset fault. The first reset fault includes at least one of the following: microcontroller unit (MCU) bus communication failure, MCU memory management unit failure, operating system running error, and watchdog program flow monitoring abnormality. The first reset fault can also be called a soft reset fault.
[0066] MCU bus communication failures refer to various faults and errors that occur when data is transmitted between a microcontroller and other devices via a bus, such as signal interference, data loss or errors, poor connections, and bus conflicts.
[0067] MCU memory management unit failures refer to various faults and errors that occur during the reading, writing, or management of memory, such as data corruption, memory access conflicts, address decoding errors, memory read / write failures, and buffer overflows.
[0068] Operating system errors refer to faults and errors that occur during the operation of a computer's operating system, such as operating system crashes, boot failures, file system errors, driver errors, and permission errors.
[0069] Watchdog program flow monitoring anomalies refer to software or hardware failures that cause the system to fail to execute program flows as expected, such as system crashes, slow responses, deadlocks, and error logs. Watchdogs are monitoring tools that can be used in embedded and real-time systems.
[0070] It is worth noting that the first reset fault can be one or multiple. For example, the first reset fault may be an MCU memory management unit fault, or an operating system runtime error and a watchdog timer flow monitoring anomaly.
[0071] The second reset fault refers to any reset fault other than the first reset fault, such as power management chip failure, electrically erasable programmable read-only memory (EEPROM) failure, and processor failure. The second reset fault can be called a hard reset fault.
[0072] Power management integrated circuit (PMIC) failure refers to abnormal situations that occur in the process of controlling and managing the power supply of equipment by the power management integrated circuit, such as unstable power output, overvoltage or undervoltage, thermal runaway and current overload.
[0073] EEPROM faults refer to abnormal situations in the data storage, reading, or programming process of electrically erasable programmable read-only memory, such as data loss, read errors, write failures, and startup failures.
[0074] In the above technical solution, the reset faults of the vehicle chassis power domain controller are classified into first reset faults and second reset faults. Different solutions can be adopted according to different reset fault types, and differentiated initialization processes can be executed. This can effectively reduce the initialization time of the vehicle chassis power domain controller caused by some reset faults, thereby improving the safety and reliability of the vehicle.
[0075] It should be noted that fault detection can be used to determine whether the vehicle chassis power domain controller has experienced a first reset fault.
[0076] Step 120: Execute the first reset procedure to initialize the running program and hardware corresponding to the first reset fault.
[0077] Furthermore, after determining that the vehicle chassis power domain controller has a first reset fault, the first reset procedure is executed to initialize the running program and hardware corresponding to the first reset fault, while the running program and hardware unrelated to the first reset fault are not processed.
[0078] For example, the first reset fault is an MCU storage management unit fault. After determining that the vehicle chassis power domain controller has an MCU storage management unit fault, the first reset process is executed to initialize the running program and hardware corresponding to the MCU storage management unit fault (initialization time is, for example, 100 milliseconds). Running programs and hardware unrelated to the MCU storage management unit fault are not processed.
[0079] The reset control method provided in this application, after determining that the vehicle chassis power domain controller has a first reset fault, executes a first reset procedure to initialize the running program and hardware corresponding to the first reset fault. This can effectively reduce the initialization time after the vehicle chassis power domain controller has a first reset fault and is reset, reduce the safety risk after the vehicle chassis power domain controller has a reset fault, and improve the safety and reliability of the vehicle.
[0080] In one embodiment of this application, the method further includes:
[0081] After the vehicle chassis power domain controller is initialized, a reset fault detection is performed on the vehicle chassis power domain controller.
[0082] If a reset fault is detected in the vehicle chassis power domain controller, the type of the reset fault is determined;
[0083] The soft reset flag is processed according to the type of reset fault.
[0084] It is easy to understand that after the vehicle chassis power domain controller is initialized, a reset fault detection is performed on the vehicle chassis power domain controller in real time to detect whether a reset fault has occurred. If a reset fault is detected in the vehicle chassis power domain controller, the type of reset fault is determined.
[0085] In one embodiment of this application, determining the type of reset fault when a reset fault is detected in the vehicle chassis power domain controller includes:
[0086] If the output level of each functional module of the vehicle chassis power domain controller does not meet the preset requirements or cannot receive the level, it is determined that the vehicle chassis power domain controller has a reset fault.
[0087] Obtain the fault code corresponding to the reset fault, and determine the type of the reset fault based on the fault code.
[0088] Optionally, the vehicle chassis power domain controller monitors the output level of each functional module in real time. If the output level of each functional module's receiver does not meet the preset requirements, it is determined that the vehicle chassis power domain controller has a reset fault, the fault code corresponding to the reset fault is obtained, and the type of reset fault is determined based on the fault code.
[0089] Optionally, if the vehicle chassis power domain controller cannot receive the output level of each functional module receiver, it is determined that the vehicle chassis power domain controller has a reset fault, the fault code corresponding to the reset fault is obtained, and the type of reset fault is determined based on the fault code.
[0090] In the above technical solution, when the output level of each functional module does not meet the preset requirements or the level cannot be received, it is determined that the vehicle chassis power domain controller has a reset fault. By obtaining the fault code corresponding to the reset fault, the type of reset fault can be determined. The vehicle chassis power domain controller can be detected and the type of reset fault can be determined in a timely manner. A differentiated initialization process can be executed, which can effectively reduce the initialization time of the vehicle chassis power domain controller caused by some reset faults, and improve the safety and reliability of the vehicle.
[0091] In one embodiment of this application, processing the soft reset flag according to the type of the reset fault includes:
[0092] In the case that the type of reset fault is a first reset fault, the soft reset flag in the memory is set to valid;
[0093] In the case that the type of reset fault is a second reset fault, the soft reset flag in the memory is set to invalid.
[0094] Furthermore, the soft reset flag can be processed according to the type of reset fault. For example, if the type of reset fault is the first reset fault, which is a software fault, it can also be called a soft reset fault. In this case, the soft reset flag in the memory is set to valid to indicate the first reset fault.
[0095] When the type of reset fault is a second reset fault, it belongs to a fault other than software-related faults and can also be called a hard reset fault. In this case, the soft reset flag in the memory is set to invalid, indicating a second reset fault.
[0096] Optionally, the memory can be EEPROM, EPROM (Erasable Programmable Read-Only Memory), and PROM (Programmable Read-Only Memory), etc.
[0097] In the above technical solution, the reset faults of the vehicle chassis power domain controller can be divided according to whether the reset fault is the first reset fault or the second reset fault. This allows the soft reset flag in the memory to be set to valid or invalid, facilitating the subsequent execution of differentiated initialization procedures.
[0098] In the above technical solution, by detecting reset faults in the vehicle chassis power domain controller, and processing the soft reset flag according to the type of reset fault, the reset faults of the vehicle chassis power domain controller can be classified, which facilitates the subsequent execution of differentiated initialization processes. This effectively reduces the initialization time of the vehicle chassis power domain controller caused by some reset faults, thereby improving the safety and reliability of the vehicle.
[0099] In one embodiment of this application, determining that the vehicle chassis power domain controller has experienced a first reset fault includes:
[0100] Read the soft reset flag from memory;
[0101] If the soft reset flag is valid, it is determined that the vehicle chassis power domain controller has experienced a first reset fault.
[0102] It is easy to understand that when a fault is detected in the vehicle chassis power domain controller, the soft reset flag in the memory is read. If the soft reset flag is valid, it is determined that the vehicle chassis power domain controller has a first reset fault. The first reset procedure is executed to initialize the running program and hardware corresponding to the first reset fault. Running programs and hardware unrelated to the first reset fault are not processed.
[0103] In the above technical solution, the fault type of the vehicle chassis power domain controller can be determined by reading the soft reset flag in the memory. Different solutions can be adopted according to different reset fault types, and differentiated initialization processes can be executed. This can effectively reduce the initialization time of the vehicle chassis power domain controller caused by some reset faults, thereby improving the safety and reliability of the vehicle.
[0104] In one embodiment of this application, the method further includes:
[0105] If the soft reset flag is invalid, it is determined that a second reset fault has occurred in the vehicle chassis power domain controller;
[0106] A second reset procedure is executed to initialize all operating programs and hardware of the vehicle chassis power domain controller.
[0107] It is easy to understand that if the soft reset flag is invalid, it is determined that the vehicle chassis power domain controller has a second reset fault, and the second reset procedure is executed to initialize all the running programs and hardware of the vehicle chassis power domain controller.
[0108] For example, the second reset fault is a power management chip fault. After determining that the power management chip of the vehicle chassis power domain controller has a fault, the second reset procedure is executed to initialize all running programs and hardware of the vehicle chassis power domain controller (initialization time is, for example, 300 milliseconds).
[0109] In the above technical solution, when the soft reset flag is invalid, it is determined that the vehicle chassis power domain controller has a second reset fault. The second reset process is executed to initialize all the operating programs and hardware of the vehicle chassis power domain controller, thereby reducing potential risks and improving the safety and reliability of the vehicle.
[0110] In one embodiment of this application, the method further includes:
[0111] After the first or second reset procedure is completed, a reset fault detection is performed on the vehicle chassis power domain controller.
[0112] It is easy to understand that after the first or second reset process is completed, real-time reset fault detection of the vehicle chassis power domain controller can promptly identify potential faults.
[0113] Figure 2 This is the second schematic flowchart of a vehicle chassis power domain controller reset control method provided in some embodiments of this application, as shown below. Figure 2 As shown, the vehicle chassis power domain controller reset control method includes steps 210, 215, 220, 225, 230, 235, 240, 245, 250, 255 and 260.
[0114] Step 210: Restart the vehicle chassis power domain controller;
[0115] Step 215: Execute the initialization function;
[0116] Step 220: Read the soft reset flag from the memory;
[0117] Step 225: Determine if the soft reset flag is valid;
[0118] Step 230: If the soft reset flag is valid, execute the first reset procedure;
[0119] Step 235: If the soft reset flag is invalid, execute the second reset procedure;
[0120] Step 240: Initialization complete;
[0121] Step 245: Perform fault detection to determine if there is a reset fault;
[0122] Step 250: Determine the type of reset fault and whether a first reset fault has occurred;
[0123] Step 255: If a first reset failure occurs, set the soft reset flag to active.
[0124] Step 260: If a second reset failure occurs, set the soft reset flag to invalid.
[0125] In the above technical solution, after the vehicle chassis power domain controller is initialized, a reset fault detection is performed on the vehicle chassis power domain controller; if the output level of each functional module of the vehicle chassis power domain controller does not meet the preset requirements or cannot receive the level, a reset fault is determined to have occurred in the vehicle chassis power domain controller; the fault code corresponding to the reset fault is obtained, and the type of the reset fault is determined according to the fault code; if the type of the reset fault is a first reset fault, the soft reset flag in the memory is set to valid; if the type of the reset fault is a second reset fault, the soft reset flag in the memory is set to invalid; the vehicle chassis power domain controller restarts, executes the initialization function, and reads the soft reset flag in the memory; if the soft reset flag is valid, a first reset fault is determined to have occurred in the vehicle chassis power domain controller; a first reset procedure is executed to initialize the running program and hardware corresponding to the first reset fault; if the soft reset flag is invalid, a second reset fault is determined to have occurred in the vehicle chassis power domain controller; a second reset procedure is executed to initialize all running programs and hardware of the vehicle chassis power domain controller; after the first reset procedure or the second reset procedure is executed, a reset fault detection is performed on the vehicle chassis power domain controller.
[0126] In the above technical solution, the reset faults of the vehicle chassis power domain controller are classified into first reset faults and second reset faults. After determining that the vehicle chassis power domain controller has a first reset fault, the first reset procedure is executed to initialize the corresponding running program and hardware. Different solutions can be adopted according to different reset fault types, and differentiated initialization procedures can be executed. After the first or second reset procedure is completed, the vehicle chassis power domain controller is detected for reset faults in real time. Potential faults can be detected in a timely manner, which can effectively reduce the initialization time after the vehicle chassis power domain controller has a first reset fault and is reset, reduce the safety risks after the vehicle chassis power domain controller has a reset fault, and improve the safety and reliability of the vehicle.
[0127] Figure 3 This application provides schematic diagrams of the structure of a vehicle chassis power domain controller reset control device according to some embodiments, such as... Figure 3 As shown, the vehicle chassis power domain controller reset control device 30 includes a fault determination unit 301 and an execution unit 302.
[0128] The fault determination unit 301 is used to determine that the vehicle chassis power domain controller has a first reset fault.
[0129] The execution unit 302 is used to execute the first reset procedure to initialize the running program and hardware corresponding to the first reset fault.
[0130] Optionally, the fault determination unit 301 is used for:
[0131] Read the soft reset flag from memory;
[0132] If the soft reset flag is valid, it is determined that the vehicle chassis power domain controller has experienced a first reset fault.
[0133] Optionally, the device further includes a fault detection unit for:
[0134] After the vehicle chassis power domain controller is initialized, a reset fault detection is performed on the vehicle chassis power domain controller.
[0135] Optionally, the fault determination unit 301 is further configured to:
[0136] If a reset fault is detected in the vehicle chassis power domain controller, the type of the reset fault is determined;
[0137] Optionally, the execution unit 302 is further configured to:
[0138] The soft reset flag is processed according to the type of reset fault.
[0139] Optionally, the fault determination unit 301 is used for:
[0140] If the output level of each functional module of the vehicle chassis power domain controller does not meet the preset requirements or cannot receive the level, it is determined that the vehicle chassis power domain controller has a reset fault.
[0141] Obtain the fault code corresponding to the reset fault, and determine the type of the reset fault based on the fault code.
[0142] Optionally, the execution unit 302 is used for:
[0143] In the case that the type of reset fault is a first reset fault, the soft reset flag in the memory is set to valid;
[0144] In the case that the type of reset fault is a second reset fault, the soft reset flag in the memory is set to invalid.
[0145] Optionally, the fault determination unit 301 is further configured to:
[0146] If the soft reset flag is invalid, it is determined that a second reset fault has occurred in the vehicle chassis power domain controller;
[0147] Optionally, the execution unit 302 is further configured to:
[0148] A second reset procedure is executed to initialize all operating programs and hardware of the vehicle chassis power domain controller.
[0149] Optionally, the first reset fault includes at least one of the following: MCU bus communication fault, MCU memory management unit fault, operating system runtime error, and watchdog program flow monitoring abnormality;
[0150] The second reset fault is any reset fault other than the first reset fault.
[0151] Optionally, the fault detection unit is further configured to:
[0152] After the first or second reset procedure is completed, a reset fault detection is performed on the vehicle chassis power domain controller.
[0153] In the above technical solution, after determining that the vehicle chassis power domain controller has a first reset fault, the first reset procedure is executed to initialize the running program and hardware corresponding to the first reset fault. This can effectively reduce the initialization time after the vehicle chassis power domain controller has a first reset fault and is reset, reduce the safety risk after the vehicle chassis power domain controller has a reset fault, and improve the safety and reliability of the vehicle.
[0154] The vehicle chassis power domain controller reset control device 30 in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. This electronic device can be the vehicle chassis power domain controller or other devices; this application embodiment does not specifically limit its capabilities.
[0155] The vehicle chassis power domain controller reset control device 30 in this embodiment can be a device with an operating system. This operating system can be a Microsoft (Windows) operating system, an Android operating system, an iOS operating system, or other possible operating systems; this embodiment does not specifically limit the specific operating system.
[0156] The vehicle chassis power domain controller reset control device 30 provided in this application embodiment can achieve... Figures 1 to 2 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.
[0157] In some embodiments, such as Figure 4As shown, this application embodiment also provides an electronic device 400, including a processor 401, a memory 402, and a computer program stored in the memory 402 and executable on the processor 401. When the program is executed by the processor 401, it implements the various processes of the above-described vehicle chassis power domain controller reset control method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0158] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.
[0159] This application also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described vehicle chassis power domain controller reset control method embodiment and achieves the same technical effect. To avoid repetition, it will not be described again here.
[0160] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.
[0161] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described vehicle chassis power domain controller reset control method.
[0162] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.
[0163] This application also provides a vehicle, including: a vehicle chassis power domain controller, the vehicle chassis power domain controller including the vehicle chassis power domain controller reset control device as described above. The vehicle can be a gasoline vehicle, a natural gas vehicle, or a new energy vehicle, and the new energy vehicle can be a pure electric vehicle, a hybrid electric vehicle, or a range-extended vehicle, etc.
[0164] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described vehicle chassis power domain controller reset control method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0165] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.
[0166] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
[0167] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the related technology, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0168] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.
[0169] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0170] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.
[0171] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other.
[0172] The above are merely preferred embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
Claims
1. A method for resetting a vehicle chassis power domain controller, characterized in that, include: The vehicle chassis power domain controller was found to have experienced a first reset fault. The first reset procedure is executed to initialize the running program and hardware corresponding to the first reset fault.
2. The vehicle chassis power domain controller reset control method according to claim 1, characterized in that, The determination that the vehicle chassis power domain controller has experienced a first reset fault includes: Read the soft reset flag from memory; If the soft reset flag is valid, it is determined that the vehicle chassis power domain controller has experienced a first reset fault.
3. The vehicle chassis power domain controller reset control method according to claim 2, characterized in that, The method further includes: After the vehicle chassis power domain controller is initialized, a reset fault detection is performed on the vehicle chassis power domain controller. If a reset fault is detected in the vehicle chassis power domain controller, the type of the reset fault is determined; The soft reset flag is processed according to the type of reset fault.
4. The vehicle chassis power domain controller reset control method according to claim 3, characterized in that, When a reset fault is detected in the vehicle chassis power domain controller, determining the type of the reset fault includes: If the output level of each functional module of the vehicle chassis power domain controller does not meet the preset requirements or cannot receive the level, it is determined that the vehicle chassis power domain controller has a reset fault. Obtain the fault code corresponding to the reset fault, and determine the type of the reset fault based on the fault code.
5. The vehicle chassis power domain controller reset control method according to claim 3, characterized in that, The step of processing the soft reset flag according to the type of reset fault includes: In the case that the type of reset fault is a first reset fault, the soft reset flag in the memory is set to valid; In the case that the type of reset fault is a second reset fault, the soft reset flag in the memory is set to invalid.
6. The vehicle chassis power domain controller reset control method according to any one of claims 2-5, characterized in that, The method further includes: If the soft reset flag is invalid, it is determined that a second reset fault has occurred in the vehicle chassis power domain controller; A second reset procedure is executed to initialize all operating programs and hardware of the vehicle chassis power domain controller.
7. The vehicle chassis power domain controller reset control method according to claim 5, characterized in that, The first reset fault includes at least one of the following: MCU bus communication failure, MCU memory management unit failure, operating system runtime error, and watchdog program flow monitoring abnormality; The second reset fault is any reset fault other than the first reset fault.
8. The vehicle chassis power domain controller reset control method according to claim 6, characterized in that, The method further includes: After the first or second reset procedure is completed, a reset fault detection is performed on the vehicle chassis power domain controller.
9. A vehicle chassis power domain controller reset control device, characterized in that, include: The fault determination unit is used to determine if a first reset fault has occurred in the vehicle chassis power domain controller. The execution unit is used to execute the first reset procedure to initialize the running program and hardware corresponding to the first reset fault.
10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the vehicle chassis power domain controller reset control method as described in any one of claims 1-8.
11. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the vehicle chassis power domain controller reset control method as described in any one of claims 1-8.
12. A vehicle, characterized in that, include: A vehicle chassis power domain controller, wherein the vehicle chassis power domain controller includes the vehicle chassis power domain controller reset control device as described in claim 9.