Domain controller power down and reset method, domain controller, device and medium

Abstract

The application discloses a domain controller power-off and reset method, a domain controller, equipment and a medium, the power-off method comprises the following steps: an MCU sends a power-off request to an SOC in response to a power-off instruction of the SOC, the SOC performs system shutdown related operations according to the power-off request, and feeds back a response signal to the MCU after completing the system shutdown related operations; and the MCU executes power-off operations on the SOC according to the response signal fed back by the SOC. The scheme improves the stability and reliability of system operation, and further improves the safety, reliability and robustness of the system. In addition, on the basis of safe power-off, the application scheme can also reset the domain controller in combination with application scenarios, meeting the safety, reliability and robustness requirements of the power-off and reset of the automatic driving domain controller related application scenarios.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of automatic driving, in particular to a domain controller power-off and reset method, a domain controller, a device and a medium. BACKGROUND

[0002] In the existing power-off process of the automatic driving domain controller, a forced power-off mode is usually adopted to disconnect the power supply of the SOC (stem on Chip, system-level chip) or disconnect the power supply of the entire system. This power-off mode is relatively simple and rough, and no related system file saving and safe power-off process is performed, and the system is abnormally exited by forced power-off.

[0003] Therefore, the existing power-off mode may cause damage and loss of system files, and when the system is entered again, the startup of the system will be abnormal, the normal use of the function cannot be ensured, or the log will be unexpectedly written to be full or the OTA (Over The Air, Over The Air) will fail, and only the software version can be recovered by line brushing. SUMMARY

[0004] The main purpose of the embodiment of the present application is to provide a domain controller power-off and reset method, a domain controller, a device and a medium, which aims to realize safe power-off and / or safe reset of the domain controller and improve the safety and reliability of system operation.

[0005] To achieve the above purpose, the embodiment of the present application provides a domain controller power-off method, which is applied to an MCU, and the method comprises:

[0006] In response to a power-off instruction for the SOC, a power-off request is sent to the SOC, and the SOC performs system shutdown related operations according to the power-off request;

[0007] A response signal fed back by the SOC after completing the system shutdown related operations is received;

[0008] The SOC is executed according to the response signal.

[0009] Optionally, after the step of responding to the power-off instruction for the SOC, sending the power-off request to the SOC, and performing the system shutdown related operations by the SOC according to the power-off request, the method further comprises:

[0010] In the case that the response signal fed back by the SOC is not received within a preset time, a preset timeout mechanism is used for corresponding processing.

[0011] Optionally, the step of using the preset timeout mechanism for corresponding processing comprises:

[0012] A fault is reported to system application software, and / or the SOC is executed according to the power-off operation.

[0013] Optionally, the method further comprises:

[0014] in response to a reset instruction for the SOC, sending a reset command to the SOC, and performing a self-reset operation by the SOC according to the reset command.

[0015] Optionally, the method further comprises:

[0016] in response to a board-level reset instruction for resetting the board-level of the domain controller, performing a self-reset operation on the MCU;

[0017] sending a power-on instruction to the SOC, and performing a system restart related operation by the SOC according to the power-on instruction.

[0018] Embodiments of the present application also propose a domain controller power-off method, which is applied to an SOC, and the method comprises:

[0019] receiving a power-off request sent by an MCU;

[0020] performing a system shutdown related operation according to the power-off request;

[0021] feeding back a response signal to the MCU to inform the MCU to perform a power-off operation on the SOC.

[0022] Embodiments of the present application also propose a domain controller reset method, which is applied to an MCU, and the method comprises:

[0023] in response to a reset instruction for the domain controller, sending a reset command to an SOC, and performing a system shutdown related operation by the SOC according to the reset command;

[0024] receiving a response signal fed back by the SOC after completing the system shutdown related operation;

[0025] performing a corresponding reset operation on the domain controller according to the response signal, and informing the SOC to perform a corresponding operation.

[0026] Optionally, the step of performing a corresponding reset operation on the domain controller according to the response signal, and informing the SOC to perform a corresponding operation comprises:

[0027] performing a reset operation on the SOC according to the response signal, and informing the SOC to perform a self-reset operation through a soft reset instruction.

[0028] Optionally, the reset instruction is a board-level reset instruction for resetting the domain controller board level, and the step of performing corresponding reset operation on the domain controller according to the response signal and notifying the SOC to perform corresponding operation comprises:

[0029] performing self-reset operation on the MCU according to the response signal;

[0030] sending a power-on instruction to the SOC, and performing system restart related operation according to the power-on instruction by the SOC.

[0031] Optionally, after the step of sending a reset command to the SOC in response to the reset instruction of the domain controller, and performing system shutdown related operation according to the reset command by the SOC, the method further comprises:

[0032] in the case that the response signal fed back by the SOC is not received within a preset time, performing corresponding processing by using a preset timeout mechanism.

[0033] Optionally, the step of performing corresponding processing by using a preset timeout mechanism comprises:

[0034] reporting a fault to system application software, and / or performing corresponding reset operation.

[0035] The embodiment of the application further provides a domain controller reset method, which is applied to an SOC, and the method comprises:

[0036] receiving a reset command sent by an MCU;

[0037] performing system shutdown related operation according to the reset command;

[0038] feeding back a response signal to the MCU to notify the MCU to perform corresponding reset operation on the domain controller;

[0039] performing corresponding operation in response to the instruction of performing corresponding reset operation on the domain controller by the MCU.

[0040] Optionally, the reset instruction is an SOC reset instruction for resetting the SOC, and the step of performing corresponding reset operation in response to the instruction of performing corresponding reset operation on the domain controller by the MCU comprises:

[0041] receiving a soft reset instruction sent by the MCU for performing corresponding reset operation on the SOC;

[0042] performing self-reset operation according to the soft reset instruction, and performing system restart related operation.

[0043] Optionally, the reset instruction is a board-level reset instruction for resetting the domain controller board level, and the step of executing a corresponding reset operation in response to the related instruction of the MCU performing a corresponding reset operation on the domain controller comprises:

[0044] receiving a power-on instruction sent by the MCU after the self-reset operation;

[0045] performing system restart related operations according to the power-on instruction.

[0046] The embodiment of the application also provides a domain controller, which comprises an MCU and an SOC, wherein the MCU is in communication connection with the SOC.

[0047] The MCU is configured to: in response to a power-off instruction for the SOC, send a power-off request to the SOC, perform system shutdown related operations on the SOC according to the power-off request, receive a response signal fed back by the SOC after the system shutdown related operations are completed, and perform a power-off operation on the SOC according to the response signal;

[0048] The SOC is configured to: receive the power-off request sent by the MCU, perform system shutdown related operations according to the power-off request, and feed back a response signal to the MCU to inform the MCU to perform a power-off operation on the SOC.

[0049] The MCU is configured to: in response to a reset instruction for the domain controller, send a reset command to the SOC, perform system shutdown related operations on the SOC according to the reset command, receive a response signal fed back by the SOC after the system shutdown related operations are completed, perform a corresponding reset operation on the domain controller according to the response signal, and inform the SOC to perform a corresponding operation;

[0050] The SOC is configured to: receive the reset command sent by the MCU, perform system shutdown related operations according to the reset command, feed back a response signal to the MCU, and perform a corresponding operation in response to the related instruction of the MCU performing a corresponding reset operation on the domain controller.

[0051] The embodiment of the application also provides a domain controller power-off device, which comprises:

[0052] A response module is configured to: in response to a power-off instruction for the SOC, send a power-off request to the SOC, and perform system shutdown related operations on the SOC according to the power-off request.

[0053] A receiving module is configured to: receive a response signal fed back by the SOC after the system shutdown related operations are completed.

[0054] The execution module is configured to perform a power-off operation on the SOC according to the response signal.

[0055] The embodiment of the present application also provides a domain controller reset device, which comprises:

[0056] The response module is configured to send a reset command to the SOC in response to a reset instruction for the domain controller, and perform system shutdown related operations on the SOC according to the reset command.

[0057] The receiving module is configured to receive a response signal fed back by the SOC after the SOC completes the system shutdown related operations.

[0058] The reset operation execution module is configured to perform a corresponding reset operation on the domain controller according to the response signal, and notify the SOC to perform a corresponding operation.

[0059] The embodiment of the present application also provides a vehicle-mounted device, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, and the computer program is executed by the processor to implement the method for powering off the domain controller or the method for resetting the domain controller.

[0060] The embodiment of the present application also provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method for powering off the domain controller or the method for resetting the domain controller.

[0061] The embodiment of the present application provides a domain controller power-off and reset method, device, domain controller, equipment and medium, wherein the MCU sends a power-off request to the SOC in response to a power-off instruction for the SOC, the SOC performs system shutdown related operations according to the power-off request, the SOC feeds back a response signal to the MCU after completing the system shutdown related operations, and the MCU performs a power-off operation on the SOC according to the response signal fed back by the SOC. In the power-off operation process, the MCU sends a power-off request to the SOC, the SOC performs system shutdown related operations (such as closing applications and systems, saving data, etc.) according to the power-off request, and the SOC and the MCU can perform handshake signal interaction to complete the related operations of the SOC, so that the system and application software will not be abnormally exited due to forced power-off, but will be exited with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. In addition, on the basis of safe power-off, the reset of the domain controller can be realized in combination with application scenarios, so as to meet the safety, reliability and robustness requirements of the power-off and reset of the domain controller in the automatic driving application scenario. BRIEF DESCRIPTION OF DRAWINGS

[0062] Figure 1 Figure 1 is a schematic diagram of a functional module of a domain controller power-down and reset device according to the present application;

[0063] Figure 2 Figure 2 is a schematic diagram of a connection structure of an MCU and a SOC of a domain controller according to an embodiment of the present application;

[0064] Figure 3 Figure 3 is an interaction timing diagram of an MCU and a SOC in a domain controller power-down method according to an embodiment of the present application;

[0065] Figure 4 Figure 4 is an interaction timing diagram of an MCU and a SOC in a domain controller reset method according to an embodiment of the present application;

[0066] Figure 5 Figure 5 is a flowchart of a first embodiment of a domain controller power-down method according to the present application;

[0067] Figure 6 Figure 6 is a detailed flowchart of a domain controller power-down method according to an embodiment of the present application;

[0068] Figure 7 Figure 7 is a flowchart of a second embodiment of a domain controller power-down method according to the present application;

[0069] Figure 8 Figure 8 is a flowchart of a first embodiment of a domain controller reset method according to the present application;

[0070] Figure 9 Figure 9 is a detailed flowchart of a SOC individual reset in a domain controller reset method according to an embodiment of the present application;

[0071] Figure 10 Figure 10 is a detailed flowchart of a board-level reset in a domain controller reset method according to an embodiment of the present application;

[0072] Figure 11 Figure 11 is a flowchart of a second embodiment of a domain controller reset method according to the present application;

[0073] Figure 12 Figure 12 is a schematic diagram of a functional module of an embodiment of a domain controller power-down device according to the present application;

[0074] Figure 13 Figure 13 is a schematic diagram of a functional module of an embodiment of a domain controller reset device according to the present application.

[0075] The implementation, functional features and advantages of the present application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0076] It should be understood that the specific embodiments described herein merely exemplify the application and do not limit the application.

[0077] The main solution of the embodiment of the application is that: in response to a power-off instruction of the SOC, the MCU sends a power-off request to the SOC, the SOC performs system shutdown related operations according to the power-off request, and after the SOC completes the system shutdown related operations, the SOC feeds back a response signal to the MCU, and the MCU performs power-off operations on the SOC according to the response signal fed back by the SOC. In the power-off operation process, the MCU sends a power-off request to the SOC, the SOC performs system shutdown related operations (such as closing applications and systems, saving data, etc.) according to the power-off request, and the SOC and the MCU can perform handshake signal interaction to complete the power-off operation of the SOC, so that the system and application software will not abnormally exit due to forced power-off in the power-off process, but will exit with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. In addition, on the basis of safe power-off, the application scheme can also reset the domain controller in combination with the application scene, meeting the safety, reliability and robustness requirements of the power-off and reset of the automatic driving domain controller in the application scene.

[0078] The technical terms involved in the embodiment of the application are:

[0079] SOC is the abbreviation of stem on Chip, also known as system on chip, which means that it is a product, a dedicated target integrated circuit, which contains a complete system and all the contents of embedded software.

[0080] From a narrow sense, SOC is the core chip integration of the information system, which integrates the key components of the system on a chip; from a broad sense, SOC is a micro system, and the academic circle generally tends to define SOC as integrating microprocessors, analog IP cores, digital IP cores and memories (or off-chip memory control interfaces) on a single chip, which is usually user customized or a standard product for specific purposes.

[0081] OTA, full name over the air, refers to over the air download, which is a technology for remotely managing software and SIM card data on a mobile terminal device through a mobile communication air interface. In the field of automobiles, especially pure electric vehicles, software can be remotely managed through the interface of mobile communication, and the traditional method is to upgrade the software of the corresponding ECU through the vehicle OBD. Therefore, the reaction speed of the car driving computer can be changed through OTA upgrade, thereby bringing better operation experience to the user. At the same time, through OTA upgrade, the maximum range of the pure electric vehicle can be increased to a certain extent, and the use state of the automobile battery can be adjusted. There are many methods for upgrading the automobile OTA, one of which is to upgrade online after connecting the automobile to the network, and the other is to download offline data packets for upgrading.

[0082] The embodiment of the present application considers that: in the power-off process of the existing automatic driving domain controller, a forced power-off mode is usually adopted, which is relatively simple and rough, and no related system file saving and safe power-off process is performed, which may cause damage and loss of system files, and when the system is entered again, the system startup exception will be caused, the normal use of the function cannot be ensured, or the log will be unexpectedly written and exploded or OTA will fail, and only the software version can be recovered through line brushing.

[0083] Therefore, the embodiment of the present application proposes a solution, which can realize safe power-off and / or safe reset of the domain controller, and improve the safety and reliability of system operation.

[0084] The embodiment of the present application can be applied to the scenarios of automatic driving domain controller License activation / deactivation, OTA, system power-off / restart, etc., in order to avoid the problems that system forced power-off may cause damage and loss of system files, or cause log to be unexpectedly written and exploded or OTA to fail, and taking into account the system reliability and robustness requirements, a safe power-off and safe reset method of the automatic driving domain controller is proposed.

[0085] The main implementation logic of the embodiment of the present application is: when the system needs to be powered off, the MCU sends a power-off request to the SOC, when the SOC application receives the power-off request of the MCU, the system actively closes and saves data and other system shutdown related operations, and then notifies the MCU to perform power-off operation. In this process, the system and application software can exit with preparation and save related data, so as to improve the stability and reliability of system operation, and further improve the reliability and robustness of the system.

[0086] On the basis of safe power-off, in combination with application scenarios, the embodiment of the present application proposes two implementation modes of domain controller reset: SOC reset (Tegra reset) and board-level reset (Aurix reset).

[0087] In particular, with reference to Figure 1 , Figure 1 is a functional module diagram of the device to which the domain controller power-off and reset device belongs. The domain controller power-off and reset device can be a device independent of the device and capable of data processing, which can be carried on the device in the form of hardware or software. The device can be a vehicle-mounted device, or a smart mobile terminal such as a mobile phone, a tablet computer, etc. having a data processing function, or a fixed terminal device or a server having a data processing function, etc.

[0088] In the embodiment, the terminal device to which the domain controller power-off and reset device belongs at least includes an output module 110, a processor 120, a memory 130, and a communication module 140.

[0089] The memory 130 stores an operating system and a domain controller power-off and reset program; the output module 110 can be a display screen, etc. The communication module 140 can include a WIFI module, a mobile communication module, a Bluetooth module, etc. and communicates with external devices or servers through the communication module 140.

[0090] Among them, as an implementation manner, the domain controller power-off and reset program in the memory 130 is implemented by the processor to realize the following steps:

[0091] In response to the power-off instruction of the SOC, a power-off request is sent to the SOC, and the SOC performs system shutdown related operations according to the power-off request;

[0092] A response signal fed back by the SOC after completing the system shutdown related operations is received;

[0093] The SOC is executed according to the response signal.

[0094] Further, the domain controller power-off and reset program in the memory 130 is implemented by the processor to realize the following steps:

[0095] In the case that the response signal fed back by the SOC is not received within a preset time, a preset timeout mechanism is used for corresponding processing.

[0096] Further, the domain controller power-off and reset program in the memory 130 is implemented by the processor to realize the following steps:

[0097] In the case that the response signal fed back by the SOC is not received within a preset time, a fault is reported to the system application software, and / or the SOC is executed.

[0098] Further, the domain controller power-off and reset program in the memory 130 is implemented by the processor to realize the following steps:

[0099] In response to the reset instruction of the SOC, a reset command is sent to the SOC, and the SOC performs a self-reset operation according to the reset command.

[0100] Further, when the domain controller power-off and reset program in the memory 130 is executed by the processor, the following steps are further implemented:

[0101] In response to a board-level reset instruction of resetting the domain controller at the board level, a self-reset operation is performed on the MCU;

[0102] A power-on instruction is sent to the SOC, and the SOC performs a system restart related operation according to the power-on instruction.

[0103] Among them, as an implementation manner, when the domain controller power-off and reset program in the memory 130 is executed by the processor, the following steps are implemented:

[0104] Receive the power-off request sent by the MCU;

[0105] According to the power-off request, a system shutdown related operation is performed;

[0106] A response signal is fed back to the MCU to inform the MCU to perform a power-off operation on the SOC.

[0107] Among them, as an implementation manner, when the domain controller power-off and reset program in the memory 130 is executed by the processor, the following steps are implemented:

[0108] In response to a reset instruction of the domain controller, a reset command is sent to the SOC, and the SOC performs a system shutdown related operation according to the reset command;

[0109] Receive the response signal fed back by the SOC after completing the system shutdown related operation;

[0110] According to the response signal, a corresponding reset operation is performed on the domain controller, and the SOC is informed to perform a corresponding operation.

[0111] Further, when the domain controller power-off and reset program in the memory 130 is executed by the processor, the following steps are further implemented:

[0112] According to the response signal, a reset operation is performed on the SOC, and a soft reset instruction is sent to the SOC to perform a self-reset operation.

[0113] Further, when the domain controller power-off and reset program in the memory 130 is executed by the processor, the following steps are further implemented:

[0114] According to the response signal, a self-reset operation is performed on the MCU;

[0115] sending a power-on instruction to the SOC, and performing system restart related operations according to the power-on instruction by the SOC.

[0116] wherein, as an implementation form, the domain controller power-off and reset program in the memory 130 is implemented by the processor to perform the following steps:

[0117] receiving a reset command sent by the MCU;

[0118] performing system shutdown related operations according to the reset command;

[0119] feeding back a response signal to the MCU to inform the MCU to perform corresponding reset operations on the domain controller;

[0120] performing corresponding operations in response to the related instructions of the MCU to perform corresponding reset operations on the domain controller.

[0121] Further, the domain controller power-off and reset program in the memory 130 is implemented by the processor to perform the following steps:

[0122] receiving a soft reset instruction sent by the MCU to perform corresponding reset operations on the SOC;

[0123] performing self-reset operations according to the soft reset instruction, and performing system restart related operations.

[0124] Further, the domain controller power-off and reset program in the memory 130 is implemented by the processor to perform the following steps:

[0125] receiving a power-on instruction sent by the MCU after performing self-reset operations;

[0126] performing system restart related operations according to the power-on instruction.

[0127] The embodiment sends a power-off request to the SOC in response to a power-off instruction of the SOC, and the SOC performs system shutdown related operations according to the power-off request. After the SOC completes the system shutdown related operations, a response signal is fed back to the MCU. The MCU performs a power-off operation on the SOC according to the response signal fed back by the SOC. In the power-off operation process, the MCU sends a power-off request to the SOC, and the SOC performs system shutdown related operations (such as closing applications and systems, saving data, etc.) according to the power-off request. After the SOC and the MCU interact with the handshake signal, the power-off operation of the SOC is completed. In the power-off process, the system and application software will not abnormally exit due to forced power-off, but will exit with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. In addition, on the basis of safe power-off, the application scheme can also reset the domain controller in combination with the application scenario, meeting the safety, reliability and robustness requirements of the power-off and reset of the automatic driving domain controller in the application scenario.

[0128] In addition, the embodiment of the application provides a domain controller which can be applied to an automatic driving scene. The domain controller can include an MCU (micro control unit) and an SOC. The MCU is in communication connection with the SOC.

[0129] As an implementation manner, the specific connection mode of the MCU and the SOC can refer to the mode shown in Figure 2 The MCU can specifically adopt a chip TC397, the SOC can specifically adopt a chip Orin-X, and the MCU is further connected with an MCU power management chip TLF35584.

[0130] The TLF35584 and the MCU are connected through SPI and 35884_RESET, the MCU and the SOC are connected through SPI and Ethernet (ETH), and in addition, the MCU and the SOC are further connected through SOC_RESET_N and SOC_MCU_Handshake hard-wire signal.

[0131] The TLF35584 is responsible for power management of the MCU, and the MCU is responsible for completing power-on and power-off control of the SOC. When the SoC side needs to perform power-on and power-off and reset operations, different instructions are sent to the MCU, and the MCU initiates execution of corresponding power-off and reset processes.

[0132] Specifically, as an implementation manner, the MCU is configured to send a power-off request to the SOC in response to a power-off instruction of the SOC, perform system shutdown related operations according to the power-off request, receive a response signal fed back by the SOC after the SOC completes the system shutdown related operations, and perform a power-off operation on the SOC according to the response signal.

[0133] The SOC is configured to receive a power-down request sent by the MCU, perform system shutdown related operations according to the power-down request, and feed back a response signal to the MCU to inform the MCU to perform a power-down operation on the SOC.

[0134] In this embodiment, the process of the MCU and the SOC interacting to implement the SOC power-down operation can refer to Figure 3 .

[0135] And / or

[0136] As another embodiment, the MCU is configured to send a reset command to the SOC in response to a reset instruction of the domain controller, perform corresponding reset operations on the domain controller according to the reset command, receive a response signal fed back by the SOC after the SOC completes the system shutdown related operations, perform corresponding reset operations on the domain controller according to the response signal, and inform the SOC to perform corresponding operations.

[0137] The SOC is configured to receive a reset command sent by the MCU, perform system shutdown related operations according to the reset command, feed back a response signal to the MCU, and perform corresponding operations in response to a related instruction of the MCU to perform corresponding reset operations on the domain controller.

[0138] In this embodiment, the process of the MCU and the SOC interacting to implement the domain controller reset operation can refer to Figure 4 .

[0139] Therefore, the power-down operation of the SOC is completed through the handshake signal interaction between the SOC and the MCU, so that the system and the application software will not abnormally exit due to forced power-off during the power-down process, but will exit with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. In addition, on the basis of safe power-down, the domain controller reset can also be implemented in combination with the application scenario, meeting the safety, reliability and robustness requirements of the power-down and reset in the automatic driving domain controller related application scenario.

[0140] Based on the above device and domain controller hardware architecture but not limited to the above architecture, the method embodiment of the present application is proposed.

[0141] The execution subject of the method of the embodiment can be a domain controller power-off and reset device. The domain controller power-off and reset device can be a device capable of data processing independent of equipment, which can be carried on the equipment in the form of hardware or software. The equipment can be a vehicle-mounted device, or a smart mobile terminal such as a mobile phone or a tablet computer having a data processing function, or a fixed terminal device or a server having a data processing function. The embodiment takes a vehicle-mounted device domain controller in an automatic driving scenario as an example.

[0142] Referring to Figure 5 , Figure 5 FIG. 1 is a flowchart of a domain controller power-off method according to a first embodiment of the present application. The domain controller power-off method is applied to an MCU of a domain controller, and the method comprises the following steps.

[0143] In step S101, in response to a power-off instruction for the SOC, a power-off request is sent to the SOC, and the SOC performs system shutdown related operations according to the power-off request.

[0144] The embodiment relates to safe power-off processing of an SOC. The SOC safe power-off process can cover various SOC power-off processes, and the main implementation logic is that when the system needs to be powered off, the MCU sends a power-off request to the SOC, the SOC performs system active closing and data saving and other system shutdown related operations after receiving the power-off request from the MCU, and then notifies the MCU that the power-off operation can be performed, thereby completing the safe power-off of the SOC by the MCU.

[0145] Specifically, when the system needs to be powered off, such as in the scenarios of activation / deactivation of an automatic driving domain controller license, OTA, system power-off / restart, etc., the system needs to be powered off, and a power-off instruction for the SOC is triggered.

[0146] In combination with Figure 3 , the MCU sends a power-off request to the SOC in response to the power-off instruction for the SOC.

[0147] After receiving the power-off request sent by the MCU, the SOC performs system shutdown related operations according to the power-off request.

[0148] The system shutdown related operations can include but are not limited to closing system application software, closing an operating system, saving data, etc.

[0149] Therefore, in the SOC power-down process, the system and application software will not abnormally exit due to forced power-off, but will exit with preparation and can save relevant data, thereby improving the stable reliability of system operation, and further improving the safety reliability and robustness of the system. The present scheme will not cause the system forced power-off to cause damage and loss of system files, or cause problems such as accidental log explosion or OTA failure, and meets the system reliability and robustness requirements.

[0150] After the SOC completes the system shutdown related operation, a response signal of system shutdown completion is sent to the MCU to inform the MCU to perform the power-down operation on the SOC.

[0151] Step S102, receiving the response signal fed back by the SOC after completing the system shutdown related operation;

[0152] Step S103, performing the power-down operation on the SOC according to the response signal.

[0153] After the MCU receives the response signal fed back by the SOC after completing the system shutdown related operation, the power-down operation is performed on the SOC according to the response signal, that is, the power of the SOC is turned off, thereby realizing the safe power-down of the SOC.

[0154] In the above scheme, the MCU sends a power-down request to the SOC in response to the power-down instruction of the SOC, the SOC performs system shutdown related operation according to the power-down request, the SOC feeds back a response signal to the MCU after completing the system shutdown related operation, and the MCU performs the power-down operation on the SOC according to the response signal fed back by the SOC. In the power-down operation process, the MCU sends a power-down request to the SOC, the SOC performs system shutdown related operation (such as closing applications and systems, saving data, etc.) according to the power-down request, and the SOC and the MCU can interact with each other to complete the power-down operation of the SOC. In the power-down process, the system and application software will not abnormally exit due to forced power-off, but will exit with preparation and can save relevant data, thereby improving the stable reliability of system operation, and further improving the safety reliability and robustness of the system.

[0155] Further, after the above step of responding to the power-down instruction of the SOC, sending a power-down request to the SOC, and performing system shutdown related operation by the SOC according to the power-down request, the following scheme can also be included:

[0156] If the response signal fed back by the SOC is not received within a preset time, a preset timeout mechanism is used for corresponding processing.

[0157] The embodiment considers that when the MCU sends a power-off request to the SOC, if the SOC cannot send or the MCU side does not receive a response signal of the SOC feedback for a long time (the time can be configured according to actual conditions), an experienced timeout mechanism can be used for bottom handling.

[0158] The scheme of using the preset timeout mechanism for corresponding processing can be as follows.

[0159] The MCU reports a fault to system application software, and / or the MCU continues to perform a power-off operation on the SOC.

[0160] The detailed process of the embodiment can be referred to as shown in Figure 6 .

[0161] As Figure 6 and in combination with Figure 2 , Figure 3 and Figure 5 , the embodiment implements the related detailed process of the SOC safe power-off as follows.

[0162] (1) The MCU sends a power-off request power-off req to the SOC through an SPI bus or an Ethernet link;

[0163] (2) After receiving the power-off request power-off req, the SOC performs related operations such as closing a GuestOS application software, closing an operating system, and saving data;

[0164] (3) When the system completes shutdown, the SOC sends a handshake signal Handshake to the MCU through a GPIO to tell the MCU that the shutdown is completed;

[0165] (4) After receiving the handshake signal, the MCU performs SOC Power-off to close the power supply of the SOC;

[0166] Among them, the SOC sends a handshake signal Handshake to the MCU through a GPIO to tell the MCU that the shutdown is completed, and the MCU can perform a power-off operation. When the SOC cannot send or the MCU side does not receive the handshake signal Handshake for a long time, an experienced timeout mechanism can be used for bottom handling.

[0167] The specific scheme can be as follows: when a timeout occurs, the MCU does not receive the handshake signal Handshake sent by the SOC, the MCU reports a fault to the application software, and at the same time, continues to perform a power-off operation on the SOC, so that the request of the power-off operation is responded.

[0168] Among them, as an implementation manner, the value of Timeout can adopt an empirical value, which is obtained by averaging multiple test values and adding 2S as the empirical time required for software to close, for example, Timeout can be set to 20S.

[0169] Therefore, through the above scheme, specifically, the MCU sends a power-off request to the SOC in response to the power-off instruction of the SOC, the SOC performs system shutdown related operations according to the power-off request, and the MCU performs power-off operations on the SOC according to the response signal fed back by the SOC after the SOC completes the system shutdown related operations; In the power-off operation process, the MCU sends a power-off request to the SOC, the SOC performs system shutdown related operations (such as closing applications and systems, saving data, etc.) according to the power-off request, and the SOC and the MCU can interact with each other to complete the power-off operation of the SOC, so that the system and application software will not be abnormally exited due to forced power-off during the power-off process, but will be exited with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. Among them, in the case where the response signal fed back by the SOC is not received within a preset time, a preset timeout mechanism can be used for corresponding processing, such as reporting a fault to the application software by the MCU, while continuing to perform the power-off operation of the SOC, so that the request for the SOC power-off operation can be responded to, meeting the scene requirements.

[0170] Further, on the basis of the above safe power-off operation scheme, the embodiment can also include a scheme for resetting the domain controller.

[0171] Specifically, on the basis of safe power-off, in combination with application scenarios, the embodiment proposes two implementation manners of domain controller reset: SOC individual reset (Tegra reset) and board-level reset (Aurix reset).

[0172] As an implementation manner, for the implementation of SOC individual reset, the following scheme can be adopted:

[0173] The MCU sends a reset command to the SOC in response to the reset instruction of the SOC, and the SOC performs self-reset operation according to the reset command.

[0174] Among them, the related content of the self-reset operation of the SOC can refer to the related embodiments of the subsequent reset operation, which will not be described here in detail.

[0175] As another implementation manner, for the implementation of board-level reset, the following scheme can be adopted:

[0176] The MCU performs a self-reset operation on the MCU in response to a board-level reset instruction for resetting the board level of the domain controller.

[0177] The SOC is sent a power-on instruction, and the SOC performs system restart related operations according to the power-on instruction.

[0178] The board-level reset operation can refer to the related embodiments of the subsequent reset operation, which will not be described in detail here.

[0179] Therefore, on the basis of safe power-off, the embodiment of the application can also realize the reset of the domain controller in combination with the application scenario, and can realize the SOC reset and the board-level reset, meeting the safety, reliability and robustness requirements of the power-off and reset of the automatic driving domain controller in the application scenario.

[0180] Reference Figure 7 , Figure 7 The flowchart of the second embodiment of the domain controller power-off method of the application is shown. The domain controller power-off method is applied to the SOC of the domain controller.

[0181] As shown in Figure 7 , the domain controller power-off method proposed in this embodiment includes:

[0182] Step S201, receiving the power-off request sent by the MCU;

[0183] The embodiment relates to the safe power-off processing of the SOC. The SOC safe power-off flow can cover various SOC power-off processes, and the main implementation logic is that when the system needs to be powered off, the MCU sends a power-off request to the SOC, the SOC applies the power-off request from the MCU, performs system shutdown related operations such as system active closing and data saving, and then notifies the MCU that the power-off operation can be performed, thereby completing the safe power-off of the MCU to the SOC.

[0184] Specifically, when the system needs to be powered off, such as in the scenarios of automatic driving domain controller License activation / deactivation, OTA, system power-off / restart, etc., the system needs to be powered off, and the power-off instruction of the SOC is triggered.

[0185] In combination with Figure 3 , the MCU sends a power-off request to the SOC in response to the power-off instruction of the SOC.

[0186] The SOC receives the power-off request sent by the MCU, so as to perform system shutdown related operations according to the power-off request.

[0187] Step S202, performing system shutdown related operations according to the power-off request;

[0188] After the SOC receives the power-down request sent by the MCU, the SOC performs system shutdown related operations according to the power-down request.

[0189] The system shutdown related operations can include, but are not limited to, closing system application software, closing an operating system, saving data, and the like.

[0190] Thus, during the SOC power-down process, the system and application software will not abnormally exit due to forced power-off, but will exit with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. The system will not be forced to power off, which can cause damage and loss of system files, or cause unexpected log writing or OTA failure, and the like, and the system reliability and robustness requirements are balanced.

[0191] At step S203, a response signal is fed back to the MCU to inform the MCU to perform a power-down operation on the SOC.

[0192] After the SOC completes the system shutdown related operations, the SOC sends a system shutdown completion response signal to the MCU to inform the MCU to perform a power-down operation on the SOC.

[0193] The above-mentioned scheme is used in the power-down operation process. The MCU sends a power-down request to the SOC. The SOC performs system shutdown related operations (such as closing applications and systems, saving data, and the like) according to the power-down request. The SOC and the MCU can perform handshake signal interaction to complete the power-down operation of the SOC. During the power-down process, the system and application software will not abnormally exit due to forced power-off, but will exit with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system.

[0194] The embodiment realizes the detailed process of the safe power-down processing of the SOC. For details, refer to Figure 6 , which will not be described here.

[0195] Refer to Figure 8 , Figure 8 is a flowchart of a domain controller reset method first embodiment of the application. The domain controller reset method is applied to the MCU of a domain controller. The method comprises the following steps:

[0196] At step S301, in response to a reset instruction of the domain controller, a reset command is sent to the SOC. The SOC performs system shutdown related operations according to the reset command.

[0197] The embodiment relates to the reset processing of a domain controller, and specifically can realize SOC individual reset (Tegra reset) and board-level reset (Aurix reset).

[0198] The main implementation logic is that when the system needs to reset the domain controller, the MCU sends a reset command to the SOC, the SOC applies the reset command received from the MCU to perform system shutdown related operations such as system active closing and data saving, and then notifies the MCU that the reset operation can be performed. The MCU performs corresponding reset operations on the domain controller according to different situations of the reset command.

[0199] Specifically, when the system needs to reset the domain controller, such as in the scenarios of automatic driving domain controller License activation / deactivation, OTA, system power-off / restart, etc., the system needs to perform SOC reset or board reset, and the reset instruction of the domain controller is triggered.

[0200] As shown in Figure 4 In response to the reset instruction of the domain controller, the MCU sends a reset command to the SOC.

[0201] After the SOC receives the reset command sent by the MCU, the system shutdown related operation is performed according to the reset command.

[0202] The system shutdown related operation can include but is not limited to closing system application software, closing operating system, saving data, etc.

[0203] Therefore, during the domain controller reset process, the system and application software will not abnormally exit due to forced power-off, but will exit with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. The present scheme will not cause the system to be forced to power off, which may cause damage and loss of system files, or cause unexpected log explosion or OTA failure, etc., and takes into account the system reliability and robustness requirements.

[0204] After the SOC completes the system shutdown related operation, the SOC sends a system shutdown completion response signal to the MCU to notify the MCU to perform a reset operation on the SOC.

[0205] Step S302, receiving the response signal fed back by the SOC after completing the system shutdown related operation;

[0206] Step S303, performing corresponding reset operations on the domain controller according to the response signal, and notifying the SOC to perform corresponding operations.

[0207] After the MCU receives the response signal fed back by the SOC after completing the system shutdown related operation, the corresponding operation is performed on the SOC according to the response signal.

[0208] perform a corresponding reset operation on the domain controller according to the response signal, and notify the SOC to perform a corresponding operation, which can include the following scheme:

[0209] The MCU performs a reset operation on the SOC according to the response signal, and notifies the SOC to perform a self-reset operation through a soft reset instruction (in combination with a reset command). Figure 9

[0210] As another scenario, the reset instruction is a board-level reset instruction for resetting the domain controller board, that is, the system needs to be reset at the board level. The MCU performs a corresponding reset operation on the domain controller according to the response signal, and notifies the SOC to perform a corresponding operation, which includes the following scheme:

[0211] First, the MCU performs a self-reset operation on the MCU according to the response signal; then, the MCU sends a power-on instruction to the SOC, and the SOC performs system restart related operations according to the power-on instruction.

[0212] Accordingly, through the above scheme, the MCU responds to the reset instruction of the domain controller, sends a reset command to the SOC, and the SOC performs system shutdown related operations according to the reset command; receives the response signal fed back by the SOC after completing the system shutdown related operations; performs a corresponding reset operation on the domain controller according to the response signal, and notifies the SOC to perform a corresponding operation. In the reset operation process, the MCU sends a reset command to the SOC, the SOC performs system shutdown related operations (such as closing applications and systems, saving data, etc.) according to the reset command, and the SOC and the MCU can interact with each other through a handshake signal to complete the related operations of the SOC. The MCU performs a corresponding reset operation on the domain controller according to different reset instructions. This makes the system and application software not abnormally exit due to forced power-off during the reset process, but can exit with preparation and save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system.

[0213] Further, after the above step of responding to the reset instruction of the domain controller, sending a reset command to the SOC, and the SOC performing system shutdown related operations according to the reset command, the following scheme is further included:

[0214] If the response signal fed back by the SOC is not received within a predetermined time, a preset timeout mechanism is used for corresponding processing.

[0215] ​The embodiment considers that when the MCU sends a reset command to the SOC, if the SOC cannot send or the MCU side does not receive the response signal of the SOC feedback for a long time (the time can be configured according to actual conditions), an experienced timeout mechanism can be used for bottoming out.

[0216] The scheme of using the preset timeout mechanism for corresponding processing can be as follows:

[0217] The MCU reports the fault to the system application software, and / or the MCU continues to perform the corresponding reset operation.

[0218] The reset refinement process of the domain controller can be implemented with reference to Figure 9 and Figure 10 .

[0219] As shown in Figure 9 and in combination with Figure 2 , Figure 4 and Figure 8 , if the domain controller only needs to reset the SOC alone, the related refinement process of the SOC reset of the domain controller implemented by the embodiment is as follows:

[0220] (1) The MCU sends a Tegrareset reset command to the SOC through an SPI bus or an Ethernet link;

[0221] (2) After the SOC receives the Tegrareset reset command, the SOC performs operations such as closing the Guest OS application software and the operating system, saving data, and the like;

[0222] (3) When the system completes shutdown, the SOC sends a Handshake handshake signal to the MCU through a GPIO hard line to tell the MCU that the shutdown is completed;

[0223] (4) After the MCU receives the handshake signal, the MCU performs a SOC reset operation, that is, the MCU sends a reset (soft reset) instruction to the SOC;

[0224] (5) Then, the SOC side Orin-X performs self-reset according to the instruction of the MCU, and restarts the Guest OS (the operating system of the SOC) and the application. In the above process, the SOC does not power off, but only performs a soft reset operation.

[0225] The SOC sends a Handshake handshake signal through a GPIO to tell the MCU that the shutdown is completed and the reset operation can be performed. When the SOC cannot send the Handshake handshake signal, an experienced timeout mechanism can be used, and when the timeout occurs and the MCU does not receive the Handshake handshake signal, the SOC reset operation is also performed.

[0226] That is, when the MCU issues a Tegra reset command, the internal timer module starts timing, and then the SOC receives the reset command and performs a shutdown operation of the Guest OS. Meanwhile, the MCU waits for a handshake signal sent by the SOC through the GPIO. When the timer at the MCU end has not received a response signal indicating that the system shutdown is complete after a preset time (for example, 20 seconds), the MCU reports a fault to the application software and continues to perform a reset operation of the SOC, so that the system can operate normally.

[0227] Thus, according to the above scheme, the MCU sends a reset command to the SOC in response to a reset instruction of the domain controller, the SOC performs system shutdown related operations according to the reset command, receives a response signal fed back by the SOC after the SOC completes the system shutdown related operations, performs a power-down operation on the SOC according to the response signal, and performs a corresponding reset operation on the domain controller. In the reset operation process, the MCU sends a reset command to the SOC, the SOC performs system shutdown related operations (such as closing applications and systems, saving data, etc.) according to the reset command, and the SOC and the MCU can interact with each other through handshake signals to complete the shutdown related operations of the SOC. Then, the MCU performs a corresponding reset operation on the domain controller according to different reset instructions. In the reset process, the system and the application software will not abnormally exit due to forced power-off, but will exit with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. If no response signal fed back by the SOC is received within a preset time, a preset timeout mechanism can be used for corresponding processing, such as reporting a fault to the application software and continuing to perform a reset operation of the SOC, so that the system can operate normally. Thus, the command of the single reset operation of the SOC can be responded, and the scene requirement can be met.

[0228] As shown in Figure 10 and in combination with Figure 2 , Figure 4 and Figure 8 , if it is necessary to perform a board-level system reset of the entire autonomous driving domain controller, the embodiment implements the related detailed process of the board-level reset of the domain controller as follows:

[0229] (1) The MCU sends an Aurix reset command to the SOC through an SPI bus or an Ethernet link;

[0230] (2) After receiving the reset command, the SOC performs related operations such as closing the Guest OS application software and operating system, saving data, etc.

[0231] (3) When the system completes shutdown, the SOC sends a Handshake handshake signal to the MCU through the GPIO, telling the MCU that the system shutdown has been completed.

[0232] (4) After receiving the handshake signal, the MCU performs SOC Power off, which closes the power supply of the SOC;

[0233] (5) The MCU performs a self-reset operation;

[0234] (6) The MCU sends a PowerON instruction to the SOC, and then restarts the Guest OS.

[0235] When the MCU issues an Aurixreset reset command, the internal timer module starts timing, and then the SOC receives the reset command and performs a shutdown operation of the Guest OS. Meanwhile, the MCU waits for the Handshake handshake signal sent by the SOC through the GPIO. When the timer at the MCU end has not received the system shutdown completion signal within a preset time (such as 20S), the MCU reports a fault to the application software, and then performs a power-off operation of the SOC, and then performs a MCU reset and subsequent processes, so that the system can run normally.

[0236] Therefore, according to the above scheme, the MCU sends a reset command to the SOC in response to a reset instruction of the domain controller, the SOC performs system shutdown related operations according to the reset command, receives a response signal fed back by the SOC after the SOC completes the system shutdown related operations, performs a power-off operation on the SOC according to the response signal, and performs a corresponding reset operation on the domain controller. In the reset operation process, the MCU sends a reset command to the SOC, the SOC performs system shutdown related operations (such as closing the application and system, saving data, etc.) according to the reset command, and the SOC and the MCU can complete the power-off operation of the SOC after handshake signal interaction, and then the MCU performs a corresponding reset operation on the domain controller according to the corresponding reset instruction. In the reset process, the system and the application software will not be abnormally exited due to forced power-off, but will be exited with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. In the case where the response signal fed back by the SOC is not received within a preset time, a preset timeout mechanism can be used for corresponding processing, such as reporting a fault to the application software by the MCU, continuing to perform a power-off operation of the SOC, and then performing a MCU reset and subsequent processes, so that the system can run normally, so that the command of the domain controller board-level reset operation can be responded to, and the scene requirement can be met.

[0237] Reference Figure 11 , Figure 11A flowchart of a second embodiment of a domain controller reset method. The domain controller reset method is applied to a SOC of a domain controller, and the domain controller reset method comprises:

[0238] In step S401, a reset command sent by an MCU is received.

[0239] The embodiment relates to a reset process of a domain controller, and can realize SOC individual reset (Tegra reset) and board-level reset (Aurix reset).

[0240] The main implementation logic is as follows: when the system needs to reset the domain controller, the MCU sends a reset command to the SOC, the SOC applies the reset command received from the MCU, performs system shutdown-related operations such as system active closing and data saving, and then notifies the MCU that the reset operation can be performed, and the MCU performs corresponding reset operations on the domain controller according to different reset commands.

[0241] Specifically, when the system needs to reset the domain controller, such as in the scenarios of automatic driving domain controller License activation / deactivation, OTA, system power-off / restart, etc., the system needs to perform SOC individual reset or board-level reset, and the reset instruction of the domain controller is triggered.

[0242] In combination with Figure 4 As shown in the figure, the MCU sends a reset command to the SOC in response to the reset instruction of the domain controller.

[0243] The SOC receives the reset command sent by the MCU, so as to perform system shutdown-related operations according to the reset command.

[0244] In step S402, system shutdown-related operations are performed according to the reset command.

[0245] After the SOC receives the reset command sent by the MCU, system shutdown-related operations are performed according to the reset command.

[0246] The system shutdown-related operations can include but are not limited to: closing system application software, closing an operating system, saving data, etc.

[0247] Therefore, in the domain controller reset process, the system and the application software will not abnormally exit due to forced power-off, but will exit with preparation and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. The scheme will not cause the problems of system file damage and loss caused by forced power-off, or accidental log writing or OTA failure, and can meet the system reliability and robustness requirements.

[0248] Step S403, feedback response signal to the MCU to inform the MCU to perform corresponding reset operation on the domain controller;

[0249] After the SOC completes the system shutdown related operation, the SOC sends a response signal of system shutdown completion to the MCU to inform the MCU to perform reset operation on the SOC.

[0250] After the MCU receives the response signal feedback by the SOC after completing the system shutdown related operation, the MCU performs corresponding operation on the SOC according to the response signal to perform corresponding reset operation on the domain controller.

[0251] Step S404, in response to the related instruction of the MCU performing corresponding reset operation on the domain controller, perform corresponding operation.

[0252] After the MCU completes the related operation on the SOC, the MCU performs corresponding reset operation on the domain controller according to different reset instructions. In response to the related instruction of the MCU performing corresponding reset operation on the domain controller, the SOC performs corresponding operation.

[0253] Among them, as one scenario, the reset instruction is the SOC reset instruction of resetting the SOC, that is, the system needs to perform SOC reset alone, and in response to the related instruction of the MCU performing corresponding reset operation on the domain controller, the SOC performing corresponding operation can include the following scheme:

[0254] The SOC receives the self-reset operation notification sent by the MCU, that is, the soft reset instruction (combined with Figure 9 reset command), performs self-reset operation according to the soft reset instruction, and performs system restart related operation.

[0255] Among them, as another scenario, the reset instruction is the board level reset instruction of resetting the domain controller board, that is, the system needs to perform board level reset, and in response to the related instruction of the MCU performing corresponding reset operation on the domain controller, the SOC performing corresponding operation can include the following scheme:

[0256] Firstly, the MCU performs self-reset operation on the MCU according to the response signal; then, the MCU sends power-on instruction to the SOC;

[0257] Then, the SOC performs system restart related operation according to the power-on instruction after receiving the power-on instruction sent by the MCU after performing self-reset operation.

[0258] Therefore, by the above scheme, the SOC receives the reset command sent by the MCU; performs system shutdown related operations according to the reset command; feeds back a response signal to the MCU to inform the MCU to perform a power-off operation on the SOC, and the MCU performs a corresponding reset operation on the domain controller; and in response to the related instruction of the MCU performing the corresponding reset operation on the domain controller, performs the corresponding reset operation. In the reset operation process, the MCU sends the reset command to the SOC, the SOC performs system shutdown related operations (such as closing applications and systems, saving data, etc.) according to the reset command, and the SOC and the MCU can interact with the handshake signal to complete the related operations of the SOC, and then the MCU performs the corresponding reset operation on the domain controller according to different reset instructions. In the reset process, the system and application software will not be abnormally exited due to forced power-off, but will be prepared to exit and can save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system.

[0259] Further, on the basis of the above scheme, the following schemes are further included:

[0260] If the MCU does not receive the response signal fed back by the SOC within a preset time, the MCU adopts a preset timeout mechanism to perform corresponding processing.

[0261] The embodiment considers that when the MCU sends a reset command to the SOC, if the SOC cannot send or the MCU side does not receive the response signal fed back by the SOC for a long time (the time can be configured according to actual conditions), an experienced timeout mechanism can be used for bottom handling.

[0262] The scheme of adopting the preset timeout mechanism to perform corresponding processing can be as follows:

[0263] The MCU reports a fault to system application software, and / or the MCU continues to perform the corresponding reset operation.

[0264] The embodiment of implementing the reset refinement process of the domain controller can refer to Figure 9 and Figure 10 , which will not be described here.

[0265] In addition, as shown in Figure 12 , the embodiment of the application proposes a domain controller power-off device, which comprises:

[0266] A response module, configured to send a power-off request to the SOC in response to a power-off instruction of the SOC, and perform system shutdown related operations on the SOC according to the power-off request.

[0267] The receiving module is configured to receive a response signal fed back after the SOC completes the system shutdown related operation.

[0268] The executing module is configured to perform a power-off operation on the SOC according to the response signal.

[0269] The principle and implementation process of the domain controller power-off are realized in the embodiment, and please refer to the above embodiments, which will not be repeated here.

[0270] In addition, as Figure 13 shown, the embodiment of the present application also provides a domain controller reset device, which comprises:

[0271] The response module is configured to send a reset command to the SOC in response to a reset instruction of the domain controller, and the SOC performs a system shutdown related operation according to the reset command.

[0272] The receiving module is configured to receive a response signal fed back after the SOC completes the system shutdown related operation.

[0273] The reset operation executing module is configured to perform a corresponding reset operation on the domain controller according to the response signal, and notify the SOC to perform a corresponding operation.

[0274] The principle and implementation process of the domain controller reset are realized in the embodiment, and please refer to the above embodiments, which will not be repeated here.

[0275] The embodiment of the present application provides a terminal device, which comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and when the computer program is executed by the processor, the method for the domain controller power-off or the method for the domain controller reset is realized.

[0276] Since the domain controller power-off program or the domain controller reset program is executed by the processor, all the technical solutions of the above corresponding embodiments are adopted, and at least all the beneficial effects brought by the above corresponding embodiments are achieved, which will not be repeated here.

[0277] The embodiment of the present application provides a computer readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the method for the domain controller power-off or the method for the domain controller reset is realized.

[0278] Since the power-off procedure of the domain controller or the domain controller reset procedure is executed by the processor, all the technical solutions of the corresponding embodiments are adopted, and at least all the beneficial effects brought by all the technical solutions of the corresponding embodiments are achieved, and thus will not be repeated here.

[0279] The domain controller power-off and reset method and device, the domain controller, the equipment and the medium provided by the embodiment of the application have the following beneficial effects: the MCU sends a power-off request to the SOC in response to a power-off instruction of the SOC, the SOC performs system shutdown related operations according to the power-off request, and the SOC feeds back a response signal to the MCU after completing the system shutdown related operations, and the MCU performs a power-off operation on the SOC according to the response signal fed back by the SOC. In the power-off operation process, the MCU sends a power-off request to the SOC, the SOC performs system shutdown related operations (such as closing applications and systems, saving data, etc.) according to the power-off request, and the SOC and the MCU can perform handshake signal interaction to complete the power-off operation of the SOC, so that the system and the application software will not abnormally exit due to forced power-off in the power-off process, but can exit with preparation and save related data, thereby improving the stability and reliability of system operation, and further improving the safety, reliability and robustness of the system. In addition, on the basis of safe power-off, the application scheme can also reset the domain controller in combination with application scenarios, and meets the safety, reliability and robustness requirements of the power-off and reset of the autonomous driving domain controller in the application scenario.

[0280] It should be noted that in this document, the terms "comprise", "comprise", or any other variant thereof are intended to cover non-exclusive inclusion, so that processes, methods, articles or methods comprising a series of elements not only include those elements, but also include other elements not explicitly listed or inherent to such processes, methods, articles or methods. Without more limitations, the element defined by the statement "comprises a" does not exclude the presence of another identical element in the process, method, article or method comprising the element.

[0281] The above-mentioned serial numbers of the embodiments of the application are only for description, and do not represent the advantages and disadvantages of the embodiments.

[0282] Those skilled in the art can clearly understand the above-mentioned embodiment method can be realized by means of software and the necessary general hardware platform, of course, also can be through hardware, but in many cases the former is the better embodiment. Based on such understanding, the technical solutions of the present application essentially or say the part of the contribution to the prior art can be embodied in the form of software products, the computer software product is stored in the above-mentioned storage medium (such as ROM / RAM, magnetic disc, optical disc), including a number of instructions to make a terminal device (may be a mobile phone, computer, server, controlled terminal, or network equipment, etc.) executes the method of each embodiment of the present application.

[0283] The above is only the preferred embodiment of the present application, not therefore limit the patent scope of the present application, any equivalent structure or equivalent flow transformation made by using the content of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for powering down a domain controller, the method comprising: The method is applied to an MCU, and the method comprises: In a preset scenario, triggering a power-off instruction of a SOC through a domain controller, wherein the preset scenario comprises one of License activation, License deactivation, OTA, system power-off or system restart; In response to the power-off instruction of the SOC, sending a power-off request to the SOC, and performing system shutdown related operations by the SOC according to the power-off request; Receiving a response signal fed back by the SOC after completing the system shutdown related operations; Performing power-off operations on the SOC according to the response signal; After the step of responding to the power-off instruction of the SOC, sending the power-off request to the SOC, and performing system shutdown related operations by the SOC according to the power-off request, the method further comprises: In the case that the response signal fed back by the SOC is not received within a preset time, performing corresponding processing by using a preset timeout mechanism; The step of performing corresponding processing by using the preset timeout mechanism comprises: Reporting a fault to system application software, and / or performing power-off operations on the SOC.

2. The method of any one of claim 1, characterized in that, The method further comprises: In response to a reset instruction of the SOC, sending a reset command to the SOC, and performing self-reset operations by the SOC according to the reset command.

3. The method according to any one of claims 1-2, characterized in that, The method further comprises: In response to a board-level reset instruction of resetting the board-level of the domain controller, performing self-reset operations on the MCU; Sending a power-on instruction to the SOC, and performing system restart related operations by the SOC according to the power-on instruction.

4. A method of resetting a domain controller, the method comprising: The method is applied to an MCU, and the method comprises: In a preset scenario, triggering a reset instruction of a SOC through a domain controller, wherein the preset scenario comprises one of License activation, License deactivation, OTA, system power-off or system restart; In response to the reset instruction of the domain controller, sending a reset command to the SOC, and performing system shutdown related operations by the SOC according to the reset command; Receiving a response signal fed back by the SOC after completing the system shutdown related operations; Performing corresponding reset operations on the domain controller according to the response signal, and notifying the SOC to perform corresponding operations; After the step of performing system shutdown related operations by the reset command, the method further comprises: In the case that the response signal fed back by the SOC is not received within a preset time, performing corresponding processing by using a preset timeout mechanism; The step of performing corresponding processing by using the preset timeout mechanism comprises: Reporting a fault to system application software, and / or performing corresponding reset operations.

5. The method of claim 4, wherein, The reset instruction is a SOC reset instruction of resetting the SOC, and the step of performing corresponding reset operations on the domain controller according to the response signal, and notifying the SOC to perform corresponding operations comprises: Performing reset operations on the SOC according to the response signal, and notifying the SOC to perform self-reset operations by a soft reset instruction.

6. The method of claim 4, wherein, The reset instruction is a board-level reset instruction for resetting the domain controller board level, and the step of performing corresponding reset operation on the domain controller according to the response signal and notifying the SOC to perform corresponding operation includes: Performing self-reset operation on the MCU according to the response signal; Sending a power-on instruction to the SOC, and the SOC performs system restart related operation according to the power-on instruction.

7. A method of resetting a domain controller, the method comprising: The method is applied to the SOC, and the method includes: Receiving a reset command sent by the MCU, wherein the reset command is a reset instruction for the SOC triggered by the domain controller in a preset scenario, and the preset scenario includes one of License activation, License deactivation, OTA, system power-off or system restart; Performing system shutdown related operation according to the reset command; Feedback response signal to the MCU to notify the domain controller to perform corresponding reset operation; In response to the MCU's corresponding reset operation related instruction for the domain controller, perform corresponding operation; After the step of feeding back the response signal to the MCU to notify the MCU to perform corresponding reset operation of the domain controller, it further includes: In the case that no response signal feedback from the SOC is received within a preset time, the MCU uses a preset timeout mechanism to perform corresponding processing to report the fault to the system application software and / or perform corresponding reset operation.

8. The method of claim 7, wherein, The reset instruction is a SOC reset instruction for resetting the SOC, and the step of performing corresponding reset operation in response to the MCU's corresponding reset operation related instruction for the domain controller includes: Receiving a soft reset instruction sent by the MCU to perform corresponding reset operation on the SOC; Performing self-reset operation according to the soft reset instruction to perform system restart related operation.

9. The method of claim 7, wherein, The reset instruction is a board-level reset instruction for resetting the domain controller board level, and the step of performing corresponding reset operation in response to the MCU's corresponding reset operation related instruction for the domain controller includes: Receiving a power-on instruction sent by the MCU after self-reset operation; Performing system restart related operation according to the power-on instruction.

10. A domain controller, characterized by The domain controller includes MCU and SOC, and the MCU and SOC are in communication connection; wherein: The MCU is configured to trigger a power-off instruction for the SOC through the domain controller in a preset scene, wherein the preset scene includes one of License activation, License deactivation, OTA, system power-off, or system restart; is further configured to send a power-off request to the SOC in response to the power-off instruction for the SOC, perform system shutdown related operations on the SOC according to the power-off request, receive a response signal fed back by the SOC after the SOC completes the system shutdown related operations, and perform a power-off operation on the SOC according to the response signal; is further configured to perform corresponding processing by using a preset timeout mechanism in a case where the response signal fed back by the SOC is not received within a preset time; and is further configured to report a fault to system application software and / or perform a power-off operation on the SOC. The SOC is configured to receive the power-off request sent by the MCU, perform system shutdown related operations according to the power-off request, feed back a response signal to the MCU to notify the MCU to perform a power-off operation on the SOC, and / or The MCU is configured to send a reset command to the SOC in response to a reset instruction for the domain controller, perform system shutdown related operations on the SOC according to the reset command, receive a response signal fed back by the SOC after the SOC completes the system shutdown related operations, perform a corresponding reset operation on the domain controller according to the response signal, and notify the SOC to perform a corresponding operation. The SOC is configured to receive the reset command sent by the MCU, perform system shutdown related operations according to the reset command, feed back a response signal to the MCU, and perform a corresponding operation in response to a related instruction of the MCU for performing a corresponding reset operation on the domain controller.

11. The domain controller of claim 10, wherein The MCU is further configured to send a reset command to the SOC in response to a reset instruction for the SOC, perform a self-reset operation on the SOC according to the reset command, or perform a self-reset operation on the MCU in response to a board-level reset instruction for resetting the board level of the domain controller, send a power-on instruction to the SOC, and perform system restart related operations on the SOC according to the power-on instruction.

12. The domain controller of claim 10, wherein The MCU is further configured to perform a reset operation on the SOC according to the response signal when the reset instruction is a SOC reset instruction for resetting the SOC, and notify the SOC to perform a self-reset operation by a soft reset instruction, or perform a self-reset operation on the MCU according to the response signal when the reset instruction is a board-level reset instruction for resetting the board level of the domain controller, send a power-on instruction to the SOC, and perform system restart related operations on the SOC according to the power-on instruction.

13. An in-vehicle device characterized by comprising: The vehicle-mounted device comprises a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program, when executed by the processor, implements the method for powering down the domain controller according to any one of claims 1-3 or the method for resetting the domain controller according to any one of claims 4-9.

14. A computer-readable storage medium, characterized in that, The computer program is stored on the computer readable storage medium and, when executed by the processor, implements the method for powering down the domain controller according to any one of claims 1-3 or the method for resetting the domain controller according to any one of claims 4-9.

Images