Fault detection system, method, automobile domain controller, storage medium and vehicle

By using software detection modules in automotive domain controllers to detect and parse fault data of integrated circuits, the problem of difficult IC power-on timing compatibility in domain control systems in new energy vehicles is solved, improving the accuracy of fault detection and reducing the accuracy of fault detection Hardware costs.

CN118605480BActive Publication Date: 2024-11-19BYD CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202411084425.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-08
Publication Date
2024-11-19
Estimated Expiration
2044-08-08

AI Technical Summary

Technical Problem

In new energy vehicles, the domain control system is difficult to take into account the power-on timing of all ICs due to the increase in the number of ICs, resulting in low accuracy of power-on self-test and increased hardware costs. The existing pure hardware adjustment solutions are difficult to compatible, resulting in hardware self-test The problem of low accuracy.

Method used

By introducing a software detection module into the automotive domain controller, the fault data, status data and fault indication data of the integrated circuit are detected, and fault detection and analysis are performed. If a fault is detected, the integrated circuit will be reset and data update will be performed to re-determine the detection result. , improve the accuracy of fault detection.

Benefits of technology

Without changing the hardware distribution, improve the accuracy of integrated circuit fault detection, reduce hardware costs, and avoid the problem of low accuracy caused by mismatch in hardware self-test timing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118605480B_ABST
    Figure CN118605480B_ABST
Patent Text Reader

Abstract

The present application provides a fault detection system, method, automotive domain controller, storage medium and vehicle. The fault detection system includes: at least one integrated circuit and a software detection module, the software detection module is connected to at least one of the integrated circuits, and the software detection module is used to detect the fault detection result of at least one of the integrated circuits. This solution improves the accuracy of integrated circuit fault detection without changing the hardware distribution by re-determining the fault detection result of the integrated circuit through software when an integrated circuit voltage fault is detected.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of automatic control technology, and in particular to a fault detection system, method, automobile domain controller, storage medium and vehicle. Background Art

[0002] With the continuous development of fuel vehicles into new energy vehicles, automotive electronics have gradually shifted from distributed control systems based on Controller Area Network (CAN) communication to centralized domain control system architecture. With the development of new energy vehicles, the domain control system architecture has become more and more complex, with more and more integrated functions and more and more integrated circuits (ICs).

[0003] In the related art, as the number of ICs increases and each IC includes a different power supply, it is difficult for the domain control system to take into account all power-on sequences when performing hardware power-on self-test on multiple ICs, and there may be mutual influence during the power-on self-test process, resulting in failure of the power-on self-test. Summary of the invention

[0004] The present application provides a fault detection system, method, automobile domain controller, storage medium and vehicle, aiming to solve the problem of low accuracy of power-on self-test.

[0005] In a first aspect, the present application provides a fault detection system, comprising:

[0006] at least one integrated circuit;

[0007] A software detection module, the software detection module is connected to at least one of the integrated circuits, and the software detection module is used to detect a fault detection result of at least one of the integrated circuits.

[0008] Optionally, the integrated circuit includes at least one of a fault register, a status register and a fault indication pin;

[0009] The software detection module includes:

[0010] a collection unit, the collection unit being connected to at least one of the fault register, the status register and the fault indication pin, the collection unit being used to collect at least one of the fault data of the fault register, the status data of the status register and the fault indication data of the fault indication pin;

[0011] a parsing unit, configured to parse at least one of the fault data, the state data and the fault indication data to obtain a fault detection result;

[0012] A processing unit is used to determine a target detection result of the integrated circuit according to the fault detection result.

[0013] In a second aspect, the present application provides a fault detection method, which is applied to the fault detection system, wherein the fault detection system includes a software detection module and at least one integrated circuit, and the method includes:

[0014] The software detection module detects at least one of the integrated circuits to obtain a fault detection result.

[0015] Optionally, the detecting at least one of the integrated circuits by the software detection module to obtain a fault detection result includes:

[0016] Obtaining, for at least one of the integrated circuits, through the software detection module, at least one of the fault data of a fault register, the status data of a status register, and the fault indication data of a fault indication pin in the integrated circuit;

[0017] A fault detection result is determined based on at least one of the fault data, the status data and the fault indication data.

[0018] Optionally, determining a fault detection result according to at least one of the fault data, the state data and the fault indication data includes:

[0019] If the fault data is not empty, and / or the state data has an abnormal state, and / or the fault indication data has a fault indication, then the fault detection result is determined to be that a fault exists.

[0020] Optionally, the method further includes:

[0021] If the fault detection result is that a fault exists, a target detection result of the integrated circuit is determined according to the fault type of the fault.

[0022] Optionally, determining a target detection result of the integrated circuit according to the fault type of the fault includes:

[0023] Determining a fault level of the fault and a target detection result corresponding to the fault level according to the fault type of the fault;

[0024] The fault level includes a primary fault and a secondary fault, wherein the primary fault indicates that the integrated circuit cannot be used normally, and the secondary fault indicates that the integrated circuit can be used normally.

[0025] Optionally, determining the target detection result corresponding to the fault level includes:

[0026] If the fault level is the first-level fault, determining that the target detection result is a failed state;

[0027] If the fault level is the secondary fault, or the fault detection result is that there is no fault, then it is determined that the target detection result is a pass state.

[0028] Optionally, the method further includes:

[0029] If the target detection result is the passing state, then counting the continuous cumulative number of the passing state;

[0030] If the continuous accumulated number of times is less than the set number threshold, the step of detecting at least one of the integrated circuits through the software detection module is executed until the continuous accumulated number of times reaches the set number threshold.

[0031] Optionally, the method further includes:

[0032] If the target detection result is the failed state, the continuous accumulated times are cleared to zero, and the step of detecting at least one of the integrated circuits through the software detection module is performed.

[0033] Optionally, before detecting at least one of the integrated circuits by the software detection module to obtain a fault detection result, the method further includes:

[0034] A hardware self-check is performed on at least one of the integrated circuits, and when the hardware self-check fails, it is determined that a power-on voltage of the at least one integrated circuit tends to be stable.

[0035] Optionally, before acquiring at least one of the fault data of a fault register, the status data of a status register, and the fault indication data of a fault indication pin in the integrated circuit, the method includes:

[0036] A power-on reset is performed on at least one of the integrated circuits.

[0037] Optionally, performing power-on resetting on at least one of the integrated circuits includes:

[0038] Acquire a target power source identifier of a first integrated circuit, wherein the first integrated circuit is an integrated circuit of at least one of the integrated circuits for which the fault detection result is empty or the fault detection result indicates that a fault exists;

[0039] The first integrated circuit is controlled to be reset according to the voltage change information corresponding to the target power source identifier.

[0040] Optionally, controlling the first integrated circuit to reset according to the voltage change information corresponding to the target power source identifier includes:

[0041] Obtaining power-on timing information corresponding to the first integrated circuit, the power-on timing information including a power-on duration of a power supply for the first integrated circuit, the power-on duration representing a time taken for a voltage parameter of the power supply to reach a preset stable voltage parameter;

[0042] Determining a reset time according to the power-on duration and a power-on time corresponding to the first integrated circuit;

[0043] The first integrated circuit is controlled to be reset according to the reset time.

[0044] Optionally, controlling the first integrated circuit to reset according to the reset time includes:

[0045] Identify a reset pin corresponding to a target power identifier of the first integrated circuit;

[0046] According to the reset time, each of the reset pins is controlled to perform reset adjustment on the first integrated circuit.

[0047] Optionally, determining the reset time according to the power-on duration and the power-on time corresponding to the first integrated circuit includes:

[0048] If the first integrated circuit includes at least two soft power-on power supplies, then obtaining the power-on durations corresponding to the soft power-on power supplies in the power-on timing information, and determining a maximum power-on duration among the power-on durations;

[0049] A reset time is determined according to the maximum power-on time and the power-on time corresponding to the first integrated circuit.

[0050] Optionally, performing power-on resetting on at least one of the integrated circuits includes:

[0051] During the power-on reset process, at least one of the write operations is performed, and the write operation includes: writing the fault data generated in the integrated circuit into the corresponding fault register; writing the status data generated in the integrated circuit into the corresponding status register; and writing all fault indication data generated in the integrated circuit into the fault indication pin.

[0052] In a third aspect, the present application provides a vehicle domain controller, the vehicle domain controller comprising:

[0053] one or more processors;

[0054] Memory; and

[0055] One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement any one of the fault detection methods.

[0056] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is loaded by a processor to execute the steps in any one of the fault detection methods described.

[0057] In a fifth aspect, the present application provides a vehicle, comprising a fault detection system as described in any one of the items, and the vehicle domain controller.

[0058] The present application provides a fault detection system, method, automotive domain controller, storage medium and vehicle, wherein the fault detection system comprises: at least one integrated circuit; a software detection module, wherein the software detection module is connected to at least one of the integrated circuits, and the software detection module is used to detect the fault detection result of at least one of the integrated circuits. The present solution improves the accuracy of integrated circuit fault detection without changing the hardware distribution by re-determining the fault detection result of the integrated circuit through software when an integrated circuit voltage fault is detected. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0060] Figure 1 This is a scenario diagram of a fault detection method provided by an embodiment of the present application;

[0061] Figure 2 is a structural diagram of a fault detection system provided by an embodiment of the present application;

[0062] Figure 3 This is a flowchart of an embodiment of a fault detection method provided by an embodiment of the present application;

[0063] Figure 4 A schematic diagram of an implementation flow of controlling the IC integrated circuit to reset in a fault detection method provided in an embodiment of the present application;

[0064] Figure 5 A schematic diagram of another implementation flow of a fault detection method provided in an embodiment of the present application;

[0065] Figure 6A schematic diagram of another implementation flow of a fault detection method provided in one embodiment of the present application;

[0066] Figure 7 A schematic diagram of another implementation flow of a fault detection method provided in one embodiment of the present application;

[0067] Figure 8 It is a schematic diagram of the structure of an embodiment of a vehicle domain controller provided in one embodiment of the present application. DETAILED DESCRIPTION

[0068] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0069] In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, which are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0070] In the embodiment of the present application, "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / ", unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship.

[0071] In this application, the word "exemplary" is used to mean "serving as an example, illustration, or illustration." Any embodiment described in this application as "exemplary" is not necessarily to be construed as being preferred or advantageous over other embodiments. The following description is given to enable any person skilled in the art to implement and use the invention. In the following description, details are listed for the purpose of explanation. It should be understood that a person of ordinary skill in the art can recognize that the invention can be implemented without using these specific details. In other instances, well-known structures and processes are not elaborated in detail to avoid obscuring the description of the invention with unnecessary details. Therefore, the present invention is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in this application.

[0072] With the continuous development of fuel vehicles into new energy vehicles, automotive electronics has gradually shifted from distributed control systems based on CAN communication to centralized domain control system architectures. This means that our controllers are becoming more and more complex, with more and more integrated functions and more and more ICs.

[0073] Among all kinds of ICs, whether it is PMIC for power management or high-side and low-side ICs, bridge driver and half-bridge driver ICs, sensor ICs, CAN, LIN, ETH and other communication ICs, etc., all these ICs require software driver development. Each IC has its own power timing requirements, and it is becoming increasingly difficult for the power topology of the domain control system to take into account the timing requirements of all ICs. There will also be incompatibility issues.

[0074] Taking the intelligent thermal management domain controller ED018 project as an example, the project is equipped with an L9305 IC, and the power-on timing is incompatible with the system power timing. L9305 is a current-type electronic valve driver IC, which has three working voltages: VDD, VDDIO, and Vbat. Its power timing requires that VDD and VBat are powered on almost at the same time, and VDD starts hardware self-test as soon as it is powered on. The system power architecture of our intelligent thermal management domain controller is that VDD is available as soon as it is powered on, and supplies power to the MCU. The MCU outputs a 10Khz square wave through software PWM. Only when 10Kh is available can 12VMain be output, and only when 12Vmain is available can Vbat be available. At this time, the hardware self-test of L9305 has failed. Because our 12V Vbat soft power-on is too late. However, 12Vmain soft power-on is very necessary, because 12V is power electricity, and many capacitors are added to the hardware, which needs to be protected from impact. Soft start of 12Vmain power electricity is very necessary, but it conflicts with the power-on timing requirements of L9305.

[0075] To be compatible with the timing of the hardware self-test of L9305, the hardware must be changed. When Vbat cannot be advanced, a switch is added to make VDD controllable, and the VDD of L9305 is also soft-powered, and the software ensures that VDD and VBat are powered on at the same time. If a switch is added, the hardware BOM material cost will increase, and the hardware revision, re-boarding, and project cycle will be extended.

[0076] In summary, it is becoming increasingly difficult for the power topology of the domain control system to take into account the timing requirements of all ICs, and there will indeed be incompatibility issues. The existing solution and status quo of relying solely on hardware to continuously adjust the power timing of each IC will inevitably cause the hardware cost to continue to rise. If no adjustment is made, the hardware self-test will be difficult to be compatible with the power-on timing, resulting in low hardware self-test accuracy.

[0077] Therefore, the embodiments of the present application provide a fault detection system, method, automotive domain controller, storage medium and vehicle (computer-readable storage medium may be referred to as storage medium in its entirety). When an IC integrated circuit voltage fault is detected, the IC integrated circuit is reset to recollect the status information of the IC integrated circuit corresponding to the power supply, and the detection result of the IC integrated circuit is re-determined, thereby improving the accuracy of integrated circuit fault detection without changing the hardware distribution. The following are detailed descriptions respectively.

[0078] The fault detection method in an embodiment of the present invention is applied to a fault detection device, which is arranged in a vehicle domain controller. The vehicle domain controller is included in a fault detection system, which includes at least one integrated circuit and a software detection module. The vehicle domain controller is provided with one or more processors, a memory, and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the fault detection method.

[0079] like Figure 1 As shown, Figure 1 This is a scenario diagram of the fault detection method in an embodiment of the present application. The fault detection scenario in the embodiment of the present invention includes a car 100, in which a car domain controller 200 is installed (a fault detection device is integrated in the car domain controller 200), and a computer-readable storage medium corresponding to the fault detection method is run in the car domain controller 200 to execute the steps of the fault detection method.

[0080] Understandably, Figure 1The automotive domain controller 200 in the scenario of the fault detection method shown, or the devices included in the automotive domain controller 200, do not constitute a limitation on the embodiments of the present invention, that is, the number of devices and types of devices included in the scenario of the fault detection method, or the number of devices and types of devices included in each device do not affect the overall implementation of the technical solution in the embodiments of the present invention, and can all be regarded as equivalent replacements or derivatives of the technical solution claimed to be protected in the embodiments of the present invention.

[0081] In the embodiment of the present invention, the automobile domain controller 200 is mainly used to: detect at least one of the integrated circuits through the software detection module to obtain a fault detection result.

[0082] Those skilled in the art will understand that Figure 1 The application environment shown in the figure is only one application scenario of the present application solution and does not constitute a limitation on the application scenario of the present application solution. Other application environments may also include Figure 1 More or fewer vehicle domain controllers 200, or network connection relationships of the vehicle domain controllers 200, are shown in FIG. Figure 1 Only one vehicle domain controller 200 is shown. It can be understood that the scenario of the fault detection method can also include one or more other vehicle domain controllers 200, which are not specifically limited here; the vehicle domain controller 200 can also include a memory for storing data.

[0083] In addition, in the scenario of the fault detection method of the present application, the automobile 100 may be provided with a display device, or the automobile 100 may not be provided with a display device and may be communicated with an external display device, and the display device is used to output the result of the execution of the fault detection method in the automobile domain controller 200. The automobile domain controller 200 may access a background database 300 (the background database may be in the local memory of the automobile domain controller 200, or may be set in the cloud), and the background database 300 stores information related to fault detection.

[0084] It should be noted that Figure 1 The scenario diagram of the fault detection method shown is only an example. The scenario of the fault detection method described in the embodiment of the present invention is to more clearly illustrate the technical solution of the embodiment of the present invention, and does not constitute a limitation on the technical solution provided by the embodiment of the present invention.

[0085] In one embodiment of the present application, a fault detection system is provided. Figure 2 , Figure 2 A schematic diagram of the structure of one implementation scheme of a fault detection system provided in the implementation scheme of the present application, wherein the fault detection system comprises: at least one integrated circuit 101;

[0086] A software detection module 102 , wherein the software detection module 102 is connected to at least one of the integrated circuits 101 , and the software detection module 102 is used to detect a fault detection result of at least one of the integrated circuits 101 .

[0087] In one embodiment of the present application, the integrated circuit 101 includes but is not limited to at least one of a fault register, a status register and a fault indication pin.

[0088] Based on the scenario of the above fault detection method, an embodiment of the fault detection method is proposed.

[0089] In the implementation scheme of the present application, the fault detection method is applied to the fault detection system described in the above implementation scheme, specifically by detecting at least one of the integrated circuits through a software detection module in the fault detection system to obtain a fault detection result.

[0090] Specifically, Figure 3 As shown, Figure 3 This is a flow chart of an embodiment of a fault detection method in an embodiment of the present application. The fault detection method includes steps S301-S302:

[0091] S301. Obtain, for at least one of the integrated circuits, through the software detection module, at least one of the fault data of a fault register, the status data of a status register, and the fault indication data of a fault indication pin in the integrated circuit.

[0092] Among them, the integrated circuit is also an IC integrated circuit, that is, the IC in the domain control system corresponding to the automobile domain controller.

[0093] Specifically, there are multiple fault registers in the integrated circuit, and each fault register stores corresponding fault data. It can be understood that the fault register is used to store fault codes, that is, the fault data includes fault codes, and the fault registers include: service fault register 1, service fault register 2, service fault mark register 1, service fault mark register 2, communication fault register, drive fault register 1, drive fault register 2, temperature fault register, voltage fault register, current fault register, channel fault register, open circuit fault register, short circuit fault register, etc.

[0094] Specifically, there are multiple status registers in the integrated circuit, and the status registers are used to store status data of components, control processes, loads, etc. The status data is to confirm whether the voltage of the components is stable, that is, the status data includes status data of components, control processes, loads, etc.; it can be understood that the status register: used to store the status of integrated current-related functions, including: pin status register, accidental status register 1, accidental status register 2, setting status register 1, setting status register 2, current status register, control status register, frequency status register, PID status register, channel status register, etc.

[0095] Specifically, the fault indication pin stores all the faults of the integrated circuit and does not distinguish the registers of individual faults. It can be understood that since some faults cannot correspond to corresponding faulty components, the fault information should be stored in the fault indication data corresponding to the fault indication pin; specifically, a change in the fault indication pin indicates that a certain fault has occurred, and these faults may be any one of the faults marked in red or multiple faults may occur at the same time; that is, the fault indication data includes: indications including analog ground loss fault, digital ground loss fault, data check error fault, serial peripheral interface (SerialPeripheralInterface, SPI) communication timeout fault, internal register fault, input channel fault, output channel fault, register matching fault, temperature fault, voltage fault, etc.

[0096] Specifically, in some embodiments of the present application, before obtaining, through the software detection module, at least one of the fault data of the fault register, the status data of the status register, and the fault indication data of the fault indication pin in at least one of the integrated circuits, the integrated circuit is first powered on and reset to update the data in the fault data of the fault register, the status data of the status register, and the fault indication data of the fault indication pin in the integrated circuit.

[0097] Specifically, in the implementation of the present application, the fault detection method is applied to an automobile domain controller, which includes a fault detection system. The domain controller manages and coordinates the ICs corresponding to various electronic systems and subsystems inside the vehicle. During the power-on process, the domain controller is powered on first, and the IC starts the hardware power-on self-test. However, during this process, the circuits of the IC that do not require voltage modulation can be directly powered on successfully. At this time, the power supply will not have a voltage failure, but the soft power-on power supply that requires voltage modulation in the IC will not have power immediately. Voltage modulation requires a process, which causes the hardware power-on self-test to detect that the soft power-on power supply has no power, and then reports a voltage failure. At this time, the status register corresponding to the soft power-on power supply will no longer have the status information of the soft power-on power supply. However, it can be understood that the soft power-on power supply is not powered on, but is performing voltage modulation, so the fault is inaccurate.

[0098] For example, taking IC L9305 as an example, L9305 is a current-type electronic valve driver IC, which has three power lines: VDD, VDDIO, and Vbat. VDD is powered as soon as it is powered on, and hardware self-test begins. However, Vbat is a soft power supply, and MCU needs to output a 10Khz square wave through software PWM. Only when 10Kh is available can 12VMain be output, and only when 12Vmain is available can Vbat be available. However, at this time, L9305 has given the result of hardware self-test power-on failure, and these results are fed back to the fault register, status register and the fault indication pin.

[0099] Therefore, in the implementation scheme of the present application, if a fault is detected in an integrated circuit, the integrated circuit is re-controlled to be reset so as to re-update the data corresponding to the fault register, status register and fault indication pin of the integrated circuit (fault data, status data and fault indication data) so as to ensure the accuracy of subsequent fault detection based on the software detection module on the updated data.

[0100] It can be understood that the time for controlling the reset of the integrated circuit can be flexibly configured. For example, the reset can be triggered after a preset duration of time after the integrated circuit failure is detected, or it can be determined by the corresponding power-on timing information to obtain a reset time estimate based on the corresponding type, so as to perform reset control according to the estimated reset time.

[0101] S302: Determine a fault detection result according to at least one of the fault data, the state data and the fault indication data.

[0102] Specifically, after the integrated circuit domain controller is powered on, the software detection module reads at least one of the fault data, status data and fault indication data in the fault register, the status register and the integrated circuit corresponding to the fault indication pin, and further analyzes at least one of the fault data, status data and fault indication data to obtain the detection result of the integrated circuit.

[0103] This solution improves the accuracy of integrated circuit fault detection without changing the hardware distribution by resetting the integrated circuit to recollect the status information of the integrated circuit correspondence and power supply and re-determining the detection result of the integrated circuit when the hardware detects an integrated circuit fault.

[0104] Furthermore, based on the above implementation scheme, the present application also provides an implementation scheme for determining the fault detection result. Specifically, after obtaining at least one of the fault data, the status data and the fault indication data, if the fault data is not empty, and / or the status data is in an abnormal state, and / or the fault indication data contains a fault indication, then the fault detection result is determined to be that a fault exists.

[0105] Exemplarily, if the status data is in an abnormal state, the status data can be compared with corresponding standard status data to determine whether it is an abnormal state.

[0106] Specifically, in one embodiment of the present application, the fault detection result analysis is performed only by acquiring the fault data, that is, if the fault data is not empty, then there is a fault, otherwise there is no fault.

[0107] Specifically, in one embodiment of the present application, the fault detection result analysis is performed only by acquiring the status data, that is, if the status data is abnormal, then there is a fault, otherwise there is no fault.

[0108] Specifically, in one embodiment of the present application, the fault detection result analysis is performed only by acquiring the fault indication data, that is, if the fault indication data contains a fault indication, then the fault exists, otherwise, then the fault does not exist.

[0109] It is understandable that in some other embodiments of the present application, any two or three of the fault data, the status data and the fault indication data can also be obtained simultaneously to perform fault detection result analysis, one of which satisfies the judgment of the existence of a fault, that is, the fault detection result is that a fault exists, so as to improve the accuracy of fault analysis.

[0110] Furthermore, in another implementation scheme of the present application, if the fault detection result is detected as the presence of a fault, the target detection result of the integrated circuit is further determined based on the fault type of the fault, wherein the target detection result is used to characterize whether the integrated circuit can be used normally under the premise that the fault exists.

[0111] Furthermore, the present application also provides a specific implementation scheme for determining target detection results, which specifically includes the steps of:

[0112] (1) If the fault level is the first-level fault, determining that the target detection result is a failed state;

[0113] (2) If the fault level is the level 2 fault, or the fault detection result is that there is no fault, then determining that the target detection result is a pass state.

[0114] Specifically, in the implementation scheme of the present application, the fault level of the fault is determined mainly by judging the fault type of the fault in the fault detection result, and then according to the target detection result corresponding to the fault level, specifically, the fault level includes a primary fault and a secondary fault, the primary fault indicates that the integrated circuit cannot be used normally, and the secondary fault indicates that the integrated circuit can be used normally. In the case of the primary fault, the use of the integrated circuit at the back end under the fault will cause damage to the integrated circuit, and in the case of the secondary fault, the integrated circuit can be used under the fault using the backup back end control parameters, wherein the control accuracy of the circuit element corresponding to the fault in the backup back end control parameters is less than the control accuracy of the element in the non-fault state.

[0115] For further information, see Figure 4 , Figure 4 A schematic flow chart of another fault detection method implementation scheme provided in the present application specifically includes steps S401-S404:

[0116] S401. Detect at least one of the integrated circuits using the software detection module to obtain a fault detection result.

[0117] S402: If the fault detection result is that a fault exists, determine a target detection result of the integrated circuit according to the fault type of the fault.

[0118] Specifically, the specific implementation method of steps S401-S402 refers to any of the above implementation schemes.

[0119] S403: If the target detection result is the passing state, counting the continuous cumulative number of the passing state.

[0120] S404: If the continuous accumulated number of times is less than the set number threshold, execute the step of detecting at least one of the integrated circuits through the software detection module until the continuous accumulated number of times reaches the set number threshold.

[0121] Specifically, if the continuous cumulative number of passing states is increased by one, and the continuous cumulative number after the increase is counted, if the continuous cumulative number is less than the set number threshold, the step of detecting at least one of the integrated circuits through the software detection module is further repeated until the continuous cumulative number reaches the set number threshold, so as to ensure the accuracy of fault detection.

[0122] Specifically, in another implementation scheme of the present application, if the target detection result is the failed state, the continuous cumulative number is cleared to zero, and the step of detecting at least one of the integrated circuits through the software detection module is executed to ensure that the fault is completely eliminated or does not affect the normal use of the integrated circuit.

[0123] Specifically, the present application also provides a fault detection method. In this embodiment, by performing a hardware self-test on at least one of the integrated circuits, when the hardware self-test fails, it is determined that the power-on voltage of at least one of the integrated circuits tends to be stable, and the step of further performing a test on at least one of the integrated circuits through the software detection module is performed.

[0124] In this implementation, the detection results of the hardware self-test are re-tested through software fault detection to improve the detection accuracy and the flexibility of the detection design.

[0125] Further, based on the above implementation, the present application also provides an implementation for controlling the integrated circuit to reset. For details, see Figure 5 , Figure 5 A schematic flow chart of one implementation scheme of controlling the integrated circuit to reset in the fault detection method provided in an embodiment of the present application, specifically comprising steps S501-S502:

[0126] S501. Obtain a target power source identifier of a first integrated circuit, wherein the first integrated circuit is an integrated circuit whose fault detection result is empty, or an integrated circuit whose fault detection result is a fault.

[0127] It can be understood that the integrated circuit whose target detection result is empty is the first time that the fault detection of the integrated circuit is performed based on the software detection module. In this scenario, the software detection module does not obtain the fault detection result corresponding to the integrated circuit.

[0128] In another implementation scheme of the present application, the power-on reset of at least one of the integrated circuits can also be performed after the hardware self-test. According to the above description, the main reason for the erroneous detection result during the hardware self-test is soft power-on. Therefore, in the implementation scheme of the present application, after the domain controller is powered on, the hardware self-test fault information corresponding to the hardware power-on self-test is obtained. If a fault is detected in the hardware self-test fault information, it is determined that the integrated circuit corresponding to the fault is the first integrated circuit, and the target power supply identifier corresponding to the fault is obtained.

[0129] In another embodiment of the present application, the power-on reset of at least one of the integrated circuits may also be performed after software detection, that is, the first integrated circuit is an integrated circuit for which the fault detection result indicates that there is a fault.

[0130] S502: Control the first integrated circuit to reset according to the voltage change information corresponding to the target power source identifier.

[0131] Further, after determining the target power source identifier, it is detected whether the power source corresponding to the target power source identifier is turned on, and after determining that the power source is turned on, the integrated circuit is controlled to reset.

[0132] Exemplarily, whether the power supply corresponding to the target power supply identifier is powered on can be determined by monitoring the voltage change of the power supply in real time, thereby controlling the reset.

[0133] Exemplarily, in some other embodiments of the present application, controlling the first integrated circuit to reset according to the voltage change information corresponding to the target power source identifier specifically includes the steps of:

[0134] (1) obtaining power-on timing information corresponding to the first integrated circuit, the power-on timing information including a power-on time of a power supply for the first integrated circuit, the power-on time representing a time taken for a voltage parameter of the power supply to reach a preset stable voltage parameter;

[0135] (2) determining a reset time according to the power-on time and a power-on time corresponding to the first integrated circuit;

[0136] (3) Controlling the first integrated circuit to reset according to the reset time.

[0137] The power-on timing information includes the power-on duration representing the voltage change information corresponding to the target power source identifier.

[0138] By analyzing the power-on timing information corresponding to the integrated circuit, the power-on duration of the first integrated circuit power supply can be determined, and then the reset time can be determined according to the power-on time corresponding to the first integrated circuit.

[0139] Specifically, by identifying the maximum power-on time among the power-on times, and based on the maximum power-on time and the power-on time corresponding to the integrated circuit, it is ensured that all power supplies in the IC are stable, and reset is performed under the cavity to avoid the situation where the reset is too early and the soft power-on is not successful, resulting in inaccurate data stored in the status register.

[0140] It is understandable that the hardware timing mismatch in the power-on phase is known and determined. The power-on phase will cause the power-on self-test to report VCP undervoltage fault (voltage fault includes undervoltage fault) due to the mismatch between the power timing, and the self-test will fail. However, the voltage system of VCP will eventually be provided stably, and there will be no undervoltage fault in VCP in the end. It is just that the power on time of VCP in the power-on phase is a little late, and it cannot successfully pass the power-on hardware self-test, but if we do not care about the result of the hardware self-test in the power-on phase. Because the ICs will not be used at all in the power-on phase, they have not been initialized at all, and the software driver has not been loaded for functional configuration. As long as there is no fault in the IC after the power-on is completed, it will be fine. We directly check the software from the software level after the power-on is completed, and see if there is still a fault in the chip after the power supply is stable. If there is no fault, the software check can be used to replace the hardware self-test, and the problem of hardware timing mismatch can be solved from the driver software design compatibility.

[0141] Specifically, in one implementation of the present application, the solution controls the first integrated circuit to reset according to the reset time, including the steps of:

[0142] (1) identifying a reset pin corresponding to a target power identifier of the first integrated circuit;

[0143] (2) According to the reset time, control each of the reset pins to reset the first integrated circuit.

[0144] This solution achieves reset control of the reset pin by controlling the output signal through software, and resets the reset pins corresponding to the faults respectively, performs reset processing on the faulty parts, improves reset accuracy, and reset control flexibility.

[0145] Specifically, in the embodiment of the present application, during the power-on reset process, at least one of the write operations is performed, and the write operation includes: writing the fault data generated in the integrated circuit into the corresponding fault register; writing the status data generated in the integrated circuit into the corresponding status register; writing all the fault indication data generated in the integrated circuit into the fault indication pin. The data corresponding to the fault register, the status register and the fault indication pin are updated.

[0146] Specifically, in one implementation scheme of the present application, the present scheme determines the reset time by controlling the power-on time corresponding to each power supply and the power-on time corresponding to the IC integrated circuit according to the reset time, and specifically includes the steps of:

[0147] (1) If the first integrated circuit includes at least two soft power-on power supplies, obtaining the power-on durations corresponding to the soft power-on power supplies in the power-on timing information, and determining a maximum power-on duration among the power-on durations;

[0148] (2) Determining a reset time according to the maximum power-on time and the power-on time corresponding to the first integrated circuit.

[0149] Specifically, by identifying the maximum power-on duration among the power-on durations, and based on the maximum power-on duration and the power-on time corresponding to the IC integrated circuit, it is ensured that all power supplies in the IC are stable, and a reset is performed in this scenario to avoid the situation where the reset is too early and the soft power-on is not successful, resulting in inaccurate data stored in the status register.

[0150] It can be understood that the integrated circuit includes multiple power supplies, and each power supply corresponds to a reset circuit so as to reset each power supply. When multiple voltage faults are detected in the integrated circuit, the reset circuit corresponding to each voltage fault is reset respectively. Specifically, the integrated circuit is controlled to be reset according to the reset time, including the steps of:

[0151] For example, see Figure 6 , Figure 6Another implementation scheme flow diagram of the fault detection method provided for the implementation scheme of the present application is as follows: After the domain controller is powered on, the IC will start hardware self-test. Once a self-test failure occurs, the software starts a 1ms periodic polling check of all voltages related to the system and the IC, until the voltage stabilizes and the software resets the IC that failed the hardware self-test separately, and after the reset, it establishes communication with the IC again, reads all status registers, reads all fault registers, collects the fault indication pin status, and analyzes and checks one by one according to the read and collected information. After a set of checks, the IC has no faults and is counted as a software check pass, and then the cycle is scheduled. If the software passes three times in a row, it is considered that the IC can be used normally. That is, the three times are the preset number of tests. Further, after it is considered that the IC can be used normally, the driver is loaded and it can be developed according to the normal IC driver. The configuration register initializes the IC, develops functions, abstracts interfaces, encapsulates functions, and provides them to the ASW API. The entire software fault detection compatible power timing method can be abstracted and encapsulated into a function. It can be directly added to the driver software before each IC and directly called, or it can be flexibly processed according to the situation of each IC to implement the method of the present invention. Furthermore, if the software fault detection finds that there is a fault, but it is not a power undervoltage or overvoltage but a load open circuit fault, the IC initialization can continue. Because the load does not start to be controlled during the system power-on initialization phase, if a load-related fault is reported during the software check phase, you don’t need to worry about it and continue to initialize the IC. If there is still a load-related fault after the driver is running, report it to the application layer truthfully.

[0152] For further information, see Figure 7 , Figure 7 A flowchart of another implementation scheme of the fault detection method provided in the implementation scheme of the present application is provided. The flowchart takes L9305IC as an example, and the system KL30 is the domain control system.

[0153] Specifically, after the system KL30 signal is valid, the 5V power supply starts to have power, and 5V is directly connected to the L9305 VDD pin. At this time, the L9305 starts the power-on hardware self-test operation, but at the same time, the MCU starts to power on. After the MCU is powered on, it will load BOOTLOADER, and then jump from BOOTLOADER to APP. After entering APP, each module will be initialized, including PWM initialization. After PWM initialization is completed and 10KHz PWM is output, the system's 12Vmain will start, and 12Vmain will input L930512V VBat. After L9305 12V VBat is powered, VCP will start to output. This process is a soft power-on process. At this time, it is later than the L9035 self-test time and does not meet the L9305 power-on timing. The chip itself naturally reports a VCP undervoltage fault, and the power-on self-test fails. The chip is unusable.

[0154] Since the ICs are not used at all during the power-on phase, they have not been initialized, and the software driver has not been loaded for functional configuration. Therefore, as long as the IC is not faulty after power-on is completed, it will be fine. Therefore, this solution is divided into three important steps to see if the chip is still faulty after the power supply is stable.

[0155] Step 1: Confirm that the voltage of each power supply of the IC is stable. Confirm whether the power supply status is stable, and ensure that the software fault detection is started after the power supply status is stable, that is, the integrated circuit is controlled to reset. If the software check is performed without waiting for the power supply voltage to stabilize, it is easy to misjudge and continue to get undervoltage faults. There are two solutions to determine whether the IC power supply voltage is stable: Solution 1, you can read the status of each power supply of the IC to ensure whether the power supply is stable, directly collect or read the status of the relevant power register through ADC, or read the status of the power good pin, etc. Solution 2, you can obtain the time parameters for the stability of the IC power supply through experiments, because the power supply timing of the system is generally determined. How long after power-on will the IC power supply be powered on, until the power-on of each power supply of the IC is finally completed, and then the IC power supply is stable. This time parameter is basically determined and can be measured by experiment. Delay in software to wait for the stability of each power supply of the IC. This solution requires a lot of experiments and multi-scenario coverage tests to obtain the time parameters for the stability of the IC power supply. Step 1 Ensure that the power supplies of the IC are stable before proceeding to step 2.

[0156] Step 2: Actively reset the IC. You can reset the IC by directly operating the reset pin, or some ICs can be reset by SPI commands. The purpose of the reset is to clear the known undervoltage faults that may exist during the power-on phase. Check if there are other faults.

[0157] Step 3: The software checks all registers and confirms 0 faults. Read all fault registers of the IC at one time, and then analyze them one by one to determine whether there are still faults in the IC after the power supplies of each line are stable. After confirming 0 faults, the fault detection is completed.

[0158] The IC driver software compatible power-on timing mismatch fault detection method of the present invention can be applied to PMIC, high-side and low-side IC, bridge drive and half-bridge drive IC, sensor IC, CAN, LIN, ETH and other communication ICs. It is also applicable to various complex embedded control systems including but not limited to automotive electronic systems.

[0159] Further, based on the above implementation scheme, the present application also provides a vehicle domain controller, the vehicle domain controller comprising:

[0160] one or more processors;

[0161] Memory; and

[0162] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the steps in the fault detection method described in any of the above embodiments.

[0163] In combination with the above embodiments, it can be known that in some of the embodiments of the present application, the vehicle domain controller part may include the vehicle domain controller of the above embodiments, and one or more processors and memories in the vehicle domain controller part are integrated on a circuit board body included in the vehicle domain controller, and the circuit board body is set in the vehicle domain controller.

[0164] It is understandable that in some other embodiments of the present application, the processor and memory in the vehicle domain controller may not be integrated on the vehicle domain controller, that is, the processor and memory are respectively arranged in the vehicle domain controller as components of the vehicle domain controller.

[0165] like Figure 8 As shown, Figure 8 It is a schematic diagram of the structure of an embodiment of the automobile domain controller provided in the embodiments of the present application.

[0166] Specifically, the vehicle domain controller may include one or more processing core processors 1001, one or more computer-readable storage media memories 1002, a power supply 1003, an input unit 1004 and other components. Those skilled in the art will understand that Figure 8 The vehicle domain controller structure shown in the figure does not constitute a limitation on the vehicle domain controller, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:

[0167] The processor 1001 is the image processing center, which uses various interfaces and lines to connect various parts of the entire automotive domain controller. By running or executing software programs and / or modules stored in the memory 1002, and calling the data stored in the memory 1002, the various functions of the automotive domain controller and processing data are executed, thereby monitoring the automotive domain controller as a whole. It can be understood that the processor 1001 transmits signals with the controller. Optionally, the processor 1001 may include one or more processing cores; preferably, the processor 1001 can integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application programs, etc., and the modem processor mainly processes wireless communications. It can be understood that the above-mentioned modem processor may not be integrated into the processor 1001.

[0168] The memory 1002 can be used to store software programs and modules. The processor 1001 executes various functional applications and data processing by running the software programs and modules stored in the memory 1002. The memory 1002 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the automobile domain controller, etc. In addition, the memory 1002 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 1002 may also include a memory controller to provide the processor 1001 with access to the memory 1002.

[0169] In some embodiments of the present application, the fault detection device can be implemented in the form of a computer program. The computer program can be Figure 8 The memory of the automobile domain controller can store various program modules constituting the fault detection device, and the computer program composed of each program module enables the processor to execute the steps of the fault detection method of each embodiment of the present application described in this specification.

[0170] For example, the automobile domain controller includes a processor, a memory, and a network interface connected through a system bus. The processor of the automobile domain controller is used to provide computing and control capabilities. The memory of the automobile domain controller includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the automobile domain controller is used to communicate with an external automobile domain controller through a network connection. When the computer program is executed by the processor, a fault detection method is implemented.

[0171] The automobile domain controller also includes a power supply 1003 for supplying power to various components. Preferably, the power supply 1003 can be logically connected to the processor 1001 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. The power supply 1003 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0172] The automotive domain controller may further include an input unit 1004, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0173] Although not shown, the automobile domain controller may also include a display unit, etc., which will not be described in detail here. Specifically in this embodiment, the processor 1001 in the automobile domain controller will load the executable files corresponding to the processes of one or more application programs into the memory 1002 according to the following instructions, and the processor 1001 will run the application programs stored in the memory 1002, thereby realizing various functions, as follows:

[0174] The software detection module detects at least one of the integrated circuits to obtain a fault detection result.

[0175] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0176] To this end, an embodiment of the present invention provides a computer-readable storage medium, which may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc. A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in any one of the fault detection methods provided in the embodiments of the present invention. For example, the computer program may be loaded by a processor to execute the following steps:

[0177] The software detection module detects at least one of the integrated circuits to obtain a fault detection result.

[0178] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the detailed description of other embodiments above, and will not be repeated here.

[0179] In specific implementation, the above units or structures can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units or structures can refer to the previous method embodiments, which will not be repeated here.

[0180] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0181] Furthermore, an embodiment of the present application also provides a vehicle, comprising a fault detection system as described in any of the above embodiments, and a vehicle domain controller as described in any of the above embodiments.

[0182] The above is a detailed introduction to a fault detection system, method, automotive domain controller, storage medium and vehicle provided in the embodiments of the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A fault detection system, It is characterized in that include: at least one integrated circuit; a software detection module, the software detection module being connected to at least one of the integrated circuits, and the software detection module being used to detect a fault detection result of at least one of the integrated circuits; wherein, through the software detection module, for at least one of the integrated circuits, at least one of the fault data of the fault register, the status data of the status register, and the fault indication data of the fault indication pin in the integrated circuit is obtained; determining a fault detection result according to at least one of the fault data, the state data and the fault indication data; Before acquiring at least one of the fault data of the fault register in the integrated circuit, the status data of the status register, and the fault indication data of the fault indication pin, the method further includes: Acquire a target power source identifier of a first integrated circuit, wherein the first integrated circuit is an integrated circuit of at least one of the integrated circuits for which the fault detection result is empty or the fault detection result indicates that a fault exists; Obtaining power-on timing information corresponding to the first integrated circuit, the power-on timing information including a power-on duration of a power supply for the first integrated circuit, the power-on duration representing a time taken for a voltage parameter of the power supply to reach a preset stable voltage parameter; Determining a reset time according to the power-on duration and a power-on time corresponding to the first integrated circuit; The first integrated circuit is controlled to be reset according to the reset time.

2. The fault detection system according to claim 1, It is characterized in that The integrated circuit includes at least one of a fault register, a status register, and a fault indication pin; The software detection module includes: a collection unit, the collection unit being connected to at least one of the fault register, the status register and the fault indication pin, the collection unit being used to collect at least one of the fault data of the fault register, the status data of the status register and the fault indication data of the fault indication pin; a parsing unit, configured to parse at least one of the fault data, the state data and the fault indication data to obtain a fault detection result; A processing unit is used to determine a target detection result of the integrated circuit according to the fault detection result.

3. A fault detection method, It is characterized in that Applied to the fault detection system according to claim 1 or 2, the fault detection system comprises a software detection module and at least one integrated circuit, the method comprises: Obtaining, for at least one of the integrated circuits, through the software detection module, at least one of the fault data of a fault register, the status data of a status register, and the fault indication data of a fault indication pin in the integrated circuit; determining a fault detection result according to at least one of the fault data, the state data and the fault indication data; Before acquiring at least one of the fault data of the fault register in the integrated circuit, the status data of the status register, and the fault indication data of the fault indication pin, the method includes: performing a power-on reset on at least one of the integrated circuits; The power-on resetting of at least one of the integrated circuits comprises: Acquire a target power source identifier of a first integrated circuit, wherein the first integrated circuit is an integrated circuit of at least one of the integrated circuits for which the fault detection result is empty or the fault detection result indicates that a fault exists; Obtaining power-on timing information corresponding to the first integrated circuit, the power-on timing information including a power-on duration of a power supply for the first integrated circuit, the power-on duration representing a time taken for a voltage parameter of the power supply to reach a preset stable voltage parameter; Determining a reset time according to the power-on duration and a power-on time corresponding to the first integrated circuit; The first integrated circuit is controlled to be reset according to the reset time.

4. The fault detection method according to claim 3, It is characterized in that The determining of the fault detection result according to at least one of the fault data, the state data and the fault indication data comprises: If the fault data is not empty, and / or the state data has an abnormal state, and / or the fault indication data has a fault indication, then the fault detection result is determined to be that a fault exists.

5. The fault detection method according to claim 4, It is characterized in that The method further comprises: If the fault detection result is that a fault exists, a target detection result of the integrated circuit is determined according to the fault type of the fault.

6. The fault detection method according to claim 5, It is characterized in that The step of determining a target detection result of the integrated circuit according to the fault type of the fault includes: Determining a fault level of the fault and a target detection result corresponding to the fault level according to the fault type of the fault; The fault level includes a primary fault and a secondary fault, wherein the primary fault indicates that the integrated circuit cannot be used normally, and the secondary fault indicates that the integrated circuit can be used normally.

7. The fault detection method according to claim 6, It is characterized in that Determining the target detection result corresponding to the fault level includes: If the fault level is the first-level fault, determining that the target detection result is a failed state; If the fault level is the secondary fault, or the fault detection result is that there is no fault, then it is determined that the target detection result is a pass state.

8. The fault detection method according to claim 7, It is characterized in that The method further comprises: If the target detection result is the passing state, then counting the continuous cumulative number of the passing state; If the continuous accumulated number of times is less than the set number threshold, the step of detecting at least one of the integrated circuits through the software detection module is executed until the continuous accumulated number of times reaches the set number threshold.

9. The fault detection method according to claim 8, It is characterized in that The method further comprises: If the target detection result is the failed state, the continuous accumulated times are cleared to zero, and the step of detecting at least one of the integrated circuits through the software detection module is performed.

10. The fault detection method according to any one of claims 3 to 9, It is characterized in that Before detecting at least one of the integrated circuits by the software detection module to obtain a fault detection result, the method further includes: A hardware self-check is performed on at least one of the integrated circuits, and when the hardware self-check fails, it is determined that a power-on voltage of the at least one integrated circuit tends to be stable.

11. The fault detection method according to claim 3, It is characterized in that The controlling the first integrated circuit to reset according to the reset time includes: Identify a reset pin corresponding to a target power identifier of the first integrated circuit; According to the reset time, each of the reset pins is controlled to perform reset adjustment on the first integrated circuit.

12. The fault detection method according to claim 3, It is characterized in that The determining the reset time according to the power-on time and the power-on time corresponding to the first integrated circuit includes: If the first integrated circuit includes at least two soft power-on power supplies, then obtaining the power-on durations corresponding to the soft power-on power supplies in the power-on timing information, and determining a maximum power-on duration among the power-on durations; A reset time is determined according to the maximum power-on time and the power-on time corresponding to the first integrated circuit.

13. The fault detection method according to claim 3, It is characterized in that The power-on resetting of at least one of the integrated circuits comprises: During the power-on reset process, at least one of the write operations is performed, and the write operation includes: writing the fault data generated in the integrated circuit into the corresponding fault register; writing the status data generated in the integrated circuit into the corresponding status register; and writing all fault indication data generated in the integrated circuit into the fault indication pin.

14. A car domain controller, It is characterized in that The automobile domain controller comprises: one or more processors; Memory; and One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the fault detection method according to any one of claims 3 to 13.

15. A computer-readable storage medium, It is characterized in that A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in the fault detection method according to any one of claims 3 to 13.

16. A vehicle, It is characterized in that It comprises the fault detection system as claimed in any one of claims 1 to 2, and the automobile domain controller as claimed in claim 14.

Citation Information

Patent Citations

  • Reset circuit for multi-power-supply system

    CN102522968A

  • Fault detection method of automatic driving controller and automatic driving controller

    CN110308732A

  • Power-on reset device of multi-power-supply system

    CN111510122A

  • Method for acquiring fault information of fault integration module and related equipment thereof

    CN115408184A

  • Failure detection system for detecting failure of functional blocks of integrated circuits

    US5617429A