Specification Of NVRAM Manager - AUTOSAR
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1Document TitleSpecification of NVRAMManagerDocument OwnerDocument ResponsibilityDocument Identification NoAUTOSARAUTOSAR033Document StatusPart of AUTOSAR StandardPart of Standard ReleaseFinalClassic Platform4.3.1Document Change HistoryDateRelease Changed ARReleaseManagement1 of 190Change Description Correction for write protection anderase requests forNvMWriteBlockOnce blocks Clarification regarding implicitrecovery of dataset blocks minor corrections / clarifications /editorial changes; For details pleaserefer to the ChangeDocumentation Added NvM FirstInitAll andNvM GetActiveServicefunctionalities NvM SetRamBlockStatus worksalso for explicit synchronizationblocks The interaction between NvM andBswM is clarified. Other small clarifications andupdates. Clarified behavior related torestoring default data for blocks andfor handling ofMEMIF BLOCK INVALID job result Added additional information relatedto the block states in chapter7.2.2.14 and related subchapters Updated NvM Init andNvM ValidateAll function prototypes Debugging support marked asobsoleteDocument ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1Document Change HistoryDateRelease Changed ARReleaseManagement2 of 190Change Description Detailed pass/fail conditions forproduction errors Added the NvM ValidateAllfunctionality Updated return values for Init andSingleBlock callbacks Other small clarifications Removed job postpone in case ofexplicit synchronization failed afterconfigured number of retries Updated Service Interfaces tables Renamed configuration parameterNvMRamBlockHeaderInclude toNvMBlockHeaderInclude Editorial changes AddedNvMRamBlockHeaderInclude andNvMMainFunctionPeriodconfiguration parameters Corrected bugs forNvMWriteVerificationDataSize andNvMNvramBlockIdentifierparameters Other small clarifications inrequirement Editorial changes Removed chapter(s) on changedocumentationDocument ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1Document Change HistoryDateRelease Changed by2013-03-154.1.1AUTOSARAdministration2011-12-223 of 1904.0.3AUTOSARAdministrationChange Description Added NvM ReadPRAMBlock,NvM WritePRAMBlock andNvM RestorePRAMBlockDefaultsAPIs Production Errors and ExtendedProduction Errors classification Clarifications for explicitsynchronization mechanism Modeling of Services: introduction offormal descriptions of serviceinterfaces Changes regardingNvM CancelJobs API,NvmSetRamBlockStatus API, Initcallback, handling of redundantblocks,queue sizes and usage ofMemoryMapping Reworked according to the newSWS BSWGeneral Added NvM CancelJobs behaviour Added NvM and BswM interaction Added NvM SetBlockLockStatusAPI functional description Corrected inconsistency between Cinterface and port interface Updated Include structure Updated configuration parametersdescription and rangeDocument ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1Document Change HistoryDateRelease Changed by2010-09-303.1.5AUTOSARAdministration2010-02-024 of 1903.1.4AUTOSARAdministrationChange Description Behavior specified to preventpossible loss of data duringshutdown References to DEM for productionerrors, new config containerNvmDemEventParameterRefs NvMMaxNoOfWriteRetries renamedto NvMMaxNumOfWriteRetries Note in chapter 7.1.4.5 completed Null pointer handling changed Chapter “Version check” updated New DET errorNVM E PARAM POINTER Chapter 10 updated,NvMMainFunctionCycleTimemoved, NvMSelectBlockForWriteAlladded, some ranges corrected Behavior specified when NVRAMblock ID 1 shall be written Chapter 12 updated Handling of single-block callbacksduring asynchronous multi-blockspecified. Some minor changes, typoscorrected The following features had impacton this document: Debugging concept Error handler concept Memory related concepts The following major features werenecessary to implement theseconcepts: Static Block Id Check Write Verification Read Retry buffered read/write-operations Legal disclaimer revisedDocument ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1Document Change HistoryDateRelease Changed ion2005-05-311.0AUTOSARAdministration5 of e Description Technical Office SWSImprovements are incorporated. Requirement IDs for configurationparameters (chapter 10) added. Management of the RAM block statespecified more precisely. The NVRAM Manager doesn'tsupport non-sequential NVRAMblock IDs any longer. Document meta informationextended Small layout adaptations made Legal disclaimer revised AUTOSAR service descriptionadded in chapter 11 Reentrancy of callback functionsspecified Details regarding memory hardwareabstraction addressing schemeadded Legal disclaimer revised “Advice for users” revised “Revision Information” added Document structure adapted tocommon Release 2.0 SWSTemplate. Major changes in chapter 10 Structure of document changedpartly Initial releaseDocument ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1DisclaimerThis work (specification and/or software implementation) and the material containedin it, as released by AUTOSAR, is for the purpose of information only. AUTOSARand the companies that have contributed to it shall not be liable for any use of thework.The material contained in this work is protected by copyright and other types ofintellectual property rights. The commercial exploitation of the material contained inthis work requires a license to such intellectual property rights.This work may be utilized or reproduced without any modification, in any form or byany means, for informational purposes only. For any other purpose, no part of thework may be utilized or reproduced, in any form or by any means, without permissionin writing from the publisher.The work has been developed for automotive applications only. It has neither beendeveloped, nor tested for non-automotive applications.The word AUTOSAR and the AUTOSAR logo are registered trademarks.6 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1Table of Contents123456789Introduction and functional overview9Acronyms and abbreviations11Related documentation123.1Input documents .123.2Related specification.13Constraints and assumptions144.1Limitations .144.2Applicability to car domains .144.3Conflicts .14Dependencies to other modules155.1File structure .155.1.1 Header file structure .155.2Memory abstraction modules .165.3CRC module .175.4Capability of the underlying drivers .17Requirements traceability18Functional specification277.1Basic architecture guidelines .277.1.1 Layer structure .277.1.2 Addressing scheme for the memory hardware abstraction .277.1.3 Basic storage objects.297.1.4 Block management types .337.1.5 Scan order / priority scheme .397.2General behavior .417.2.1 Functional requirements .417.2.2 Design notes .427.3Error Clasification .657.3.1 Development Errors .657.3.2 Runtime Errors.667.3.3 Transient faults .667.3.4 Production Errors .667.3.5 Extended Production Errors .677.4Error detection .71API specification788.1API .788.1.1 Imported types .788.1.2 Type definitions.788.1.3 Function definitions .788.1.4 Expected Interfaces .1398.1.5 API Overview .1448.2Service Interfaces .1458.2.1 Client-Server-Interfaces .1458.2.2 Implementation Data Types .1528.2.3 Ports .154Sequence Diagrams1569.1Synchronous calls.1569.1.1 NvM Init .1569.1.2 NvM SetDataIndex.1567 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.19.1.3 NvM GetDataIndex .1579.1.4 NvM SetBlockProtection .1579.1.5 NvM GetErrorStatus .1589.1.6 NvM GetVersionInfo .1589.2Asynchronous calls .1599.2.1 Asynchronous call with polling .1599.2.2 Asynchronous call with callback .1609.2.3 Cancellation of a Multi Block Request .1619.2.4 BswM Interraction .16210 Configuration specification16610.1 How to read this chapter .16610.2 Containers and configuration parameters .16610.2.1 NvM .16610.2.2 NvMCommon .16610.2.3 NvMBlockDescriptor .17210.2.4 NvMTargetBlockReference .18510.2.5 NvMEaRef .18510.2.6 NvMFeeRef.18510.2.7 NvmDemEventParameterRefs.18610.3 Common configuration options .18810.4 Published parameters .18911 Not applicable requirements190FiguresFigure 1: Memory Structure of Different Block TypesFigure 2: Logical Structure of Different Block TypesFigure 3: NvM Include structureFigure 4: NVRAM Manager interactions overviewFigure 5: NV Block layoutFigure 6: RAM Block layoutFigure 7: ROM block layoutFigure 8: NV block layout with Static Block ID enabledFigure 9: Redundant NVRAM Block layoutFigure 10: Dataset NVRAM block layoutFigure 11: RAM Block StatesFigure 12: UML sequence diagram NvM InitFigure 13: UML sequence diagram NvM SetDataIndexFigure 14: UML sequence diagram NvM GetDataIndexFigure 15: UML sequence diagram NvM SetBlockProtectionFigure 16: UML sequence diagram NvM GetErrorStatusFigure 17: UML sequence diagram NvM GetVersionInfoFigure 18: UML sequence diagram for asynchronous call with pollingFigure 19: UML sequence diagram for asynchronous call with callbackFigure 20: UML sequence diagram for cancellation of asynchronous call8 of 1Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.11Introduction and functional overviewThis specification describes the functionality, API and the configuration of theAUTOSAR Basic Software module NVRAM Manager (NvM).The NvM module shall provide services to ensure the data storage and maintenanceof NV (non volatile) data according to their individual requirements in an automotiveenvironment. The NvM module shall be able to administrate the NV data of anEEPROM and/or a FLASH EEPROM emulation device.The NvM module shall provide the required synchronous/asynchronous services forthe management and the maintenance of NV data (init/read/write/control).The relationship between the different blocks can be visualized in the followingpicture:-Figure 1: Memory Structure of Different Block Types9 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1id Component Model«abstract»NVRAM Block-Block Management Type:constraints{exact composition depends on Management type}{handling depends on Block Management Type}NV BlockRAM Block«realize»«user data»ROM Block«realize»«realize»Administrativ e Block«realize»Basic Storage Obj ectNV DataFigure 2: Logical Structure of Different Block Types10 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.12Acronyms and abbreviationsAcronyms and abbreviations, which have a local scope and therefore are notcontained in the AUTOSAR glossary, must appear in a local glossary.Abbreviation/ Acronym:Description:A “Basic Storage Object” is the smallest entity of a“NVRAM block”. Several “Basic Storage Objects” can beused to build a NVRAM Block. A “Basic Storage Object“can reside in different memory locations (RAM/ROM/NVmemory).NVRAM BlockThe “NVRAM Block” is the entire structure, which isneeded to administrate and to store a block of NV data.NV dataThe data to be stored in Non-Volatile memory.Block Management Type Type of the NVRAM Block. It depends on the(configurable) individual composition of a NVRAM Block inchunks of different mandatory/optional Basic StorageObjects and the subsequent handling of this NVRAM block.RAM BlockThe „RAM Block“ is a „Basic Storage Object“. It representsthe part of a „NVRAM Block“ which resides in the RAM.See [SWS NvM 00126]ROM BlockThe „ROM Block“ is a „Basic Storage Object“. It representsthe part of a „NVRAM Block“ which resides in the ROM.The „ROM Block“ is an optional part of a „NVRAMBlock“.[SWS NvM 00020]NV BlockThe „NV Block“ is a „Basic Storage Object“. It representsthe part of a „NVRAM Block“ which resides in the NVmemory. The „NV Block“ is a mandatory part of a „NVRAMBlock“. [SWS NvM 00125]NV Block HeaderAdditional information included in the NV Block if themechanism “Static Block ID” is enabled.Administrative BlockThe “Administrative Block” is a “Basic Storage Object”. Itresides in RAM. The “Administrative Block” is a mandatorypart of a “NVRAM Block”. [SWS NvM 00135]DETDefault Error Tracer – module to which development errorsare reported.DEMDiagnostic Event Manager – module to which productionrelevant errors are reportedNVNon volatileFEEFlash EEPROM EmulationEAEEPROM AbstractionFCFSFirst come first servedBasic Storage Object11 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.13Related documentation3.1 Input documents[1] List of Basic Software ModulesAUTOSAR TR BSWModuleList.pdf[2] Layered Software ArchitectureAUTOSAR EXP LayeredSoftwareArchitecture.pdf[3] General Requirements on Basic Software ModulesAUTOSAR SRS BSWGeneral.pdf[4] Requirements on Memory ServicesAUTOSAR SRS MemoryServices.pdf[5] Specification of EEPROM AbstractionAUTOSAR SWS EEPROMAbstraction[6] Specification of Flash EEPROM EmulationAUTOSAR SWS FlashEEPROMEmulation[7] Specification of Memory Abstraction InterfaceAUTOSAR SWS MemoryAbstractionInterface[8] Specification of Memory MappingAUTOSAR SWS MemoryMapping[9] Virtual Functional BusAUTOSAR EXP VFB.pdf[10] Software Component TemplateAUTOSAR TPS SoftwareComponentTemplate[11] Specification of RTE SoftwareAUTOSAR SWS RTE.pdf[12] Specification of ECU ConfigurationAUTOSAR TPS ECUConfiguration.pdf[13] Basic Software Module Description TemplateAUTOSAR TPS BSWModuleDescriptionTemplate[14] Specification of CRC RoutinesAUTOSAR SWS CRCLibrary[15] General Specification of Basic Software ModulesAUTOSAR SWS BSWGeneral.pdf12 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.13.2 Related specificationAUTOSAR provides a General Specification on Basic Software modules [15] (SWSBSW General), which is also valid for NVRAM Manager.Thus, the specification SWS BSW General shall be considered as additional andrequired specification for NVRAM Manager.13 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.14Constraints and assumptions4.1 LimitationsLimitations are given mainly by the finite number of “Block Management Types” andtheir individual treatment of NV data. These limits can be reduced by an enhanceduser defined management information, which can be stored as a structured part ofthe real NV data. In this case the user defined management information has to beinterpreted and handled by the application at least.4.2 Applicability to car domainsNo restrictions.4.3 ConflictsNone14 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.15Dependencies to other modulesThis section describes the relations to other modules within the basic software.5.1 File structure5.1.1 Header file structureFigure 3: NvM Include structureThe include file structure shall be as follows:15 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1[SWS NvM 00077] ⌈ An API interface NvM.h that provides the function prototypesto access the underlying NVRAM functions. ⌋ ( )[SWS NvM 00550] ⌈A type header NvM Types.h that provides the types for theNvM module. ⌋ ( )[SWS NvM 00755] ⌈The file NvM Types.h shall include Rte NvM Type.h toinclude the types which are common used by BSW Modules and SoftwareComponents. NvM Types.h and NvM.h shall only contain types, that are not alreadydefined in Rte NvM Type.h. ⌋ (SRS BSW 00447)[SWS NvM 00551] ⌈A callback interface NvM Cbk.h that provides the callbackfunction prototypes to be used by the lower layers ⌋ ( )[SWS NvM 00552] ⌈A type header NvM Cfg.h that provides the configurationparameters for the NvM module. ⌋ ( )[SWS NvM 00689] ⌈NvM Cfg.h shall include NvM Types.h. ⌋ ( )[SWS NvM 00690] ⌈NvM Types.h shall include Std Types.h. ⌋ ( )[SWS NvM 00553] ⌈NvM.h shall include NvM Cfg.h. ⌋ ( )[SWS NvM 00554] ⌈NvM module shall include NvM.h, Dem.h, MemIf.h,SchM NvM.h, NvM MemMap.h. ⌋ ( )[SWS NvM 00555] ⌈NvM module shall include Crc.h. ⌋ ( )[SWS NvM 00556] ⌈NvM module shall include Det.h. ⌋ ( )[SWS NvM 00691] ⌈Only NvM.h shall be included by the upper layer. ⌋ ( )5.2 Memory abstraction modulesThe memory abstraction modules abstract the NvM module from the subordinateddrivers which are hardware dependent. The memory abstraction modules provide aruntime translation of each block access initiated by the NvM module to select thecorresponding driver functions which are unique for all configured EEPROM orFLASH storage devices. The memory abstraction module is chosen via the NVRAMblock device ID which is configured for each NVRAM block.16 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.15.3 CRC moduleThe NvM module uses CRC generation routines (8/16/32 bit) to check and togenerate CRC for NVRAM blocks as a configurable option. The CRC routines haveto be provided externally [ref. to ch. 8.1.4.2].5.4 Capability of the underlying driversA set of underlying driver functions has to be provided for every configured NVRAMdevice as, for example, internal or external EEPROM or FLASH devices. The uniquedriver functions inside each set of driver functions are selected during runtime via amemory hardware abstraction module (see chapter 5.2). A set of driver functions hasto include all the needed functions to write to, to read from or to maintain (e.g. erase)a configured NVRAM device.17 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.16Requirements traceabilityRequirementDescriptionSatisfied bySRS BSW 00005 Modules of the µC AbstractionLayer (MCAL) may not havehard coded horizontal interfacesSWS NvM 00744SRS BSW 00006 The source code of softwaremodules above the µCAbstraction Layer (MCAL) shallnot be processor and compilerdependent.SWS NvM 00744SRS BSW 00007 All Basic SW Modules written inC language shall conform to theMISRA C 2012 Standard.SWS NvM 00744SRS BSW 00009 All Basic SW Modules shall bedocumented according to acommon standard.SWS NvM 00744SRS BSW 00010 The memory consumption of allBasic SW Modules shall bedocumented for a definedconfiguration for all supportedplatforms.SWS NvM 00744SRS BSW 00101 The Basic Software Module shall SWS NvM 00399, SWS NvM 00400be able to initialize variables andhardware in a separateinitialization functionSRS BSW 00160 Configuration files of AUTOSARBasic SW module shall bereadable for human beingsSWS NvM 00744SRS BSW 00161 The AUTOSAR Basic Softwareshall provide a microcontrollerabstraction layer which providesa standardized interface tohigher software layersSWS NvM 00744SRS BSW 00162 The AUTOSAR Basic Softwareshall provide a hardwareabstraction layerSWS NvM 00744SRS BSW 00164 The Implementation of interrupt SWS NvM 00744service routines shall be done bythe Operating System, complexdrivers or modulesSRS BSW 00167 All AUTOSAR Basic SoftwareModules shall provideconfiguration rules andconstraints to enable plausibilitychecksSWS NvM 00028SRS BSW 00168 SW components shall be testedby a function defined in acommon API in the Basis-SWSWS NvM 00744SRS BSW 00170 The AUTOSAR SW Components SWS NvM 00744shall provide information about18 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1their dependency from faults,signal qualities, driver demandsSRS BSW 00171 Optional functionality of a BasicSW component that is notrequired in the ECU shall beconfigurable at pre-compile-timeSWS NvM 00028SRS BSW 00172 The scheduling strategy that isSWS NvM 00464built inside the Basic SoftwareModules shall be compatible withthe strategy used in the systemSRS BSW 00302 All AUTOSAR Basic SoftwareModules shall only exportinformation needed by othermodulesSWS NvM 00744SRS BSW 00304 All AUTOSAR Basic SoftwareModules shall use the followingdata types instead of native Cdata typesSWS NvM 00744SRS BSW 00306 AUTOSAR Basic SoftwareModules shall be compiler andplatform independentSWS NvM 00744SRS BSW 00307 Global variables namingconventionSWS NvM 00744SRS BSW 00308 AUTOSAR Basic SoftwareModules shall not define globaldata in their header files, but inthe C fileSWS NvM 00744SRS BSW 00309 All AUTOSAR Basic SoftwareModules shall indicate all globaldata with read-only purposes byexplicitly assigning the constkeywordSWS NvM 00744SRS BSW 00312 Shared code shall be reentrantSWS NvM 00744SRS BSW 00314 All internal driver modules shallSWS NvM 00744separate the interrupt framedefinition from the service routineSRS BSW 00321 The version numbers ofAUTOSAR Basic SoftwareModules shall be enumeratedaccording specific rulesSWS NvM 00744SRS BSW 00323 All AUTOSAR Basic SoftwareSWS NvM 00027Modules shall check passed APIparameters for validitySRS BSW 00325 The runtime of interrupt serviceroutines and functions that arerunning in interrupt context shallbe kept shortSWS NvM 00744SRS BSW 00327 Error values naming conventionSWS NvM 00023, SWS NvM 00027SRS BSW 00328 All AUTOSAR Basic SoftwareModules shall avoid theduplication of codeSWS NvM 0074419 of 190Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1SRS BSW 00330 It shall be allowed to use macros SWS NvM 00744instead of functions wheresource code is used and runtimeis criticalSRS BSW 00331 All Basic Software Modules shall SWS NvM 00023, SWS NvM 00027strictly separate error and statusinformationSRS BSW 00333 For each callback function it shall SWS NvM 00467, SWS NvM 00468,be specified if it is called fromSWS NvM 00469interrupt context or notSRS BSW 00334 All Basic Software Modules shall SWS NvM 00744provide an XML file that containsthe meta dataSRS BSW 00335 Status values naming convention SWS NvM 00744SRS BSW 00336 Basic SW module shall be ableto shutdownSWS NvM 00744SRS BSW 00337 Classification of developmenterrorsSWS NvM 00023SRS BSW 00341 Module documentation shallcontains all needed informationsSWS NvM 00744SRS BSW 00342 It shall be possible to create anAUTOSAR ECU out of modulesprovided as source code andmodules provided as objectcode, even mixedSWS NvM 00744SRS BSW 00343 The unit of time for specificationand configuration of Basic SWmodules shall be preferably inphysical time unitSWS NvM 00744SRS BSW 00344 BSW Modules shall support link- SWS NvM 00744time configurationSRS BSW 00347 A Naming seperation of differentinstances of BSW drivers shallbe in placeSWS NvM 00744SRS BSW 00348 All AUTOSAR standard typesSWS NvM 00744and constants shall be placedand organized in a standard typeheader fileSRS BSW 00353 All integer type definitions ofSWS NvM 00744target and compiler specificscope shall be placed andorganized in a single type headerSRS BSW 00360 AUTOSAR Basic SoftwareModules callback functions areallowed to have parametersSWS NvM 00467, SWS NvM 00468,SWS NvM 00469SRS BSW 00361 All mappings of not standardized SWS NvM 00744keywords of compiler specificscope shall be placed andorganized in a compiler specifictype and keyword headerSRS BSW 00371 The passing of function pointers20 of 190SWS NvM 00744Document ID 033: AUTOSAR SWS NVRAMManager- AUTOSAR confidential -
Specification of NVRAM ManagerAUTOSAR CP Release 4.3.1as API parameter is forbidden forall AUTOSAR Basic SoftwareModulesSRS BSW 00373 The main processing function of SWS NvM 00464each AUTOSAR Basic SoftwareModule shall be namedaccording the defined conventionSRS BSW 00375 Basic Software Modules shallreport wake-up reasonsSWS NvM 00744SRS BSW 00378 AUTOSAR shall provide aboolean typeSWS NvM 00744SRS BSW 00381 The pre-compile time parameters SWS NvM 00028shall be placed into a separateconfiguration header fileSRS BSW 00383 The Basic Software ModuleSWS NvM 00465, SWS NvM 00466specifications shall specify whichother configuration files fromother modules they use at leastin the descriptionSRS BSW 00384 The Basic Software Modulespecifications shall specify atleast in the description whichother modules they requireSWS NvM 00465, SWS NvM 00466SRS BSW 00385 List possible error notificationsSWS NvM 00023, SWS NvM 00027SRS BSW 00386 The BSW shall specify theconfiguration for detecting anerrorSWS NvM 00023, SWS NvM 00027SRS BSW 00388 Containers shall be used togroup configuration parametersthat are defined for the sameobjectSWS NvM 00028SRS BSW 00389 Containers shall have namesSWS NvM 00028SRS BSW 00390 Parameter content shall beunique within the mo
Specification of NVRAM Manager AUTOSAR CP Release 4.3.1 9 of 190 Document ID 033: AUTOSAR_SWS_NVRAMManager - AUTOSAR confidential - 1 Introduction and functional overview This specification describes the functionality, API and the configuration of the AUTOSAR Ba
AUTOSAR 3.x AUTOSAR 4.x AUTOSAR 3.x is used in serial production projects by: Audi / Volkswagen / Porsche Daimler Fiat / Chrysler Volvo Trucks (incl. Construction Machines) AUTOSAR 4.x is used in serial production projects by: BMW GM Toyota Volvo Cars AUTOSAR 4.x is generally announced by Ford PSA
Simon Fürst, BMW Group Safetronic 2011 8 Nov. 2011, Sheraton Arabellapark Hotel, Munich. 2 8 Nov. 2011 AUTOSAR and Functional Safety . Basic aspects of AUTOSAR architecture and methodology Safety mechanisms supported by AUTOSAR Technical safety concepts supported by AUTOSAR Relationship to ISO 26262 and Conclusion
AUTOSAR User Group, i.e. the Artop User Group . –It is a group of AUTOSAR members and partners, i.e. users of AUTOSAR, with a special interest in AUTOSAR tools. –Was launched in October 2008 and the members currently are: –Continental –Geensys –Peugeot Citroën (PSA)–BMW Car IT –New members are welcome to join the User Group.
Both, Releases 2.0 and 2.1, are in use by several AUTOSAR members for series produc-tions. 2.2. Overview on AUTOSAR Phase II Three releases had been planned for AUTOSAR Phase II, providing a continuous improve-ment of the specifications and introducing new concepts. Release 3.0 was published early 2008 on the AUTOSAR web site [1]. It included a .
2 Introduction to AUTOSAR Simulink approach to AUTOSAR Overview of Modeling SWCs & Modeling Styles AUTOSAR Design Workflows Bottom Up, Top Down & Round Trip Advanced Topics –Top 5 Startup, Reset, and Shutdown Modeling Basic Software (BSW) Access J-MAAB Type B Architectu
Adaptive Environment - The AUTOSAR Adaptive environment for adaptive design AUTOSAR Builder is based on Eclipse and uses Artop. Artop is an open AUTOSAR tool environment that is available for free. It enables you to build your own tools and integrate from other tool vendors. For more details, see the AUTOSAR Builder Overview document. 1.
AUTOSAR 3.x: First specification: 2007 Mature solution used for series production 2010ff Adaptations necessary OEM-specific extensions AUTOSAR 4.x: First specification: 2009 First mature specification: 2012 (4.0.3) 4.0.3 is the right version for development start in 2012 New functions: safety, Ethernet/IP, multicore, AUTOSAR Status
Introduction to AutoCAD Academic Resource Center . What is CAD? Computer Aided Drafting Autodesk is the most popular drawing program Many student versions available for free online at students.autodesk.com o AutoCAD o Architecture o Mechanical o Revit o Inventor o Civil o MEP o etc. Capabilities: o 2D line drawings o 3D constructions o Rendering o Part Assemblies . Workshop Goals .
