SNIP_CLASSIC_WDG_SECTION_8_3_Function_definitions_WATCHDOGINTERFACE

8.3 Function definitions [SWS_WdgIf_00017] Upstream requirements: SRS_Wdg_12165, SRS_Wdg_12167, SRS_MemHwAb_14019 ⌈The Watchdog Interface shall map the APIs specified in this chapter to the API of the underlying drivers. For functional behavior refer to the specification of the watchdog driver⌋ [SWS_WdgIf_00018] Upstream requirements: SRS_MemHwAb_14020 ⌈The Watchdog Interface shall use the parameter DeviceIndex for selection of watchdog drivers. If only one watchdog driver is configured, the parameter DeviceIndex shall be ignored.⌋ [SWS_WdgIf_00013] Upstream requirements: SRS_BSW_00304 ⌈The data type for the watchdog device index shall be uint8. DeviceIndex shall provide a zero-based consecutive index.⌋ [SWS_WdgIf_00019] Upstream requirements: SRS_MemHwAb_14021 ⌈If only one watchdog driver is configured, the Watchdog Interface shall cause no runtime overhead when mapping the Watchdog Interface API to the API of the corresponding Watchdog Driver.⌋ Implementation hint: This could be done by using macros as for example #define WdgIf_SetMode(DeviceIndex, WdgMode) \ Wdg_SetMode(WdgMode) [SWS_WdgIf_00020] Upstream requirements: SRS_MemHwAb_14021 ⌈If more than one watchdog driver is configured, the Watchdog Interface shall use efficient mechanisms to map the API calls to the appropriate watchdog driver.⌋ Implementation hint: One solution is to use tables of pointers to functions where the parameter DeviceIndex is used as array index, for example #define WdgIf_SetMode(DeviceIndex, WdgMode) \ SetModeFctPtr[DeviceIndex](WdgMode) Note: The service IDs are related to the service IDs of the watchdog driver specification [7]. For that reason, they may not start with 0.