SNIP_CLASSIC_OS_SECTION_4_3_3_Software_Module_Design_Requirements

[SRS_BSW_00348] All AUTOSAR standard types and constants shall be placed and organized in a standard type header file ⌈ Description: All AUTOSAR standard types and constants shall be placed and organized in a standard type header file. Standard type header file naming convention: Std_Types.h This standard type header file shall • include the Platform specific type header (Platform_Types.h) • define the type Std_ReturnType • define values for E_OK and E_NOT_OK • define values for STD_ON, STD_OFF, STD_HIGH, STD_LOW, STD_ACTIVE, STD_IDLE Rationale: Provide uniform framework wide access to standard types to be used by all modules. Use Case: Each module that uses AUTOSAR integer data types and/or the standard return type shall include the file Std_Types.h. Dependencies: [SRS_BSW_00357], [SRS_BSW_00353] Supporting Material: Important note for implementation of this header file: Because E_OK is already defined within [3, OSEK OS], E_OK has to be checked for being already defined: /* for ISO 17356-3 compliance this typedef has been added */ #ifndef STATUSTYPEDEFINED #define STATUSTYPEDEFINED typedef unsigned char StatusType; #define E_OK 0 #endif ⌋ [SRS_BSW_00353] All integer type definitions of target and compiler specific scope shall be placed and organized in a single type header ⌈ Description: All integer type definitions of target and compiler specific scope shall be placed and organized in a single type header. Name of platform types header file: Platform_Types.h Rationale: Separate compiler and µC-specific integer types from standard types. Use Case: Changing the microcontroller and/or compiler shall only affect a limited number of files. Dependencies: [SRS_BSW_00308], [SRS_BSW_00348] Supporting Material: – ⌋