SNIP_CLASSIC_ECUM_FIGURE_Figure_7_17

Figure 7.17: Partitions inside an ECU In a multi core architecture the EcuM has to be distributed in a way , that one instance per core exists. There is one designated master core in which the boot loader starts the master Ecu M via EcuM_Init. The master EcuM starts some drivers, determines the Post Build configuration and starts all remaining cores with all their satellite EcuMs. Each EcuM now starts the core local OS and all core local BswMs (in every partition resides exactly one BswM). If the same image of EcuM is executed on every core of the ECU, the ECU Manager’s behavior has to differ on the different cores. This can be accomplished by the ECU Manager by testing first whether it is on a master or a slave core and act appropriately . The ECU Manager module supports the same phases on a MultiCore ECU as are available on conventional ECUs (i.e. ST ARTUP , UP , SHUTDOWN and SLEEP). If safety mechanisms are used, The ECU State Manager has to run with full trust level. This section uses previous ECU Manager terms for various ECU states, notably Run/ PostRun. With flexible ECU management, the system integrator determines the ECU’s states’ names and semantics. Methods to ensure a de-initialization phase must be upheld, however. The names used here are therefore not normative.