On-vehicle controller interface control circuit, control method and vehicle

Abstract

The present application discloses a vehicle-mounted controller interface control circuit, a control method and a vehicle, which relate to the field of vehicle technology and can avoid controller reset caused by simulator access and avoid affecting the debugging of the controller by the simulator. A vehicle-mounted controller interface control circuit comprises: a JTAG interface circuit, one end of which is used to access the simulator and the other end is used to access the vehicle-mounted controller, the JTAG interface circuit comprises a reset signal pin, the reset signal pin is used to provide a reset signal to the vehicle-mounted controller; the reset signal pin is electrically connected to a control circuit, the control circuit is used to filter out the reset signal transmitted from the simulator to the reset signal pin, and the reset signal is used to control the reset of the vehicle-mounted controller.

Description

Technical Field

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

[0002] Currently, during the vehicle development phase, it is necessary to debug the software of the vehicle controller through a simulator when the vehicle is powered on to implement the software control logic.

[0003] However, during the debugging stage of the vehicle, when the vehicle is powered on, the controller is connected to the emulator through the interface. The connection of the emulator will pull down the potential of the reset pin of the interface. The pulled-down reset pin will transmit the reset signal to the controller, causing the controller to reset, resulting in interruption of the software operation in the controller and affecting the debugging of the controller. Summary of the invention

[0004] The embodiments of the present application provide a vehicle-mounted controller interface control circuit, a control method and a vehicle, which can avoid controller reset caused by simulator access and avoid affecting the simulator's debugging of the controller.

[0005] According to a first aspect of an embodiment of the present application, there is provided a vehicle controller interface control circuit, comprising:

[0006] A JTAG interface circuit, one end of which is used to access the emulator and the other end of which is used to access the vehicle controller, wherein the JTAG interface circuit includes a reset signal pin, and the reset signal pin is used to provide a reset signal to the vehicle controller;

[0007] The reset signal pin is electrically connected to a control circuit, and the control circuit is used to filter out the reset signal transmitted from the simulator to the reset signal pin, and the reset signal is used to control the vehicle controller to reset.

[0008] In some implementations, the control circuit includes a filtering branch, and when the JTAG interface circuit is connected to the emulator, the filtering branch is used to filter out a first reset signal transmitted from the emulator to the JTAG interface circuit.

[0009] In some embodiments, the control circuit includes a transmission branch, which is used to transmit a non-first reset signal to the vehicle controller, and the non-first reset signal is a reset signal other than the first reset signal of the emulator connected to the JTAG interface circuit.

[0010] In some embodiments, the JTAG interface circuit includes a JTAG interface;

[0011] When the reset signal is at a low level, the reset signal is valid, and when the reset signal is at a high level, the reset signal is invalid.

[0012] In some embodiments, the filtering branch comprises an inverter; and / or,

[0013] The transmission branch includes a resistor.

[0014] In some embodiments, the filter branch includes a switch component, and when the JTAG interface circuit is connected to the emulator, the switch component of the filter branch is turned on, and after the emulator is connected to the JTAG interface circuit and transmits the first reset signal, the switch component of the filter branch is turned off; and / or,

[0015] The transmission branch includes a switch component. When the JTAG interface circuit is connected to the emulator, the switch component of the transmission branch is closed. After the emulator is connected to the JTAG interface circuit and transmits the first reset signal, the switch component of the transmission branch is opened.

[0016] A second aspect of the embodiment of the present application provides a vehicle controller interface control method, which is applied to the vehicle controller interface control circuit as described in the first aspect, and the method includes:

[0017] Controlling one end of the JTAG interface circuit to be connected to the emulator, and controlling the other end of the JTAG interface circuit to be connected to the vehicle controller;

[0018] The reset signal transmitted from the emulator to the reset signal pin of the JTAG interface circuit is filtered out, wherein the reset signal is used to control the resetting of the vehicle-mounted controller.

[0019] In some implementations, filtering out the reset signal transmitted by the emulator to the reset signal pin of the JTAG interface circuit includes:

[0020] filtering out a first reset signal transmitted by the emulator to the JTAG interface circuit;

[0021] After the emulator is connected to the JTAG interface circuit to transmit the first reset signal, a non-first reset signal is transmitted to the vehicle controller, wherein the non-first reset signal is a reset signal other than the first reset signal of the emulator connected to the JTAG interface circuit.

[0022] According to a third aspect of an embodiment of the present application, a vehicle is provided, including:

[0023] The vehicle controller interface control circuit as described in the first aspect.

[0024] In some embodiments, the vehicle further comprises:

[0025] An on-board controller electrically connected to a JTAG interface circuit of the on-board controller interface control circuit;

[0026] The vehicle-mounted controller includes a central controller, and the central controller includes at least one of a domain controller, a storage unit outside the domain controller, a power module of the domain controller, and an Ethernet switch.

[0027] The vehicle controller interface control circuit provided in the embodiment of the present application is electrically connected to the control circuit via a reset signal pin. The control circuit can filter out the reset signal transmitted by the emulator to the reset signal pin. After the JTAG interface circuit is connected to the emulator to lower the potential of the reset signal pin, the control circuit can invalidate the low-level reset signal. The vehicle controller will not be affected by the low-level reset signal, the vehicle controller will not be reset, and software debugging can be performed normally. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 A schematic structural block diagram of a vehicle controller interface control circuit provided in an embodiment of the present application;

[0029] Figure 2 A schematic structural block diagram of another vehicle-mounted controller interface control circuit provided in an embodiment of the present application;

[0030] Figure 3 A schematic structural diagram of a JTAG interface circuit provided in an embodiment of the present application;

[0031] Figure 4 A schematic flowchart of a vehicle controller interface control method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to better understand the technical solutions provided by the embodiments of this specification, the technical solutions of the embodiments of this specification are described in detail below through the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.

[0033] In this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of more restrictions, the elements limited by the statement "comprise one..." do not exclude the existence of other identical elements in the process, method, article or equipment including the elements. The term "more than two" includes two or more than two situations.

[0034] At present, during the vehicle development stage, it is necessary to debug the software of the vehicle controller through the simulator when the vehicle is powered on to implement the software control logic. However, during the vehicle debugging stage, when the vehicle is powered on, the controller is connected to the simulator through the interface. The connection of the simulator will pull down the reset pin potential of the interface. The reset pin pulled down will transmit the reset signal to the controller, which will reset the controller, interrupt the software operation in the controller, and affect the debugging of the controller.

[0035] In view of this, an embodiment of the present application provides a vehicle-mounted controller interface control circuit, a control method and a vehicle, which can avoid controller reset caused by simulator access and avoid affecting the simulator's debugging of the controller.

[0036] In a first aspect of the embodiments of the present application, a vehicle controller interface control circuit is provided. Figure 1 This is a schematic structural block diagram of a vehicle controller interface control circuit provided in an embodiment of the present application. Figure 1 As shown, the vehicle controller interface control circuit provided in the embodiment of the present application includes: a JTAG interface circuit 100, one end of which is used to connect to the emulator 200, and the other end is used to connect to the vehicle controller 300, the JTAG interface circuit 100 includes a reset signal pin 110, and the reset signal pin 110 is used to provide a reset signal to the vehicle controller 300; the reset signal pin 110 is electrically connected to the control circuit 120, and the control circuit 120 is used to filter out the reset signal transmitted from the emulator 200 to the reset signal pin 110, and the reset signal is used to control the reset of the vehicle controller 300.

[0037] It should be noted that the emulator 200 may be a Lauterbach emulator, and the emulator 200 may be used to debug the software program of the vehicle controller 300 . The JTAG interface circuit 100 provides a connection interface between the emulator 200 and the vehicle controller 300 .

[0038] It should be noted that during the debugging phase of the vehicle, the software of the vehicle controller needs to be debugged through the emulator when the vehicle is powered on to implement the software control logic. When the vehicle is powered on, the JTAG interface circuit is connected to the emulator. The connection of the emulator will pull down the potential of the reset signal pin. After the reset signal pin is connected to the vehicle controller, the reset signal formed by the low potential of the reset signal pin will reset the vehicle controller. The reset of the vehicle controller will cause the software program in the vehicle controller to be interrupted, thereby affecting the debugging process of the vehicle controller.

[0039] For the above problems, refer to Figure 1 A control circuit 120 is set on the reset signal pin 110 of the JTAG interface circuit 100. After the JTAG interface circuit 100 is connected to the emulator 200 and the potential of the reset signal pin 110 is pulled down, the control circuit 120 can filter out the low-level reset signal. The filtering method can be shielding or inverting, so that the low-level reset signal is invalid. Then, the vehicle controller 300 will not be affected by the low-level reset signal, the vehicle controller 300 will not be reset, and software debugging can be performed normally.

[0040] The vehicle controller interface control circuit provided in the embodiment of the present application is electrically connected to the control circuit 120 via the reset signal pin 110. The control circuit 120 can filter out the reset signal transmitted from the emulator 200 to the reset signal pin 110. After the JTAG interface circuit 100 is connected to the emulator 200 and the potential of the reset signal pin 110 is lowered, the control circuit 120 can make the low-level reset signal invalid. Then, the vehicle controller 300 will not be affected by the low-level reset signal, the vehicle controller 300 will not be reset, and software debugging can be performed normally.

[0041] In some implementations, when the reset signal is at a low level, the reset signal is valid, and when the reset signal is at a high level, the reset signal is invalid. A valid reset signal will control the vehicle controller to reset. Figure 1 After the JTAG interface circuit 100 is connected to the emulator 200 and the potential of the reset signal pin 110 is pulled down, the control circuit 120 can convert the low-level reset signal into a high-level signal, making the low-level reset signal invalid. Then, the reset signal received by the vehicle controller 300 is a high-level signal. Under the action of the control circuit 120, the vehicle controller 300 will not be affected by the low-level reset signal, the vehicle controller 300 will not be reset, and software debugging can be performed normally.

[0042] In some embodiments, Figure 2 This is a schematic structural block diagram of another vehicle controller interface control circuit provided in an embodiment of the present application. Figure 2As shown, the control circuit 120 includes a filter branch 121. When the JTAG interface circuit 100 is connected to the emulator 200, the filter branch 121 is used to filter out the first reset signal transmitted from the emulator 200 to the JTAG interface circuit 100. The control circuit 120 includes a transmission branch 122. The transmission branch 122 is used to transmit a non-first reset signal to the vehicle controller 300. The non-first reset signal is a reset signal other than the first reset signal when the emulator 200 is connected to the JTAG interface circuit.

[0043] refer to Figure 2 , the filter branch 121 is connected to the reset signal pin 110 during the transmission of the first reset signal after the emulator 200 is connected to the JTAG interface circuit 100. The filter branch 121 can filter out the first reset signal to prevent the first reset signal from controlling the reset of the vehicle controller 300. It should be noted that the first reset signal is a low-level signal generated by the emulator 200 connecting to the JTAG interface circuit 100, which causes the potential of the reset signal pin 110 to be pulled down. The low-level signal will be transmitted to the vehicle controller 300 to cause it to reset. The low-level signal as the first reset signal is filtered out, and the vehicle controller 300 can be reset when the emulator 200 is connected after power-on. After the first reset signal, the transmission branch 122 can normally transmit the reset signal on the reset signal pin 110 to the vehicle controller 300, which can avoid affecting the normal reset of the vehicle controller 300.

[0044] It should be noted that the control of the filter branch 121 and the transmission branch 122 accessing the reset signal pin 110 can be controlled by the signal received by the JTAG interface circuit 100 or by the internal pin of the JTAG interface circuit 100 through signal transmission. For example, when the corresponding pin of the JTAG interface circuit 100 accesses the signal of the emulator 200, the filter branch 121 can be triggered to access the reset signal pin 110 through circuit design, and the transmission branch 122 can be connected to the reset signal pin 110 after the set time is reached by timing.

[0045] For example, Figure 3 The following is a schematic diagram of a JTAG interface circuit provided in an embodiment of the present application. Figure 3 As shown, the reset signal pin of the JTAG interface is connected to the control circuit, one end of the control circuit is connected to the input reset signal RESET_JTAG, and the other end outputs the output reset signal RESET_SYSTEM, and the output reset signal RESET_SYSTEM is used to be transmitted to the vehicle controller. Figure 3The model of the JTAG interface shown is FTSH-105-01-L-DV-K-TR, and the interface chip J9004 has 10 pins, which are identified by numbers 1-10 respectively. The 10th pin is the reset signal pin, and the 2nd, 4th, 6th, and 8th pins are used to access the emulator and receive the controller debugging signals MCU_JTAG_TMS, MCU_JTAG_TCK, MCU_JTAG_TDO, and MCU_JTAG_TDI respectively. The 1st pin is connected to the power supply voltage signal P3_3V_IO3P3, and the 3rd, 5th, 7th, and 9th pins are grounded. Inductor B9002, a first capacitor C9010, a second capacitor C9011, and a resistor R9041 are also provided. The JTAG interface is also equipped with 6 test points, namely I9012ICT_0.8mm, I9013 ICT_0.8mm, I9014 ICT_0.8mm, I9015 ICT_0.8mm, I9016 ICT_0.8mm and I9032 ICT_0.8mm; the JTAG interface is also equipped with ESD structure, that is, Zener diodes, namely D9002, D9005, D9006, D9007 and D9008, and the model is SP3022-01ETG.

[0046] Exemplarily, Table 1 is an example of the corresponding reset signal on the reset signal pin. As shown in Table 1, by adding a control circuit to the JTAG interface, when the vehicle is connected to the emulator when it is powered on, even if the RESET_JTAG signal of the JTAG interface is pulled low, the vehicle controller will not be reset. The control circuit on the reset signal pin ensures that the RESET_SYSTEM signal remains in a high level state after the emulator is connected. After the emulator is connected and stable, the RESET_SYSTEM logic level can still be controlled normally through emulator debugging, and it is consistent with RESET_JTAG.

[0047]

[0048] Table 1

[0049] In some implementations, the filtering branch 121 includes an inverter; the inverter can convert a low-level reset signal into a high-level signal, which is easy to implement and has a simple structure.

[0050] In some implementations, the transmission branch 122 includes a resistor, which can play a role in voltage division protection to prevent excessively high voltage signals from damaging the onboard controller.

[0051] In some embodiments, the filter branch 121 includes a switch component. When the JTAG interface circuit 100 is connected to the emulator 200, the switch component of the filter branch 121 is turned on. After the emulator 200 is connected to the JTAG interface circuit 100 and transmits the first reset signal, the switch component of the filter branch 121 is turned off. Exemplarily, the switch component of the filter branch 121 can be triggered to turn on or off by the circuit design in the JTAG interface circuit 100 to filter the first reset signal of the emulator.

[0052] In some embodiments, the transmission branch 122 includes a switch component. When the JTAG interface circuit 100 is connected to the emulator 200, the switch component of the transmission branch 122 is closed. After the emulator 200 is connected to the JTAG interface circuit 100 and the first reset signal is transmitted, the switch component of the transmission branch 122 is turned on. Exemplarily, when the emulator 200 is connected to the JTAG interface circuit 100, the switch component of the filter branch 121 is turned on, and the switch component of the transmission branch 122 is turned off. Then, the filter branch 121 is connected to the reset signal pin 110, and the first reset signal can be filtered, that is, the first low-level signal is filtered. After the first low-level signal passes, the reset signal pin 110 returns to a high level, and the switch component of the filter branch 121 can be closed, and the switch component of the transmission branch 122 is turned on to transmit a normal reset signal.

[0053] The vehicle controller interface control circuit provided by the embodiment of the present application can solve the problem that the vehicle's ECU (control unit) software is abnormally interrupted due to the reset of the controller when connected to the simulator during the vehicle development stage, resulting in the ECU being unable to restart and reset, requiring the ECU to be returned to the factory for repair or parts being scrapped. That is, it can solve the system reset waiting time caused by connecting to the simulator in the power-on state, saving the development cycle.

[0054] A second aspect of the embodiment of the present application provides a vehicle controller interface control method, which is applied to the vehicle controller interface control circuit as described in the first aspect. Figure 4 The following is a schematic flow chart of a vehicle controller interface control method provided in an embodiment of the present application. Figure 4 As shown, the vehicle controller interface control method includes:

[0055] S400: Control one end of the JTAG interface circuit to connect to the emulator, and control the other end of the JTAG interface circuit to connect to the vehicle controller. Figure 1 , controlling the JTAG interface circuit 100 to connect the emulator 200 and the vehicle controller 300 .

[0056] S500: Filter out the reset signal transmitted from the emulator to the reset signal pin of the JTAG interface circuit, wherein the reset signal is used to control the reset of the vehicle controller. A control circuit 120 is set on the reset signal pin 110 of the JTAG interface circuit 100. After the JTAG interface circuit 100 is connected to the emulator 200 and the potential of the reset signal pin 110 is pulled down, the control circuit 120 can filter out the low-level reset signal. The filtering method can be shielding or inverting, so that the low-level reset signal is invalid. Then, the vehicle controller 300 will not be affected by the low-level reset signal, and the vehicle controller 300 will not be reset, and the software debugging can be performed normally.

[0057] In some implementations, step S500 may include:

[0058] Filter out the first reset signal transmitted from the emulator to the JTAG interface circuit.

[0059] Exemplarily, when the reset signal is at a low level, the reset signal is valid, and when the reset signal is at a high level, the reset signal is invalid. A valid reset signal will control the vehicle controller to reset. Figure 1 After the JTAG interface circuit 100 is connected to the emulator 200 and the potential of the reset signal pin 110 is pulled down, the control circuit 120 can convert the low-level reset signal into a high-level signal, making the low-level reset signal invalid. Then, the reset signal received by the vehicle controller 300 is a high-level signal. Under the action of the control circuit 120, the vehicle controller 300 will not be affected by the low-level reset signal, and the vehicle controller 300 will not be reset, so the software debugging can be performed normally.

[0060] refer to Figure 2 When the JTAG interface circuit 100 is connected to the emulator 200 , the filter branch 121 is used to filter out the first reset signal transmitted from the emulator 200 to the JTAG interface circuit 100 .

[0061] After the simulator is connected to the JTAG interface circuit and transmits the first reset signal, a non-first reset signal is transmitted to the vehicle controller, wherein the non-first reset signal is a reset signal other than the first reset signal of the simulator being connected to the JTAG interface circuit.

[0062] Exemplary, reference Figure 2, the transmission branch 122 is used to transmit a non-first reset signal to the vehicle controller 300. The non-first reset signal is a reset signal other than the first reset signal of the emulator 200 connected to the JTAG interface circuit. The filter branch 121 is connected to the reset signal pin 110 during the transmission of the first reset signal after the emulator 200 is connected to the JTAG interface circuit 100. The filter branch 121 can filter out the first reset signal to prevent the first reset signal from controlling the vehicle controller 300 to reset. It should be noted that the first reset signal is a low-level signal generated by the potential of the reset signal pin 110 being pulled down when the emulator 200 is connected to the JTAG interface circuit 100. The low-level signal will be transmitted to the vehicle controller 300 to cause it to reset. The low-level signal as the first reset signal will be filtered out, so that the vehicle controller 300 can be reset when the emulator 200 is connected after power-on. After the first reset signal, the transmission branch 122 can normally transmit the reset signal on the reset signal pin 110 to the vehicle controller 300 , thereby avoiding affecting the normal reset of the vehicle controller 300 .

[0063] According to a third aspect of an embodiment of the present application, a vehicle is provided, including:

[0064] The vehicle controller interface control circuit as described in the first aspect.

[0065] In some embodiments, reference Figure 1 The vehicle further includes: an on-board controller 300, which is electrically connected to a JTAG interface circuit 100 of the on-board controller interface control circuit.

[0066] Exemplarily, the vehicle controller may include a central controller of the vehicle, and the central controller may include at least one of a domain controller, a storage unit outside the domain controller, a power module of the domain controller, and an Ethernet switch. The domain controller inside the central controller may be an intelligent cockpit system controller or an intelligent driving system controller, which is not specifically limited in the embodiments of the present application.

[0067] The vehicle provided in the embodiment of the present application is provided with a vehicle controller interface control circuit, which can solve the problem that the software operation of the vehicle's ECU (control unit) is abnormally interrupted due to the reset of the controller connected to the simulator during the vehicle development stage, resulting in the ECU being unable to restart and reset, and requiring the ECU to be returned to the factory for repair or parts being scrapped. That is, the system reset waiting time caused by connecting to the simulator in the power-on state can be solved, saving the development cycle.

[0068] It should be noted that in the above embodiments, the description of each embodiment has its own emphasis, and for parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0069] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-readable program code.

[0070] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0071] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0072] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0073] An embodiment of the present application also provides a computer program product, which includes computer software instructions. When the computer software instructions are executed on a processing device, the processing device executes the process of the vehicle controller interface control method.

[0074] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integration. Available media can be magnetic media, (e.g., floppy disk, hard disk, tape), optical media (e.g., DVD), or semiconductor media (e.g., solid state disk (solid state disk, SSD)), etc.

[0075] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0076] In the several embodiments provided in the present application, it should be understood that the disclosed devices, apparatuses and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0077] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

[0079] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0080] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

[0081] Although the preferred embodiments of this specification have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of this specification.

[0082] Obviously, those skilled in the art can make various changes and modifications to this specification without departing from the spirit and scope of this specification. Thus, if these modifications and variations of this specification fall within the scope of the claims of this specification and their equivalents, this specification is also intended to include these modifications and variations.

Claims

1. A vehicle controller interface control circuit, characterized in that: include: A JTAG interface circuit, one end of which is used to access the emulator and the other end of which is used to access the vehicle controller, wherein the JTAG interface circuit includes a reset signal pin, and the reset signal pin is used to provide a reset signal to the vehicle controller; The reset signal pin is electrically connected to a control circuit, the control circuit is used to filter out the reset signal transmitted from the simulator to the reset signal pin, the reset signal is used to control the vehicle controller to reset; The control circuit comprises a filtering branch, and when the JTAG interface circuit is connected to the emulator, the filtering branch is used to filter out the first reset signal transmitted from the emulator to the JTAG interface circuit; The control circuit comprises a transmission branch, the transmission branch is used to transmit a non-first reset signal to the vehicle-mounted controller, the non-first reset signal is a reset signal other than the first reset signal of the emulator connected to the JTAG interface circuit; The filtering branch comprises an inverter; and / or, The transmission branch includes a resistor; The filter branch includes a switch component. When the JTAG interface circuit is connected to the emulator, the switch component of the filter branch is turned on. After the emulator is connected to the JTAG interface circuit and transmits the first reset signal, the switch component of the filter branch is turned off. and / or, The transmission branch includes a switch component. When the JTAG interface circuit is connected to the emulator, the switch component of the transmission branch is closed. After the emulator is connected to the JTAG interface circuit and transmits the first reset signal, the switch component of the transmission branch is opened.

2. The vehicle controller interface control circuit according to claim 1, characterized in that: When the reset signal is at a low level, the reset signal is valid, and when the reset signal is at a high level, the reset signal is invalid.

3. A vehicle controller interface control method, characterized in that: Applied to the vehicle controller interface control circuit as claimed in claim 1 or 2, the method comprises: Controlling one end of the JTAG interface circuit to be connected to the emulator, and controlling the other end of the JTAG interface circuit to be connected to the vehicle controller; The reset signal transmitted from the emulator to the reset signal pin of the JTAG interface circuit is filtered out, wherein the reset signal is used to control the resetting of the vehicle-mounted controller.

4. The vehicle controller interface control method according to claim 3, characterized in that: The filtering out the reset signal transmitted by the emulator to the reset signal pin of the JTAG interface circuit includes: filtering out a first reset signal transmitted by the emulator to the JTAG interface circuit; After the emulator is connected to the JTAG interface circuit to transmit the first reset signal, a non-first reset signal is transmitted to the vehicle controller, wherein the non-first reset signal is a reset signal other than the first reset signal of the emulator connected to the JTAG interface circuit.

5. A vehicle, characterized in that: include: The vehicle controller interface control circuit according to any one of claims 1 or 2.

6. The vehicle according to claim 5, characterized in that Also includes: An on-board controller electrically connected to a JTAG interface circuit of the on-board controller interface control circuit; The vehicle-mounted controller includes a central controller, and the central controller includes at least one of a domain controller, a storage unit outside the domain controller, a power module of the domain controller, and an Ethernet switch.

Images