188, 1118 AM AUTOSAR BSW | AUTOSAR Basie Sotware | Low Level Modules AUTOSAR Basie Software (BSW) Tutorial ‘ame aur Langage Inti arc we wl ne the AUTOSAR ASW (Basle Software) ayer (the layer below RTE} tis one of the Important layers which helps aplication layer to use, communicate with ferent peripherals of MCU. Ifyou ae new toAUTOSAR then | recommend you to check ou inkoductory acs. The BSW configuration which we do Configurator software tke Vact- DaVinci Confauatar's actualy configuration of this layer which below RTE layer. We have already seen the AUTOSAR layered architecture in bre, oday we wl se tin deta. Buy From the Ind tect your business with th what matters mest PN COBEN ed iby r Microcontroll Fig: AUTOSAR detailed layered architecture ado ‘Above figure shows detaled AUTOSAR Layered architecture. Lets summarize it htps:/autosarutorials.convautosar-basio-softwars-bsw! ws188, 1118 AM AUTOSAR BSW | AUTOSAR Basie Software | Low Level Modules ‘+The mild black layer is the microcntroeron which the AUTOSAR woul work ‘+The blocks in ed color les under MCAL (Microcontroller Abstraction Layer which has rivers for accessing peripherals. MCALIsthe lowest layer of BSW this layers highly MCU dependent which ‘means, his block inthis ayer wll change on change inthe MCU, ‘+The layers in Green color (except CDD) lies under ECU Abstraction Layet. Abstraction inthis case means to ide lower level deals ofthe module and just expose APs to upper layers for implementing ‘unctionalty. This layer abstracts te MCAL layer rom upper layer and provides APs for accessing ‘extemal as well as ineral divers. ECU abstraction layer is useful for making upper ayers ECU ‘nantwace independant ‘+ ext layer is the CDD (Complex Device Drivers) which connects SWC ftom application tyer rectly with the MCU via RTE Itis use or wetingfunctonsidvers of pergheralsfextemal deves not defined In AUTOSAR or functions which requires very high timing constraints beyond OS timer minimum tick resolution, But his layers highly hardware dependent and hence theres very less scope of reuse abilty or portability, ‘+ The next layer isthe Senices Layer (al blocks in blue) which is he top most layer ofthe BSW, This layer provides base services fr aplication, RTE, BSW modules. Serves lke: Operating system functionality, ‘Conmunicaon senices, Memory Services (fr NVRAM), ECU slate management, ec ‘We wil se each block ofeach layer in etal my future atts, Internal and External Drivers in AUTOSAR: IMAUTOSAR contest, there are to types of river based on peripheral used they are Internal anc external crivers. Internal divers are used to access internal peripherals located in mirocontlle ‘ecgherals Ike Internal EEPROM, ADC eo, External devers are used to accass extemal peripheral lacatoc ‘outside the mircontrle ke extemal Flash, EEPROM, Watchdog, et. The inleral diver les n MCAL layer \ereas the extemal diver les inthe ECU abstraction layer. Thee are exceptions for some external devices lke memory mapped memories, which can be accessed by microcontroller directly and hence divers fr such vies les in MCAL, Concept of Interfaces, Handlers and Manager /AUTOSAR also implements the concep of Interfaces, Handlers and Managers. Pease dont confuse his with ‘ort nterfaces @ |The interfaces les in the ECU abstraction ‘ayer whereas the managers ls inthe Services layer The interfaces provides a funclonalty to abstract the lower lovel modules and exposes a generic APL ‘cess which canbe used by upper layers. Interfaces provides access to specif lype of device respective of ‘number of devices existing of same type and independent of hardware. The handlers contol the concurent ‘multiple and asynchronous access of one or multiple cents, handrs also performs bufering.queung et-The handler functionality soften implemented in the ctver or interface, Amanager ofers specie services to multiple ‘lens. tis required in al cases where only handle isnot suficient For example NVRAM manager controls the cesses to intmallexternal Flash memory, Lets start learning about layers in deta 1, MCAL (Microcontrofler Abstraction Layer): ‘This layer consists of following moduleblocks ‘+ Microcontroller Drivers: This module has internal cvrs for accessing the intemal peripherals ofthe \VCU lke Watchdog, General purpose times, or have functions for direct access to MCU tke Cores. {+ Memory Drivers: This module has drivers for accessing on chip memories ike intemal Flash, interna EEPROM, or memory mapped devices Ike external fash “+ Crypto Drivers: This module has devers for on chip Crypto devices Ike SHE, HSM. htps:/autosarutorials.convautosar-basio-softwars-bsw! 26188, 1118 AM AUTOSAR BSW | AUTOSAR Basie Software | Low Level Modules ‘+ Wroless Communication Drivers: This module has drivers for wireless network systems (in-vehicle or (of beard communication), ‘+ Communication Drivers: This module has drivers fr on board communication tke SP, 126 etc anc ‘also has the crivers for Vehicle communication tke CAN, Elaxay. ‘+ VO Drivers: This module has divers for accessing and using the UO pins of MCU including cgtal anc ‘Analog, PM. 2. Complex Device Drivers Or CDD: ‘This module useful in implementing nonstandard funconaliy within BSW stack. There can be many cases ‘nen we need to implement some functonalty which isnot supported by AUTOSAR, so CDD is used for such cases. Ori functonalty requires strict ing constraints which may be lesser than the minimum ting of /AUTOSAR OS resolution then Complex Device Drivers module is useful, ast recy helps connecting the MCL. wth the application {ut complex rivers functionality is highly MCU and application dependent andthe code may not be easy o pot. 3.ECU Abstraction Layer: ECU abstraction layer helps in achieving ECU hardware independence (hardware Independence not only of [MCU chip but ferent extemal peripherals of ECU board also) Lets look atthe blocks inthis ayer: + VO Hardware Abstraction: In eal Ife ECUs, the UO peripherals can be on chip or on board and the ECU hardware layout tke MCU pin connectons or pin inversions may be complex. In conventional software wing, we would have to consider such ow evel detals aso, but inAUTOSAR its no. This module ‘abstracts such low level deta rom Application and only provides APIs for using the Us. This is MCU independentbecauseitjust pons to lower evel crivers) but is ECU hardware dependent because it uses «extemal divers for on-board peripherals, which if changed then UO hardware abstraction frit wil also change. “+ Communication Hardware Abstraction This module abstracts the locaton of communication controls and the ECU hardware layout The application don't know about which communication controle case of CAN) is used or wich pins used or even which type of communication buss used ‘ether itis CAN, FlexRay or other it just “understands the data which willbe transmited and received ‘respective of communication cenrllas selected ison chip aan board, This made is used ot _actieving suc eve of nareware independence. It gves APs which willbe called by respective modules and perform data transmission or reception, ‘+ Crypto Hardware Abstraction: Ths module abstracts th crypto functionally by hiding the information of the Crypto used (intemal, extemal device or sofware based). Again upper layers are unknown ofthe ‘ype of Crypto used or even which Crypto is used Ike whether its on-chip or onboard or coed ir software, Ths module provides mechanism for accessing the Crypto device. “+ Memory Hardware Abstraction: This module aso abstracts the location ofthe memory device use. “The memory can be on-chip or on-board andthe on-board memory may have diferent ECU hardware layoutike the memory chip difernces) but all this information is abstracted from application 2s only ‘noms about data and has no control aver the typeof memory device tobe selected + Onboard Device Abstraction: Tis module provides abstraction ftom ECU specific on board devices, ‘This madule contains divers for on board devices which cannot be called as sensors or actuators ot timers tke intemal or external watchdog timers “Tithere aid you had a WOW moment? ino, then please read again all he things above @ . hada WOW ‘moment when | rst understood tis, because it's so ntetigety designed andthe level ot haroware Independence ECU abstacton layer ofrs is amazing 4. Services: htps:/autosarutorials.convautosar-basio-softwars-bsw!188, 1118 AM AUTOSAR BSW | AUTOSAR Basie Software | Low Level Modules ‘+ Communication Services: This is a group of modules for vehicle network communication which aims at oreviing uniform seroes for network management, peovising unifocm interface to vehicle network for communication and lagrostie communication, also te hide potecol and message properties from te ‘application. Communication Services interfaces wih the communication crivers(n MCL) with the hep of (Communication Hardware Abstraction (as discussed above). This is MCU and ECU hardware independent but dependent on bus ype. So, some part ofthese services may change f the bus type (CAN, FlexRay etc) changed. For more information on communication sences you can check out this a Off board Communication Services: This is 2 group of modules for vehicle to outer lets ‘communication ia an adhoc wireless network. thas twee Becks used fr implementing diferent {unconalties. This module provides a uniform intrtace for Wireless Ethernet twork by hing protoco and message properties. ‘+ Memory Services: This service consists of one module the NVRAM manage Is responsible or the ‘management of non volatile data (adr Kom diferent memary divers), General, application requires string data in memery fr future use, so this module Is used to implement his in a uiform way ‘and prouide abstraction from memory locations and lowe level properties. Memory Services provides ‘mechanism for nonvolatile data management saving, loading, checksum, et. Tiss MCU and ECU hardware independent and is highly configurable ‘System Services: This i @ group of madules which canbe used by modules of al layers. Examples are eal Tme Operating System, Eror messenger. These services can be some MCU dependent or may support special MCU capable (Ike Tme Sence), partly ECU Hardware and application dependent inthis way the moderately detailed ciscussion on BSW ends, | hope | explained itn easy language. Danit worry # you dont understand some terms you wil understand it soon by eading future aries @ Ifyou nave any doubts please comment it below, Like Us On Facebook! or Potow age Subscribe For Newsletters! your good email adress.) Buy From the Industry Leader Protect your busiress with the cybersecurity leeder so you cen fo what matters most CrowaStrike® Learn htps:/autosarutorials.convautosar-basio-softwars-bsw! 46