AUTOSAR METHODOLOGY @BMW.

Bernd Jäger, 28th September 20169th AUTOSAR Open Conference, GothenburgAUTOSAR METHODOLOGY @BMW.

OVERVIEW.AUTOSAR Methodology at BMW1AUTOSAR Versions and Roadmap2Configuration Process until Generation 20153Vision Generation 2021 and Current Status Generation 20184Tool Architecture5Tool Development6ECU Configuration Flow7AUTOSAR Tool Requirements for the FuturePage 2

PLATFORM SOFTWARE ROADMAP GENERATIONS 2008 UNTIL 2021.VERSION OVERVIEW.Delivery as exampleAdaptive AUTOSAR 1.0Delivery as series production codeAUTOSAR 4.2AUTOSAR 4.0AUTOSAR 2.1/3.0Introduction ofAIDA-SymphonyAUTOSAR 1.0/2.0BAC4 Rel. 3Generation 2021 AUTOSAR 4.2 BAC4 Rel. 2Generation 2018BAC4 Rel. 1Generation 2015BAC2/3Generation 2011In use until 2035SC6Generation 2008X5In use until 2032MCVIn use until 2029In use until 2022AUTOSAR Methodology at BMWIn use until 20257erOne platform SW architecture forall electronic control units.Page 3

AIDA SYMPHONY ROADMAP.ECU CONFIGURATION PROCESS GENERATION 2015.Artext, AUTOSAR BuilderXyz.arxmlSWCDBNEXyz.arxmlSystem Template3-8 weeksneededCurrent Status: Different Tools generate AUTOSAR configuration files. The ECU Integrator has to merge andadd missing parameters.Generation orCAFEditorAUTOSAR System toolconfigurator, generatorAUTOSAR Methodology at BMWIterationcyclesby iences 3-8 Weeks per export needed, until mappingcorrect and tested (empirical determined). Risk of remaining consistency errors high Late changes in on board network are notfeasible due to manual D2SMapping Diagnostic Configuration errors found2 weeks after first integrationSeite 4

AIDA SYMPHONY ROADMAP.EXAMPLE SYSTEM FUNCTION PARAMETERS.BMW System Function Software-Components (SW-C)Sample Application SW-Cs (optional)BMWBUtilBMWSysTimeBMWDarhBMWCodingBMWPia PnSBMWCplBMWEdchBMWCodingSampleBMWWurSampleAUTOSAR Runtime Environment (RTE)Memory ServicesCommunication ServicesE2ELibI/O Hardware WEthDiagMMXxx TpBMW CanTSynBEthTSynBswMWdgMDltComMFiMIPduMBMW FrTSynBAUTOSAR OSDemNvMSoAdTCP/IPOnboard DeviceAbstractionMemory HW AbstractionComplexDriversNmlfSystem ServicesXCPCrcLibBMWPia ClientSampleNmLibrariesI/O Signal InterfaceDriverfor ext.ADCASICDriverfor ext.I/OASICBMWPnSCommunication HW AbstractionMemIfXxx 6PnDm34Additional7045DioPortAdcIcuPwmFrEthI/O DriversCanFlsDiagnoseExt.DrvCommunication DriversEepFlsTstRamTstCoreTstMemory DriversMCUWdgGptMCU DriversTrcv.LinEaSpiEcuMWdgIfSys. Function Components with the number of configuration parameters:Microcontroller10232 system function components with 1200 parameters can lead up to 30000 configurations per ECU.Example DSC: 320 Parameter (static configuration)480 Parameter (dynamic configuration)can lead tocan lead toapprox. 400approx. 29.400different configurations.different configurations. Manual work at supplier site led to a lot of different errors.AUTOSAR Methodology at BMWSeite 5

AIDA SYMPHONY ROADMAP.VISION 2021.Vision for 2021BMW provides the BMW System Software (BMWspecific parts of the BAC architecture) and forintegration ECUs domain specific customer functionSoftware Components. In addition BMW delivers anECU-specific configuration, which is based on allinformation BMW knows, and will partially fill the finalconfiguration of the ECU. The partial configuration willbe verified , continuously exported and support bestthe continuous integration approach.AUTOSAR Methodology at BMWGoal 2015 for Symphony in Generation 2018BMW provides for diagnostic at least 60% of theconfiguration parameters and forthe remaining system functions 20% in an AUTOSARtool readable xml file.The communication stack will be configured up to 70%.Integration ECUs will getthe Software Component Descriptions for theapplication components deliveredby BMW and partly the configuration of the RTE.Seite 6

AIDA SYMPHONY ROADMAP.WHICH FILE CONFIGURES WHICH MODULE IN AUTOSAR 4.2.2BMW System Function Software-Components (SW-C)Sample Application SW-Cs (optional)BMWBUtilBMWSysTimeBMWDarhBMWCodingBMWPia cation ServicesI/O Hardware AbstractionComXxx TpEthTSynMemory HW swMFiMOnboard Device AbstractionNvMSDBMW CanTSynAUTOSAR OSDemStbMIpduME2ELibDebugDcmXxxSMMemory ServicesSoAdTCP/IPComplexDriversNmfSystem ServicesDriverfor ext.ADCASICDriverfor ext.I/OASICBMWPnSXxx InterfaceWdgIfTrcv.PortDioAdcPwmEthFrCanI/O DriversLinSpiCommunication eMemory DriversMCUWdgMCU DriversGptEcuMEaConfigured withService NeedsI/O Signal InterfaceCommunication HW AbstractionMemIfConfigured by ECUSystem DescriptionConfigured by ECUConfiguration (ECUC)AUTOSAR Runtime Environment (RTE)BMW FrTSynCrcLibBMWPia ClientSampleNmLibrariesMicrocontrollerAUTOSAR StandardBMW SpecificAUTOSAR Methodology at BMWConfigured in SP2018Seite 7

AIDA SYMPHONY ROADMAP.ECU CONFIGURATION PROCESS FOR GENERATION 2018Delivery of verifiedand consistentconfigurationsPrimaGeneration 2018BMW System Function Software-Components (SW-C)BMWSysTimeBMWDarhBMWCodingBMWPia PnSBMWCplMemory ServicesCommunication ServicesDebugSDDcmEthTSynBMW FrTSynBBMW CanTSynBIPduMBswMDltWdgMFiMComMDemAUTOSAR OSECUC.arxmlBMWWurSampleI/O Hardware AdTCP/IPMemory HW AbstractionOnboard DeviceAbstractionComplexDriversI/O Signal InterfaceDriverfor ext.ADCASICDriverfor ext.I/OASICBMWPnSCommunication HW AbstractionMemIfXxx InterfaceBMWSrvTrcv.DioPortAdcPwmIcuFrI/O DriversEthFlsExt.DrvCommunication DriversEepFlsTstCoreTstMemory DriversMCUWdgGptMCU gSampleAUTOSAR Runtime Environment (RTE)System ServicesE2ELibXxxSMCrcLibBMWPia ClientSampleBMWEdchNmlfZedisSample Application SW-Cs (optional)BMWBUtilNmLibrariesXCPfibexXxx TpBNEECUSystemDescriptionarxmlTarget generation 2018 for newly developed ECUsThe ECU Integrator receives two ECU specificconfiguration files from BMW.LinContinuousVerificationMicrocontrollerSystem functionrequirementsECUConfigurationPermanent enhancementof consistency checksBMWAUTOSAR Methodology at BMWECUIntegrator(Supplier)Goal with AIDA Symphony Daily export with consistency checked possible. Risk of remaining consistency errors low Late changes in on-board network are possible Diagnostic configuration 1st time rightSeite 8

AIDA SYMPHONY ROADMAP.TOOL ARCHITECTURE.Pluginintegratedin SymphonyProductProjectspecific Pluginwritten by ProjectSys Func OwnerEcu PLPRIMAADDBNEZEDISCAFEPRIMA ConnectornuDIB rPRIMA Import-WFSymAdmASCENTServer torValidation UIWorkflow UIBundle UISysParam UIARXMLSplitterARXMLExtractorSys Desc GenUser InterfaceSWCIFDTypeECU-C ort aramCodingImportValidation CoreCore SystemEclipseEMFXtextValidation UtilKOM ValidationBasic ValidationsExtended ValidationsModel AccessWorkspace CoreModel ConversionSym Core ConversionSym1.x CoreSymFibex CoreWorkflow CoreAR 4.2.x CoreBundle2.x CoreFibex 4.1.1 CoreProcessing ModelAR IntegrationSphinxARTOP 4.5Symphony ASCENT RepositoryAUTOSAR Methodology at BMWAutosar ExportIn-Place EnrichmentsValidatePlatformExtract DocWorkflowsIncQueryLoggingMylynTeamGitSVNSymphony Build ServerSeite 9

AIDA SYMPHONY WORKFLOW.ECLIPSE DEVELOPMENT ENVIRONMENT AND TOOLS.FibexImportxmlCoding is similar tofibex import.Development Symphony Eclipse DevelopmentInternalModelMagic DrawxmlexportEcoreModelInternal data modelAUTOSARExportEMF SphinxEclipseEnterprise Arch.ARModelAUTOSAR Methodology at BMWMWE 2generatejava tendXtextSphinxMylyn: Eclipse Feature to interconnectto tickets systems like JIRA.Junit: Test Framework for Java Units.IncQuery: Framework to decscribe complexqueries to EMF models.Log4J: Standard Logging Frameworkin Java Environment.ARTOP: Sphinx based framework to useAUTOSAR models.Xtend: Extension of JAVA programming languageespecially to develop model transformations.Xtext: Framework to develop applicationsbased on own text based languages.Sphinx: Extension of EMF (Eclipse ModelingFramework) to use models in own applications.MWE2: Framework to program Workflows.EcoreModelArtopSeite 10

AIDA SYMPHONY WORKFLOW.TOOL DEVELOPMENT WORKFLOW.developerdeveloper partialunit testsDevelopmentCodechangeTestspassedUnit Tests Integration testscomplete (Golden Reference)TestspassedJenkinsTestspassedcommitCheck outAutomatic Test ExecutionStatus o.k.CodereviewsGerrit(Commit(master)branch)Code reviewspassedSlave DevelopmentTrunkMergeGerrit(master)TestsfetchFinal TestingpassedMaster DevelopmentTrunkCode Checkins from otherdevelopersProductionAUTOSAR Methodology at BMWSeite 11

AIDA SYMPHONY WORKFLOW.EXAMPLE ECU CONFIGURATION honyECU SystemDescription.arxmlECU C.arxmlDatabaseGerrit ofAUTOSAR(master)ToolingASCENTECU SystemDescription.arxmlECU erritApplication(master)SWCDsADDSymphonySF-UI1. Fill Input data basesAUTOSAR Methodology at BMWAUTOSARRTEGeneratorRTE ttgeneratorMAKEBoleroEvalboardModule parameterDescription filesBACRef.2. Choose corresponding input versionsof Input data bases3. Generate export4. Check warnings or errors and changeinput database until valid exportpossibleBMW LibraryManualConfiguration(GUI)5. Import artefacts withyour AUTOSAR Tooling6. Complete configurationTooling from BMWTooling of supplier7. Start AUTOSARand BMW generatorsSeite 12

AIDA SYMPHONY WORKFLOW.HOW IS THE ECU CONFIGURATION AND SW BUILT MANAGED IN THE PROJECT?AIDA Symphony delivers ECU SystemDescription and ECUCs for an ECU Project2The integrator imports the partially filledECUCs provided by AIDA Symphony to theAUTOSAR Tool3Integrator completes the ECUC configuration4Integrator generates the BSW and BMWSystem Function modules (BAC4).5ECU System Description Files are imported tothe RTE Generator6RTE is generated7Software is compiled and sbAUTOSARECUC EditorECU SystemDescription45SupplierSWCDBMW SWCDand BSWMDRTE6RTE ProjectSource FilesxDescription on next page.AUTOSAR Tooling7ECUSoftware

AIDA SYMPHONY WORKFLOW.CHALLENGES FOR PROJECTS TO AUTOMATE WORKFLOWaAUTOSAR Tooling related issues:1. Removed ECUC values may not be removed in the AUTOSAR Tooling.2. Changed ECUC values may not be correctly updated in AUTOSAR Tooling.3. Some parameters are reset to default when the ECU System Description is imported.4. Top-level shall be processed correctly (SystemTemplate Chapter 10, the standard approach)bIntegrator related task (Can not be automated except by specific project rule sets):1. BMW provides a partially filled ECU configurationSometimes the integrator has to extend the provided configuration with the project/ HW specific content.Examples are: Runnable to OS Task mapping, diagnostic debouncing information, BSW main cycle times, etc.

AIDA SYMPHONY ROADMAP.FUTURE REQUIREMENTS ON AUTOSAR TOOLING AND SPECIFICATION.AUTOSAR Tooling AUTOSAR Tool Chain shall be run-able on Linux. Full tool functionality shall be controllable by command line. 1st and 2nd Tier Suppliers to support completely integrated tool flow to enable real continuous integration.AUTOSAR Specification Usage of Diagnostic Extract Template, released in AUTOSAR 4.2.2 would reduce the pre-configuration ofdiagnostic modules by 40% compared to today’s approach of BMW Upstream Mapping rules between the BSW Parameters and the M2 Parameters need to be completed in thenext Release of the AUTOSAR Standard.AUTOSAR Methodology at BMWPage 15

BACKUP.Seite 16

AUTOSAR Methodology at BMW Page 2. OVERVIEW. AUTOSAR Versions and Roadmap Configuration Process until Generation 2015 Vision Generation 2021 and Current Status Generation 2018 Tool Architecture Tool Development ECU Configuration Flow AUTOSAR Tool Requirements for the Future