JP2018151717A - Automobile electronic control device - Google Patents

Automobile electronic control device Download PDF

Info

Publication number
JP2018151717A
JP2018151717A JP2017045603A JP2017045603A JP2018151717A JP 2018151717 A JP2018151717 A JP 2018151717A JP 2017045603 A JP2017045603 A JP 2017045603A JP 2017045603 A JP2017045603 A JP 2017045603A JP 2018151717 A JP2018151717 A JP 2018151717A
Authority
JP
Japan
Prior art keywords
core
initialization
cores
data
electronic control
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
JP2017045603A
Other languages
Japanese (ja)
Other versions
JP6660902B2 (en
Inventor
匡彰 日野
Masaaki Hino
匡彰 日野
尊文 鈴木
Takafumi Suzuki
尊文 鈴木
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Astemo Ltd
Original Assignee
Hitachi Automotive Systems Ltd
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 Hitachi Automotive Systems Ltd filed Critical Hitachi Automotive Systems Ltd
Priority to JP2017045603A priority Critical patent/JP6660902B2/en
Publication of JP2018151717A publication Critical patent/JP2018151717A/en
Application granted granted Critical
Publication of JP6660902B2 publication Critical patent/JP6660902B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Hardware Redundancy (AREA)
  • Test And Diagnosis Of Digital Computers (AREA)
  • Microcomputers (AREA)
  • Stored Programmes (AREA)

Abstract

PROBLEM TO BE SOLVED: To provide an automobile electronic control device capable of performing initialization in an equivalent time period with a normal condition regardless of the number of faulty cores.SOLUTION: A core 1110 transmits question data to a core 1120. On the basis of the received question data, answer data is calculated with a predetermined calculation formula, and it is returned to the core 1110. The core 1110 receives the answer data from the core 1120. The core 1110 uses correct answer data preliminarily embedded in a program, and is compared with the data returned from the core 1120. When the data calculated by the core 1120 and the correct answer data match, it is determined to be normal and the core 1120 performs normal control. If the answer data calculated by the core 1120 and the correct answer data do not match, the core 1120 is stopped. In the logic, the diagnosis of the core 1120 is conducted by replacing the core 1110 with the core 1120.SELECTED DRAWING: Figure 5

Description

本発明は、自動車用電子制御装置の初期化技術に関する。 The present invention relates to an initialization technology for an electronic control device for an automobile.

近年、自動車用電子制御装置では複数の演算ユニット(以下、コア)を有する1つのCPU(以下、マルチコアCPUという)を備えた自動車用電子制御装置が普及しつつある。マルチコアCPUの目的の一つに、あるコアの故障に対する堅牢制があげられる。すなわち、あるコアが故障し、これを他コアが検知した場合に、正常なコアにより故障したコアの処理を代替して行う。多くの場合、処理量を減らして縮退運転を行う。装置が完全に停止するよりも、機能を限定して縮退運転を行う方が、安全である。縮退運転時においても、正常時の通常制御と同等の安全性を確保する。そのためには、処理時間の長期化を避け、簡素な処理を行う。   2. Description of the Related Art In recent years, automotive electronic control devices including a single CPU (hereinafter referred to as a multi-core CPU) having a plurality of arithmetic units (hereinafter referred to as cores) have become widespread. One of the purposes of a multi-core CPU is a robust system against a certain core failure. That is, when a certain core fails and this is detected by another core, the processing of the failed core is replaced with a normal core. In many cases, the reduced amount of processing is performed to perform degenerate operation. Rather than stopping the device completely, it is safer to perform degenerate operation with limited functions. Even during degenerate operation, safety equivalent to normal control during normal operation is ensured. For this purpose, simple processing is performed while avoiding a prolonged processing time.

特開2013−200602特許文献1では、マルチコアCPUにおいて、独立にあるコアAとあるコアBが初期化処理を行うことで起動時間の短縮を可能にする。In Japanese Patent Application Laid-Open No. 2013-200462, in a multi-core CPU, an independent core A and a certain core B perform initialization processing, thereby enabling a reduction in startup time.

初期化時点でマルチコアCPUのコアAが故障している場合においても、コアBによる縮退運転を行うため、電子制御装置の初期化を行い起動する。このとき、コアAで初期化している機能は初期化されないという課題がある。   Even when the core A of the multi-core CPU is faulty at the time of initialization, the electronic control unit is initialized and started in order to perform the degenerate operation by the core B. At this time, there is a problem that the function initialized by the core A is not initialized.

また、初期化は、必ずしも均等に並列化できない課題がある。たとえば、起動後、コアAがCPUクロックの設定を行っている間、コアBは他機能の初期化を行うことが出来ない。あるいは、機能によって初期化量の大小があり、コアAの初期化中にコアBに待ちが発生する場合がある。このように、コアAが初期化中にコアBに待ちが発生する場合がある。   Also, there is a problem that initialization cannot always be performed in parallel. For example, after starting up, while core A is setting the CPU clock, core B cannot initialize other functions. Alternatively, depending on the function, the amount of initialization may be large and the core B may wait while the core A is being initialized. As described above, there is a case where the core B waits while the core A is initializing.

また、正常時よりも異常時の初期化完了時間が遅くなる課題がある。初期化が完了した後にコアの正常判定を行った時点でコアAについて故障を検知したとする。この場合、前記故障したコアAが初期化した機能に関しては、コアBが初期化をやり直す必要がある。すべての機能の初期化をコアBが行うことになり、コアAの初期化処理時間とコアBの初期化処理時間の差、すなわち、コアBの待ち時間分だけ、正常時よりも異常時の方が初期化時間は長くなる。   In addition, there is a problem that the initialization completion time at the time of abnormality is slower than normal. Assume that a failure is detected for core A when the normality of the core is determined after initialization is completed. In this case, with respect to the function initialized by the failed core A, the core B needs to perform initialization again. All functions are initialized by Core B, and the difference between the initialization processing time of Core A and the initialization processing time of Core B, that is, the waiting time of Core B, is more abnormal than normal. The initialization time is longer.

本発明は、これらの課題を解決するための手段である。   The present invention is a means for solving these problems.

上記課題を解決するために本発明の自動車用電子制御装置は、複数のコアで同時に初期化処理を開始し、複数のコアで同じ機能に対して重複して初期化処理をする。   In order to solve the above-described problem, the electronic control apparatus for an automobile of the present invention starts the initialization process simultaneously with a plurality of cores, and performs the initialization process for the same function redundantly with the plurality of cores.

本発明によれば、故障しているコアの数によらずに、初期化を正常時と同等の時間で実施することが可能である。これにより、運転者に違和感を与えない。また、ソフトウェア制御の開始時刻がハードウェアの起動時間に対して一定となり、ハードウェア制御の制御ロジックを、正常時と異常時で切り替える必要が無くなる。   According to the present invention, it is possible to perform initialization in a time equivalent to that in the normal time regardless of the number of cores that have failed. As a result, the driver does not feel uncomfortable. Also, the software control start time is constant with respect to the hardware startup time, and it is not necessary to switch the control logic of the hardware control between normal and abnormal.

自動車用電子制御装置の概略図である。It is the schematic of the electronic controller for motor vehicles. 2つの正常なコアによる初期化処理を示す図である。It is a figure which shows the initialization process by two normal cores. コアの相互監視による故障判定方法を示す図である。It is a figure which shows the failure determination method by mutual monitoring of a core. 制御用個別部初期化を含む初期化処理を示す図である。It is a figure which shows the initialization process containing the individual part for control initialization. コア異常時の初期化処理を示す図である。It is a figure which shows the initialization process at the time of core abnormality. 初期化時にRAMの設定と故障判定を行う図である。It is a figure which performs RAM setting and failure determination at the time of initialization. 初期化時にRAMの設定と故障判定を行う処理手順を示す図である。It is a figure which shows the process sequence which performs the setting of RAM and failure determination at the time of initialization. 他方のコアの初期化が正しく実施されているかを判定する図である。It is a figure which determines whether initialization of the other core is implemented correctly. 3つ以上のコアによる初期化処理後に通常制御実施を示す図である。It is a figure which shows normal control implementation after the initialization process by three or more cores.

以下に本発明の実施形態について、図面を用いて説明する。   Embodiments of the present invention will be described below with reference to the drawings.

本発明の実施例1について、図1から図3を用いて説明する。   A first embodiment of the present invention will be described with reference to FIGS.

図1に示すように、自動車用電子制御装置10(以下、ECU)には、外部バッテリから電源が供給され電源ICによって電源制御される。ユーザがイグニッションスイッチをONすると、電源ICは外部接続ポートからマイコン100に電源が供給されると共にリセット信号をマイコン100に入力する。リセット信号により、マイコン100に内蔵されているCPU(Central Processing Unit)1100の内にあるコア1110、コア1120、コア1130、コア1140までのコアが同時に演算を開始する。   As shown in FIG. 1, power is supplied to an automobile electronic control device 10 (hereinafter referred to as ECU) from an external battery and is controlled by a power supply IC. When the user turns on the ignition switch, the power supply IC supplies power to the microcomputer 100 from the external connection port and inputs a reset signal to the microcomputer 100. In response to the reset signal, the cores 1110, 1120, 1130, and 1140 in the CPU (Central Processing Unit) 1100 built in the microcomputer 100 simultaneously start operation.

実施例1として、コア数Nが2の場合について、初期化手順を図2に示す。   FIG. 2 shows an initialization procedure in the case where the number N of cores is 2 as the first embodiment.

実施例1においては、各コアで使用する初期化プログラムはROM1300に格納されており、CPU1110はROM1300からプログラムを読み出して実行する。   In the first embodiment, the initialization program used in each core is stored in the ROM 1300, and the CPU 1110 reads the program from the ROM 1300 and executes it.

初期化手順を図2に示す。   The initialization procedure is shown in FIG.

リセット信号により演算を開始するタイミングがt1000である。タイミングt1000において、コア1110は初期化プログラム1500に従い、マイコン100の各機能の初期化を開始する。たとえば、クロックやタイマ、外部出力、共有メモリであり、コア1110とコア1120で共通に使用する機能である。   The timing at which the calculation is started by the reset signal is t1000. At timing t1000, the core 1110 starts to initialize each function of the microcomputer 100 according to the initialization program 1500. For example, a clock, a timer, an external output, and a shared memory are functions commonly used by the core 1110 and the core 1120.

一方、コア1120も初期化プログラム1500に従い、マイコン100の各機能の初期化を開始する。すなわち、コア1110とコア1120は同一のプログラムを用いる。これにより、プログラムの作成および管理が容易となる。   On the other hand, the core 1120 also starts initialization of each function of the microcomputer 100 according to the initialization program 1500. That is, the core 1110 and the core 1120 use the same program. This facilitates program creation and management.

コア1110とコア1120が同時にプログラムを実行する場合、演算はそれぞれのコアで独立しているため、時間的に同時刻に実行可能である。ところが、共有機能、たとえば図1の共有レジスタ1101にアクセスする場合、資源競合が発生する。CPUではこのような競合を調停するため、バス1190に調停機能がある。すなわち、コア1110とコア1120が同時に実行開始しても、共有機能の設定を行う際に、ハードウェアの調停機能により、たとえばコア1110が優先されてコア1120が待たされ、競合を起こすことなく、初期化は正常に行われる。この副作用として、コア1110とコア1120の実行時間がずれることになる。この時間は、資源共有待ち時間t212であり、自動車の挙動に影響が及ぶことや、運転者が気づく時間ではない。いずれにせよ、コア1110が初期化処理10011を完了した時点t1001において、コア1120の初期化処理10021は実行中である。そのため、この時点でコア1110がコア1120の故障判定を行うと、コア1120が返答できずに判断ミスを起こす可能性がある。そこで、初期化処理と故障判定の間に明示的に待ち処理を行う。これらの待ち処理が10012と10022である。   When the core 1110 and the core 1120 execute a program at the same time, the calculation can be executed at the same time in time because each core is independent. However, when accessing the shared function, for example, the shared register 1101 of FIG. 1, resource contention occurs. The CPU has an arbitration function in the bus 1190 to arbitrate such contention. That is, even if the core 1110 and the core 1120 start executing simultaneously, when setting the shared function, the core arbitration function, for example, the core 1110 is prioritized and the core 1120 is waited, without causing a conflict. Initialization is successful. As a side effect, the execution times of the core 1110 and the core 1120 are shifted. This time is the resource sharing waiting time t212 and is not the time that the behavior of the automobile is affected or the driver notices. In any case, at time t1001 when the core 1110 completes the initialization process 10011, the initialization process 10021 of the core 1120 is being executed. For this reason, if the core 1110 makes a failure determination of the core 1120 at this time, the core 1120 may not be able to respond and a determination error may occur. Therefore, an explicit wait process is performed between the initialization process and the failure determination. These waiting processes are 10012 and 10028.

その後、相互にコアの故障判定を行う。コアの相互監視による故障判定方法を図3に示す。   Thereafter, the cores are determined to fail each other. FIG. 3 shows a failure determination method based on mutual monitoring of cores.

S3400において、コア1110がコア1120に問題データを送信する。コア1120はS3500でコア1110から送信された問題データを受信する。S3501で受信した問題データを元に、予め決められた計算式で回答データを算出し、S3502でコア1110に返信する。コア1110はS3401でコア1120から回答データを受信する。   In S3400, the core 1110 transmits the problem data to the core 1120. The core 1120 receives the problem data transmitted from the core 1110 in S3500. Based on the problem data received in S3501, answer data is calculated using a predetermined calculation formula, and is returned to the core 1110 in S3502. The core 1110 receives the response data from the core 1120 in S3401.

S3402において、コア1110は予めプログラムに埋め込まれた正解データを用い、コア1120から返信されたデータと照合する。コア1120の算出したデータと正解データが一致すれば正常と判断しコア1120は通常制御行うS3043。一方コア1120の算出した回答データと正解データが一致しない場合はS3404にてコア1120を停止する。   In S3402, the core 1110 uses the correct data embedded in the program in advance, and collates with the data returned from the core 1120. If the data calculated by the core 1120 matches the correct answer data, it is determined as normal and the core 1120 performs normal control S3043. On the other hand, if the answer data calculated by the core 1120 does not match the correct answer data, the core 1120 is stopped in S3404.

前記ロジックにおいて、コア1110とコア1120を入れ替えることで、コア1120の診断を行う。   In the logic, the core 1110 and the core 1120 are exchanged to diagnose the core 1120.

故障判定により両方のコアの正常が確認されれば、制御2015と2025を行う。正常時の制御は各コアで機能分配された、最適な制御である。   If the normality of both cores is confirmed by the failure determination, control 2015 and 2025 are performed. The normal control is an optimal control in which functions are distributed among the cores.

一方、コア1110がコア1120の異常を検知した場合、縮退運転モードに切り替える。この場合、コア1110のみで運転するため、制御2015は縮退運転用となる。   On the other hand, when the core 1110 detects an abnormality of the core 1120, the core 1110 switches to the degenerate operation mode. In this case, since the operation is performed only with the core 1110, the control 2015 is for the degenerate operation.

この場合においても機能の初期化は完了しているため、やり直す必要は無い。すなわち、正常時と同じ時間で機能の初期化が完了し、縮退運転モードへの移行開始が可能である。   Even in this case, since the initialization of the function is completed, there is no need to start over. In other words, the initialization of the function is completed in the same time as normal, and the transition to the degenerate operation mode can be started.

本実施例ではコア1110とコア1120に同一の初期化プログラムを用いるため、プログラムの作成及び管理が容易となる。   In the present embodiment, since the same initialization program is used for the core 1110 and the core 1120, the creation and management of the program become easy.

本発明の実施例2について、図4と図5を用いて説明する。なお、実施例1と同様の構成については説明を省略する。   A second embodiment of the present invention will be described with reference to FIGS. Note that the description of the same configuration as that of the first embodiment is omitted.

実施例2においては、図4に示すように、故障判定を行うための最低限の初期化である共通部初期化と、制御のための初期化である個別部初期化に分けて、初期化を実施する。   In the second embodiment, as shown in FIG. 4, initialization is divided into common part initialization, which is the minimum initialization for performing failure determination, and individual part initialization, which is initialization for control. To implement.

実施例1と同様に共通部初期化11011と共通部初期化11021は、同一のプログラムである。あるいは、共通部初期化11011でレジスタ1101を初期化中に、資源競合を避けるため、共通部初期化11021は共有RAM1200の初期化を行い、その後、共通部初期化11011で共有RAM1200を初期化中に、共通部初期化11021がレジスタ1101の初期化を行っても良い。これにより、資源競合待ちが発生せずに高速化が見込める。   Similar to the first embodiment, the common unit initialization 11011 and the common unit initialization 11021 are the same program. Alternatively, in order to avoid resource contention while the register 1101 is being initialized by the common unit initialization 11011, the common unit initialization 11021 initializes the shared RAM 1200, and then the common unit initialization 11011 is initializing the shared RAM 1200. In addition, the common unit initialization 11021 may initialize the register 1101. As a result, it is possible to increase the speed without waiting for resource competition.

故障判定は実施例1と同様である。   The failure determination is the same as in the first embodiment.

故障判定の結果、正常な場合、コア1110は、制御11015に合わせて個別部初期化 11014を行う。例えば、ローカルRAM1150の初期化である。また、コア1120は、制御11025に合わせて個別部初期化 11024を行う。   If the result of the failure determination is normal, the core 1110 performs individual unit initialization 11014 in accordance with the control 11015. For example, initialization of the local RAM 1150. In addition, the core 1120 performs individual unit initialization 11024 in accordance with the control 11025.

一方、故障判定11013にてコア1120の故障を検知した場合、図5に示すように縮退運転モードへ切り替える12015。   On the other hand, when a failure of the core 1120 is detected in the failure determination 11013, as shown in FIG.

個別部初期化 12014は縮退運転用の初期化であり、例えば、個別部初期化 11014とは、ローカルRAM1150の値が異なる。また、停止処理12024は、例えば無限ループ処理やコア1110によるコア1120クロック停止処理であり、故障したコア1120が共有機能に対してアクセスしないようにする。   The individual unit initialization 12014 is initialization for degenerate operation. For example, the value of the local RAM 1150 is different from the individual unit initialization 11014. The stop process 12024 is, for example, an infinite loop process or a core 1120 clock stop process by the core 1110, and prevents the failed core 1120 from accessing the shared function.

実施例2では、起動から故障判定までの時間を、正常時とコア故障時で同等とすることが可能である。   In the second embodiment, the time from the start to the failure determination can be made equal between the normal time and the core failure time.

本発明の実施例3について、図6から図8を用いて説明するなお、先の実施例と同様の構成については説明を省略する。   The third embodiment of the present invention will be described with reference to FIGS. 6 to 8. Note that the description of the same configuration as the previous embodiment is omitted.

実施例3においては、初期化時にRAMの設定と故障判定を行う。初期化処理を図6に示す。   In the third embodiment, RAM setting and failure determination are performed during initialization. The initialization process is shown in FIG.

リセット信号により演算を開始するタイミングがt210である。タイミングt210において、コア1110は共通部初期化プログラム2111に従い、マイコン100の共有メモリ1200の初期化を開始する。   The timing for starting the operation by the reset signal is t210. At timing t <b> 210, the core 1110 starts to initialize the shared memory 1200 of the microcomputer 100 in accordance with the common unit initialization program 2111.

一方、コア1120も共通部初期化プログラム2122に従い、マイコン100の各機能の初期化を開始する。   On the other hand, the core 1120 also starts initialization of each function of the microcomputer 100 according to the common unit initialization program 2122.

このときの共通初期化プログラム2111の処理を図7に示す。   The processing of the common initialization program 2111 at this time is shown in FIG.

すなわち、Global RAM1200に格納される変数aの初期化S3000、変数bの初期化S3001、変数cの初期化S3002を実施する。   That is, initialization S3000 of variable a stored in global RAM 1200, initialization S3001 of variable b, and initialization S3002 of variable c are performed.

この間にコア1120は、共通部初期化プログラム2121を実施するが、この処理を図8に示す。すなわち、S3100でコア1120は、コア11110が行った初期化が正しく実施されているかを初期化変数aの読み出し、書き込み予定のデータと照合して正確性を確認するS3100。   During this time, the core 1120 executes the common unit initialization program 2121. This process is shown in FIG. That is, in S3100, the core 1120 confirms the accuracy by checking whether the initialization performed by the core 11110 is correctly performed by reading the initialization variable a and checking the data to be written S3100.

初期化が正常に実施されていないと判断するとコア1110のコア正常フラグをOFFにするS3101。ちなみに、コア正常フラグは、S3100以前にONとしておく。この場合、コア1110で初期化が正常に実施できなかったので、S3102にてコア1120が変数aの初期化を実施する。この手順を変数b及びcにも実施する。   If it is determined that the initialization has not been performed normally, the core normal flag of the core 1110 is turned OFF S3101. Incidentally, the core normal flag is set to ON before S3100. In this case, since initialization could not be normally performed in the core 1110, the core 1120 performs initialization of the variable a in S3102. This procedure is also performed for variables b and c.

本処理により、コア1110の故障判定が可能である。この時点でコア1120の診断は完了していない。次に、コア1120の診断を行うために、実行順番を入れ替える。処理2111と処理2121では、処理2121に判定処理があるので、処理時間が長くなる。そこで、コア1110は待ち処理2112を行い、コア1120が共通部初期化2123を開始するまで待つ。共通部初期化2123の処理を図7に示す。また、共通部初期化2113の処理を図8に示す。先行するコア1120のRAM初期化をコア1110が読み出し診断することで、コア1120が異常な場合にコア1120正常フラグによる診断を行う。   By this processing, it is possible to determine the failure of the core 1110. At this point, the diagnosis of the core 1120 has not been completed. Next, in order to diagnose the core 1120, the execution order is changed. In the processing 2111 and the processing 2121, since the processing 2121 includes the determination processing, the processing time becomes long. Therefore, the core 1110 performs a waiting process 2112 and waits until the core 1120 starts the common unit initialization 2123. The common part initialization 2123 process is shown in FIG. Further, the common part initialization 2113 process is shown in FIG. When the core 1110 reads and diagnoses the RAM initialization of the preceding core 1120, when the core 1120 is abnormal, the diagnosis is performed using the core 1120 normal flag.

コア1120は処理時間差の調整のため、待ち処理2122を行う。   The core 1120 performs a waiting process 2122 to adjust the processing time difference.

最後に、故障判定2114および故障判定2124で、コア正常フラグを判定して、相互にコア故障を検知する。   Finally, in the failure determination 2114 and the failure determination 2124, the core normal flag is determined and the core failure is detected mutually.

例えば、コア1120が停止している場合、コア1120正常フラグはOFFとなる。コア1120の正常時と故障時でコア1110の処理は変わらないため、起動完了t215の時間は同等である。   For example, when the core 1120 is stopped, the core 1120 normal flag is OFF. Since the processing of the core 1110 does not change between when the core 1120 is normal and when it fails, the time for the start completion t215 is the same.

本実施例により、コアの初期化完了とともにコア故障の検知が可能である。   According to this embodiment, it is possible to detect a core failure when the initialization of the core is completed.

本発明の実施例4について、図9を用いて説明する。なお、先の実施例と同様の構成については説明を省略する。   A fourth embodiment of the present invention will be described with reference to FIG. The description of the same configuration as in the previous embodiment is omitted.

本実施例では、コア数Nが3以上のCPUの場合の初期化手順を図9を用いて示す。   In this embodiment, an initialization procedure in the case of a CPU having a core number N of 3 or more is shown using FIG.

リセット信号により演算を開始するタイミングがt220である。タイミングt220において、コア1110は共通部初期化プログラム2211に従い、マイコン100の各機能の初期化を開始する。   The timing for starting the operation by the reset signal is t220. At timing t <b> 220, the core 1110 starts to initialize each function of the microcomputer 100 according to the common unit initialization program 2211.

一方、コア1120、コア1130、コア1140も各共通部初期化プログラムに従い、マイコン100の各機能の初期化を開始する。   On the other hand, the core 1120, the core 1130, and the core 1140 also start initialization of each function of the microcomputer 100 in accordance with each common unit initialization program.

コア数が、3以上の場合は、予めペアとなるコアを決めておき、そのペアによって故障判定を実施する。例えばコア1110とコア1120、コア1130とコア1140とする。   When the number of cores is 3 or more, a core to be paired is determined in advance, and failure determination is performed based on the pair. For example, a core 1110 and a core 1120, and a core 1130 and a core 1140 are used.

このように予めペアとなるコアを用いて、実施例1で示した共通部初期化、故障判定、個別部初期化をペアのコア同士で実施する。つまりコア1110はペアではないコア1130やコア1140の共通部初期化処理を待つ必要がなく、ペアのコア1120の共通部初期化処理2221が完了するのを待つだけで良い。   In this way, using the cores that are paired in advance, the common part initialization, the failure determination, and the individual part initialization described in the first embodiment are performed between the paired cores. In other words, the core 1110 does not need to wait for the common part initialization process of the core 1130 or the core 1140 that is not a pair, but only waits for the common part initialization process 2221 of the paired core 1120 to be completed.

但し、通常制御を開始するタイミングである通常制御開始t226は全てのコアで揃える必要があるため、各コアで個別部初期化処理完了後にコア1110の待ち処理2215、コア1120の待ち処理2225、コア1130の待ち処理2235、コア1140の待ち処理2245を実施する。   However, since the normal control start t226 that is the timing for starting the normal control needs to be aligned for all the cores, the waiting process 2215 of the core 1110, the waiting process 2225 of the core 1120 after completion of the individual unit initialization process in each core, the core A waiting process 2235 of 1130 and a waiting process 2245 of the core 1140 are executed.

本実施例において、どのコアが故障したとしても、起動時間は正常時と同等である。   In this embodiment, no matter which core fails, the start-up time is equivalent to that at normal time.

Claims (3)

車両機能を制御するCPUを有し、
前記CPU内部の演算部であるコアを複数有し、
前記複数のコアにより共通部の初期化を行う自動車用電子制御装置であって、
ECU起動後、コアの故障判定を行う前に、複数のコアで同一の初期化プログラムを実行することを特徴とする自動車用電子制御装置
A CPU for controlling vehicle functions;
Having a plurality of cores that are arithmetic units inside the CPU,
An automotive electronic control device that initializes a common part with the plurality of cores,
An electronic control device for an automobile, wherein the same initialization program is executed by a plurality of cores after the ECU is started and before the core failure is determined.
前記コアを3個以上有し、
初期化処理前に予めペアとなるコアを決めておき、そのペアごとに同一の機能の初期化を実施することを特徴とする請求項1に記載の自動車用電子制御装置。
Having three or more cores,
The automotive electronic control device according to claim 1, wherein cores to be paired are determined in advance before initialization processing, and the same function is initialized for each pair.
あるコアAがあるコアBに優先して前記初期化プログラムを開始し、途中で前記初期化の順位を入れ替えて、前記コアBが前記コアAに優先して初期化を行うことを特徴とする請求項1に記載の自動車用電子制御装置。   A certain core A starts the initialization program in preference to a certain core B, the order of the initialization is changed in the middle, and the core B performs initialization in preference to the core A The automobile electronic control device according to claim 1.
JP2017045603A 2017-03-10 2017-03-10 Automotive electronic control unit Active JP6660902B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2017045603A JP6660902B2 (en) 2017-03-10 2017-03-10 Automotive electronic control unit

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2017045603A JP6660902B2 (en) 2017-03-10 2017-03-10 Automotive electronic control unit

Publications (2)

Publication Number Publication Date
JP2018151717A true JP2018151717A (en) 2018-09-27
JP6660902B2 JP6660902B2 (en) 2020-03-11

Family

ID=63680429

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2017045603A Active JP6660902B2 (en) 2017-03-10 2017-03-10 Automotive electronic control unit

Country Status (1)

Country Link
JP (1) JP6660902B2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113377584A (en) * 2020-03-10 2021-09-10 本田技研工业株式会社 Electronic control device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007094528A (en) * 2005-09-27 2007-04-12 Canon Inc Method for using memory of multiprocessor system
JP2014049013A (en) * 2012-09-03 2014-03-17 Hitachi Automotive Systems Ltd Electronic control system for automobile
JP2017027381A (en) * 2015-07-23 2017-02-02 富士通株式会社 Parallel computer, initialization method of parallel computer, and start program

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007094528A (en) * 2005-09-27 2007-04-12 Canon Inc Method for using memory of multiprocessor system
JP2014049013A (en) * 2012-09-03 2014-03-17 Hitachi Automotive Systems Ltd Electronic control system for automobile
JP2017027381A (en) * 2015-07-23 2017-02-02 富士通株式会社 Parallel computer, initialization method of parallel computer, and start program

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113377584A (en) * 2020-03-10 2021-09-10 本田技研工业株式会社 Electronic control device
CN113377584B (en) * 2020-03-10 2024-05-03 本田技研工业株式会社 Electronic control device

Also Published As

Publication number Publication date
JP6660902B2 (en) 2020-03-11

Similar Documents

Publication Publication Date Title
JP4831599B2 (en) Processing equipment
US8527681B2 (en) Data processing system, data processing method, and apparatus
EP2413484A2 (en) Safety control system
JP5843786B2 (en) Monitoring computer in the control unit
JP6266239B2 (en) Microcomputer
CN107526290B (en) Method for operating a controller
CN107077407B (en) Vehicle control device
US8509989B2 (en) Monitoring concept in a control device
US20110072313A1 (en) System for providing fault tolerance for at least one micro controller unit
JPS5968004A (en) Fail-safe method of on-vehicle computer
JP6007677B2 (en) Safety control system and processor of safety control system
JP6660902B2 (en) Automotive electronic control unit
JP5582748B2 (en) Electronic control device for vehicle
JP2016222018A (en) Cpu monitoring device, vehicle control system, and cpu monitoring method
CN115373919A (en) Soc debugging method and system, electronic equipment and storage medium
US10514970B2 (en) Method of ensuring operation of calculator
WO2014080245A1 (en) Data processing device, method of execution error detection and integrated circuit
KR102275869B1 (en) Apparatus and method of vehicle control
JP5978873B2 (en) Electronic control unit
US20230001939A1 (en) Vehicle mounted electronic control apparatus
JP7333251B2 (en) electronic controller
JP6588068B2 (en) Microcomputer
JP6887277B2 (en) Electronic control device for automobiles
JP2018063599A (en) Mutual monitoring system
CN116701032A (en) Data exchange method and device, electronic chip and storage medium

Legal Events

Date Code Title Description
A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20170313

A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20181106

A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20181107

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20190328

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20190409

A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20190517

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20191105

A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20191224

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20200114

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20200210

R150 Certificate of patent or registration of utility model

Ref document number: 6660902

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150

S533 Written request for registration of change of name

Free format text: JAPANESE INTERMEDIATE CODE: R313533

R350 Written notification of registration of transfer

Free format text: JAPANESE INTERMEDIATE CODE: R350

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250