Vehicle-mounted component, debugging method and vehicle

Abstract

The invention provides a vehicle-mounted component, a debugging method and a vehicle. The vehicle-mounted component at least comprises a control module, a debugging module and a debugging interface, wherein the debugging module is respectively connected with the control module and the debugging interface. The control module is used for providing a first signal for the debugging module, and the first signal is used for indicating whether the vehicle-mounted component is allowed to be debugged or not. And the debugging module is used for stopping supplying power to the control module when determining that the vehicle-mounted component is not allowed to be debugged according to the first signal and detecting that the debugging interface is connected with the debugging device. The debugging safety of the vehicle-mounted component is higher, the practicability of the vehicle-mounted component is improved, and the cost of the vehicle-mounted component is reduced.

Description

Technical Field

[0001] The present application relates to the field of debugging technology, and in particular to a vehicle-mounted component, a debugging method and a vehicle. Background Art

[0002] With the rapid development of the Internet of Vehicles, the requirements for the network security of vehicle-mounted components are getting higher and higher. For vehicles circulated in the market, their vehicle-mounted components may be disassembled by attackers, and the software of the vehicle-mounted components may be read out through the simulator. Then the attackers can do further research to explore potential vulnerabilities and create malicious software to invade other vehicles. Therefore, in order to ensure that only authorized personnel can directly access and debug vehicle-mounted components through the debugging interface, secure debugging has become an indispensable technology in vehicle network security.

[0003] The existing security debugging solutions mainly rely on pure software interaction to debug vehicle components. However, this method cannot prevent attackers from directly debugging the chip by physically accessing the debugging device. Therefore, how to improve the security of debugging vehicle components has become one of the current research hotspots. Summary of the invention

[0004] The embodiments of the present application provide a vehicle-mounted component, a debugging method and a vehicle, which improve the safety of debugging of the vehicle-mounted component.

[0005] In a first aspect, an embodiment of the present application provides a vehicle-mounted component. The vehicle-mounted component includes at least a control module, a debugging module and a debugging interface, and the debugging module is connected to the control module and the debugging interface respectively. The control module is used to provide a first signal to the debugging module, wherein the first signal is used to indicate whether the vehicle-mounted component is allowed to be debugged. The debugging module is used to stop supplying power to the control module when it is determined that the vehicle-mounted component is not allowed to be debugged according to the first signal and when it is detected that the debugging interface is connected to a debugging device.

[0006] In the embodiment of the present application, the vehicle-mounted component adds a debugging module outside the control module, and when it is determined that the vehicle-mounted component does not allow debugging and detects that a debugging device is connected to the debugging interface, the control module can be stopped from being powered on, which can effectively prevent an attacker from directly debugging the vehicle-mounted component by physically accessing the debugging device, thereby improving the security of debugging the vehicle-mounted component. In addition, the vehicle-mounted component sets the debugging module outside the control module, which improves its practicality and reduces the cost of the control module.

[0007] In combination with the first aspect, in a feasible implementation, the debugging module includes a debugging circuit and a power supply circuit, the debugging circuit is respectively connected to the power supply circuit, the control module, and the debugging interface, and the power supply circuit is also connected to the control module. The debugging circuit is used to determine whether the vehicle-mounted component allows debugging based on the first signal. The debugging circuit is also used to detect whether the debugging interface is connected to the debugging device. The debugging circuit is also used to control the power supply circuit to stop supplying power to the control module when it is determined that the vehicle-mounted component does not allow debugging and it is detected that the debugging interface is connected to the debugging device.

[0008] In combination with the first aspect, in a feasible implementation, the debugging circuit at least includes a control circuit and a switch circuit, the control circuit is respectively connected to the switch circuit, the control module, and the power supply circuit, and the switch circuit is also respectively connected to the control module and the debugging interface. The switch circuit is used to establish a connection between the control module and the debugging interface if it is determined according to the first signal that the vehicle-mounted component allows debugging. The switch circuit is also used to disconnect the connection between the control module and the debugging interface if it is determined according to the first signal that the vehicle-mounted component does not allow debugging. The switch circuit is also used to send a second signal to the control circuit, wherein the second signal is used to indicate whether the debugging interface is connected to the debugging device.

[0009] In combination with the first aspect, in a feasible implementation, the control circuit is used to determine whether to control the power supply circuit to stop supplying power to the control module according to the first signal and the second signal.

[0010] In combination with the first aspect, in a feasible implementation, the control circuit is used to control the power supply circuit to stop supplying power to the control module when it is determined according to the first signal that the vehicle-mounted component is not allowed to be debugged, and when it is determined according to the second signal that the debugging interface is connected to the debugging device.

[0011] In combination with the first aspect, in a feasible implementation, the debugging module is also used to power the control module when it is determined based on the first signal that the vehicle-mounted component allows debugging, or when it is determined based on the first signal that the vehicle-mounted component does not allow debugging and the debugging interface is not connected to the debugging device.

[0012] In combination with the first aspect, in a feasible implementation, the control module is used to obtain a third signal through the vehicle bus, and determine whether the vehicle component is in a debugging mode according to the third signal.

[0013] In combination with the first aspect, in a feasible implementation, the third signal includes a target key, and the control module is further configured to determine that the vehicle-mounted component is in a debugging mode if it is determined that the target key is consistent with a preset key. The control module is further configured to determine that the vehicle-mounted component is not in a debugging mode if it is determined that the target key is inconsistent with the preset key.

[0014] In a second aspect, an embodiment of the present application provides a debugging method. The method is applied to a vehicle-mounted component, and the vehicle-mounted component includes at least a control module, a debugging module and a debugging interface, and the debugging module is connected to the control module and the debugging interface respectively. The method includes: providing a first signal to the debugging module through the control module, wherein the first signal is used to indicate whether the vehicle-mounted component is allowed to be debugged. When the debugging module determines that the vehicle-mounted component is not allowed to be debugged according to the first signal, and detects that the debugging interface is connected to a debugging device, the control module is stopped from being powered.

[0015] In combination with the second aspect, in a feasible implementation, the debugging module includes a debugging circuit and a power supply circuit, the debugging circuit is respectively connected to the power supply circuit, the control module, and the debugging interface, and the power supply circuit is also connected to the control module, and the debugging module stops supplying power to the control module when it is determined by the first signal that the vehicle-mounted component does not allow debugging, and detects that the debugging interface is connected to a debugging device, including: determining by the debugging circuit whether the vehicle-mounted component is allowed to be debugged according to the first signal. Detecting by the debugging circuit whether the debugging interface is connected to a debugging device. When it is determined by the debugging circuit that the vehicle-mounted component is not allowed to be debugged, and detects that the debugging interface is connected to the debugging device, the power supply circuit is controlled to stop supplying power to the control module.

[0016] In combination with the second aspect, in a feasible implementation, the debugging circuit at least includes a control circuit and a switch circuit, the control circuit is respectively connected to the switch circuit, the control module, and the power supply circuit, and the switch circuit is also respectively connected to the control module and the debugging interface, and the debugging is used to determine whether the vehicle-mounted component is allowed to be debugged according to the first signal, including: if the switch circuit determines that the vehicle-mounted component is allowed to be debugged according to the first signal, then the connection between the control module and the debugging interface is established. If the switch circuit determines that the vehicle-mounted component is not allowed to be debugged according to the first signal, then the connection between the control module and the debugging interface is disconnected.

[0017] In combination with the second aspect, in a feasible implementation, detecting whether the debug interface is connected to a debug device through the debug circuit includes: outputting a second signal through the switch circuit, wherein the second signal is used to indicate whether the debug interface is connected to a debug device.

[0018] In combination with the second aspect, in a feasible implementation, when the debugging circuit determines that the on-board component does not allow debugging and detects that the debugging interface is connected to the debugging device, the power supply circuit is controlled to stop supplying power to the control module, including: when the control circuit determines that the on-board component does not allow debugging according to the first signal and determines that the debugging interface is connected to the debugging device according to the second signal, the power supply circuit is controlled to stop supplying power to the control module.

[0019] In combination with the second aspect, in a feasible implementation, the method also includes: powering the control module by the debugging module when it is determined according to the first signal that the vehicle-mounted component allows debugging, or when it is determined according to the first signal that the vehicle-mounted component does not allow debugging and the debugging interface is not connected to the debugging device.

[0020] In combination with the second aspect, in a feasible implementation, the method further includes: obtaining a third signal through the vehicle bus by the control module, and determining whether the vehicle component is in a debugging mode according to the third signal.

[0021] In combination with the second aspect, in a feasible implementation, the third signal includes a target key, and the method further includes: if the control module determines that the target key is consistent with a preset key, determining that the vehicle-mounted component is in a debugging mode. If the control module determines that the target key is inconsistent with the preset key, determining that the vehicle-mounted component is not in the debugging mode.

[0022] In a third aspect, an embodiment of the present application provides a vehicle, which may include the vehicle-mounted component of the first aspect.

[0023] By implementing the embodiment of the present invention, the vehicle-mounted component can stop supplying power to the control module by adding a debugging module outside the control module when it is determined that the vehicle-mounted component does not allow debugging and detects that a debugging device is connected to the debugging interface, which can effectively prevent an attacker from directly debugging the vehicle-mounted component by physically accessing the debugging device, thereby improving the security of debugging the vehicle-mounted component. In addition, the vehicle-mounted component sets the debugging module outside the control module, which improves its practicality and reduces the cost of the control module. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 is a schematic structural diagram of a vehicle-mounted component provided in an embodiment of the present application;

[0026] Figure 2 is another structural schematic diagram of a vehicle-mounted component provided in an embodiment of the present application;

[0027] Figure 3 is another structural schematic diagram of a vehicle-mounted component provided in an embodiment of the present application;

[0028] Figure 4 is another structural schematic diagram of a vehicle-mounted component provided in an embodiment of the present application;

[0029] Figure 5 is another structural schematic diagram of a vehicle-mounted component provided in an embodiment of the present application;

[0030] Figure 6 It is a flowchart of a debugging method provided by an embodiment of the present application;

[0031] Figure 7 It is another flowchart of a debugging method provided in an embodiment of the present application;

[0032] Figure 8 It is another flowchart of a debugging method provided in an embodiment of the present application;

[0033] Fig. 9 It is a structural schematic diagram of a vehicle provided in an embodiment of the present application.

[0034] The vehicle-mounted component 10 , the control module 11 , the debugging module 12 , the debugging interface 13 , the debugging circuit 121 , the power supply circuit 122 , the control circuit 1211 , the switch circuit 1212 , the debugging device 20 , the simulator 201 , and the terminal device 30 . DETAILED DESCRIPTION

[0035] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0036] The existing security debugging solutions mainly rely on pure software interaction to debug vehicle-mounted components. However, this method cannot prevent attackers from directly debugging vehicle-mounted components by physically accessing the debugging device. Therefore, the technical problem to be solved by this application is: how to improve the security of debugging vehicle-mounted components.

[0037] See also Figure 1 , Figure 1 Schematic diagram of the structure of a vehicle-mounted component provided in an embodiment of the present application. Figure 1 As shown, the vehicle-mounted component 10 may at least include a control module 11, a debugging module 12 and a debugging interface 13. The debugging module 12 may be connected to the control module 11 and the debugging interface 13 respectively.

[0038] In a specific implementation, the control module 11 may be used to provide a first signal to the debugging module 12. Here, the first signal may be used to indicate whether the vehicle-mounted component 10 is allowed to be debugged. The debugging module 12 may be used to stop supplying power to the control module 11 when it is determined according to the first signal that the vehicle-mounted component 10 is not allowed to be debugged and when it is detected that the debugging interface 13 is connected to the debugging device 20.

[0039] It should be noted that the first signal may be a level signal. For example, if the control module 11 provides a high level signal to the debugging module 12, it indicates that the vehicle-mounted component 10 allows debugging. If the control module 11 provides a low level signal to the debugging module 12, it indicates that the vehicle-mounted component 10 does not allow debugging.

[0040] Optionally, the control module 11 may be a device with a control function in any form, such as a control chip, a controller, etc. The embodiment of the present application does not specifically limit the implementation form of the control module 11.

[0041] Optionally, when the control module 11 is a control chip, the control chip may be packaged using a BGA (Ball Grid Array) package to avoid exposing its pins.

[0042] Optionally, the debugging interface 13 is an interface for debugging the vehicle-mounted component 10, such as a JTAG (Joint Test Action Grid) interface. The embodiment of the present application does not specifically limit the implementation form of the debugging interface 13.

[0043] In the embodiment of the present application, the vehicle-mounted component 10 adds a debugging module 12 outside the control module 11, and when it is determined that the vehicle-mounted component 10 does not allow debugging and detects that the debugging interface 13 is connected to the debugging device 20, it stops supplying power to the control module 11, which can effectively prevent an attacker from directly debugging the vehicle-mounted component 10 by physically accessing the debugging device, thereby improving the security of debugging the vehicle-mounted component. In addition, the vehicle-mounted component 10 sets the debugging module 12 outside the control module 11, which improves its practicality and reduces the cost of the control module 11.

[0044] It should be noted that after the vehicle-mounted component 10 detects that an attacker has physically accessed the debugging device to perform debugging and stops supplying power to the control module 11, when it is detected that the attacker has stopped debugging, the vehicle-mounted component 10 can restore power to the control module 11 so that the vehicle-mounted component 10 can operate normally.

[0045] In an optional implementation, the debugging module 12 can also be used to power the control module 11 when it is determined based on a first signal provided by the control module that the vehicle-mounted component 10 allows debugging, or when it is determined based on the first signal that the vehicle-mounted component does not allow debugging and it is detected that the debugging interface 13 is not connected to the debugging device 20.

[0046] For some possible implementations, see Figure 2 , Figure 2 is another structural diagram of a vehicle-mounted component provided in an embodiment of the present application. Figure 2 As shown, the debugging module 12 may include a debugging circuit 121 and a power supply circuit 122. The debugging circuit 121 may be connected to the power supply circuit 122, the control module 11, and the debugging interface 13 respectively, and the power supply circuit 122 may also be connected to the control module 11.

[0047] In a specific implementation, the debugging circuit 121 may be used to determine whether the vehicle-mounted component allows debugging according to the first signal provided by the control module 11. The debugging circuit 121 may also be used to detect whether a debugging device is connected to the debugging interface 13. The debugging circuit 121 may also be used to control the power supply circuit 122 to stop supplying power to the control module 11 when it is determined that the vehicle-mounted component 10 does not allow debugging and it is detected that the debugging device 20 is connected to the debugging interface 13.

[0048] It should be noted that when it is determined that the vehicle-mounted component 10 is not allowed to be debugged and it is detected that the debugging interface 13 is connected to the debugging device 20 , it indicates that there is an abnormality in the debugging process of the vehicle-mounted component 10 , that is, an attacker is trying to invade to debug the vehicle-mounted component 10 .

[0049] In an optional embodiment, the debugging circuit 121 can also be used to control the power supply circuit 122 to supply power to the control module 11 when it is determined that the vehicle-mounted component 10 allows debugging, or when it is determined that the vehicle-mounted component 10 does not allow debugging and it is detected that the debugging interface 13 is not connected to the debugging device 20.

[0050] In an optional embodiment, the power supply circuit 122 may include at least a controllable switch device (hereinafter referred to as a first controllable switch device for the sake of distinction), and the first controllable switch device may be connected to the control module 11 and the debugging circuit 121, respectively. In a specific implementation, the debugging circuit 121 may be used to control the first controllable switch device to close to supply power to the control module 11 when it is determined that the vehicle-mounted component 10 allows debugging, or when it is determined that the vehicle-mounted component 10 does not allow debugging and it is detected that the debugging interface 13 is not connected to the debugging device 20. The debugging circuit 121 may also be used to control the first controllable switch device to open to stop supplying power to the control module 11 when it is determined that the vehicle-mounted component 10 does not allow debugging and it is detected that the debugging interface 13 is connected to the debugging device 20.

[0051] It should be noted that, in actual implementation, the power supply circuit 122 may also include components such as resistors, and the embodiments of the present application do not impose specific limitations on this.

[0052] For some possible implementations, see Figure 3 , Figure 3 is another structural diagram of a vehicle-mounted component provided in an embodiment of the present application. Figure 3 As shown, the debugging circuit 121 may include a control circuit 1211 and a switch circuit 1212. The control circuit 1211 may be connected to the switch circuit 1212, the control module 11, and the power supply circuit 122 respectively, and the switch circuit 1212 may be connected to the control module 11 and the debugging interface 13 respectively.

[0053] In a specific implementation, the switch circuit 1212 can be used to establish a connection between the control module 11 and the debugging interface 13 if it is determined according to the first signal provided by the control module 11 that the vehicle-mounted component 10 allows debugging. The switch circuit 1212 can also be used to disconnect the connection between the control module 11 and the debugging interface 13 if it is determined according to the first signal that the vehicle-mounted component 10 does not allow debugging. The switch circuit 1212 can also be used to send a second signal to the control circuit 1211. Here, the second signal is used to indicate whether the debugging interface 13 is connected to the debugging device 20.

[0054] Optionally, the switch circuit 1212 can be used to establish a connection between the control module 11 and the debugging interface 13 if it is determined that the first signal provided by the control module 11 is a first type of signal. Here, the first type of signal can be used to indicate that the vehicle-mounted component 10 allows debugging. The switch circuit 1212 can also be used to disconnect the connection between the control module 11 and the debugging interface 13 if it is determined that the first signal is a second type of signal. Here, the second type of signal can be used to indicate that the vehicle-mounted component 10 does not allow debugging.

[0055] It should be noted that the second signal may be a level signal.

[0056] Exemplarily, if the switch circuit 1212 determines that the debug interface 13 is connected to the debug device 20, it may send a high level signal to the control circuit 1211. If the switch circuit 1212 determines that the debug interface 13 is not connected to the debug device 20, it may send a low level signal to the control circuit 1211.

[0057] In an optional implementation, the control circuit 1211 is further configured to determine whether to control the power supply circuit 122 to stop supplying power to the control module 11 according to the first signal and the second signal.

[0058] In an optional embodiment, the control circuit 1211 can be used to control the power supply circuit 122 to stop supplying power to the control module 11 when it is determined according to the first signal that the vehicle-mounted component 10 is not allowed to be debugged, and when it is determined according to the second signal that the debugging interface 13 is connected to the debugging device 20.

[0059] In an optional embodiment, the control circuit 1211 can be used to control the power supply circuit 122 to supply power to the control module 11 when it is determined based on the first signal that the vehicle-mounted component 10 allows debugging, or when it is determined based on the first signal that the vehicle-mounted component 10 does not allow debugging and it is determined based on the second signal that the debugging interface 13 is not connected to the debugging device 20.

[0060] Optionally, the switch circuit 1212 may include at least one controllable switch device (hereinafter referred to as the second controllable switch device for easy distinction), and the second controllable switch device may be connected to the control circuit 1211, the control module 11, and the debugging interface 13 respectively.

[0061] In a specific implementation, the second controllable switch device can be used to close the second controllable switch device to establish a connection between the control module 11 and the debugging interface 13 if it is determined according to the first signal provided by the control module 11 that the vehicle-mounted component 10 allows debugging. The second controllable switch device can also be used to open the second controllable switch device to disconnect the connection between the control module 11 and the debugging interface 13 if it is determined according to the first signal that the vehicle-mounted component 10 does not allow debugging.

[0062] In the embodiment of the present application, the second controllable switch device may be a JTAG connection switch, which is used to establish a connection between the control module 11 and the debugging interface 13 .

[0063] It should be noted that, in actual implementation, the switch circuit 1212 may also include other components such as resistors. The embodiment of the present application does not specifically limit the implementation form of the switch circuit 1212.

[0064] In an alternative embodiment, see Figure 4 , Figure 4 is another structural diagram of a vehicle-mounted component provided in an embodiment of the present application. Figure 4 As shown, the control circuit 1211 may include an exclusive-OR gate NXOR and an OR gate OR. The exclusive-OR gate may be connected to the control module 11, the switch circuit 1212, and the OR gate respectively, and the OR gate may also be connected to the power supply circuit 122.

[0065] In a specific implementation, the XNOR gate can be used to output a sixth signal according to the first signal output by the control module 11 and the second signal output by the switch circuit 1212. The OR gate can be used to output a seventh signal according to the sixth signal and the first signal output by the control module 11. Here, the seventh signal can be used to indicate whether the power supply circuit 122 supplies power to the control module 11.

[0066] In some feasible implementations, the control module 11 may also be used to obtain a third signal through the vehicle bus of the vehicle, and determine whether the vehicle component 10 is in the debugging mode according to the third signal.

[0067] That is, the control module 11 can establish a communication connection with the vehicle through the vehicle bus to obtain a corresponding strategy to determine whether the vehicle-mounted component 10 is in the debugging mode. By obtaining the strategy by establishing a communication connection between the control module 11 and the vehicle, the strategy can be updated in real time according to the demand, thereby improving the safety of the vehicle-mounted component 10.

[0068] In an optional implementation, the control module 11 may establish a communication connection with the vehicle via a CAN (Controller Area Network) bus to obtain a third signal to determine whether the vehicle-mounted component 10 is in the debugging mode.

[0069] Optionally, the third signal may include a key or an unlocking protocol for determining whether the vehicle-mounted component 10 is in the debugging mode, which is not specifically limited in the embodiments of the present application. Specifically, when the third signal includes a key, the key may be encrypted using an asymmetric encryption method, which is not specifically limited in the embodiments of the present application.

[0070] In an optional embodiment, when the third signal includes a target key, the control module 11 can also be used to determine that the vehicle-mounted component 10 is in the debugging mode if it is determined that the target key is consistent with the preset key, that is, the vehicle-mounted component 10 allows debugging. The control module 11 can also be used to determine that the vehicle-mounted component 10 is not in the debugging mode if it is determined that the target key is inconsistent with the preset key, that is, the vehicle-mounted component 10 does not allow debugging.

[0071] Optionally, the debugging device 20 may be an electronic device that can be used to debug the vehicle-mounted component 10, such as a simulator, etc. The embodiment of the present application does not specifically limit the implementation form of the debugging device 20.

[0072] Optionally, when the debugging device 20 is an emulator 201, see Figure 5 , Figure 5 is another structural diagram of a vehicle-mounted component provided in an embodiment of the present application. Figure 5 As shown, the emulator 201 can be connected to the debugging interface 13 and the terminal device 30 respectively.

[0073] In a specific implementation, the terminal device 30 can transmit the debugging control signal to the control module 11 of the vehicle-mounted component 10 through the debugging apparatus 20 to debug the vehicle-mounted component 10. Here, the debugging control signal is used to obtain the code or data in the control module 11.

[0074] That is to say, when the debugging module 12 determines that the vehicle-mounted component 10 allows debugging and detects that the debugging interface 13 is connected to the debugging device 20, the debugging device 20 can pass the control signal output by the terminal device 30 to the control module 11 through the debugging interface 13 and the debugging module 12 in sequence, so that the emulator 201 can communicate directly with the control module 11, and then the code or data in the control module 11 of the vehicle-mounted component 10 can be obtained to realize the debugging of the vehicle-mounted component 10.

[0075] Optionally, the terminal device 30 may be any electronic device with a simulation test function, such as a smart phone, a portable notebook computer, a desktop computer, a tablet computer, etc. The embodiment of the present application does not specifically limit the implementation form of the terminal device 30 .

[0076] It should be noted that, in the embodiment of the present application, the vehicle-mounted component 10 may be a PCB (Printed Circuit Board) of a vehicle component system, such as a PCB of an engine system, a PCB of a brake system, etc. The embodiment of the present application does not impose any specific limitation on this.

[0077] See also Figure 6 , Figure 61 is a flow chart of a debugging method provided in an embodiment of the present application. The debugging method can be applied to the vehicle-mounted component 10 described in the previous embodiment. In the embodiment of the present application, the specific structure and function of the vehicle-mounted component 10 can be referred to the corresponding description in the previous embodiment, and this embodiment will not be repeated. Figure 6 As shown, the debugging method may specifically include the following steps:

[0078] S101, providing a first signal to a debugging module through a control module.

[0079] In some feasible implementations, the vehicle-mounted component 10 may provide a first signal to the debugging module 12 through the control module 11. Here, the first signal may be used to indicate whether the vehicle-mounted component 10 is allowed to be debugged.

[0080] Here, the specific process of the vehicle-mounted component 10 providing the first signal to the debugging module through the control module 11 can refer to the process of the control module 11 providing the first signal to the debugging module 12 described above, which will not be repeated here.

[0081] S102: When the debugging module determines, based on the first signal, that the vehicle-mounted component is not allowed to be debugged and detects that a debugging device is connected to the debugging interface, stopping power supply to the control module.

[0082] In some feasible implementations, the vehicle-mounted component 10 can stop supplying power to the control module 11 through the debugging module 12 when it is determined that the vehicle-mounted component 10 does not allow debugging according to the first signal and when it is detected that the debugging interface 13 is connected to the debugging device 20 .

[0083] Here, the specific process of the vehicle-mounted component 10 stopping supplying power to the control module 11 through the debugging module 12 when it is determined based on the first signal that the vehicle-mounted component 10 is not allowed to be debugged, and when it is detected that the debugging interface 13 is connected to the debugging device 20, can be referred to the process described above in which the debugging module 12 stops supplying power to the control module 11 when it is determined based on the first signal that the vehicle-mounted component 10 is not allowed to be debugged, and when it is detected that the debugging interface 13 is connected to the debugging device 20, and will not be repeated here.

[0084] In an optional embodiment, when the debugging module 12 includes a debugging circuit 121 and a power supply circuit 122, the vehicle-mounted component 10 can determine whether the vehicle-mounted component 10 allows debugging according to the first signal through the debugging circuit 121. The vehicle-mounted component 10 can also detect whether the debugging interface 13 is connected to the debugging device 20 through the debugging circuit 121. The vehicle-mounted component 10 can also control the power supply circuit 122 to stop supplying power to the control module 11 when it is determined through the debugging circuit 121 that the vehicle-mounted component 10 does not allow debugging and detects that the debugging interface 13 is connected to the debugging device 20. Here, the specific process can be referred to the relevant description above, and it will not be repeated here.

[0085] In an optional implementation, when the debugging circuit 121 includes a control circuit 1211 and a switch circuit 1212, the vehicle-mounted component 10 can establish a connection between the control module 11 and the debugging interface 13 if the vehicle-mounted component 10 is determined to allow debugging according to the first signal through the switch circuit 1212. The vehicle-mounted component 10 can also disconnect the connection between the control module 11 and the debugging interface 13 if the vehicle-mounted component 10 is determined not to allow debugging according to the first signal through the switch circuit 1212. Here, the specific process can be referred to the relevant description above, and it will not be repeated here.

[0086] Optionally, the vehicle-mounted component 10 may also output a second signal through the switch circuit 1212. Here, the second signal is used to indicate whether the debugging interface 13 is connected to the debugging device 20. Here, the specific process of the vehicle-mounted component 10 outputting the second signal through the switch circuit 1212 can refer to the process of the switch circuit 1212 outputting the second signal described above, which will not be repeated here.

[0087] Optionally, the vehicle-mounted component 10 can control the power supply circuit 122 to stop supplying power to the control module 11 when the control circuit 1211 determines that the vehicle-mounted component 10 is not allowed to be debugged according to the first signal and determines that the debugging interface 13 is connected to the debugging device 20 according to the second signal.

[0088] For some possible implementations, see Figure 7 , Figure 7 FIG. 1 is another flow chart of a debugging method provided in an embodiment of the present application. Figure 7 As shown, the debugging method may further include the steps of:

[0089] S103, supplying power to the control module through the debugging module when it is determined according to the first signal that the vehicle-mounted component allows debugging, or when it is determined according to the first signal that the vehicle-mounted component does not allow debugging and the debugging interface is not connected to a debugging device.

[0090] In some feasible implementations, the vehicle-mounted component 10 can power the control module 11 through the debugging module 12 when it is determined based on the first signal that the vehicle-mounted component 10 allows debugging, or when it is determined based on the first signal that the vehicle-mounted component 10 does not allow debugging and the debugging interface 13 is not connected to the debugging device 20.

[0091] Here, the specific process of the vehicle-mounted component 10, through the debugging module 12, supplying power to the control module 11 when it is determined according to the first signal that the vehicle-mounted component 10 is allowed to be debugged, or when it is determined according to the first signal that the vehicle-mounted component 10 is not allowed to be debugged and the debugging interface 13 is not connected to the debugging device 20, can be referred to the previous debugging module 12. When it is determined according to the first signal that the vehicle-mounted component 10 is allowed to be debugged, or when it is determined according to the first signal that the vehicle-mounted component 10 is not allowed to be debugged and the debugging interface 13 is not connected to the debugging device 20, the specific process of supplying power to the control module 11 will not be repeated here.

[0092] For some possible implementations, see Figure 8 , Figure 8 FIG. 1 is another flow chart of a debugging method provided in an embodiment of the present application. It should be understood that step S104 may be performed before step S101. Figure 8 As shown, the debugging method may further include the steps of:

[0093] S104, obtaining a third signal through the vehicle bus through the control module, and determining whether the vehicle component is in the debugging mode according to the third signal.

[0094] In some feasible implementations, the vehicle-mounted component 10 may obtain a third signal through the vehicle-mounted bus via the control module 11 , and determine whether the vehicle-mounted component 10 is in the debugging mode according to the third signal.

[0095] Here, the vehicle-mounted component 10 obtains the third signal through the vehicle-mounted bus through the control module 11, and determines whether the vehicle-mounted component 10 is in the debugging mode according to the third signal. The specific process can be referred to the previous control module 11 obtaining the third signal through the vehicle-mounted bus, and determining whether the vehicle-mounted component 10 is in the debugging mode according to the third signal. The process will not be repeated here.

[0096] In some feasible implementations, when the third signal includes the target key, the vehicle-mounted component 10 can determine that the vehicle-mounted component 10 is in the debugging mode if the control module 11 determines that the target key is consistent with the preset key. The vehicle-mounted component 10 can also determine that the vehicle-mounted component 10 is not in the debugging mode if the control module 11 determines that the target key is inconsistent with the preset key. Here, the specific process can be found in the relevant description above, which will not be repeated here.

[0097] The present application also provides a vehicle, see Fig. 9, Fig. 9 is a schematic diagram of the structure of a vehicle provided in an embodiment of the present application. Fig. 9 As shown, the vehicle may include the vehicle-mounted component 10 described in the above embodiment. The vehicle may also include a plurality of wheels, a seat, a vehicle-mounted power supply, electrical equipment, and the like.

[0098] It should be noted that, for the sake of simplicity, for any of the above-mentioned embodiments of the vehicle-mounted components, debugging methods and vehicles, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the described order of actions, because according to this application, some of its steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by this application.

[0099] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps is not limited to the listed steps, but optionally includes steps that are not listed, or optionally includes other steps inherent to these processes, methods, products or devices.

[0100] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0101] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the present application to be protected, those skilled in the art may understand and implement other changes to the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "a" does not exclude multiple situations. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0102] The embodiments of the present application are introduced in detail above. Specific examples are used herein to illustrate the principles and implementation methods of a vehicle-mounted component, a debugging method and a vehicle of the present application. The description of the above embodiments is used to help understand the method and core idea of ​​the present application. At the same time, for a person skilled in the art, according to the idea of ​​a vehicle-mounted component, a debugging method and a vehicle of the present application, there may be changes in the specific implementation method and the scope of application. In summary, the content of this specification should not be understood as a limitation on the present application.

[0103] Those skilled in the art should be aware that in one or more of the above examples, the functions described in this application can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media can be any available media that can be accessed by general or special-purpose computers.

[0104] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only the specific implementation methods of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

Claims

1. A vehicle-mounted component, characterized in that: The vehicle-mounted component includes a control module, a debugging module and a debugging interface, and the debugging module is connected to the control module and the debugging interface respectively; The control module is used to provide a first signal to the debugging module, wherein the first signal is used to indicate whether the vehicle-mounted component is allowed to be debugged; The debugging module is used to stop supplying power to the control module when it is determined according to the first signal that the vehicle-mounted component does not allow debugging and it is detected that the debugging interface is connected to a debugging device.

2. The vehicle-mounted component according to claim 1, characterized in that: The debugging module includes a debugging circuit and a power supply circuit, the debugging circuit is connected to the power supply circuit, the control module, and the debugging interface respectively, and the power supply circuit is also connected to the control module; The debugging circuit is used to determine whether the vehicle-mounted component allows debugging according to the first signal; The debugging circuit is also used to detect whether the debugging interface is connected to the debugging device; The debugging circuit is also used to control the power supply circuit to stop supplying power to the control module when it is determined that the vehicle-mounted component does not allow debugging and it is detected that the debugging interface is connected to the debugging device.

3. The vehicle-mounted component according to claim 2, characterized in that: The debugging circuit includes a control circuit and a switch circuit, the control circuit is respectively connected to the switch circuit, the control module, and the power supply circuit, and the switch circuit is also respectively connected to the control module and the debugging interface; The switch circuit is used to establish a connection between the control module and the debugging interface if it is determined according to the first signal that the vehicle-mounted component allows debugging; The switch circuit is further used to disconnect the control module from the debugging interface if it is determined according to the first signal that the vehicle-mounted component does not allow debugging; The switch circuit is further used to send a second signal to the control circuit, wherein the second signal is used to indicate whether the debugging interface is connected to the debugging device.

4. The vehicle-mounted component according to claim 3, characterized in that: The control circuit is used to determine whether to control the power supply circuit to stop supplying power to the control module according to the first signal and the second signal.

5. The vehicle-mounted component according to claim 4, characterized in that: The control circuit is used to control the power supply circuit to stop supplying power to the control module when it is determined according to the first signal that the vehicle-mounted component is not allowed to be debugged, and when it is determined according to the second signal that the debugging interface is connected to the debugging device.

6. The vehicle-mounted component according to claim 1, characterized in that: The debugging module is also used to power the control module when it is determined according to the first signal that the vehicle-mounted component allows debugging, or when it is determined according to the first signal that the vehicle-mounted component does not allow debugging and the debugging interface is not connected to the debugging device.

7. The vehicle-mounted component according to any one of claims 1 to 6, characterized in that: The control module is used to obtain a third signal through the vehicle bus, and determine whether the vehicle component is in a debugging mode according to the third signal.

8. The vehicle-mounted component according to claim 7, characterized in that: The third signal includes a target key, and the control module is further configured to determine that the vehicle-mounted component is in a debugging mode if it is determined that the target key is consistent with a preset key; The control module is also used to determine that the vehicle-mounted component is not in the debugging mode if it is determined that the target key is inconsistent with the preset key.

9. A debugging method, characterized in that: Applied to a vehicle-mounted component, the vehicle-mounted component at least includes a control module, a debugging module and a debugging interface, the debugging module is connected to the control module and the debugging interface respectively, and the method includes: Providing a first signal to the debugging module through the control module, wherein the first signal is used to indicate whether the vehicle-mounted component is allowed to be debugged; When the debugging module determines that the vehicle-mounted component is not allowed to be debugged according to the first signal and detects that the debugging interface is connected to a debugging device, the power supply to the control module is stopped.

10. The method according to claim 9, characterized in that The debugging module includes a debugging circuit and a power supply circuit. The debugging circuit is connected to the power supply circuit, the control module, and the debugging interface respectively. The power supply circuit is also connected to the control module. When the debugging module determines that the vehicle-mounted component is not allowed to be debugged according to the first signal and detects that the debugging interface is connected to a debugging device, the control module stops supplying power to the control module, including: Determining whether the vehicle-mounted component is allowed to be debugged according to the first signal by the debugging circuit; Detecting, by means of the debugging circuit, whether the debugging interface is connected to a debugging device; When it is determined by the debugging circuit that the vehicle-mounted component does not allow debugging and it is detected that the debugging interface is connected to the debugging device, the power supply circuit is controlled to stop supplying power to the control module.

11. The method according to claim 10, characterized in that The debugging circuit at least includes a control circuit and a switch circuit, the control circuit is respectively connected to the switch circuit, the control module, and the power supply circuit, and the switch circuit is also respectively connected to the control module and the debugging interface, and the debugging is used to determine whether the vehicle-mounted component is allowed to be debugged according to the first signal, including: If it is determined by the switch circuit according to the first signal that the vehicle-mounted component allows debugging, then establishing a connection between the control module and the debugging interface; If the switch circuit determines according to the first signal that the vehicle-mounted component does not allow debugging, the connection between the control module and the debugging interface is disconnected.

12. The method according to claim 11, characterized in that The step of detecting whether the debugging interface is connected to a debugging device by means of the debugging circuit comprises: A second signal is outputted through the switch circuit, wherein the second signal is used to indicate whether the debugging interface is connected to a debugging device.

13. The method according to claim 11 or 12, characterized in that: The step of controlling the power supply circuit to stop supplying power to the control module when it is determined by the debugging circuit that the vehicle-mounted component is not allowed to be debugged and it is detected that the debugging interface is connected to the debugging device comprises: When the control circuit determines according to the first signal that the vehicle-mounted component is not allowed to be debugged, and determines according to the second signal that the debugging interface is connected to the debugging device, the power supply circuit is controlled to stop supplying power to the control module.

14. The method according to claim 9, characterized in that The method further comprises: The control module is powered by the debugging module when it is determined according to the first signal that the vehicle-mounted component allows debugging, or when it is determined according to the first signal that the vehicle-mounted component does not allow debugging and the debugging interface is not connected to the debugging device.

15. The method according to any one of claims 9 to 14, characterized in that: The method further comprises: The control module is used to obtain a third signal through the vehicle bus, and it is determined whether the vehicle component is in the debugging mode according to the third signal.

16. The method according to claim 15, characterized in that The third signal includes a target key, and the method further includes: If it is determined by the control module that the target key is consistent with the preset key, it is determined that the vehicle-mounted component is in the debugging mode; If it is determined by the control module that the target key is inconsistent with the preset key, it is determined that the vehicle-mounted component is not in the debugging mode.

17. A vehicle, characterized in that: The vehicle comprises the vehicle-mounted component according to any one of claims 1-8.

Images