Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
o -Architecture
o -Methodology
o -Application Interface
KPIT solutions
o -R3.x and R4.0
o -KPIT Solution is evaluated by OEMs/Tier1s consortium
MCAL:
lowest layer of the basic software
hardware dependent layer
works with internal drivers .
acts as a bridge between hardware and upper layers
. inputs needed for MCAL Software Specifications and datasheet of
microcontroller
VECTOR E_LEARNINg
o Requirements
->supporting driver assistance systems in critical driving manoeuver
->improving fuel economy
->conforming to environmental standards
global development partnership of automotive OEMs,
automotive suppliers and other companies in the software,
semiconductor and electronics industries
advantages of AUTOSAR:
o ->Mastery over increasing product and process complexity
o ->Ability to optimize the ECU network by flexible integration, relocation
and exchange of functions
o ->Maintainability over entire product life cycles
Disadvantages:
o ->AUTOSAR does not offer any capability of describing the functional
behavior of a software component
-Port Module
o ->Handles and intializes pins across the whole MCU
-Inter-module dependencies
-Intialization order
MCU initialization
Watchdog initialization
port initialization
Individual module initialization-ADC,PWM,ICU,DIO
MCU Drivers
-IoHwAb
-RTE Elements
Variable Data Prototype (VDP)-used to configure what type of data we want to
exchange
Mode declaration group-used to configure diff. states in which you want to
implement
Client Server Operation-Argument Data Prototype-definition of diff arguments
CalPrm Element-Defintion of calibration element
Connectors:
-Assembly(P2R)-If two components present in the same composition want to
connect with each other, they can use assembly connector
-Delegation(P2P or R2R)-If two components of diff. compositions want to connect
with each other, delgation connector is used to delegate the ports, we further use
assembly to connect the delegated ports
Internal structure:
o -Runnable Entity->Schedulable
-Basic interaction between application and RTE takes place
through runnable entity
o -RTE Events-> Used to access a runnable entity
o -Exclsive Areas-> critical sections of the code
Intra ECU Comm.
-communication between two components/modules of the same ECU
-realised through RTE
SENDER-REEIVER COMM:
-multiple senders or multiple receivers
-Implicit & Explicit comm.
-unqueued and queued comm
-all datatypes are supported
-feature of providing initial value
-alive time mode feature-if the comm is unable to transmit data in a given time
then it will notify the RTE
CLIENT-SERVER COMM:
-Basic elements:
o ->client-server operation-configuration of arguements
->datatype specification
->direction specification
o ->inout dir.->exchange of data between client and
server
o ->in dir.->client is giving data to server
o ->out dir.->server giving data to client
o ->return values-server returns some standard value
-synchronous comm:
o -also called blocking comm.
o -RTE called doesn't return untill there is a response from the server
-asynchronous comm
o -server request is sent after completing the RTE call
-RTE Result
o ->application tries to get a response from the RTE
Comm between two functions within the software comm:
o InterRunnableVariables are used for this purpose:
explicit
implicit
OSEK OS Specifications:
European automotive consortium responsible for open standards for the
automotive industry
-Reason
o ->increasing quantity and complexity of software content
o ->lack of qualified software engineers
o ->desire for high quality products
-reusable code
-3 standars-
o ->OS standard
o ->comm module
o ->OSEK NM standard
OSEK is statically configured OS-no room for changing the configurations when
the code is running on the MCU
Protection features
-timing protection-ensures that a task is releasing a particular resource within the
specified time
o Advantages
-resets your MCU
-predictive behaviour of OS incase f hardware
Event:
wait event:making a particular task to wait
MODULE INTERACTION
-Protocol Data Unit-Information flowing through the stack
COM-communication manager
-controls start and stop of I-PDU groups
-Monitors and controls the the PDU groups
CAnIf(Interface Module)
provides an interface to manage diff. CAN hardware devices
CANSM(State Manager)
-responsible for the control flow abstraction of CAN networks
CANNm
-coordinates transition between normal mode and bus-sleep mode
BswM-mode arbitration,mode control