SNIP_CLASSIC_PLATFORM_SECTION_2012_Standard

2012 Standard. [SRS_BSW_00009] All Basic SW Modules shall be documented according to a common standard. [SRS_BSW_00010] The memory consumption of all Basic SW Modules shall be documented for a defined configuration for all supported platforms. [SRS_BSW_00101] The Basic Software Module shall be able to initialize variables and hardware in a separate initialization function [SRS_BSW_00159] All modules of the AUTOSAR Basic Software shall support a tool based configuration [SRS_BSW_00160] Configuration files of AUTOSAR Basic SW module shall be readable for human beings [SRS_BSW_00161] The AUTOSAR Basic Software shall provide a microcontroller abstraction layer which provides a standardized interface to higher software layers [SRS_BSW_00162] The AUTOSAR Basic Software shall provide a hardware abstraction layer [SRS_BSW_00164] The Implementation of interrupt service routines shall be done by the Operating System, complex drivers or modules [SRS_BSW_00167] All AUTOSAR Basic Software Modules shall provide configuration rules and constraints to enable plausibility checks [SRS_BSW_00168] SW components shall be tested by a function defined in a common API in the Basis-SW [SRS_BSW_00170] The AUTOSAR SW Components shall provide information about their dependency from faults, signal qualities, driver demands [SRS_BSW_00171] Optional functionality of a Basic-SW component that is not required in the ECU shall be configurable at pre-compile-time [SRS_BSW_00172] The scheduling strategy that is built inside the Basic Software Modules shall be compatible with the strategy used in the system [SRS_BSW_00300] All AUTOSAR Basic Software Modules shall be identified by an unambiguous name [SRS_BSW_00301] All AUTOSAR Basic Software Modules shall only import the necessary information ▽ △ Number Heading [SRS_BSW_00302] All AUTOSAR Basic Software Modules shall only export information needed by other modules [SRS_BSW_00304] All AUTOSAR Basic Software Modules shall use only AUTOSAR data types instead of native C data types [SRS_BSW_00305] Data types naming convention [SRS_BSW_00306] AUTOSAR Basic Software Modules shall be compiler and platform independent [SRS_BSW_00307] Global variables naming convention [SRS_BSW_00308] AUTOSAR Basic Software Modules shall not define global data in their header files, but in the C file [SRS_BSW_00309] All AUTOSAR Basic Software Modules shall indicate all global data with read-only purposes by explicitly assigning the const keyword [SRS_BSW_00310] API naming convention [SRS_BSW_00312] Shared code shall be reentrant [SRS_BSW_00314] All internal driver modules shall separate the interrupt frame definition from the service routine [SRS_BSW_00318] Each AUTOSAR Basic Software Module file shall provide version numbers in the header file [SRS_BSW_00321] The version numbers of AUTOSAR Basic Software Modules shall be enumerated according specific rules [SRS_BSW_00323] All AUTOSAR Basic Software Modules shall check passed API parameters for validity [SRS_BSW_00325] The runtime of interrupt service routines and functions that are running in interrupt context shall be kept short [SRS_BSW_00327] Error values naming convention [SRS_BSW_00328] All AUTOSAR Basic Software Modules shall avoid the duplication of code [SRS_BSW_00330] It shall be allowed to use macros instead of functions where source code is used and runtime is critical [SRS_BSW_00331] All Basic Software Modules shall strictly separate error and status information [SRS_BSW_00333] For each callback function it shall be specified if it is called from interrupt context or not [SRS_BSW_00334] All Basic Software Modules shall provide an XML file that contains the meta data [SRS_BSW_00335] Status values naming convention [SRS_BSW_00336] Basic SW module shall be able to shutdown [SRS_BSW_00337] Classification of development errors [SRS_BSW_00339] Reporting of production relevant error status [SRS_BSW_00341] Module documentation shall contains all needed informations [SRS_BSW_00342] It shall be possible to create an AUTOSAR ECU out of modules provided as source code and modules provided as object code, even mixed [SRS_BSW_00343] The unit of time for specification and configuration of Basic SW modules shall be preferably in physical time unit ▽ △ Number Heading [SRS_BSW_00344] BSW Modules shall support link-time configuration [SRS_BSW_00345] BSW Modules shall support pre-compile configuration [SRS_BSW_00346] All AUTOSAR Basic Software Modules shall provide at least a basic set of module files [SRS_BSW_00347] A Naming seperation of different instances of BSW drivers shall be in place [SRS_BSW_00348] All AUTOSAR standard types and constants shall be placed and organized in a standard type header file [SRS_BSW_00350] All AUTOSAR Basic Software Modules shall allow the enabling/disabling of detection and reporting of development errors. [SRS_BSW_00351] Encapsulation of compiler specific methods to map objects [SRS_BSW_00353] All integer type definitions of target and compiler specific scope shall be placed and organized in a single type header [SRS_BSW_00357] For success/failure of an API call a standard return type shall be defined [SRS_BSW_00358] The return type of init() functions implemented by AUTOSAR Basic Software Modules shall be void [SRS_BSW_00359] All AUTOSAR Basic Software Modules callback functions shall avoid return types other than void if possible [SRS_BSW_00360] AUTOSAR Basic Software Modules callback functions are allowed to have parameters [SRS_BSW_00369] All AUTOSAR Basic Software Modules shall not return specific development error codes via the API [SRS_BSW_00373] The main processing function of each AUTOSAR Basic Software Module shall be named according the defined convention [SRS_BSW_00374] All Basic Software Modules shall provide a readable module vendor identification [SRS_BSW_00375] Basic Software Modules shall report wake-up reasons [SRS_BSW_00377] A Basic Software Module can return a module specific types [SRS_BSW_00378] AUTOSAR shall provide a boolean type [SRS_BSW_00379] All software modules shall provide a module identifier in the header file and in the module XML description file. [SRS_BSW_00380] Configuration parameters being stored in memory shall be placed into separate c-files [SRS_BSW_00383] The Basic Software Module specifications shall specify which other configuration files from other modules they use at least in the description [SRS_BSW_00384] The Basic Software Module specifications shall specify at least in the description which other modules they require [SRS_BSW_00385] List possible error notifications [SRS_BSW_00386] The BSW shall specify the configuration and conditions for detecting an error [SRS_BSW_00388] Containers shall be used to group configuration parameters that are defined for the same object [SRS_BSW_00389] Containers shall have names [SRS_BSW_00390] Parameter content shall be unique within the module ▽ △ Number Heading [SRS_BSW_00392] Parameters shall have a type [SRS_BSW_00393] Parameters shall have a range [SRS_BSW_00394] The Basic Software Module specifications shall specify the scope of the configuration parameters [SRS_BSW_00395] The Basic Software Module specifications shall list all configuration parameter dependencies [SRS_BSW_00396] The Basic Software Module specifications shall specify the supported configuration classes for changing values and multiplicities for each parameter/container [SRS_BSW_00397] The configuration parameters in pre-compile time are fixed before compilation starts [SRS_BSW_00398] The link-time configuration is achieved on object code basis in the stage after compiling and before linking [SRS_BSW_00399] Parameter-sets shall be located in a separate segment and shall be loaded after the code [SRS_BSW_00400] Parameter shall be selected from multiple sets of parameters after code has been loaded and started [SRS_BSW_00401] Documentation of multiple instances of configuration parameters shall be available [SRS_BSW_00402] Each module shall provide version information [SRS_BSW_00403] The Basic Software Module specifications shall specify for each parameter/ container whether it supports different values or multiplicity in different configuration sets [SRS_BSW_00404] BSW Modules shall support post-build configuration [SRS_BSW_00405] BSW Modules shall support multiple configuration sets [SRS_BSW_00406] A static status variable denoting if a BSW module is initialized shall be initialized with value 0 before any APIs of the BSW module is called [SRS_BSW_00407] Each BSW module shall provide a function to read out the version information of a dedicated module implementation [SRS_BSW_00408] All AUTOSAR Basic Software Modules configuration parameters shall be named according to a specific naming rule [SRS_BSW_00409] All production code error ID symbols are defined by the Dem module and shall be retrieved by the other BSW modules from Dem configuration [SRS_BSW_00410] Compiler switches shall have defined values [SRS_BSW_00411] All AUTOSAR Basic Software Modules shall apply a naming rule for enabling/disabling the existence of the API [SRS_BSW_00413] An index-based accessing of the instances of BSW modules shall be done [SRS_BSW_00414] Init functions shall have a pointer to a configuration structure as single parameter [SRS_BSW_00415] Interfaces which are provided exclusively for one module shall be separated into a dedicated header file [SRS_BSW_00416] The sequence of modules to be initialized shall be configurable ▽