Electronic control device and start-up control method
By communicating with other control units to set a failure wake-up identifier, the electronic control device ensures normal startup of the microcomputer despite register failures in the wake-up circuit.
Patent Information
- Application Number
- JP2023080714
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-16
- Publication Date
- 2024-11-28
- Estimated Expiration
- 2043-05-16
AI Technical Summary
In an electronic control device, a failure in the register of the wake-up circuit can prevent proper authentication of the wake-up identifier, leading to impossible activation control of the microcomputer.
The electronic control device communicates with other control units to determine register failures and sets a failure wake-up identifier, allowing the wake-up circuit to activate the microcomputer even if the register fails.
This approach enables normal startup control of the main microcomputer even when the register of the wake-up circuit fails, ensuring reliable operation.
Smart Images

Figure 2024164961000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an electronic control device and a startup control method. [Background technology]
[0002] As an example of a technology for properly performing startup processing in an electronic control unit installed in a vehicle, a technology has been proposed in which the operational requirements of each application are determined based on the power supply state and startup requirements, and only applications that satisfy the operational requirements are started. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2006-327217 A Summary of the Invention [Problem to be solved by the invention]
[0004] Here, in the electronic control device, a wake-up circuit that performs startup control of a main microcomputer may have a configuration that performs startup control of a microcomputer (microcomputer) that performs control processing of an in-vehicle device when a specific wake-up identifier is received from an external unit, etc. In such a configuration, if a failure occurs in the register of the wake-up circuit, authentication of the wake-up identifier may not be performed normally, and a situation may arise in which startup control becomes impossible.
[0005] Therefore, an object of one aspect of the present invention is to enable an electronic control device to normally control the startup of a microcomputer even when a failure occurs in a register of a wake-up circuit. [Means for solving the problem]
[0006] In one aspect of the present invention, an electronic control device includes a computer and a wake-up circuit that starts the computer when a wake-up identifier that matches a value set in a register is received. The electronic control device is also communicatively connected to one or more other electronic control devices. The electronic control device performs the following process. That is, the computer determines whether or not a fault has occurred in the register of the wake-up circuit. If a fault has occurred in the register, the computer transmits a fault code according to the fault content to the other electronic control device, and sets a fault wake-up identifier corresponding to the fault code in the register. Furthermore, the wake-up circuit starts the computer when it receives a fault wake-up identifier corresponding to the fault code from the other electronic control device. Effect of the Invention
[0007] According to one aspect of the present invention, even if a failure occurs in a register of a wake-up circuit in an electronic control device, startup control of a main microcomputer can be performed normally. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is an explanatory diagram illustrating an example of a control system according to an embodiment of the present invention. [Diagram 2] 2 is a diagram showing the configuration of a register of a wake-up IC in one embodiment of the present invention. FIG. [Diagram 3] 4 is a sequence diagram showing states and processes of a main microcomputer, a wake-up IC, and an external unit in one embodiment of the present invention. FIG. [Figure 4] 4 is a flowchart showing a process of the main microcomputer executed when the main microcomputer is first started up in one embodiment of the present invention. [Diagram 5] 4 is a flowchart showing a process of the main microcomputer executed when the main microcomputer is first started up in one embodiment of the present invention. [Figure 6]5 is a flowchart showing a process of an external unit executed when a main microcomputer is restarted in one embodiment of the present invention. [Figure 7] 5 is a flowchart showing the process of the wake-up IC executed when the main microcomputer is restarted in one embodiment of the present invention. [Figure 8] 4 is a diagram showing an example of data (normal) in a register of a wakeup IC in one embodiment of the present invention. FIG. [Figure 9] 11 is a diagram showing an example of data in a register of a wakeup IC (when an error occurs) in one embodiment of the present invention. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the present invention is not limited to the embodiment described in this specification, and different embodiments and their modifications can be appropriately combined.
[0010] [Control system configuration] 1 shows an example of a control system 1 according to this embodiment. The control system 1 is mounted on a vehicle such as an automobile, and controls various devices related to the running of the vehicle. Depending on the type of in-vehicle device to be controlled, the control system 1 can be classified into a powertrain control system such as engine control, a vehicle control system such as electric power steering and brake control, a body control system such as airbags and surroundings monitoring, and an information system such as a navigation system and a GPS (Global Positioning System). The control system 1 includes an ECU 10 (Electronic Control Unit) which is an electronic control device that controls the in-vehicle devices, and external units 50A to 50C.
[0011] The ECU 10 includes a wake-up circuit (IC) 20 and a main microcomputer 30. The wake-up IC 20 and the main microcomputer 30 are connected by a Serial Peripheral Interface (SPI) bus and a Controller Area Network (CAN) bus. An inhibit (INH) signal is transmitted from the wake-up IC 20 to the main microcomputer 30 from an inhibit terminal, thereby controlling the startup of the main microcomputer 30. The ECU 10 is also connected to a battery 40, and power is supplied from the battery 40 to the wake-up IC 20 and the main microcomputer 30.
[0012] The wake-up IC 20 is an electronic circuit having a function of activating the main microcomputer 30 when a predetermined condition is satisfied. The predetermined condition will be described in detail later. The wake-up IC 20 includes a control unit 21, a register 22, and communication interfaces 23A to 23C.
[0013] The control unit 21 transmits an INH signal to the main microcomputer 30 to start up the main microcomputer 30 according to the operation mode in which the wakeup IC 20 operates. The register 22 stores various setting values used in the operation of the control unit 21. Details of the data stored in the register 22 will be described later. The communication interfaces 23A to 23C have a function of realizing communication between the wake-up IC 20 and the outside. For example, the communication interfaces 23A and 23B are composed of a CAN (Controller Area Network) transceiver or the like, and the communication interface 23A performs CAN communication with the external units 50A to 50C, and the communication interface 23B performs CAN communication with the main microcomputer 30. The communication interface 23C performs SPI communication with the main microcomputer 30. The communication interface 23D outputs an INH signal to the main microcomputer 30 via an INH terminal. Note that the wake-up IC 20 has a terminal that operates a wake-up function when a wake-up signal (activation command) is input from the outside, but in this embodiment, the terminal is omitted from the illustration as it is open.
[0014] The main microcomputer 30 includes a processor 31, a RAM 32, a ROM 33, and communication interfaces 34A to 34C, which are interconnected by an internal bus. The processor 31 is hardware that executes an instruction set (such as data transfer, calculation, processing, control, and management) described in a program, and is composed of an arithmetic unit, registers that store instructions and information, peripheral circuits, etc. The functions of the processor 31 are realized by executing a program. The processes executed by the processor 31 will be described in detail later.
[0015] The RAM 32 is made of a volatile memory in which data is lost when the power supply is cut off, and provides a temporary storage area for use by the processor during operation. The ROM 33 includes a non-volatile memory (such as an EEPROM) that allows data to be electrically rewritten, and a non-volatile memory (such as a code flash) that stores data that does not need to be rewritten in principle. The ROM 33 stores various data used when the processor 31 executes the program, and data of the program itself. The communication interfaces 34A to 34C have a function of realizing communication between the main microcomputer 30 and the outside. For example, the communication interface 34A performs CAN communication with the wakeup IC 20, and the communication interface 34B performs SPI communication with the wakeup IC 20. The communication interface 34C receives an INH signal transmitted from the wakeup IC 20 and starts up the main microcomputer 30 via the main relay.
[0016] The external units 50A to 50C are, for example, other electronic control devices that control in-vehicle devices in the same way as the ECU 10. Note that the number of external units may be one or more, and is not limited to the example of this embodiment. In this embodiment, the communication method between the ECU 10 and the external units 50A to 50C is CAN, but any communication method such as LIN (Local Interconnect Network), Ethernet (registered trademark), FlexRay, etc. can be used. Similarly, the communication method between the wake-up IC 20 and the main microcomputer 30 is not necessarily limited to the above example. Furthermore, although not shown in the figure, the ECU 10 is also connected to be able to communicate with the in-vehicle device to be controlled.
[0017] 2 shows an example of the configuration of the storage area of the register 22 of the wakeup IC 20. The register 22 includes two types of storage areas: a control register and a status register. The control register includes an operation mode setting area in which information identifying an operation mode is set, and a wakeup CANID setting area in which a wakeup CANID (described in detail later) which is one form of a wakeup identifier is set. The status register includes an error setting area in which information indicating that an illegal write has been performed in the wakeup IC 20 is set.
[0018] [Main microcontroller startup process and technical issues] Here, the process performed when the wakeup IC 20 starts up the main microcomputer 30 will be described. The wakeup IC 20 goes into standby mode when power is supplied from the battery 40, and when it receives a start-up command from the main microcomputer 30, it starts up the main microcomputer 30 and transitions to normal mode. When the main microcomputer 30 shuts down, the wakeup IC 20 transitions from normal mode to sleep mode. When it subsequently receives a start-up command from the main microcomputer 30, it starts up the main microcomputer 30 again and transitions to normal mode. This transition between normal mode and sleep mode is performed based on a control signal received from the main microcomputer 30 by SPI communication. Specifically, the main microcomputer 30 transmits a signal for setting information for identifying the operation mode of the wakeup IC 20 in an operation mode setting area of the register 22. The wakeup IC 20 operates in an operation mode based on the information set in the operation mode setting area of the register 22.
[0019] Here, there are two types of sleep modes of the wakeup IC 20. One mode is a selective sleep mode in which the main microcomputer 30 is started up when a specific CANID is received (WUF: Wake Up Frame). In this selective sleep mode, the wakeup IC 20 performs authentication processing for the wakeup CANID received from the external units 50A to 50C. Specifically, the wakeup IC 20 transmits a start-up command to the main microcomputer 30 when the received wakeup CANID matches with the one set in the wakeup CANID setting area of the register 22. The wakeup CANID in this wakeup CANID setting area is set by the main microcomputer 30 at the time of initial startup. Note that the matching here may include a state in which the two match, or a state in which the two correspond to each other based on a predetermined rule even if they do not match. In other words, the wakeup IC 20 does not start up the main microcomputer 30 when it receives a CANID that does not match the CANID set in the wakeup CANID setting area of the register 22. The other mode is a sleep wake-up mode (WUP) in which the main microcomputer 30 is started not only when a specific CANID is received, but also when the CAN bus is operating, i.e., when there is a voltage change in the CAN bus (WUP: Wake Up Pattern).As described above, in this embodiment, the input terminal is open and disabled for the pattern (LWU: Local Wake Up) in which the wake-up function operates when a wake-up signal is input from the outside.
[0020] Here, a technical problem when the wakeup IC 20 restarts the main microcomputer 30 will be described. Normally, when the main microcomputer 30 is in a shut-down state, the wakeup IC 20 operates in the selective sleep mode among the above-mentioned operation modes. However, if some kind of failure such as sticking occurs in the register 22, the main microcomputer 30 may not be able to set the wakeup CANID correctly in the wakeup CANID setting area of the register 22. In this case, the wakeup CANID received from outside does not match the one set in the wakeup CANID setting area of the register 22, and authentication cannot be performed correctly. As a result, a situation may occur in which the wakeup IC 20 cannot start the main microcomputer 30 even though it receives a start-up request from the main microcomputer 30. According to this embodiment, it is possible to prevent the occurrence of such a situation in which the main microcomputer 30 cannot be started.
[0021] [Processing from the initial start-up of the main microcontroller to shutdown and restart] Here, an example of the processing executed from the initial startup to shutdown and restart of the main microcomputer 30 will be described. In this description, a sequence diagram of Fig. 3 showing the operations of the wake-up IC 20, the main microcomputer 30, and the external units 50A to 50C and flowcharts shown in Figs. 4 to 7 will be referenced. 4 and 5 show the processing of the main microcomputer 30 at the initial startup when the wake-up IC 20 and the main microcomputer 30 are connected to the battery 40 to supply power and receive a startup command from an external unit 50A to 50C.
[0022] In step 101 (denoted as S101 in the figure, and so on below), the main microcomputer 30 transitions to a startup mode (Smode). In step 102, the main microcomputer 30 performs an initial process at the time of startup. The initial process here is, for example, initialization of the RAM 32.
[0023] In step 103 , the main microcomputer 30 performs SPI communication and writes a predetermined setting value to the register 22 of the wake-up IC 20 . In step 104 , the main microcomputer 30 performs SPI communication and reads the setting value of the register 22 of the wake-up IC 20 that was written in step 103 .
[0024] In step 105, the main microcomputer 30 determines whether or not a fault was detected in the register 22 of the wake-up IC 20 in the previous process. For example, the main microcomputer 30 can determine whether or not a fault was detected in the wake-up IC 20 in the previous process based on the value of a fault flag stored in a non-volatile memory in the ROM 33 that is electrically rewritable. This fault flag is a value that is set in step 112, which will be described later. If no fault is detected, the process proceeds to step 106 (No), and if a fault is detected, the process proceeds to step 107 (Yes).
[0025] In step 106, the main microcomputer 30 performs an echo-back diagnosis on a portion of the storage area of the register 22 to determine whether or not a fault has occurred in the register 22 of the wake-up IC 20. Specifically, the main microcomputer 30 determines whether or not a fault has occurred by checking whether or not the setting value written in step 103 to the wake-up CANID setting area of the register 22 of the wake-up IC 20 can be read normally in step 104.
[0026] In step 107, the main microcomputer 30 performs an echo back diagnosis on the entire memory area of the register 22 to determine whether or not a fault has occurred in the register 22 of the wake-up IC 20. Specifically, the main microcomputer 30 determines whether or not a fault has occurred by checking whether or not the setting values written in step 103 to the entire memory area (the entire control register and status register) of the register 22 of the wake-up IC 20 can be read normally in step 104.
[0027] In step 108, the main microcomputer 30 determines whether the result of the echo back diagnosis is normal, i.e., whether the setting value written to the register 22 of the wake-up IC 20 in step 103 can be read normally in step 104. If the setting value can be read normally, the process proceeds to step 109 (Yes); if the setting value cannot be read normally, i.e., if a fault has occurred in the register 22, the process proceeds to step 110 (No). Note that if the result of the echo back diagnosis is not normal, the main microcomputer 30 can repeat steps 103 to 108 within the allowable time range and retry writing to and reading from the register 22.
[0028] In step 109, the main microcomputer 30 sets the wakeup CANID for normal operation in the register 22 of the wakeup IC 20. Note that in step 103 described above, the main microcomputer 30 may write the wakeup CANID for normal operation as a predetermined setting value in the wakeup CANID setting area. In this case, this process may be omitted.
[0029] In step 110, the main microcomputer 30 notifies the external units 50A to 50C, which can send a start-up command to the wake-up IC 20, of a fault code corresponding to the type of fault. In step 111, the main microcomputer 30 sets, in the register 22 of the wake-up IC 20, a wake-up CANID upon failure corresponding to the fault code notified to the external units 50A-50C in step 109. Note that the wake-up CANID upon failure corresponding to the fault code here is an identifier that can be specified by applying a predetermined rule based on the information included in the fault code. Specific examples of these fault codes and wake-up CANID upon failure will be described later. In addition, the memory area of the register 22 in which the wake-up CANID upon failure is set is a memory area that has been confirmed to function normally in the echo back diagnosis. For example, the memory area may be a spare area corresponding to a memory area in which a fault has occurred. In step 112, the main microcomputer 30 writes a value indicating that a failure has been detected in the register 22 to a failure flag in the ROM 33, which is a non-volatile memory that allows electrically rewriting of data.
[0030] In step 113, the main microcomputer 30 determines whether or not a shutdown command has been received. Specifically, when the wakeup IC 20 receives a shutdown command from the external units 50A to 50C via CAN communication, the wakeup IC 20 notifies the main microcomputer 30 that a shutdown command has been received. If a shutdown command has been received, the process proceeds to step 114 (Yes), and if not, the process continues normal operation (No). In step 114, the main microcomputer 30 transmits a control signal to the wakeup IC 20 to cause the wakeup IC 20 to transition to the selective sleep mode. As a result, the wakeup IC 20 transitions to the selective sleep mode and stops transmitting the INH signal to the main microcomputer 30. In step 115, the main microcomputer 30 performs a shutdown process.
[0031] 6 shows the processes executed by the external units 50A to 50C when the main microcomputer 30 is restarted from a shut down state by a start-up command from the external units 50A to 50C. The external units 50A to 50C execute the processes when the conditions for starting up the main microcomputer 30 are satisfied according to their respective functions.
[0032] In step 121, the external units 50A to 50C determine whether or not a fault code has been notified by the main microcomputer 30. The fault code is the one notified by the main microcomputer 30 in the above-mentioned step 110. If a fault code has been notified, the process proceeds to step 123 (Yes), and if not, the process proceeds to step 122 (No). In step 122, the external units 50A to 50C transmit a normal wake-up CANID to the wake-up IC 20. In step 123, the external units 50A to 50C identify the wakeup CAN ID during failure that corresponds to the failure code notified by the main microcomputer 30. Then, the external units 50A to 50C transmit the wakeup CAN ID during failure to the wakeup IC 20.
[0033] FIG. 7 shows the process executed in the wake-up IC 20. In step 131, the wakeup IC 20 receives a wakeup CANID from the external unit 50A to 50C. As described above, the wakeup CANID received from the external unit 50A to 50C is a normal wakeup CANID when no failure occurs in the register 22, and is a failure-time wakeup CANID when a failure occurs.
[0034] In step 132, the wakeup IC 20 performs authentication processing on the received wakeup CANID. Specifically, the wakeup IC 20 compares the received wakeup CANID with the wakeup CANID set in the register 22, and determines whether or not the two match. At this time, if the received wakeup CANID is not a normal wakeup CANID but a fault wakeup CANID, the wakeup IC 20 compares the received wakeup CANID with the value of the memory area in which the fault wakeup CANID was set in step 111. If the two match, the process proceeds to step 133 (Yes), and if not, the process ends (No). If the two do not match, an error signal may be output to the external units 50A to 50C that are the senders of the wakeup CANID. In step 132, the wakeup IC 20 performs a process of starting up the main microcomputer 30. That is, the wakeup IC 20 transmits an INH signal to the main microcomputer 30. As a result, the main microcomputer 30 starts up.
[0035] [Specific examples of data used in the processing of this embodiment] Here, the above processing will be described with reference to specific examples shown in FIG. 8 and FIG. 9 with regard to the transmission / reception value, the fault code, and the wake-up CAN ID in the echo back diagnosis of the data in the wake-up CAN ID setting area of the register 22. 8 shows a specific example of data under normal circumstances. For example, referring to an example of the "SWK_CTRL_6" register, the data sent from the main microcomputer 30 in the echo back diagnosis is "0000", and the received data is also "0000", which matches. In this case, the main microcomputer 30 sets "FFFFFFF", which is the wakeup CANID under normal circumstances, in the wakeup CANID setting area of the register 22. Then, when the external units 50A-50C start up the main microcomputer 30, the external units 50A-50C transmit the wakeup CANID of "FFFFFFF" to the wakeup IC 20.
[0036] On the other hand, FIG. 9 shows a specific example of data when an abnormality such as data fixation occurs in the register 22. For example, referring to the example of the register "SWK_CTRL_6", the transmission data from the main microcomputer 30 in the echo back diagnosis is "0000", while the received data is "FFFF", and the two are not consistent. In this case, the main microcomputer 30 sets "106FFFF", which is a value obtained by combining "106" indicating the address number of the register and "FFFF", which is the value of the received data, as a fault code. Then, the main microcomputer 30 transmits the fault code to the external units 50A to 50C. In addition, the main microcomputer 30 sets "0000106F", which is a value obtained by combining "0000", which is the value of the transmission data in the echo back diagnosis, "106", which is the address number of the register, and "F", which is the value of the wakeup key, in the wakeup CANID setting area of the register 22, as a fault wakeup CANID. When starting up the main microcomputer 30, the external units 50A to 50C receive a fault code from the main microcomputer 30 and therefore identify the fault wake-up CANID. Specifically, the external units 50A to 50C use information contained in the received fault code "106FFFF". Then, by applying the same rules as when the main microcomputer 30 set the fault wake-up CANID in the register 22, the external units 50A to 50C identify "0000106F" as the fault wake-up CANID. In this example, it is assumed that the external units 50A to 50C have already identified that the value of the transmission data in the echo back diagnosis is "0000". Then, the external units 50A to 50C transmit the wake-up CANID of "0000106F" to the wake-up IC 20. The main microcomputer 30 compares the received value "0000106F" with the "0000106F" set in the wake-up CAN ID setting area of the register 22, and since the two are consistent (match), it performs startup processing of the main microcomputer 30.
[0037] [Effects of this embodiment] According to this embodiment, as described above, when a failure occurs in the register 22, the main microcomputer 30 transmits a failure code corresponding to the failure content of the register 22 to the external units 50A to 50C. The main microcomputer 30 also sets a failure wakeup CANID corresponding to the failure code in the register 22. Then, when the external units 50A to 50C transmit a start-up command for the main microcomputer 30 to the wakeup IC 20, if a failure code is received, the external units 50A to 50C transmit a failure wakeup CANID corresponding to the failure code. As a result, in the authentication process of the wakeup CANID in the wakeup IC 20 operating in the selective sleep mode, the wakeup CANID in the register 22 and the wakeup CANID received from the external units 50A to 50C are consistent. Therefore, even if a failure occurs in the register 22 while the wakeup IC 20 is operating in the selective sleep mode, the main microcomputer 30 can be started up.
[0038] Furthermore, in this embodiment, the fault code transmitted to the external units 50A-50C and the fault wakeup CANID set in the register 22 contain address information of the storage area in which the fault has occurred. This makes it possible to identify which storage area in the register 22 the fault wakeup CANID corresponds to in the wakeup CANID authentication process in the wakeup IC 20. Therefore, for example, when the fault wakeup CANID is set in a spare area or the like corresponding to the storage area in which the fault has occurred, it becomes possible to identify which spare area the wakeup CANID should be compared with.
[0039] Furthermore, in this embodiment, the fault code and the wake-up CANID upon failure include the values of the transmitted and received data in the echo-back diagnosis. This makes it possible to identify how the fixation of the register 22 has occurred from the fault code and the wake-up CANID upon failure. In the above-mentioned specific example, the received data of the echo-back diagnosis is included in the fault code, and the transmitted data of the echo-back diagnosis is included in the wake-up CANID upon failure, but this is merely an example. For example, it is possible for at least one of the fault code and the wake-up CANID upon failure to include both the transmitted data and the received data of the echo-back diagnosis, or conversely, such data may not be included. Also, as an example, the fault code and the wake-up CANID upon failure may have the same value.
[0040] Furthermore, in this embodiment, if a fault occurs in the register 22, a fault flag is set to a value indicating that a fault has been detected in the register. Then, at the next startup, the fault flag is referenced, and if a fault is detected in the register 22, it is determined whether or not a fault has occurred for the entire storage area of the register 22. Here, in this embodiment, as described above, even if a fault occurs in the register 22, the main microcomputer 30 can be started normally. Therefore, even if the echo back diagnosis is performed on the entire storage area of the register 22 to improve diagnostic accuracy when a fault is detected in the register 22, the startup process can be performed without any problems.
[0041] [others] The above-described embodiments of the present invention are merely some of the possible implementations within the technical scope of the present invention, and are disclosed as examples of the present invention, and do not limit the technical scope of the present invention. Furthermore, the functional and physical configurations in each embodiment are not limited to the above-described aspects, and for example, each function or physical resource can be integrated and implemented, or conversely, can be further distributed and implemented, and further, some of the configurations can be added, deleted, or replaced with other configurations. [Explanation of symbols]
[0042] 1... control system, 10... ECU, 20... wake-up IC, 21... control unit, 22... register, 30... main microcomputer, 31... processor, 32... RAM, 33... ROM, 40... battery, 50A to 50C... external unit
Claims
1. 1. An electronic control device comprising: a computer; and a wake-up circuit for waking up the computer upon receiving a wake-up identifier matching a value set in a register; the electronic control device being communicatively connected to one or more other electronic control devices, the computer determines whether or not a fault has occurred in the register of the wake-up circuit, and if a fault has occurred in the register, transmits a fault code corresponding to the fault to the other electronic control device, and sets a fault wake-up identifier corresponding to the fault code in the register; wake-up circuitry wakes up the computer when the wake-up circuitry receives the wake-up-on-failure identifier corresponding to the fault code from the other electronic control device; Electronic control unit.
2. The electronic control device according to claim 1 , wherein the fault code and the wake-up-on-failure identifier include address information of a fault location in the register.
3. 3. The electronic control device according to claim 1, wherein the fault code and the wake-up-on-failure identifier include at least a portion of the value of data transmitted between the computer and the wake-up circuit to determine whether or not a fault has occurred in the register of the wake-up circuit.
4. 3. The electronic control device according to claim 1 or 2, wherein, when a fault occurs in the register, the computer sets a fault flag in the memory to a value indicating that a fault has been detected in the register, and at the next startup, refers to the fault flag and, when a fault is detected in the register, determines whether or not a fault has occurred for the entire memory area of the register, while, when no fault is detected in the register, determines whether or not a fault has occurred for a part of the memory area of the register.
5. 1. An electronic control device comprising: a computer; and a wake-up circuit for waking up the computer upon receiving a wake-up identifier matching a value set in a register; the electronic control device being communicatively connected to one or more other electronic control devices, the computer determines whether or not a fault has occurred in the register of the wake-up circuit, and if a fault has occurred in the register, transmits a fault code corresponding to the fault to the other electronic control device, and sets a fault wake-up identifier corresponding to the fault code in the register; The wake-up circuit wakes up the computer when the wake-up circuit receives the wake-up-on-fault identifier corresponding to the fault code from the other electronic control device. A startup control method for executing a process.
Citation Information
Patent Citations
Controller equipped with soft error detection circuit
JP2010231417A
Communication system
JP2013255034A
Failure detection method
JP2022184459A
On-vehicle device, on-vehicle system, control method and computer program
JP2023152363A
Electronic control device and method for daiagnosing wake-up circuit
WO2022075006A1
