DEENESPTFRRUARHIKOZHNL
CLASSIC Modul: nvm Rolle: heuristic Konfidenz: 90%

SNIP_CLASSIC_NVM_SECTION_5_2_3_4_Standard_header_files

Quelle: AUTOSAR_SRS_BSWGeneral.pdf (Seite 62) • Ziel-Anforderung: SWS_Std_00013

Wortlaut

5.2.3.4 Standard header files [SRS_BSW_00348] All AUTOSAR standard types and constants shall be placed and organized in a standard type header file ⌈ Type: Draft 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)  include the compiler specific language extension header (Compiler.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 ISO 17356-3, 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 ⌋(RS_BRF_01024) [SRS_BSW_00353] All integer type definitions of target and compiler specific scope shall be placed and organized in a single type header ⌈ Type: Valid 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: -- ⌋(RS_BRF_02080) [SRS_BSW_00361] All mappings of not standardized keywords of compiler specific scope shall be placed and organized in a compiler specific type and keyword header ⌈ Type: Valid Description: All mappings of not standardized keywords of compiler specific scope shall be placed and organized in a compiler specific type and keyword header. Name of compiler specific type/keyword header file: Compiler.h Rationale: Provision of a compiler specific header containing proprietary pre-processor directives as well as wrapper macros for all specialized language extensions. Use Case: Different compilers can require extended keywords to be placed in different places It is not possible to accommodate the different implementations with inline macros, so a function-like macro style is adopted instead. This macro wraps the return type of the function and therefore permits additions to made, such as __far__, either before or after the return type. Dependencies: [SRS_BSW_00306], [SRS_BSW_00348] Supporting Material: -- ⌋(RS_BRF_02080)

Versionen & Provenienz · Zugeordnete Anforderungen

Diese Angaben zeigt der Versions-Explorer.

Begründung & Zuweisungs-Evidenz

definition of STD_ACTIVE and STD_IDLE

Dokumenten-Herkunft & Rückverfolgbarkeit

Spezifikations-Dokument AUTOSAR_SRS_BSWGeneral.pdf
Dokumentseite Seite 62
Ziel-Modul nvm (classic)
Ziel-Anforderung SWS_Std_00013
Semantische Rolle heuristic
Automatisierungs-Konfidenz 0.90