SNIP_CLASSIC_ECUM_SECTION_7_6_3_Internal_Representation_of_Wakeup_States

7.6.3 Internal Representation of Wakeup States The EcuM manager module offers the following interfaces to ascertain the state of those wakeup sources: • EcuM_GetPendingWakeupEvents • EcuM_GetValidatedWakeupEvents • EcuM_GetExpiredWakeupEvents and manipulates the state of the wakeup sources through the following interfaces • EcuM_ClearWakeupEvent • EcuM_SetWakeupEvent • EcuM_ValidateWakeupEvent • EcuM_CheckWakeup • EcuM_DisableWakeupSources • EcuM_EnableWakeupSources • EcuM_StartWakeupSources • EcuM_StopWakeupSources The ECU Manager module can manage up to 32 wakeup sources. The state of the wakeup sources is typically represented at the EcuM interfaces named above by means of an EcuM_WakeupSourceType bitmask where the individual wakeup sources correspond to a fixed bit position. There are 5 predefined bit positions and the rest can be assigned by configuration. See section 8.2.3 EcuM_WakeupSourceType for details. On the one hand, the ECU Manager module manages the modes of each wakeup source. On the other hand, the ECU Manager module presupposes that there are "internal variables" (i.e. EcuM_WakeupSourceType instances) that track which wakeup sources are in a particular state (especially NONE (i.e. cleared), PENDING, VALIDATED and EXPIRED). The ECU Manager module uses these "internal variables" in the respective interface definitions to define the semantics of the interface. Whether these "internal variables" are indeed implemented is therefore of secondary importance. They are simply used to explain the semantics of the interfaces.