MPU rapid failure monitoring method and device, vehicle and storage medium

Abstract

The invention relates to the technical field of vehicles, in particular to an MPU rapid failure monitoring method and device, a vehicle and a storage medium, and the method comprises the steps: judging whether a microprocessor unit MPU is in a power-on state, if the MPU is in the power-on state, judging whether a heartbeat signal of the MPU is received within a preset time, and if the heartbeat signal of the MPU is not received within the preset time, judging whether the MPU is in the power-on state; and if not, judging that the MPU is in a failure state, and resetting and restarting the MPU through the power supply control pin. Therefore, the problems that the voltage monitoring cannot cover all heartbeat monitoring, the delay is high, whether the system fails or not can be judged in a long time in the heartbeat monitoring aspect, and rapid failure judgment and recovery cannot be realized in the early starting stage of the MPU, so that the user experience is reduced and the like are solved; the MCU can quickly monitor the failure of the MPU system and reset the MPU system by the aid of the UART / SPI during startup, so that the failure recovery time is remarkably shortened, and a user is prevented from perceiving abnormities.

Description

Technical Field

[0001] This application relates to the technical field of vehicles, and particularly relates to a monitoring method, device, vehicle and storage medium for rapid failure of an MPU. Background Art

[0002] With the development of intelligent cockpit technology, its application in passenger cars and commercial vehicles is becoming more and more extensive. The cockpit domain controller integrates functions such as multimedia entertainment, vehicle settings, and air conditioning control, and conducts data interaction with other electronic control units. It is an important part of the intelligent cockpit. However, in a complex vehicle environment, especially during system startup or operation, if an MPU (Microprocessor Unit) fails, it will seriously affect the user experience.

[0003] In related technologies, the detection of the survival state of the MPU system mainly relies on the monitoring of instantaneous voltage jumps and the communication heartbeat link between the MCU (Microcontroller Unit) and the MPU.

[0004] However, the above methods have certain limitations. In terms of voltage jump monitoring, not all types of voltage waveform changes can be covered. For example, short-term (such as 10 ms) voltage fluctuations cannot be detected; in terms of the MCU-MPU heartbeat link, it depends on the establishment of communication after the Android system starts, so it takes a long time to determine whether the system fails, and rapid failure determination and recovery cannot be achieved in the early stage (within 10 seconds) of MPU startup, thus reducing the user experience, which urgently needs to be solved. Summary of the Invention

[0005] This application provides a monitoring method, device, vehicle and storage medium for rapid failure of an MPU to solve the problems that voltage monitoring cannot cover all, heartbeat monitoring has a high delay, and it takes a long time to determine whether the system fails in terms of heartbeat monitoring, and rapid failure determination and recovery cannot be achieved in the early stage of MPU startup, thus reducing the user experience.

[0006] The first aspect embodiment of this application provides a monitoring method for rapid failure of an MPU, including the following steps: determining whether the microprocessor unit MPU is in a powered-on state; if the MPU is in the powered-on state, determining whether a heartbeat signal of the MPU is received within a preset time; if the heartbeat signal of the MPU is not received within the preset time, determining that the MPU is in a failure state, and resetting and restarting the MPU through a power control pin.

[0007] Preferably, before determining whether the microprocessor unit MPU is in a powered-on state, it further includes:

[0008] Determine whether the domain controller is in the wake-up state;

[0009] If the domain controller is in the wake-up state, control the MCU to initialize, and after the initialization of the microcontroller unit MCU is completed, control the MPU to power on through the power control pin.

[0010] Preferably, before determining whether the heartbeat signal of the MPU is received within a preset time, it further includes:

[0011] Determine whether the MPU has completed initialization;

[0012] If the MPU has completed initialization, control the MPU to start the heartbeat signal service, and set the priority of the MPU heartbeat signal service to receive the heartbeat signal of the MPU according to the priority of the MPU heartbeat signal service.

[0013] Preferably, after determining whether the heartbeat signal of the MPU is received within a preset time, it further includes:

[0014] If the heartbeat signal of the MPU is received within the preset time, determine that the MPU is in the alive state;

[0015] Control the MPU to start, and after the MPU starts, register and load the UART (Universal Asynchronous Receiver Transmitter) / SPI (Serial Peripheral Interface) communication serial port, and control the application layer service to take over the heartbeat signal of the MPU.

[0016] Preferably, after determining that the MPU is in the failure state, it further includes:

[0017] Obtain the number of MPU failures;

[0018] Generate a corresponding reset and restart strategy based on the number of MPU failures, so that when the number of MPU failures reaches the target number of failures, reset and restart the MPU based on the reset and restart strategy corresponding to the target number of failures, and record the failure information of each reset and restart.

[0019] The second aspect of the present application provides a monitoring device for the rapid failure of an MPU, including: a first judgment module, configured to judge whether a microprocessor unit (MPU) is in a powered-on state; a second judgment module, configured to judge whether a heartbeat signal of the MPU is received within a preset time if the MPU is in the powered-on state; a control module, configured to determine that the MPU is in a failure state if the heartbeat signal of the MPU is not received within the preset time, and reset and restart the MPU through a power control pin.

[0020] Preferably, before judging whether the microprocessor unit (MPU) is in a powered-on state, the first judgment module is further configured to:

[0021] Judge whether a domain controller is in a wake-up state;

[0022] If the domain controller is in the wake-up state, control the MCU to be initialized, and after the initialization of the microcontroller unit (MCU) is completed, control the MPU to be powered on through a power control pin.

[0023] Preferably, before judging whether the heartbeat signal of the MPU is received within a preset time, the second judgment module is further configured to:

[0024] Judge whether the MPU is initialized;

[0025] If the MPU is initialized, control the MPU to start a heartbeat signal service, and set the priority of the MPU heartbeat signal service to receive the heartbeat signal of the MPU according to the priority of the MPU heartbeat signal service.

[0026] Preferably, after judging whether the heartbeat signal of the MPU is received within a preset time, the second judgment module further includes:

[0027] If the heartbeat signal of the MPU is received within the preset time, determine that the MPU is in a survival state;

[0028] Control the MPU to start, and after the MPU starts, register and load a UART / SPI communication serial port, and control the application layer service to take over the heartbeat signal of the MPU.

[0029] Preferably, after determining that the MPU is in a failure state, the control module is further configured to:

[0030] Obtain the number of times the MPU fails;

[0031] Generate a corresponding reset and restart strategy based on the number of MPU failures, so that when the number of MPU failures reaches the target number of failures, reset and restart the MPU based on the reset and restart strategy corresponding to the target number of failures, and record the failure information for each reset and restart.

[0032] An embodiment of the third aspect of the present application provides a vehicle, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the program to implement the method for monitoring rapid failure of the MPU as described in the above embodiment.

[0033] An embodiment of the fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, and the program is executed by a processor to implement the method for monitoring rapid failure of the MPU as described in the above embodiment.

[0034] Therefore, the present application has at least the following beneficial effects: Determine whether the microprocessor unit (MPU) is in the powered-on state. If the MPU is in the powered-on state, determine whether a heartbeat signal of the MPU is received within a preset time. If the heartbeat signal of the MPU is not received within the preset time, determine that the MPU is in a failure state, and reset and restart the MPU through the power control pin. Thus, problems such as voltage monitoring being unable to cover all cases, high heartbeat monitoring latency, and requiring a long time to determine whether the system has failed in heartbeat monitoring, and being unable to achieve rapid failure determination and recovery in the early stage of MPU startup, thereby reducing the user experience, are solved. By quickly enabling the MCU to monitor the MPU system failure and reset it by means of UART / SPI at startup, the fault recovery time is significantly shortened, and the user is prevented from perceiving abnormalities.

[0035] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present application. Description of the Drawings

[0036] The above and / or additional aspects and advantages of the present application will become apparent and easy to understand from the following description of the embodiments in conjunction with the drawings, where:

[0037] Figure 1 It is a flowchart of a method for monitoring rapid failure of an MPU according to an embodiment of the present application;

[0038] Figure 2 It is a schematic diagram of a system architecture according to an embodiment of the present application;

[0039] Figure 3 It is a flowchart of an overall solution according to an embodiment of the present application;

[0040] Figure 4An exemplary diagram of a monitoring device for rapid failure of an MPU according to an embodiment of the present application;

[0041] Figure 5 A schematic structural diagram of a vehicle according to an embodiment of the present application.

[0042] Description of reference numerals: 100 - First judgment module; 200 - Second judgment module; 300 - Control module. Detailed implementation manners

[0043] The embodiments of the present application will be described in detail below. The examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals represent the same or similar elements or elements with the same or similar functions from beginning to end. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present application, and should not be construed as a limitation to the present application.

[0044] The monitoring method, device, vehicle and storage medium for rapid failure of an MPU according to an embodiment of the present application will be described below. Specifically, Figure 1 It is a schematic flowchart of a monitoring method for rapid failure of an MPU provided by an embodiment of the present application.

[0045] As Figure 1 shown, the monitoring method for rapid failure of the MPU includes the following steps:

[0046] In step S101, it is judged whether the microprocessor unit MPU is in the powered-on state.

[0047] Preferably, before judging whether the microprocessor unit MPU is in the powered-on state, it further includes: judging whether the domain controller is in the wake-up state; if the domain controller is in the wake-up state, controlling the MCU to be initialized, and after the initialization of the microcontroller unit MCU is completed, controlling the MPU to be powered on through the power control pin.

[0048] Specifically, due to the complex vehicle environment, the domain controller may encounter various problems. Especially when the system fails during startup or function usage, it will seriously affect the user experience. The voltage instantaneous jump monitoring in the related technology cannot cover all voltage waveforms, and it is also possible that extremely short voltage jumps, such as a 10-ms voltage jump, cannot be monitored. The establishment of the communication heartbeat link between the MCU and the MPU also mostly occurs when the Android system is about to / formally enter the home page display, and it requires a period of time (such as 30 seconds / 1 minute) to judge the link loss time. Therefore, the above phenomena may all cause the user to wait for a long time before the domain controller restarts the screen after the vehicle is started, thus reducing the user's driving experience. Therefore, the embodiment of the present application provides a method that can quickly enable the MCU to detect the failure of the MPU system and automatically recover it by means of the UART / SPI serial port when starting up, so as to reduce the black screen and crash time perceived by the user and improve the user's driving experience.

[0049] Specifically, as Figure 2 and Figure 3 shown, first, the system architecture in the embodiment of the present application is introduced, which mainly includes an MCU and an MPU. Among them, there is a UART / SPI between the MCU and the MPU for serial communication, including configuring serial communication parameters (such as baud rate, data bits, stop bits, etc.). When the key-controlled power is powered on or the network wakes up, that is, when the domain controller is in the wake-up state, the MCU is controlled to be initialized, and after the MCU initialization is completed, the MPU is powered on through the power control pin.

[0050] In step S102, if the MPU is in the powered-on state, it is judged whether a heartbeat signal of the MPU is received within a preset time.

[0051] Preferably, before judging whether a heartbeat signal of the MPU is received within a preset time, it further includes: judging whether the MPU has completed initialization; if the MPU has completed initialization, controlling the MPU to start the heartbeat signal service and setting the priority of the MPU heartbeat signal service, so as to receive the heartbeat signal of the MPU according to the priority of the MPU heartbeat signal service.

[0052] Among them, the preset time can be set by those skilled in the art according to actual test requirements, or obtained through a limited number of computer simulations, and no specific limitation is made here.

[0053] Specifically, after the MPU is powered on, a heartbeat link between the MPU and the MCU needs to be established. That is, after the MPU is powered on, the MPU needs to complete driver initialization, and after the MPU is initialized, control the MPU to start the heartbeat signal service. This heartbeat signal service registers and loads the UART / SPI serial port and starts sending heartbeat link data (i.e., heartbeat signals) to the MCU. Among them, the first heartbeat data should be sent within a preset time (e.g., 10 s) after the MPU is powered on. Then 10 seconds is the MPU system failure determination time agreed upon by the MCU and the MPU.

[0054] Furthermore, to prevent the heartbeat signal service from being blocked by low-priority tasks (such as non-critical driver loading, file system mounting) during the initialization process of the MPU, which may cause unnecessary resets due to heartbeat sending delays, triggering false MCU failure judgments (10-second timeout), etc., the embodiment of this application can further set the priority of the MPU heartbeat signal service. That is to say, in the system, the heartbeat signal service (or kernel thread) is set to a real-time priority (higher priority than ordinary tasks). Through the real-time scheduling policy, it is ensured that the heartbeat signal service can preempt the CPU (even if other drivers are in a busy wait state) resources in any case. At the same time, the UART / SPI controller needs to be configured as a high-priority peripheral (such as DMA (Direct Memory Access) transfer) to avoid data sending delays caused by bus contention, and lock the serial port resources during the initialization of the heartbeat signal service to prevent other modules from occupying them, thereby ensuring the real-time performance and reliability of monitoring MPU failure.

[0055] Specifically, as Figure 3 shown, when the MPU is in the powered-on state, it is necessary to determine the survival state of the MPU based on the signal link reception situation between the MCU and the MPU. That is, after the MPU is powered on, the MPU needs to send a heartbeat signal to the MCU, and the MCU judges whether it receives the heartbeat signal sent by the MPU within 10 s, so as to control the MPU to reset and restart or take over the heartbeat link with the MCU according to the reception result.

[0056] In step S103, if the heartbeat signal of the MPU is not received within the preset time, it is determined that the MPU is in a failure state, and the MPU is reset and restarted through the power control pin.

[0057] Specifically, due to the specific voltage waveform during startup, there may be a momentary low voltage that cannot be monitored by the MCU, resulting in the momentary voltage dropping so low that the MPU cannot work and fails. However, after the MCU controls the MPU to power on, it is considered that the MPU should be in a normal state. But at this time, the MPU is actually in a failed state and cannot accurately feedback to the MCU. Therefore, at this time, the MCU thinks that the MPU is still in a live state, or the MPU cannot start and initialize normally due to a system error during the power-on process. Therefore, for the above possible abnormal situations, it is necessary to further determine the heartbeat link communication between the MCU and the MPU.

[0058] Specifically, if the MCU does not receive the heartbeat signal of the MPU within 10s, it is determined that the MPU is in a failed state. That is to say, if the MCU does not receive the heartbeat signal of the MPU within 10s, it means that the MPU has failed. At this time, the power pin of the MPU can be pulled low and then pulled high (i.e., powered off and then powered on) in time through the power control pin, realizing the automatic reset and restart of the MPU, thus reducing the waiting time of the user.

[0059] Optionally, if the MPU is in a failed state, at this time, the MPU can also be controlled to enter the minimized system mode (only the serial port driver and the heartbeat service are retained), and the repair firmware is downloaded through the MCU.

[0060] Preferably, after determining that the MPU is in a failed state, it further includes: obtaining the number of MPU failures; generating a corresponding reset and restart strategy based on the number of MPU failures, so that when the number of MPU failures reaches the target number of failures, the MPU is reset and restarted based on the reset and restart strategy corresponding to the target number of failures, and the failure information of each reset and restart is recorded.

[0061] Specifically, if the MPU is in the first failure state, it means that there may be conventional voltage jumps, driver loading failures, etc. at this time. Therefore, the MPU can be directly reset and restarted through the power control pin; if the MPU fails twice in a row, it means that the domain controller is in a high temperature or there are stability problems such as power supply noise at this time. Therefore, the MPU can be reset and restarted through the power control pin + the main frequency of the MPU is reduced for recovery; if the MPU fails three times or more in a row, it means that the system software may be damaged at this time. Therefore, it can be recovered by switching to the backup firmware (such as restoring the factory image).

[0062] For example, when the MPU is at the target number of failures (for example, 2 times), the MPU is reset and restarted based on the reset and restart strategy corresponding to the number of failures of 2 times, that is, the MPU is reset and restarted through the power control pin + the main frequency of the MPU is reduced for recovery, and the failure information of the corresponding reset and restart is recorded, such as recording the reset reason (heartbeat timeout / watchdog timeout), timestamp, environmental data (voltage, temperature), for subsequent diagnostic analysis.

[0063] Thus, during the startup phase of the embodiments of the present application, a service is added at the bottom layer to establish a serial port heartbeat link with the MCU, and different voltage waveforms are used for testing. The results show that for some specific voltage waveforms (instantaneous voltage jump, voltage dropping below 9V, jump time within 50ms), the MPU will fail and stop working. However, this method can effectively monitor the failure of the MPU system and perform reset and restart recovery within a short time (10 seconds), thus effectively avoiding the long-term black screen and crash of the MPU due to instantaneous low voltage or other abnormalities during the startup phase. For the user perception, it only takes a few more seconds for the screen to light up this time, thereby effectively improving the user experience.

[0064] Preferably, after determining whether a heartbeat signal of the MPU is received within a preset time, it further includes: if the heartbeat signal of the MPU is received within the preset time, it is determined that the MPU is in a live state; the MPU is controlled to start, and after the MPU starts, the UART / SPI communication serial port is registered and loaded, and the application layer service is controlled to take over the heartbeat signal of the MPU.

[0065] Specifically, as Figure 3 shown, if the MCU receives the heartbeat signal of the MPU within the preset time (for example, 10s), it indicates that the MPU is in a live state at this time. Thus, after the MPU normally completes startup and is about to officially enter the home page, the bottom layer service receives the bootcomplete status (this status is the startup completion status), closes and releases the UART / SPI serial port occupancy, and the communication application of the application layer registers and loads the UART / SPI serial port and takes over the heartbeat signal of the MPU.

[0066] In summary, in the embodiments of the present application, the MCU is responsible for power management during startup, and controls the MPU to power on when the key-controlled power is powered on or the network wakes up. Subsequently, after the MPU completes driver initialization, it pulls up the service and sends a heartbeat signal through UART / SPI. If the MCU does not receive the heartbeat signal sent by the MPU within 10 seconds, it is considered that the MPU fails, and the MPU is reset and restarted through the power control pin. In addition, once the system starts up normally, the bottom layer service will release the UART / SPI resources for the application layer to use, thereby improving the user experience and reducing the long-term black screen waiting caused by system failures.

[0067] The monitoring method for the rapid failure of the MPU according to the embodiments of the present application determines whether the microprocessor unit (MPU) is in the powered-on state. If the MPU is in the powered-on state, it determines whether a heartbeat signal of the MPU is received within a preset time. If the heartbeat signal of the MPU is not received within the preset time, it determines that the MPU is in a failure state and resets and restarts the MPU through the power control pin. Thus, it solves the problems that voltage monitoring cannot cover all cases, the heartbeat monitoring has a high delay, and it takes a long time to determine whether the system fails in terms of heartbeat monitoring, and it is impossible to achieve rapid failure determination and recovery in the early stage of MPU startup, thereby reducing the user experience. By quickly enabling the MCU to monitor the failure of the MPU system and reset it by means of UART / SPI at startup, the fault recovery time is significantly shortened, and the user is prevented from perceiving abnormalities.

[0068] Next, a monitoring device for the rapid failure of the MPU according to the embodiments of the present application will be described with reference to the accompanying drawings.

[0069] Figure 4 It is a block diagram of the monitoring device for the rapid failure of the MPU according to the embodiments of the present application.

[0070] As Figure 4 shown, the monitoring device 10 for the rapid failure of the MPU includes: a first judgment module 100, a second judgment module 200, and a control module 300.

[0071] Among them, the first judgment module 100 is used to judge whether the microprocessor unit (MPU) is in the powered-on state;

[0072] The second judgment module 200 is used to judge whether a heartbeat signal of the MPU is received within a preset time if the MPU is in the powered-on state;

[0073] The control module 300 is used to determine that the MPU is in a failure state if the heartbeat signal of the MPU is not received within the preset time, and reset and restart the MPU through the power control pin.

[0074] Preferably, before judging whether the microprocessor unit (MPU) is in the powered-on state, the first judgment module 100 is further used to:

[0075] Judge whether the domain controller is in the wake-up state;

[0076] If the domain controller is in the wake-up state, control the MCU to be initialized, and after the initialization of the microcontroller unit (MCU) is completed, control the MPU to be powered on through the power control pin.

[0077] Preferably, before judging whether a heartbeat signal of the MPU is received within a preset time, the second judgment module 200 is further used to:

[0078] Determine whether the MPU has completed initialization;

[0079] If the MPU has completed initialization, control the MPU to start the heartbeat signal service and set the priority of the MPU heartbeat signal service to receive the heartbeat signal of the MPU according to the priority of the MPU heartbeat signal service.

[0080] Preferably, after determining whether the heartbeat signal of the MPU is received within a preset time, the second determination module 200 further includes:

[0081] If the heartbeat signal of the MPU is received within the preset time, determine that the MPU is in a live state;

[0082] Control the MPU to start, and after the MPU starts, register and load the UART / SPI communication serial port, and control the application layer service to take over the heartbeat signal of the MPU.

[0083] Preferably, after determining that the MPU is in a failure state, the control module 300 is further configured to:

[0084] Obtain the number of MPU failures;

[0085] Generate a corresponding reset and restart policy based on the number of MPU failures, so as to reset and restart the MPU based on the reset and restart policy corresponding to the target number of failures when the number of MPU failures is at the target number of failures, and record the failure information of each reset and restart.

[0086] It should be noted that the foregoing explanation of the embodiment of the method for monitoring the rapid failure of the MPU also applies to the device for monitoring the rapid failure of the MPU in this embodiment, and will not be elaborated here.

[0087] Figure 5 The structural schematic diagram of the vehicle provided by the embodiment of the present application. The vehicle may include:

[0088] A memory 501, a processor 502, and a computer program stored on the memory 501 and executable on the processor 502.

[0089] When the processor 502 executes the program, it implements the method for monitoring the rapid failure of the MPU provided in the foregoing embodiment.

[0090] Further, the vehicle further includes:

[0091] A communication interface 503 for communication between the memory 501 and the processor 502.

[0092] The memory 501 is used to store a computer program executable on the processor 502.

[0093] The memory 501 may include a high-speed RAM (Random Access Memory) memory and may also include a non-volatile memory, such as at least one disk memory.

[0094] If the memory 501, the processor 502, and the communication interface 503 are implemented independently, the communication interface 503, the memory 501, and the processor 502 can be interconnected via a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0095] Optionally, in a specific implementation, if the memory 501, the processor 502, and the communication interface 503 are integrated on a single chip, the memory 501, the processor 502, and the communication interface 503 can communicate with each other through an internal interface.

[0096] The processor 502 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0097] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the monitoring method for the rapid failure of the MPU as described above is implemented.

[0098] In the description of this specification, the descriptions with reference to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of this application. In this specification, the schematic expressions of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or N embodiments or examples. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0099] 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 specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" can explicitly or implicitly include at least one of such features. In the description of this application, the meaning of "N" is at least two, such as two, three, etc., unless otherwise specifically and clearly defined.

[0100] Any process or method description shown in a flowchart or described in other ways herein can be understood as representing a module, segment, or part of code including one or N executable instructions for implementing a customized logic function or process, and the scope of the preferred embodiments of this application includes additional implementations, where the functions can be executed in a substantially simultaneous manner or in a reverse order according to the involved functions, rather than in the order shown or discussed, which should be understood by those skilled in the technical field to which the embodiments of this application belong.

[0101] It should be understood that each part of this application can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware as in another embodiment, it can be implemented by a combination of any one or more of the following technologies well known in the art: discrete logic circuits with logic gate circuits for implementing logic functions on data signals, application specific integrated circuits with suitable combinational logic gate circuits, programmable gate arrays, field programmable gate arrays, etc.

[0102] Those of ordinary skill in the technical field of this application can understand that all or part of the steps carried by the method for implementing the above embodiments can be completed by a program instructing relevant hardware, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0103] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present application. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

Claims

1. A monitoring method for rapid failure of an MPU, characterized in that, It includes the following steps: Determine whether the microprocessor unit MPU is in the powered-on state; If the MPU is in the powered-on state, determine whether a heartbeat signal of the MPU is received within a preset time; If the heartbeat signal of the MPU is not received within the preset time, determine that the MPU is in a failure state, and reset and restart the MPU through the power control pin.

2. The method according to claim 1, wherein Before determining whether the microprocessor unit MPU is in the powered-on state, it further includes: Determine whether the domain controller is in the wake-up state; If the domain controller is in the wake-up state, control the MCU to be initialized, and after the initialization of the microcontroller unit MCU is completed, control the MPU to be powered on through the power control pin.

3. The method according to claim 1, wherein Before determining whether a heartbeat signal of the MPU is received within a preset time, it further includes: Determine whether the MPU has completed initialization; If the MPU has completed initialization, control the MPU to start the heartbeat signal service, and set the priority of the MPU heartbeat signal service to receive the heartbeat signal of the MPU according to the priority of the MPU heartbeat signal service.

4. The method according to claim 1, characterized in that, After determining whether a heartbeat signal of the MPU is received within a preset time, it further includes: If the heartbeat signal of the MPU is received within the preset time, determine that the MPU is in the alive state; Control the MPU to start, and after the MPU starts, register and load the UART / SPI communication serial port, and control the application layer service to take over the heartbeat signal of the MPU.

5. The method according to claim 1, wherein After determining that the MPU is in the failure state, it further includes: Obtain the MPU failure times; Generate a corresponding reset and restart strategy based on the MPU failure times, so as to reset and restart the MPU based on the reset and restart strategy corresponding to the target failure times when the MPU failure times reach the target failure times, and record the failure information of each reset and restart.

6. A monitoring device for rapid failure of an MPU, characterized in that, It includes: The first judgment module is used to judge whether the microprocessor unit MPU is in the powered-on state; The second judgment module is used to judge whether a heartbeat signal of the MPU is received within a preset time if the MPU is in the powered-on state; The control module is used to determine that the MPU is in a failure state if the heartbeat signal of the MPU is not received within the preset time, and reset and restart the MPU through the power control pin.

7. The device according to claim 6, wherein Before judging whether the microprocessor unit MPU is in the powered-on state, the first judgment module is further used to: Judge whether the domain controller is in the wake-up state; If the domain controller is in the wake-up state, control the MCU to be initialized, and after the initialization of the microcontroller unit MCU is completed, control the MPU to be powered on through the power control pin.

8. The device according to claim 6, characterized in that, Before judging whether a heartbeat signal of the MPU is received within a preset time, it is further used to: Judge whether the MPU has completed initialization; If the MPU has completed initialization, control the MPU to start the heartbeat signal service, and set the priority of the MPU heartbeat signal service to receive the heartbeat signal of the MPU according to the priority of the MPU heartbeat signal service.

9. A vehicle, characterized in that, It includes: A memory, a processor, and a computer program stored on the memory and executable on the processor, the processor executing the program to implement the monitoring method for rapid failure of the MPU as described in any one of claims 1-5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the monitoring method for rapid failure of the MPU as described in any one of claims 1-5.

Images