KR101726295B1 - System and method for debugging electronic control unit - Google Patents

System and method for debugging electronic control unit Download PDF

Info

Publication number
KR101726295B1
KR101726295B1 KR1020150175840A KR20150175840A KR101726295B1 KR 101726295 B1 KR101726295 B1 KR 101726295B1 KR 1020150175840 A KR1020150175840 A KR 1020150175840A KR 20150175840 A KR20150175840 A KR 20150175840A KR 101726295 B1 KR101726295 B1 KR 101726295B1
Authority
KR
South Korea
Prior art keywords
debugging
electronic control
interface
mcu
control device
Prior art date
Application number
KR1020150175840A
Other languages
Korean (ko)
Inventor
유진호
Original Assignee
주식회사 현대케피코
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 현대케피코 filed Critical 주식회사 현대케피코
Priority to KR1020150175840A priority Critical patent/KR101726295B1/en
Application granted granted Critical
Publication of KR101726295B1 publication Critical patent/KR101726295B1/en

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
    • B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
    • B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
    • B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/362—Software debugging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/362—Software debugging
    • G06F11/366—Software debugging using diagnostics
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3696—Methods or tools to render software testable

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mechanical Engineering (AREA)
  • Automation & Control Theory (AREA)
  • Human Computer Interaction (AREA)
  • Transportation (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The present invention relates to a technology to debug an electronic control device. According to the present invention, the system to debug an electronic control device, which debugs the electronic control device by using a debugging tool, comprises: a micro-control unit (MCU) which has software inside; a connector which receives a signal which is transmitted from an external device; and an interface which connects the MCU and connector. The MCU activates the interface, receives the debugging value provided after the debugging start value from the interface, and debugs the software when it is determined that a signal received from the connector is a debugging start value which is provided from the debugging tool. The present invention aims to provide a system to debug an electronic control device, which is able to debug the electronic control device even when it is assembled with a waterproof case and a method thereof.

Description

[0001] DESCRIPTION [0002] SYSTEM AND METHOD FOR DEBUGGING ELECTRONIC CONTROL UNIT [0003]

The present invention relates to a technique for debugging an electronic control device, and more particularly, to an electronic control device debugging system and method capable of debugging an electronic control device even when assembled in a waterproof case.

BACKGROUND ART [0002] With advances in electronic control technology, products equipped with an electronic control unit (ECU) are increasing in number. For example, most of moving objects such as vehicles, ships, and aircraft are equipped with electronic control devices for controlling the engine or navigation device.

Generally, an ECU mounted on a vehicle monitors and controls the state of an engine, an automatic transmission, and an ABS (Anti-lock Brake System) for vehicle control and stability according to driving conditions.

The ECU controls various actors in the vehicle according to logic in response to the values of various sensors in the vehicle, in order to operate various devices of the vehicle.

That is, the ECU controls the ignition timing of the engine, the fuel injection, the idling, and the like, and controls the overall portion of the vehicle such as the operating system, the braking system, and the steering system.

The ECU includes an input port for receiving vehicle condition information that senses a vehicle condition that senses a state change of the operating devices of the vehicle, a microcontroller unit for calculating the vehicle condition information in real time according to pre- A microcontroller unit (MCU), a memory for storing information necessary for operation of the operating devices, and an output port for transmitting the control result output from the microcontroller unit to each operating device.

On the other hand, since the ECU is used for enhancing the safety of the vehicle, if there is an error or a bug in the ECU, the safety of the driver and the passenger may be deteriorated. Therefore, it is necessary to test the ECU to find out what kind of operation is indicated when an error code is received, whether the ECU outputs a desired output value, whether the desired network design is executed or the like.

If the test result is unsatisfactory, debugging such as change operation or reprogramming for the loaded application program should be performed.

These ECUs are connected to a PC for program development and debugged, and the majority of the ECUs currently in use are connected to the PC using a Joint Test Action Group (JTAG) port.

On the other hand, in order to waterproof the ECU, the ECU can be mounted on the vehicle while assembled in the waterproof case. If the ECU is assembled in the waterproof case, the debugging operation using the JTAG port can not be performed.

That is, when the ECU is assembled in a waterproof case, the JTAG port is also covered by the waterproof case, and debugging using the JTAG port can not be performed. Therefore, there is a need for a technique capable of debugging the ECU even when the ECU is assembled in the waterproof case.

Of course, although the above has been described with respect to the ECU of the vehicle, the above-mentioned problem is not limited to the ECU of the vehicle.

SUMMARY OF THE INVENTION Accordingly, the present invention has been made keeping in mind the above problems occurring in the prior art, and it is an object of the present invention to provide an electronic control device debugging system and method capable of debugging an electronic control device even when assembled in a waterproof case. .

According to an aspect of the present invention, there is provided an electronic control unit debugging system for debugging an electronic control unit using a debugging tool, the electronic control unit debugging system comprising: An MCU (Micro Control Unit); A connector for receiving a signal transmitted from an external device; And an interface connected between the MCU and the connector. When the MCU determines that a signal received through the connector is a debugging start value provided from the debugging tool, the MCU activates the interface, And provides the debugging value to the interface through the interface to debug the software.

Upon receiving the debugging end value while debugging the software, the MCU deactivates the interface and terminates the debugging operation for the software.

The MCU includes a first connection unit connected to the connector through a first wiring and connected to the interface through a second wiring branched from the first wiring to the interface; A second connection part connected to the interface through a fourth wiring branching from a third wiring extending from the interface; And a third connection part connected to the interface via a fifth wiring.

The MCU receives the debugging start value through the first connection unit and receives the debugging value through the second connection unit.

The electronic control apparatus further includes a debugging terminal connected to the third wiring and providing a debugging value provided from the debugging tool to the second connecting unit when the debugging tool is connected to the debugging tool.

The interface may include: a fourth connection part connected to the second wiring; A fifth connection part connected to the third wiring; And a sixth connection part connected to the fifth wiring, and is activated or deactivated according to a signal provided from the MCU through the sixth connection part.

An electronic control device debugging method according to one aspect of the present invention is a method for debugging an electronic control device using a debugging tool, the method comprising: determining whether a signal received from the outside is a debugging start value while the MCU is operating; ; When the received signal is the debugging start value, activating the interface by transmitting an enable signal to the interface by the MCU; And receiving the signal transmitted from the interface, and debugging the software of the MCU based on the received signal.

The step of determining whether the value is the debugging start value is a step of directly receiving the signal received through the connector by the MCU using the first connection unit and determining whether the received signal is the debugging start value.

The step of activating the interface is to cause the MCU to ignore the signal received via the first connection.

Activating the interface is a step in which a signal received via the connector is transmitted to the second connection of the MCU via the interface.

The method further includes determining whether the received signal is a debugging end value after the MCU debugging the software.

Wherein the MCU transmits a disable signal to the interface when the received signal is a debugging end value as a result of the step of determining whether the received signal is a debugging end value, Further comprising the step of deactivating.

The method further comprises the step of the MCU operating in response to a signal received via the first connection after deactivating the interface.

According to the embodiment of the present invention as described above, the electronic control device can be debugged even when the electronic control device is assembled in the waterproof case.

Therefore, by using the debugging system according to the embodiment of the present invention, the electronic control device can be debugged both before and after assembling the electronic control device into the waterproof case.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic view showing a configuration of an electronic control unit debugging system according to an embodiment of the present invention; FIG.
2 is a diagram specifically illustrating a configuration of an electronic control unit debugging system according to an embodiment of the present invention.
3 is a flowchart illustrating a procedure according to a debugging operation of an electronic control unit debugging system according to an embodiment of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like numbers refer to like elements throughout.

In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The following terms are defined in consideration of the functions in the embodiments of the present invention, which may vary depending on the intention of the user, the intention or the custom of the operator. Therefore, the definition should be based on the contents throughout this specification.

Hereinafter, a system and method for debugging an electronic control unit according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

Here, the electronic control unit may be an electronic control unit for vehicle control that includes software for controlling the vehicle, but the electronic control unit is not limited to the vehicle control.

However, for convenience of explanation, the following description will be made by taking the electronic control device 100 as an example of an electronic control device for vehicle control.

The electronic control unit may be assembled by a waterproof case for waterproofing, but may not be assembled by the waterproof case.

That is, the electronic control device debugging system according to the present invention can debug the electronic control device in a state where the electronic control device is not assembled by the waterproof case, but also assembled by the waterproof case.

FIG. 1 is a view schematically showing a configuration of an electronic control unit debugging system according to an embodiment of the present invention, and FIG. 2 is a diagram illustrating a configuration of an electronic control unit debugging system according to an embodiment of the present invention.

1 and 2, an electronic control unit debugging system 1 according to an embodiment of the present invention may include an electronic control unit 100 (ECU) and a debugging tool 200 have. At this time, the electronic control apparatus 100 is implemented so as to be debugged by the debugging tool 200.

Specifically, the electronic control unit 100 may include a micro control unit 110, a connector 120, an interface 130, and a debugging terminal unit 140.

The MCU 110 includes first to third connection units 111 to 113 and the interface 130 may include fourth to sixth connection units 131 to 133.

In addition, the electronic control apparatus 100 may include a plurality of wirings, and first to fifth wirings L1 to L5.

The above-mentioned components 110, 120, 130, 140, and L1 to L5 may be mounted on the circuit board 150, and the circuit board 150 may be a generalized The detailed description of the circuit board 150 will be omitted.

Before describing the configurations and functions of the electronic control apparatus 100 and the debugging tool 200, the connection structure in the electronic control apparatus 100 will be described first.

The first wire L1 connects the first connection part 111 of the MCU 110 and the connector 120 and the second wire L2 connects the first wire L1 to the fourth wire L1 of the interface 130. [ And the first wiring L1 is connected to the fourth connection part 131 of the interface 130. [

The connector 120 is connected to the first connection part 111 of the MCU 110 and the fourth connection part 131 of the interface 130 and the signal output from the connector 120 is connected to the first connection part 111 Or input to the interface 130 via the fourth connection unit 131. The interface 130 is connected to the MCU 110 via the first connection unit 131,

As will be described later, a value ('travel value') input during the operation of the vehicle is transmitted to the MCU 110 through the connector 120, the first wiring L1 and the first connection part 111, A value (a 'debugging value') input from the tool 200 is transmitted to the interface 130 through the connector 120, the first wiring line L1, the second wiring line L2 and the fourth connection unit 131.

The third wiring L3 connects the fifth connecting part 131 of the interface 130 and the debugging terminal part 140 and the fourth wiring L4 connects the third wiring L3 to the MCU 110, The second connection part 112 of the MCU 110 is connected to the third wiring L3.

The second connection unit 112 of the MCU 110 is connected to the fifth connection unit 132 and the debugging terminal unit 140 of the interface 130 and is connected to the fifth connection unit 132 of the interface 130 Signal or the signal input through the debugging terminal unit 140 is transmitted to the MCU 110 via the third wiring L3, the fourth wiring L4 and the second connecting unit 112. [

The MCU 110 receives the signal output from the fifth connection unit 132 of the interface 130 or input through the debugging terminal unit 140 through the second connection unit 112 and debugs the software .

The fifth wire L5 connects the third connection part 113 of the MCU 110 and the sixth connection part 133 of the interface 130. The MCU 110 is connected to the interface 130, And provides a disable signal S_en for disabling the interface 130 or a disable signal S_dis for disabling the interface 130 to the interface 130 through the fifth wiring L5.

The connection structure in the electronic control unit 100 has been described above. Hereinafter, the operation of the electronic control apparatus 100 and the debugging tool 200 will be described in detail with reference to FIGS. 1 and 2. FIG.

The debugging system 1 includes an electronic control unit 100 and a debugging tool 200. The electronic control unit 100 includes an MCU 110, a connector 120, an interface 130, And a debugging terminal unit 140.

The MCU 110 controls and operates the electronic control unit 100, and has a high-speed, high-performance processing capability and a sufficient capacity memory so as to reduce accident damage and prevent accidents.

On the other hand, the MCU 110 incorporates software according to the installation purpose. When the vehicle is mounted on the vehicle, the MCU 110 controls the vehicle based on a value ('travel value') inputted while the vehicle is traveling.

Further, the software in the MCU 110 may be debugged before or after the MCU 110 is mounted on a vehicle.

The MCU 110 may debug the software according to a value (a 'debugging value') input through the debugging terminal unit 140, and may perform debugging of the software through the connector 120 The debugging unit may debug the software according to the debugging value input through the debugging unit.

At this time, the debugging terminal unit 140 is provided for debugging, and the debugging terminal unit 140 is used only for debugging.

When the debugging operation is performed using the debugging terminal unit 140, the debugging operation using the connector 120 is not performed. That is, the debugging value is input only from one of the connector 120 and the debugging terminal unit 140.

The debugging operation using the debugging terminal unit 140 may be performed when the electronic control unit 100 is not assembled in the waterproof case.

On the other hand, when the electronic control unit 100 is assembled in the waterproof case, the debugging terminal unit 140 is blocked from the outside by the waterproof case, and the debugging operation using the debugging terminal unit 140 can be performed.

When the debugging terminal unit 140 can not perform the debugging operation for the MCU 110, the MCU 110 is connected to the debugging tool 200 and the value input from the debugging tool 200 for debugging ('Debugging value').

On the other hand, when receiving the debugging value through the connector 120, the MCU 110 needs to determine whether the currently input value is a driving value or a debugging value.

In the embodiment of the present invention, the debugging tool 200 provides a debugging start value and a debugging end value indicating the start and end of the debugging operation for the MCU 110.

When the MCU 110 receives the debugging start value, it determines that the value input thereafter is a debugging value, and performs debugging according to the input value. When receiving the debugging end value, the MCU 110 determines that the debugging operation is completed And terminates the debugging.

If there is an input value in a state where the debugging start value is not received or the vehicle is in operation, the MCU 110 determines that the value is a driving value, and controls the vehicle according to the input value.

Upon receiving the debugging start value, the MCU 110 transmits an enable signal S_en to the interface 130 to activate the interface 130. Upon receiving the debugging end value, the MCU 110 transmits the debugging start value to the interface 130 And transmits the disable signal S_dis to inactivate it.

When the MCU 110 receives the debugging start value, the MCU 110 ignores the value input through the first connection unit 111, and upon receiving the debugging end value, the MCU 110 transmits the debugging start value, Lt; RTI ID = 0.0 > 111 < / RTI >

Accordingly, the MCU 110 is configured to receive the driving value and the debugging start value through the first connection unit 111, and receive the debugging value and the debugging end value through the second connection unit 112. That is, the MCU 110 receives the driving value and the debugging value through different paths.

The interface 130 operates according to an enable signal S_en or a disable signal S_dis transmitted from the MCU 110.

At this time, when the interface 130 receives the enable signal S_en, the fourth connection unit 131 and the fifth connection unit 132 are internally connected and activated, and when receiving the disable signal S_dis , The connection between the fourth connection part 131 and the fifth connection part 131 is released internally and deactivated.

When the interface 130 receives the enable signal S_en, the interface 130 activates and transmits a signal input through the second wiring line L2 to the second connection unit 112 of the MCU 110. [ The signal output from the interface 130 is transmitted to the second connection unit 112 of the MCU 110 through the third and fourth wires L3 and L4.

When the interface 130 receives the disable signal S_dis and is inactivated and receives the signal input through the second wire L2, the received signal is transmitted to the second connection unit 112 of the MCU 110, .

The debugging terminal unit 140 is provided for debugging, and is a generalized technology well known in the art. Therefore, a detailed description of the debugging terminal unit 140 will be omitted.

The debugging tool 200 is a structure for providing a debugging value for debugging software in the MCU 110. At this time, the debugging tool 200 may be connected to the debugging terminal unit 140, and may be connected to the connector 120.

When the debugging tool 200 is connected to the debugging terminal unit 140, the debugging tool 200 provides a debugging value.

On the other hand, when the debugging tool 200 is connected to the connector 120, the debugging tool 200 provides a debugging start value indicating the start of debugging, provides a debugging value for debugging, , It provides a debugging end value.

Other operations of the debugging tool 200 are well known in the art, and a detailed description thereof will be omitted.

The configuration of the electronic control unit debugging system according to the embodiment of the present invention has been described above. Hereinafter, an electronic control device debugging operation using the electronic control unit debugging system according to an embodiment of the present invention will be described.

3 is a flowchart illustrating a procedure of a debugging operation of an electronic control unit debugging system according to an embodiment of the present invention.

3, the debugging operation is performed in a state where the debugging tool 200 is connected to the connector 120 as shown in FIGS. 1 and 2. FIG.

Referring to FIG. 3, the MCU 110 operates (S300) and determines whether a signal received from the outside is a debugging start value (S310).

In step S300, the MCU 110 transmits a disable signal to the interface 130 so that the interface 130 is deactivated and the MCU 110 is directly connected to the connector 120 through the first connection part 111 Signal is being received.

On the other hand, if it is determined in step S310 that the received signal is not a debugging start value (S310-No), the MCU 110 repeats steps S300 and S310. That is, the MCU 110 continuously determines whether the received signal is a debugging start value.

On the other hand, if it is determined in step S310 that the received signal is the debugging start value (S310 - YES), the MCU 110 transmits an enable signal to the interface 130 to transmit the interface 130 (S320).

When the interface 130 is activated in step S320, the signal input through the connector 120 is input to the second connection unit 112 of the MCU 110 via the interface 130. [ At this time, when the MCU 110 receives the debugging start value, the MCU 110 ignores the signal received through the first connection unit 111 after the debugging start value.

After the interface 130 is activated in step S320, the MCU 110 determines that the signal received through the second connection unit 112 is a debugging value, and debugs the software according to the received signal in step S330.

Thereafter, while debugging the software according to step S330, the MCU 110 determines whether the received signal is a debugging end value (S340).

If it is determined in step S340 that the received signal is not the debugging end value (S340-No), the MCU 110 debugs the software according to the received signal (S330).

On the other hand, if it is determined in step S340 that the received signal is a debugging end value (S340 - Yes), the MCU 110 transmits a disable signal to the interface 130 to deactivate the interface 130 (S350).

If the interface 130 is deactivated in step S350, the signal input through the connector 120 is blocked by the interface 130 and is no longer transmitted to the MCU 110, And operates in response to a signal received through the connection portion 111. [

As described above, according to the electronic control apparatus debugging system and method according to the embodiment of the present invention, a debugging tool can be connected to the connector to debug the electronic control apparatus.

That is, in the past, debugging of the electronic control unit was possible only by using a debugging terminal unit separately configured for debugging the electronic control unit. However, according to the present invention, debugging of the electronic control unit can be performed without using the debugging terminal unit can do.

Therefore, in the case where the electronic control unit is assembled in the waterproof case, the debugging operation can not be performed for the electronic control unit in the related art. However, when the electronic control unit is assembled in the waterproof case The debugging operation for the electronic control unit can be performed.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, Various modifications, alterations, and alterations can be made within the scope of the present invention.

Therefore, the embodiments described in the present invention and the accompanying drawings are intended to illustrate rather than limit the technical spirit of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments and accompanying drawings . The scope of protection of the present invention should be construed according to the claims, and all technical ideas within the scope of equivalents should be interpreted as being included in the scope of the present invention.

1: Electronic control unit debugging system 100: Electronic control unit (ECU)
110: Micro control unit (MCU) 111: First connection part
112: second connection part 113: third connection part
120: connector 130: interface
131: fourth connection part 132: fifth connection part
133: sixth connection part 140: debugging terminal part
150: circuit board 200: debugging tool
L1 to L5: first to fifth wiring

Claims (13)

1. An electronic control device debugging system for debugging an electronic control device using a debugging tool,
The electronic control device includes:
MCU (Micro Control Unit) with built-in software;
A connector for receiving a signal transmitted from an external device; And
And an interface coupled between the MCU and the connector,
The MCU activates the interface and receives a debugging value provided after the debugging start value through the interface when it is determined that the signal received through the connector is a debugging start value provided from the debugging tool, Debugging
In electronic control device debugging system.
The method according to claim 1,
The MCU, when receiving the debugging end value while debugging the software, deactivates the interface and terminates the debugging operation for the software
In electronic control device debugging system.
The method according to claim 1,
The MCU includes:
A first connection part connected to the connector through a first wiring and connected to the interface through a second wiring branched from the first wiring to the interface;
A second connection part connected to the interface through a fourth wiring branching from a third wiring extending from the interface; And
And a third connection part connected to the interface through a fifth wiring
In electronic control device debugging system.
The method of claim 3,
The MCU receives the debugging start value through the first connection unit and receives the debugging value through the second connection unit
In electronic control device debugging system.
The method of claim 3,
The electronic control apparatus may further include a debugging terminal unit connected to the third wiring and providing a debugging value provided from the debugging tool to the second connecting unit when connected to the debugging tool
In electronic control device debugging system.
The method of claim 3,
The interface comprises:
A fourth connection part connected to the second wiring;
A fifth connection part connected to the third wiring; And
And a sixth connection part connected to the fifth wiring,
Activated or deactivated according to a signal provided from the MCU through the sixth connection unit
In electronic control device debugging system.
A method for debugging an electronic control device using a debugging tool, the method comprising:
Determining whether a signal received from the outside is a debugging start value while the MCU is operating;
When the received signal is the debugging start value, activating the interface by transmitting an enable signal to the interface by the MCU; And
Receiving a signal transmitted from the interface, and debugging the software of the MCU based on the received signal
Method for debugging an electronic control device.
8. The method of claim 7,
Wherein the step of determining whether the value is the debugging start value includes the step of directly receiving the signal received through the connector by the MCU using the first connection unit and determining whether the received signal is the debugging start value
In electronic control device.
9. The method of claim 8,
Wherein activating the interface comprises ignoring signals received by the MCU over the first connection
In electronic control device.
9. The method of claim 8,
Wherein activating the interface causes a signal received via the connector to be transmitted to the second connection of the MCU via the interface
In electronic control device.
8. The method of claim 7,
Further comprising: after the MCU debugging the software, determining whether the received signal is a debugging end value
Method for debugging an electronic control device.
12. The method of claim 11,
Further comprising the step of causing the MCU to send a disable signal to the interface to deactivate the interface if the received signal is a debugging end value as a result of the determination in the step of determining whether the received signal is a debugging end value
Method for debugging an electronic control device.
13. The method of claim 12,
After the step of deactivating the interface, the MCU operating in response to a signal received via the first connection
Method for debugging an electronic control device.
KR1020150175840A 2015-12-10 2015-12-10 System and method for debugging electronic control unit KR101726295B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020150175840A KR101726295B1 (en) 2015-12-10 2015-12-10 System and method for debugging electronic control unit

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020150175840A KR101726295B1 (en) 2015-12-10 2015-12-10 System and method for debugging electronic control unit

Publications (1)

Publication Number Publication Date
KR101726295B1 true KR101726295B1 (en) 2017-04-13

Family

ID=58579852

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020150175840A KR101726295B1 (en) 2015-12-10 2015-12-10 System and method for debugging electronic control unit

Country Status (1)

Country Link
KR (1) KR101726295B1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190040714A (en) * 2017-10-11 2019-04-19 현대자동차주식회사 Method and system for ECU execution time monitoring and fault finding
CN109684216A (en) * 2018-12-25 2019-04-26 郑州云海信息技术有限公司 A kind of commissioning device and electronic equipment
CN111775864A (en) * 2020-06-28 2020-10-16 广州橙行智动汽车科技有限公司 Remote debugging method and system and vehicle

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10214209A (en) * 1997-01-29 1998-08-11 Nippon Motorola Ltd Data processor having debugging function
JP2013086742A (en) * 2011-10-21 2013-05-13 Renesas Electronics Corp Debug system, electronic control unit, information processor, semiconductor package, and transceiver circuit

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10214209A (en) * 1997-01-29 1998-08-11 Nippon Motorola Ltd Data processor having debugging function
JP2013086742A (en) * 2011-10-21 2013-05-13 Renesas Electronics Corp Debug system, electronic control unit, information processor, semiconductor package, and transceiver circuit

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190040714A (en) * 2017-10-11 2019-04-19 현대자동차주식회사 Method and system for ECU execution time monitoring and fault finding
KR102410940B1 (en) 2017-10-11 2022-06-20 현대자동차주식회사 Method and system for ECU execution time monitoring and fault finding
CN109684216A (en) * 2018-12-25 2019-04-26 郑州云海信息技术有限公司 A kind of commissioning device and electronic equipment
CN111775864A (en) * 2020-06-28 2020-10-16 广州橙行智动汽车科技有限公司 Remote debugging method and system and vehicle

Similar Documents

Publication Publication Date Title
KR101726295B1 (en) System and method for debugging electronic control unit
US9031740B2 (en) Vehicle control device capable of controller area network communication and diagnostic method therefor
US20160134553A1 (en) Flexible scheduling method and apparatus in lin communication
US10839619B2 (en) Electronic control unit and method for connection authentication
US10458539B2 (en) Vehicle control device
KR101544887B1 (en) Apparatus And Method for diagnosing CAN communication error
EP3822098A1 (en) Method for configuring a trailer detection system
US20160062434A1 (en) Debug system, electronic control unit, information processing unit, semiconductor package, and transceiver circuit
US7957891B2 (en) Electronic control device for remote control and teleoperation system using same
CN210294832U (en) Dual-redundancy CAN bus communication device suitable for autonomous underwater vehicle
KR102154279B1 (en) Operating method in debugging system for vehicle
US9341666B2 (en) Method and device for establishing a fault in connecting lines between a central unit and a plurality of electronic components which are independent of one another
KR102658507B1 (en) How to configure a trailer detection system
CN103425123A (en) Automated testing method for CAN (controller area network) bus based on software script
US20020073253A1 (en) Test module
US20150146745A1 (en) Control unit for in-vehicle ethernet and method for controlling thereof
JPH0330882B2 (en)
JP4290195B2 (en) Data transmission line with data integrity checking device
CN113448276B (en) Parallel driving control circuit and system with signal acquisition instrument function
CN220064684U (en) Automobile electronic detection system based on CAN bus
WO2023106091A1 (en) On-board device, connection switching method, and connection switching program
JP7352166B2 (en) In-vehicle communication system, in-vehicle communication device and communication method for vehicle
JP3031050B2 (en) Fault diagnosis device
KR20160070304A (en) Smart junction box having diagnosis function using wireless communication and diagnosis method thereof
CN105159190A (en) On-board diagnostics signal adaptation box and signal adaptation method thereof

Legal Events

Date Code Title Description
E701 Decision to grant or registration of patent right
GRNT Written decision to grant