Vehicle machine exception handling method, microcontroller, electronic equipment and storage medium

The microcontroller detects the vehicle status and ADAS enabled status, determines the vehicle abnormality handling strategy, solves the safety hazards caused by the vehicle automatic restart in the driving state, and realizes the safety and rapid failure of the vehicle restart during driving. repair.

CN118907129APending Publication Date: 2024-11-08ZHEJIANG GEELY HLDG GRP CO LTD +1
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202410942964.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-15
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

When the car machine has abnormalities while driving, automatic restart may cause the driver to be unable to use the car machine normally, causing safety hazards.

Method used

The microcontroller detects whether the vehicle is in a driving state, and determines the abnormality handling strategy based on the enabled state of the Advanced Driver Assistance System (ADAS) and the car machine abnormal type, controls the restart timing of the system on-chip to ensure that the system is avoided in the driving state. Ineffective.

Benefits of technology

During the vehicle driving, by accurately controlling the restart timing of the system on the chip, driving safety is improved, the safety of the driver and passengers are ensured, and the fault is quickly repaired when the vehicle is not in the driving state.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118907129A_ABST
    Figure CN118907129A_ABST
Patent Text Reader

Abstract

The invention relates to the field of vehicle-mounted information entertainment product exception handling, in particular to a vehicle-mounted information entertainment product exception handling method, a microcontroller, electronic equipment and a storage medium. The vehicle-mounted machine exception handling method is applied to a microcontroller in a vehicle-mounted machine core, the microcontroller is in communication connection with a system on chip in the vehicle-mounted machine core, an advanced driving assistance system (ADAS) is configured in the system on chip, a vehicle-mounted machine chip is configured in a vehicle-mounted machine, the vehicle-mounted machine is configured in a vehicle, and the vehicle-mounted machine exception handling method comprises the following steps: if the vehicle-mounted machine is exceptional, the vehicle-mounted machine is not exceptional; detecting whether the vehicle is in a driving state; if the vehicle is in a non-driving state, controlling the on-chip system to restart; if the vehicle is in the driving state, obtaining the starting state of the ADAS and the abnormal type of the vehicle machine; and based on the starting state of the ADAS and the abnormal type of the in-vehicle infotainment device, determining an in-vehicle infotainment device abnormity processing strategy. According to the invention, the driving safety of the vehicle can be ensured when the system on chip is restarted.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle computer abnormality processing, and specifically to a vehicle computer abnormality processing method, a microcontroller, an electronic device and a storage medium. Background Art

[0002] Car computer refers to the abbreviation of the in-vehicle infotainment product installed in the vehicle. The car computer can functionally realize information communication between people and cars, cars and the outside world, and cars and cars.

[0003] The car computer may have abnormalities during operation, such as black screen, abnormal sound broadcast, abnormal screen display, etc. In the case of abnormalities, the car computer will generally resume normal operation by automatically restarting.

[0004] However, the automatic restart of the car computer will cause the driver to be unable to use the car computer normally for a period of time, which may cause safety hazards when the vehicle is driving. Summary of the invention

[0005] In view of the above, an embodiment of the present application provides a vehicle computer exception handling method, a microcontroller, an electronic device and a storage medium, which are intended to ensure the driving safety of the vehicle when the on-chip system is restarted.

[0006] In a first aspect, an embodiment of the present application provides a vehicle computer abnormality processing method, which is applied to a microcontroller in a vehicle computer chip, wherein the microcontroller is communicatively connected to a system-on-chip in the vehicle computer chip, wherein an advanced driver assistance system ADAS is configured in the system-on-chip, wherein the vehicle computer chip is configured in a vehicle computer, and wherein the vehicle computer is configured in a vehicle, wherein the vehicle computer abnormality processing method comprises:

[0007] If the vehicle computer is abnormal, detecting whether the vehicle is in a driving state;

[0008] If the vehicle is in a non-driving state, controlling the system on chip to restart;

[0009] If the vehicle is in a driving state, obtaining the activation state of the ADAS and the abnormal type of the vehicle computer;

[0010] Based on the activation state of the ADAS and the abnormality type of the vehicle computer, a vehicle computer abnormality handling strategy is determined.

[0011] In some embodiments, based on the activation state of the ADAS and the abnormal type of the vehicle computer, determining a vehicle computer abnormality handling strategy includes:

[0012] If the abnormality type of the vehicle computer includes other abnormality types except the vehicle computer communication abnormality, determining whether the ADAS is currently in an on state or an off state based on the activation state of the ADAS;

[0013] Wherein, the vehicle-computer communication abnormality indicates that the communication between the microcontroller and the system on chip is abnormal;

[0014] If the ADAS is currently in an off state, controlling the system on chip to restart;

[0015] If the ADAS is currently in an on state, after the vehicle is controlled to issue a driver takeover prompt, the system on chip is controlled to restart.

[0016] In some embodiments, controlling the vehicle to issue a driver takeover prompt includes:

[0017] If the abnormality type includes abnormal sound playback of the vehicle computer, and the screen display of the vehicle computer is normal, controlling the vehicle computer to issue a driver takeover prompt in the form of sound playback;

[0018] If the abnormality type includes abnormal display of the vehicle computer screen, and the sound playback of the vehicle computer is normal, controlling the vehicle computer to issue a driver takeover prompt in the form of a screen display;

[0019] If the abnormality type includes other abnormalities except for sound playing and screen display, controlling the vehicle computer to issue a driver takeover prompt in the form of screen display and / or sound playing;

[0020] If the abnormality type includes abnormal sound playback and abnormal screen display of the vehicle computer, the vehicle is controlled to issue a driver takeover prompt in the form of vehicle braking.

[0021] In some embodiments, if the ADAS is currently in an on state, after controlling the vehicle to issue a driver takeover prompt, controlling the system on chip to restart includes:

[0022] If the ADAS is currently in an on state and a preset sub-function in the ADAS is in an inactive state, after controlling the vehicle to issue a driver takeover prompt, controlling the system on chip to restart;

[0023] If the ADAS is currently in an on state and a preset sub-function in the ADAS is in an activated state, the system on chip is kept in an on state until the vehicle meets a preset system on chip restart condition, and the system on chip is controlled to restart;

[0024] The preset system-on-chip restart condition includes that the preset sub-function is in an inactive state, or the vehicle is in a non-driving state.

[0025] In some embodiments, after the controlling the vehicle to issue a driver takeover prompt, the method further includes:

[0026] Detect whether the driver has taken over the vehicle;

[0027] If the driver takes over the vehicle, controlling the system on chip to restart;

[0028] If the driver does not take over the vehicle, the vehicle is controlled again to issue a driver take over prompt, and after confirming that the driver takes over the vehicle, or after confirming that the ADAS is turned off, the system on chip is controlled to restart.

[0029] In some embodiments, based on the activation state of the ADAS and the abnormal type of the vehicle computer, determining a vehicle computer abnormality handling strategy includes:

[0030] If the abnormality type of the vehicle computer includes a vehicle computer communication abnormality, determining whether the ADAS is in an on state or an off state before the vehicle computer communication abnormality occurs based on the activation state of the ADAS;

[0031] Wherein, the vehicle-computer communication abnormality indicates that the communication between the microcontroller and the vehicle-computer chip is abnormal;

[0032] If the ADAS is in a turned-off state before the vehicle-machine communication abnormality occurs, controlling the on-chip system to restart;

[0033] If the ADAS is in the on-state before the vehicle-machine communication abnormality occurs, after the vehicle is controlled to brake, the on-chip system is controlled to restart.

[0034] In some embodiments, after controlling the vehicle to brake, and before controlling the system on chip to restart, the process further includes:

[0035] Detect whether the driver has taken over the vehicle;

[0036] If the driver takes over the vehicle, executing the step of controlling the system on chip to restart;

[0037] If the driver does not take over the vehicle, the vehicle is controlled to brake again, and after confirming that the driver has taken over the vehicle, the system on chip is controlled to restart.

[0038] In a second aspect, an embodiment of the present application further provides a microcontroller, which is used to execute the vehicle computer abnormality handling method described in the first aspect.

[0039] In some embodiments, the microcontroller includes a first core and a second core; the first core and the second core are communicatively connected;

[0040] The first core is used to detect whether the vehicle is in a driving state when an abnormality occurs in the vehicle computer; if the vehicle is not in a driving state, control the system on chip to restart;

[0041] The first core is further configured to send a restart detection request of the system on chip to the second core when the vehicle is in the driving state;

[0042] The second core is used to obtain the activation state of the ADAS and the abnormal type of the vehicle computer in response to the restart detection request; and determine the vehicle computer abnormality handling strategy based on the activation state of the ADAS and the abnormal type of the vehicle computer.

[0043] In some embodiments, when the vehicle computer abnormality handling strategy includes controlling the system on chip to restart, the second core is further used to send a response message to the first core to allow the system on chip to restart;

[0044] The first kernel is further configured to control the system on chip to restart after receiving the response message;

[0045] When the vehicle abnormality handling strategy includes controlling the vehicle to brake, the second core is further used to send a braking control signal to the first core;

[0046] The first core is also used to send the braking control signal to a zone controller in the vehicle after receiving the braking control signal, and the zone controller is used to control the vehicle to brake in response to the braking control signal.

[0047] In a third aspect, an embodiment of the present application further provides an electronic device, comprising a system on chip and the microcontroller described in the second aspect.

[0048] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the vehicle-machine abnormality handling method as described above.

[0049] In the embodiment of the present application, when the vehicle is not in driving state, if the vehicle computer has an abnormality, the microcontroller can control the on-chip system to restart immediately to quickly repair the fault, so that the vehicle can use the vehicle computer normally while in driving state.

[0050] When the vehicle is in motion, if an abnormality occurs in the vehicle computer, the microcontroller can determine the exception handling strategy of the on-chip system in combination with the enabled status of ADAS, so as to accurately control the restart timing of the on-chip system and avoid sudden failure of ADAS caused by sudden restart of the on-chip system. This is beneficial to improving the safety of the vehicle while driving, and thus can ensure the safety of the driver and passengers as much as possible when the vehicle computer is restarted while the vehicle is driving.

[0051] The microcontroller in the above-mentioned second aspect, the electronic device in the third aspect, and the computer-readable storage medium in the fourth aspect all correspond to the vehicle machine abnormality handling method in the first aspect. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 The figure is a schematic diagram of the structure of a vehicle computer chip provided according to an embodiment of the present application.

[0053] Figure 2 The present invention is a flowchart of the steps of a vehicle computer abnormality handling method provided according to an embodiment of the present application.

[0054] Figure 3 The flowchart is a sub-step flowchart of step 204 provided according to an embodiment of the present application.

[0055] Figure 4 The figure is a schematic diagram of the structure of a microcontroller provided according to an embodiment of the present application.

[0056] Figure 5 The present invention is a flowchart of the interaction steps between the first kernel and the second kernel provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0057] In order to more clearly understand the above-mentioned purposes, features and advantages of the present application, the present application is described in detail below in conjunction with the accompanying drawings and specific implementation methods. It should be noted that the implementation methods of the present application and the features in the implementation methods can be combined with each other without conflict.

[0058] In the following description, many specific details are set forth to facilitate a full understanding of the present application. The described implementations are only part of the implementations of the present application, rather than all the implementations.

[0059] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0060] It should be further noted that, in this article, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0061] In this application, "at least one" means one or more, and "more than one" means two or more than two. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The terms "first", "second", "third", "fourth", etc. (if any) in the specification, claims and drawings of this application are used to distinguish similar objects, rather than to describe a specific order or sequence.

[0062] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0063] The embodiments of the present application provide a vehicle computer abnormality processing method, a microcontroller, an electronic device and a computer-readable storage medium, which are described in detail below.

[0064] First, see Figure 1 , Figure 1 The schematic diagram of the structure of the vehicle chip 100 provided in the embodiment of the present application is shown in FIG. 1 , which can be configured in a vehicle, and the vehicle can be configured in a vehicle. An Advanced Driving Assistance System (ADAS) can be integrated in the vehicle.

[0065] The vehicle chip may include a system on chip (SoC). The system on chip may use a QNX (Quick Unix) operating system, but is not limited thereto. The system on chip may be integrated with a SoC power management module.

[0066] In some embodiments, the ADAS may be integrated into a system on a chip.

[0067] The embodiment of the present application configures ADAS on a system-on-chip, thereby realizing the integration of the cockpit and the driver, so that the cockpit and intelligent driving can support each other. For example, the system-on-chip in the embodiment of the present application can obtain ADAS-related information in a timely manner and perform corresponding processing, thereby improving the real-time and convenience of vehicle-computer abnormal processing. In addition, the integration of the cockpit and the driver is also conducive to reducing vehicle costs.

[0068] The vehicle computer chip may also include a microcontroller unit (MCU).

[0069] The microcontroller is in communication connection with the system on chip. For example, the microcontroller and the system on chip may communicate using a serial peripheral interface (SPI).

[0070] In some embodiments, the microcontroller may be used to detect whether an abnormality occurs in the vehicle computer and the type of abnormality so as to process the abnormality in the vehicle computer.

[0071] For example, the abnormality types of the vehicle computer may include abnormal sound playback and abnormal screen display, etc. If the on-chip system detects that the vehicle computer has such abnormalities, it may send a restart request of the on-chip system to the microcontroller. The restart request of the on-chip system may carry the abnormality type. If the microcontroller receives the restart request of the on-chip system, it may confirm that the vehicle computer has an abnormality and may determine the abnormality type of the vehicle computer based on the restart request.

[0072] In some embodiments, the abnormality type may also include vehicle-computer communication abnormality, where the vehicle-computer communication abnormality indicates abnormal communication between the microcontroller and the system on chip.

[0073] Specifically, when the communication between the system on chip and the microcontroller is normal, the system on chip will send a heartbeat to the microcontroller at regular intervals. If the microcontroller does not receive the heartbeat within a preset period of time, it means that there is a high probability of communication abnormality between the system on chip and the microcontroller, that is, the microcontroller can confirm that there is an abnormality in the vehicle computer, and the abnormality type includes vehicle computer communication abnormality.

[0074] It is understandable that when the abnormality type includes abnormal communication with the vehicle computer, it means that the microcontroller and the system on chip cannot communicate normally, which may also cause abnormal sound playback and abnormal screen display of the vehicle computer.

[0075] If the microcontroller confirms that an abnormality occurs in the vehicle computer, it can detect whether the vehicle is in a driving state; if the vehicle is in a non-driving state, control the on-chip system to restart; if the vehicle is in a driving state, obtain the enabled state of the ADAS and the abnormality type of the vehicle computer; based on the enabled state of the ADAS and the abnormality type of the vehicle computer, determine the vehicle computer abnormality handling strategy, thereby controlling the restart timing of the on-chip system.

[0076] In the embodiment of the present application, when the vehicle is not in driving state, if the vehicle computer has an abnormality, the microcontroller can control the on-chip system to restart immediately to quickly repair the fault, so that the vehicle can use the vehicle computer normally when the vehicle is in driving state.

[0077] When the vehicle is in motion, if an abnormality occurs in the vehicle computer, the microcontroller can determine the exception handling strategy of the on-chip system in combination with the enabled status of ADAS, so as to accurately control the restart timing of the on-chip system and avoid sudden failure of ADAS caused by sudden restart of the on-chip system. This is beneficial to improving the safety of the vehicle while driving, and thus can ensure the safety of the driver and passengers as much as possible when the vehicle computer is restarted while the vehicle is driving.

[0078] refer to Figure 2 As shown, Figure 2 This is a flowchart of the steps in an embodiment of the vehicle abnormality processing method of the present application, and the vehicle abnormality processing method is applied to the above-mentioned microcontroller. According to different requirements, the order of the steps in the flowchart can be changed, and some steps can be omitted.

[0079] The vehicle computer abnormality processing method may include:

[0080] Step 201, detecting whether the vehicle computer has any abnormality.

[0081] In some embodiments, step 201 may include: if the microcontroller receives a restart request from the system on chip, it may confirm that an abnormality occurs in the vehicle computer.

[0082] The restart request may include the abnormality type of the vehicle computer, such as abnormal sound playback and abnormal screen display.

[0083] In some embodiments, step 201 may further include: if the microcontroller does not receive the heartbeat of the system on chip for more than a preset time, it can be confirmed that an abnormality occurs in the vehicle computer, and the abnormality type includes abnormal communication with the vehicle computer.

[0084] The preset duration can be configured according to actual application requirements, for example, configured to 10 seconds, which is not limited in this embodiment of the present application.

[0085] If the vehicle computer has no abnormality, the process may continue to execute step 201 ; if the vehicle computer has an abnormality, the process may execute step 202 .

[0086] Step 202, detecting whether the vehicle is in a driving state.

[0087] The driving state is used to describe whether the vehicle is driving.

[0088] For example, when the vehicle is in a non-driving mode such as an abandoned mode, the vehicle's gear is in the parking gear (i.e., P gear), or the vehicle is stationary, it can be determined that the vehicle is in a non-driving state; if the vehicle is driving and the speed is greater than zero, it can be determined that the vehicle is in a driving state.

[0089] If the vehicle is not in a driving state, execute step 205; if the vehicle is in a driving state, execute steps 203 to 204.

[0090] Step 203, obtaining the activation status of the ADAS and the abnormal type of the vehicle computer.

[0091] The abnormal types of the vehicle computer may include abnormal sound playback, abnormal screen display, and abnormal vehicle computer communication, but are not limited thereto.

[0092] The enabled state can be used to describe whether ADAS is activated.

[0093] In the case where ADAS is activated, the enabled state may also include the sub-functions activated by the ADAS.

[0094] The sub-functions of ADAS may include: Autonomous Emergency Braking (AEB), Lane Keeping Assist (Lane Keeping Assist, LKA), Emergency Lane Keeping Assist (Emergency Lane Keeping Assist, ELKA), Adaptive Cruise Control (Adaptive Cruise Control, ACC), Lane Changing Assist (Lane Changing Assist, LCA), etc., but not limited to these. The sub-functions of ADAS can be configured according to actual application requirements, but not limited to these.

[0095] The sub-functions of ADAS can be automatically activated according to changes in the vehicle's driving conditions. For example, when ADAS detects that the vehicle needs to change lanes, it can activate the lane change assist system. After the vehicle is no longer in this driving condition, the sub-function of ADAS can also automatically exit, that is, it is converted to an inactivated state.

[0096] Step 204 : determining a vehicle computer abnormality handling strategy based on the activation state of the ADAS and the abnormality type of the vehicle computer.

[0097] In some embodiments, step 204 may include:

[0098] If the abnormality type of the vehicle computer includes other abnormality types except the vehicle computer communication abnormality, determine whether the ADAS is currently in the on state or the off state based on the enabled state of the ADAS. For example, it can be obtained from the system-on-chip whether the ADAS is currently in the on state or the off state; if the ADAS is currently in the off state, control the system-on-chip to restart; if the ADAS is currently in the on state, control the system-on-chip to restart after controlling the vehicle to issue a driver takeover prompt.

[0099] Normal vehicle-computer communication indicates that the on-chip system and the microcontroller can communicate normally. Therefore, the on-chip system can accurately obtain the current enabled status of ADAS from the microcontroller, which is conducive to obtaining a vehicle-computer abnormality handling strategy that conforms to the current enabled status of ADAS, thereby ensuring the safety of drivers and passengers. In addition, the embodiment of the present application can further ensure the safety of drivers and passengers by prompting the driver to take over.

[0100] In some embodiments, if the sound playback or the screen display of the vehicle computer is normal, when the on-chip system is restarted, a restart prompt can be issued based on the sound playback or screen display to remind the driver.

[0101] Further, if the ADAS is currently in an on state, after controlling the vehicle to issue a driver takeover prompt, controlling the on-chip system to restart includes:

[0102] If the ADAS is currently in an on state and a preset sub-function in the ADAS is in an inactivated state, after the vehicle is controlled to issue a driver takeover prompt, the system on chip is controlled to restart.

[0103] If the ADAS is currently in an on state and a preset sub-function in the ADAS is in an activated state, the system on chip is kept in an on state until the vehicle meets a preset system on chip restart condition, and the system on chip is controlled to restart.

[0104] The preset system-on-chip restart condition includes that the preset sub-function is in an inactive state, or the vehicle is in a non-driving state.

[0105] The preset sub-function can be set according to the ADAS sub-function that is automatically activated in the face of more dangerous road conditions, and the driver's demand for driving safety. For example, the preset sub-function may include one or more of the automobile automatic emergency braking system, lane keeping assist system, and emergency lane keeping system, but is not limited thereto.

[0106] In the embodiment of the present application, when the vehicle faces dangerous road conditions, the system on chip will not be restarted, thereby ensuring the safety of the driver.

[0107] Furthermore, the microcontroller controlling the vehicle to issue a driver takeover prompt may include: determining a form of the driver takeover prompt based on an abnormality type of the vehicle computer.

[0108] For example, if the abnormality type includes abnormal sound playback of the vehicle computer, and the screen display of the vehicle computer is normal, the vehicle computer is controlled to issue a driver takeover prompt in the form of sound playback.

[0109] If the abnormality type includes abnormal screen display of the vehicle computer, and the sound playback of the vehicle computer is normal, the vehicle computer is controlled to issue a driver takeover prompt in the form of screen display.

[0110] If the abnormality type includes other abnormalities except sound playing and picture display, the vehicle computer is controlled to issue a driver takeover prompt in the form of picture display and / or sound playing.

[0111] If the abnormality type includes abnormal sound playback and abnormal screen display of the vehicle computer, the vehicle is controlled to issue a driver takeover prompt in the form of vehicle braking.

[0112] The embodiments of the present application can improve the success rate of the vehicle sending the driver takeover prompt, and in the event of an abnormality in the vehicle computer, can also try to ensure that the driver can receive the driver takeover prompt.

[0113] Furthermore, after controlling the vehicle to issue a driver takeover prompt, for example, after controlling the vehicle to apply the brakes, the microcontroller can also detect whether the driver has taken over the vehicle; if the driver takes over the vehicle, control the on-chip system to restart; if the driver does not take over the vehicle, control the vehicle again to issue a driver takeover prompt, and after confirming that the driver has taken over the vehicle, or after confirming that the ADAS is turned off, control the on-chip system to restart.

[0114] The embodiment of the present application can further ensure driving safety by controlling the system on chip to restart after confirming that the driver has taken over. Especially in the vehicle braking scene, when the vehicle brakes, the driver may not know that the braking is used to prompt the driver to take over the vehicle. Therefore, the embodiment of the present application can ensure the driving safety of the vehicle when the sound playback and screen display of the vehicle computer are abnormal after controlling the vehicle brakes and confirming whether the driver has taken over.

[0115] In some embodiments, step 204 may also include: if the abnormality type of the vehicle computer includes vehicle computer communication abnormality, it means that the microcontroller and the system on chip cannot communicate, and the screen display and sound playback of the vehicle computer may both be abnormal. The microcontroller can determine whether the ADAS is in the on state or the off state before the vehicle computer communication abnormality occurs based on the enabled state of the ADAS; if the ADAS is in the off state before the vehicle computer communication abnormality occurs, control the system on chip to restart; if the ADAS is in the on state before the vehicle computer communication abnormality occurs, control the system on chip to restart after controlling the vehicle to brake.

[0116] Furthermore, after controlling the vehicle to brake and before controlling the on-chip system to restart, it can be detected whether the driver has taken over the vehicle; if the driver has taken over the vehicle, the step of controlling the on-chip system to restart is executed; if the driver has not taken over the vehicle, the vehicle is controlled to brake again; and after confirming that the driver has taken over the vehicle, the on-chip system is controlled to restart.

[0117] The above lists multiple embodiments for determining the vehicle computer abnormality handling strategy. In actual application, these embodiments can be combined with each other according to actual application requirements so that the vehicle computer abnormality handling strategy can be configured for various types of vehicle computer abnormalities and ADAS activation status.

[0118] For example, refer to Figure 3 As shown, the microcontroller determines the steps of the vehicle computer abnormality handling strategy based on the enabled state of the ADAS and the abnormal type of the vehicle computer, which may include:

[0119] Step 301, confirm whether the vehicle-machine communication is normal.

[0120] Specifically, the microcontroller may determine whether the vehicle-computer communication is normal based on the abnormality type of the vehicle-computer.

[0121] If the vehicle-machine communication is abnormal, execute step 302 ; if the vehicle-machine communication is normal, execute step 306 .

[0122] Step 302 , detecting whether the ADAS is activated before the communication is disconnected.

[0123] That is, the microcontroller determines whether the ADAS is in an on state or an off state before the vehicle-machine communication abnormality occurs based on the activation state of the ADAS.

[0124] If the ADAS is in the off state before the vehicle-machine communication abnormality occurs, step 312 is executed, that is, the system on chip is controlled to restart.

[0125] If the ADAS is in the on state before the vehicle-machine communication abnormality occurs, step 303 is executed.

[0126] Step 303, controlling the vehicle to brake.

[0127] After the vehicle is controlled to brake, step 304 may be executed.

[0128] Step 304, detecting whether the driver has taken over the vehicle.

[0129] If the driver takes over the vehicle, step 312 is executed, that is, the system on chip is controlled to restart.

[0130] If the driver has not taken over the vehicle, execute step 305 .

[0131] Step 305, detecting whether the number of vehicle braking times is less than a preset number.

[0132] The preset number of times can be configured according to actual application requirements, for example, the preset number of times is set to two times.

[0133] If the number of vehicle braking times is less than the preset number, the vehicle braking may continue to be controlled, that is, step 303 is continued.

[0134] If the number of vehicle braking times is greater than the preset number, step 306 may be executed, that is, waiting for the driver to take over. After the driver takes over the vehicle, the system on chip may be controlled to restart, that is, step 312 is executed.

[0135] It is understandable that, when the vehicle-computer communication is normal and the number of vehicle braking times is greater than a preset number, the microcontroller may also execute step 312 after confirming that the ADAS is turned off.

[0136] In the above step 301 , if the microcontroller confirms that the vehicle-machine communication is normal, step 307 may be executed.

[0137] Step 307 , detecting whether ADAS is currently started.

[0138] That is, the microcontroller may determine whether the ADAS is currently in an on state or an off state based on the activation state of the ADAS.

[0139] If the ADAS is currently in a shutdown state, the system on chip may be controlled to restart, that is, step 312 is executed.

[0140] For example, if ADAS is currently in the off state and the screen display or sound playback is normal, a restart prompt can be issued based on the screen display or sound playback. After the restart prompt ends, the system on the control chip restarts.

[0141] If the ADAS is currently in the on state, step 308 may be executed.

[0142] Step 308: Check whether the preset sub-function is in an activated state.

[0143] That is, the microcontroller detects whether the preset sub-function of the ADAS is in an activated state.

[0144] If the preset sub-function is in an activated state, step 311 is executed, and step 311 includes: after the preset restart condition is met, controlling the ADAS to restart.

[0145] That is, if the preset sub-function in the ADAS is in an activated state, the system on chip is kept in an on state until the vehicle meets a preset system on chip restart condition, and the system on chip is controlled to restart; wherein the preset system on chip restart condition includes that the preset sub-function is in an inactivated state, or that the vehicle is in a non-driving state.

[0146] If the preset sub-function in the ADAS is in an inactive state, step 309 may be executed.

[0147] Step 309, confirm whether the audio and video are abnormal.

[0148] That is, the microcontroller determines whether both the sound playback and the screen display of the vehicle computer are abnormal based on the abnormality type.

[0149] If one of the sound playing and the screen display of the vehicle computer is normal, step 301 and step 312 are executed, that is, the microcontroller can control the system on chip to restart after issuing a restart prompt in the form of sound playing or screen display.

[0150] If the sound playback and image display of the vehicle computer are abnormal, the microcontroller may enter step 303 .

[0151] The above is a method for determining the vehicle computer abnormality handling strategy when the vehicle is in a driving state. When the vehicle is not in a driving state, the microcontroller can execute step 205, or the microcontroller issues a restart prompt to prompt the driver and then executes step 205.

[0152] Step 205: Control the system on chip to restart.

[0153] The microcontroller may control the power supply of the system on chip so that the system on chip is restarted.

[0154] Controlling the restart of the system on chip may include: the microcontroller stores the restart time of the system on chip and the restart reason of the system on chip (such as the type of fault) in the non-volatile memory (NVM) of the microcontroller; then, the microcontroller may adjust the power state of the vehicle computer to an error mode (error mode), which may be denoted as S7. After reaching the restart time, the microcontroller may adjust the power state of the vehicle computer to a sleep mode (sleep mode), where the sleep mode may be denoted as S0.

[0155] In some embodiments, after the system on chip is restarted, a heartbeat may be sent to the microcontroller at a regular interval, and a SoC restart completion message may be sent to the microcontroller.

[0156] Through the above steps, the microcontroller can realize the abnormal repair of the vehicle computer.

[0157] The microcontroller may be a single-core microcontroller or a multi-core microcontroller.

[0158] refer to Figure 4 As shown, Figure 4 A schematic diagram of the structure of a microcontroller provided in an embodiment of the present application. The microcontroller may include a first core (denoted as core0) and a second core (denoted as core1). The first core and the second core are in communication connection.

[0159] The first core and the second core can interact with each other so that the microcontroller can implement the vehicle computer exception handling method.

[0160] Among them, the first core can be integrated with a vehicle computer power management module, and the second core can be integrated with a vehicle computer exception processing module.

[0161] refer to Figure 5 As shown, the first core and the second core interact to implement the vehicle computer abnormality processing method, and the steps may include:

[0162] Step 501: The first kernel confirms that an abnormality occurs in the vehicle computer.

[0163] In some embodiments, if the first core receives a restart request from the system on chip, it can confirm that an abnormality has occurred in the vehicle computer, and can determine the abnormality type of the vehicle computer based on the restart request, such as abnormal sound playback and abnormal screen display.

[0164] If the second core does not receive the heartbeat of the system on chip for more than a preset period of time, it can be confirmed that an abnormality has occurred in the vehicle computer, and the abnormality type includes abnormality in vehicle computer communication.

[0165] Step 502: The first core detects whether the vehicle is in a driving state.

[0166] Specifically, the first core includes a vehicle power management module. After receiving a restart request from the system on chip, the vehicle power management module can detect whether the vehicle is in a driving state.

[0167] The driving state is used to describe whether the vehicle is driving.

[0168] For example, when the vehicle is in a non-driving mode such as an abandoned mode, the vehicle's gear is in the parking gear (i.e., P gear), or the vehicle is stationary, it can be determined that the vehicle is in a non-driving state; if the vehicle is driving and the speed is greater than zero, it can be determined that the vehicle is in a driving state.

[0169] When the vehicle is in a driving state, execute step 505 ; when the vehicle is in a non-driving state, execute step 508 .

[0170] Step 503: The first core sends a restart detection request of the system on chip to the second core.

[0171] The restart detection request may carry an exception type.

[0172] If the second core receives the restart detection request of the system on chip, step 504 is executed.

[0173] Step 504: The second kernel determines a vehicle computer abnormality handling strategy.

[0174] Specifically, the second kernel obtains the activation state of the ADAS and the abnormal type of the vehicle computer; and determines the vehicle computer abnormality handling strategy based on the activation state of the ADAS and the abnormal type of the vehicle computer.

[0175] For example, if the abnormality type of the vehicle computer includes other abnormality types except the vehicle computer communication abnormality, determine whether the ADAS is currently in the on state or the off state based on the activation state of the ADAS; if the ADAS is currently in the off state, control the on-chip system to restart; if the ADAS is currently in the on state, control the on-chip system to restart after controlling the vehicle to issue a driver takeover prompt.

[0176] Furthermore, the controlling the vehicle to issue a driver takeover prompt includes:

[0177] If the abnormality type includes abnormal sound playback of the vehicle computer, and the screen display of the vehicle computer is normal, controlling the vehicle computer to issue a driver takeover prompt in the form of sound playback;

[0178] If the abnormality type includes abnormal display of the vehicle computer screen, and the sound playback of the vehicle computer is normal, controlling the vehicle computer to issue a driver takeover prompt in the form of a screen display;

[0179] If the abnormality type includes other abnormalities except for sound playing and screen display, controlling the vehicle computer to issue a driver takeover prompt in the form of screen display and / or sound playing;

[0180] If the abnormality type includes abnormal sound playback and abnormal screen display of the vehicle computer, the vehicle is controlled to issue a driver takeover prompt in the form of vehicle braking.

[0181] For another example, if the abnormality type of the vehicle computer includes vehicle computer communication abnormality, determine whether the ADAS is in the on state or the off state before the vehicle computer communication abnormality occurs based on the enabled state of the ADAS; if the ADAS is in the off state before the vehicle computer communication abnormality occurs, control the on-chip system to restart; if the ADAS is in the on state before the vehicle computer communication abnormality occurs, control the on-chip system to restart after controlling the vehicle to brake.

[0182] Step 504 is substantially the same as step 204 of the above embodiment and will not be described in detail here.

[0183] Step 505 , if the vehicle computer abnormality handling strategy includes controlling the vehicle to brake, the first core sends a braking control signal to the second core.

[0184] Step 506: The second core sends a braking control signal to a zone controller in the vehicle.

[0185] The zone controller is used to control the vehicle to perform braking in response to the braking control signal.

[0186] Step 507 : If the vehicle computer abnormality handling strategy includes controlling the system on chip to restart, the second core sends a response message to the first core to allow the system on chip to restart.

[0187] Step 508: The first kernel controls the system on chip to restart.

[0188] The embodiment of the present application divides the microcontroller into dual cores, which is beneficial to improving the efficiency of vehicle computer exception handling. In addition, the embodiment of the present application determines the vehicle computer exception handling strategy in the second core, which is beneficial to promoting the modularization of microcontroller functions, thereby reducing the complexity of software and hardware modification design on the microcontroller.

[0189] In the embodiment of the present application, the first core realizes external communication, further promoting the modularization of the microcontroller core functions, thereby further reducing the complexity involved in the microcontroller software and hardware.

[0190] An embodiment of the present application also provides an electronic device, which may include the microcontroller and the system on chip in the above embodiment.

[0191] For example, refer to Figure 1 As shown, in some embodiments, the electronic device may be a vehicle computer chip.

[0192] In other embodiments, the electronic device may also be configured as follows Figure 1 The car computer with the car computer chip shown.

[0193] Furthermore, the vehicle computer may also be configured with a display or a speaker for image display and sound playback.

[0194] An embodiment of the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned vehicle-machine abnormality handling method.

[0195] Computer-readable storage media may include high-speed random access memory and may also include non-volatile memory, such as a hard disk, an internal memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0196] If the module / unit integrated in the electronic device is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0197] In the several embodiments provided in this application, it should be understood that the disclosed electronic device and method can be implemented in other ways. For example, the electronic device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation.

[0198] In addition, each functional unit in each embodiment of the present application may be integrated into the same processing unit, or each unit may exist physically separately, or two or more units may be integrated into the same unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional modules.

[0199] It is obvious to those skilled in the art that the present application is not limited to the details of the above exemplary embodiments, and that the present application can be implemented in other specific forms without departing from the spirit or basic features of the present application. Therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-restrictive. In addition, it is obvious that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or electronic devices stated in the electronic device claim can also be implemented by the same unit or electronic device through software or hardware. The words first, second, etc. are used to indicate names, and do not indicate any particular order.

[0200] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present application and are not intended to limit it. Although the present application has been described in detail with reference to the above embodiments, a person skilled in the art should understand that the technical solution of the present application may be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present application.

Claims

1. A vehicle computer abnormality processing method, characterized in that: A microcontroller is applied to a vehicle-computer chip, the microcontroller is communicatively connected with a system-on-chip in the vehicle-computer chip, an advanced driver assistance system ADAS is configured in the system-on-chip, the vehicle-computer chip is configured in a vehicle, and the vehicle-computer is configured in a vehicle, and the vehicle-computer abnormality processing method includes: If the vehicle computer is abnormal, detecting whether the vehicle is in a driving state; If the vehicle is in a non-driving state, controlling the system on chip to restart; If the vehicle is in a driving state, obtaining the activation state of the ADAS and the abnormal type of the vehicle computer; Based on the activation state of the ADAS and the abnormality type of the vehicle computer, a vehicle computer abnormality handling strategy is determined.

2. The vehicle computer abnormality processing method according to claim 1, characterized in that: The determining of a vehicle computer abnormality handling strategy based on the activation state of the ADAS and the abnormality type of the vehicle computer includes: If the abnormality type of the vehicle computer includes other abnormality types except the vehicle computer communication abnormality, determining whether the ADAS is currently in an on state or an off state based on the activation state of the ADAS; Wherein, the vehicle-computer communication abnormality indicates that the communication between the microcontroller and the system on chip is abnormal; If the ADAS is currently in an off state, controlling the system on chip to restart; If the ADAS is currently in an on state, after the vehicle is controlled to issue a driver takeover prompt, the system on chip is controlled to restart.

3. The vehicle computer abnormality processing method according to claim 2, characterized in that: The controlling the vehicle to issue a driver takeover prompt includes: If the abnormality type includes abnormal sound playback of the vehicle computer, and the screen display of the vehicle computer is normal, controlling the vehicle computer to issue a driver takeover prompt in the form of sound playback; If the abnormality type includes abnormal display of the vehicle computer screen, and the sound playback of the vehicle computer is normal, controlling the vehicle computer to issue a driver takeover prompt in the form of a screen display; If the abnormality type includes other abnormalities except for sound playing and screen display, controlling the vehicle computer to issue a driver takeover prompt in the form of screen display and / or sound playing; If the abnormality type includes abnormal sound playback and abnormal screen display of the vehicle computer, the vehicle is controlled to issue a driver takeover prompt in the form of vehicle braking.

4. The vehicle computer abnormality processing method according to claim 2, characterized in that: If the ADAS is currently in an on state, after controlling the vehicle to issue a driver takeover prompt, controlling the system on chip to restart includes: If the ADAS is currently in an on state and a preset sub-function in the ADAS is in an inactive state, after controlling the vehicle to issue a driver takeover prompt, controlling the system on chip to restart; If the ADAS is currently in an on state and a preset sub-function in the ADAS is in an activated state, the system on chip is kept in an on state until the vehicle meets a preset system on chip restart condition, and the system on chip is controlled to restart; The preset system-on-chip restart condition includes that the preset sub-function is in an inactive state, or the vehicle is in a non-driving state.

5. The vehicle computer abnormality processing method according to any one of claims 2 to 4, characterized in that: After the controlling the vehicle to issue a driver takeover prompt, the method further includes: Detect whether the driver has taken over the vehicle; If the driver takes over the vehicle, controlling the system on chip to restart; If the driver does not take over the vehicle, the vehicle is controlled again to issue a driver take over prompt, and after confirming that the driver takes over the vehicle, or after confirming that the ADAS is turned off, the system on chip is controlled to restart.

6. The vehicle computer abnormality processing method according to claim 1, characterized in that: The determining of a vehicle computer abnormality handling strategy based on the activation state of the ADAS and the abnormality type of the vehicle computer includes: If the abnormality type of the vehicle computer includes a vehicle computer communication abnormality, determining whether the ADAS is in an on state or an off state before the vehicle computer communication abnormality occurs based on the activation state of the ADAS; Wherein, the vehicle-computer communication abnormality indicates that the communication between the microcontroller and the vehicle-computer chip is abnormal; If the ADAS is in a turned-off state before the vehicle-machine communication abnormality occurs, controlling the on-chip system to restart; If the ADAS is in the on-state before the vehicle-machine communication abnormality occurs, after the vehicle is controlled to brake, the on-chip system is controlled to restart.

7. The vehicle computer abnormality processing method according to claim 6, characterized in that: After controlling the vehicle to brake, and before controlling the system on chip to restart, the method further includes: Detect whether the driver has taken over the vehicle; If the driver takes over the vehicle, executing the step of controlling the system on chip to restart; If the driver does not take over the vehicle, the vehicle is braked again, and after confirming that the driver has taken over the vehicle, the system on chip is restarted.

8. A microcontroller, characterized in that: The microcontroller is used to execute the vehicle computer abnormality processing method according to any one of claims 1 to 7.

9. The microcontroller according to claim 8, characterized in that The microcontroller comprises a first core and a second core; the first core and the second core are communicatively connected; The first core is used to detect whether the vehicle is in a driving state when an abnormality occurs in the vehicle computer; If the vehicle is in a non-driving state, controlling the system on chip to restart; The first core is further configured to send a restart detection request of the system on chip to the second core when the vehicle is in the driving state; The second core is used for obtaining the activation state of the ADAS and the abnormal type of the vehicle computer in response to the restart detection request; Based on the activation state of the ADAS and the abnormality type of the vehicle computer, a vehicle computer abnormality handling strategy is determined.

10. The microcontroller according to claim 9, characterized in that In the case where the vehicle computer abnormality handling strategy includes controlling the system on chip to restart, the second core is further used to send a response message to the first core to allow the system on chip to restart; The first kernel is further configured to control the system on chip to restart after receiving the response message; When the vehicle abnormality handling strategy includes controlling the vehicle to brake, the second core is further used to send a braking control signal to the first core; The first core is also used to send the braking control signal to a zone controller in the vehicle after receiving the braking control signal, and the zone controller is used to control the vehicle to brake in response to the braking control signal.

11. An electronic device, characterized in that: The electronic device comprises a system on chip and a microcontroller according to any one of claims 8 to 10.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on an electronic device, the electronic device executes the vehicle abnormality processing method according to any one of claims 1 to 7.

Citation Information

Cited By

  • Controller reset monitoring method and device, vehicle, system, medium and product

    CN121704429A

  • Controller reset monitoring method, device, vehicle, system, medium and product

    CN121704429B