AUTOSAR Intro Agenda > Why AUTOSAR > What is AUTOSAR > AUTOSAR Architecture > AUTOSAR Methodology | woeczenecougmmemsece - Why AUTOSAR » Rewritten from scratch > BSW Standrdsaton > Harare Abstacton > Rsabiy of tuncons » Standardization of exchange formats | noeczeneceuncmemssce ~ Today 98% of the car are controlled by ECU directly or indirectly. In order to mange this complexity, AUTOSAR was formed. -> SoftWare must often be rewritten from scratch when hardware is changed Once an ECU is developed, whenever hardware has to be replaced, the whole process of development of software will repeat again and again through the same process, right from Application Software to Basic Software. Airbag ECU: OEM has developed an application software for airbag, that application would have been tested & would become very robust in their system. When hardware changed, the whole application will be crashed & has to written the code from scratch & has to go for development & testing.The total cost of the ECU will also become high & higher. <> ASW Standardisation avcoczenecougnumaemsece -(© Thom SCrALCH @ Nas LO BU TOF UeveLOpMENL @ LesLung. ine LoLaL Cust UT Ue EWU will also become high & higher. => BSW Standardisation Application Software should work along with hardware. It usually a MicroController. It's important that Application Software should communicate effectively with hardware. That are drivers, CAN stack, which manages the memory, manages the 0S. Application Software doesn't come alone but it also comes along with basic software which Application Software is coupled with hardware. If everytime a new hardware is replaced, OEM is not only paying for Application Software but also paying for Basic Software Layer So,the OEM doesn't want to pay for Basic Software Layer, they just want to pay for Application Software -> Hardware Abstraction a eavoczenecougamcemsece - -> Hardware Abstraction Any application that is buit in the Legacy software development mechanism is tightly coupled with hardware.The whole objective of AUTOSAR is to decoupled the Application Software from the hardware. From an Application Software perspective, if we want to develop an Application Software, its not just important that, the developer has to be very strong in, how it has to be devloped & also having understanding on MicroController that coupled along with Application Software has to be developed.once AUTOSAR is introduced,as an Application Engineer no need to worry about MicroController. Because the Application, at no where related to the MicroController. This also provides wide opportunities for industries focusing exclusive on developeing an Application Software or Basic Software. => Reusability of functions When we replace anything in the hardware, it's difficult to write software from a Su.OCCzSMeECOG THOME STO ~2 Frse,.h0 \o"ve uevuupes @ aisu ravung UnUerscanuung oN PMCrOLONLFOLLer Undt CoUpLeU aLorig with Application Software has to be developed.once AUTOSAR is introduced,as an Application Engineer no need to worry about MicroController. Because the Application, at no where related to the MicroController. This also provides wide opportunities for industries focusing exclusive on developeing an Application Software or Basic Software. -> Reusability of functions WHEA|EUREBISESSAVEHLAB|in the hardware, it's difficult to write software from scratch. If you need to add a small function to the existing ECU,it"s not possble in the legacy system. -> Standardization of exchange formats Data exchage format.One application software developer uses meter per second & another aapplication software developer uses km per hour.So there is a difference in wie Su. OCCzSMECOGTHOOMESTO ~¢ Fese QueHWE PepLdce aly eran 41 Le Nerunare, Le > UATTECULE LO WrELe suTuNare THOM scratch, If you need to add a small function to the existing ECU, it's not possble in the legacy system. -> Standardization of exchange formats Data exchage format.One application software developer uses meter per second & another application software developer uses km per hour.So there is a difference in their unit and also in terms of how they map the memory & how they conmunicate between the hardware & how they communicate between the Application Layer & lot of challenges & discussions have to be taken care Every supplier will have to write the software in that particulatr exchange format. Application Software is decoupled from the Hardware through intermediate layer (AUTOSAR layer) Primarily has 3 layer eavoczenecougamemsece - What is AUTOSAR * AUTOSAR - AUTomotive Open Systems ARchitecture + Founded in 2003 + Middleware and system-level standard, jointly developed by automobile manufacturers, electronics and software suppliers and tool vendors. =" + More than 100 members as SS s evOCzaeheCoGT Oem ESTO ~: Tee..: I AUTOSAR Consortium °—_— _ = . x s eS aS sme 2 ST AS a SaaS ie | avoczeneccougamemsece -EST = ee j= | ANCTT a woceczenecognumemsece = woeczeneccougagmcemsece woeczeneccougnnemseceu 2 a o ° a = o ° o a a o = o e u = : = a soczauecouame sO | > tis MC or HW dependent ANCIT woeczenecougnnemseceECU Abstraction Layer ty by eavoezsenecougaoes Services layer te 0S. > Itprovdes COM stack depending CANFINL 5 is part of service > ECU mode mansgerer yp ECU and Sh Run Time Environment Layer (RTE) avoceczenccougamemsece -> The Application Layer contains the, SC, which realize the ‘pplication funcional of the Eu, > This isthe piece of software that the OEM i ready to pay > Sometimes the OEM build some of the. appli theriP » For Eg: Arbag ECU noczenecouutems eae oes " peer Seer) » Three tools required 1. AUTOSAR Authoring Tool (Artop.Davinci Developer) 2. SWC Implementation Too! (Manual Coding, Matiab) 3, BSW Configuration Tool (EBTresos, Davinci Configurator) eae oaAUTOSAR Authoring Tool > Aitop > AUTOSAR XML fle (arc fle) > Three arxnl fle wil be created in Atop 1. Software Component Description 2. ECU Resource Description 3. System Description SS | eavoczenecougamemsece - . Three Descriptions » Software Component Description Creating or structuring the .< les & functions related to Application. > ECU Resource Description All the details related to Hardware will be present (Ea: pins, adc, memory) » System Description Contains details of communication protocol that will be implemented. Summary > Providing the details of how many .c files & functions are required for project. > Logics will not be written in Artop. > Only the structure will be made here. Ss | evoczenecogntemsece-:t> Writing the logics for our application using manual coding. ANCIT woeczenecounmnemsece -s » EBTresos (ElektroBit) > Configuring the complete layer. ANCIT woczenecognocmssce - eae oaavoecsencecouccemsecea -