AUTOSAR - 2 Mark Questions with Answers and Examples
1. AUTOSAR
Q: What is AUTOSAR?
A: AUTOSAR (AUTomotive Open System ARchitecture) is a standardized automotive
software architecture that promotes software reuse and interoperability. It decouples
application software from hardware.
Example: A parking assist module can run on different ECUs without code changes if
AUTOSAR-compliant.
2. AUTOSAR Consortium
Q: What is the role of the AUTOSAR Consortium?
A: The AUTOSAR Consortium defines standards for software architecture and tools for
automotive ECUs. It consists of OEMs, suppliers, and tool providers.
Example: Members like BMW and Bosch collaborate to define common interfaces.
3. AUTOSAR Architecture
Q: What are the main layers in AUTOSAR architecture?
A: The layers include Application Layer, RTE, and Basic Software (BSW). They help separate
software components, communication, and hardware access.
Example: The COM module is part of the BSW layer.
4. Stack & Modules
Q: What is the AUTOSAR software stack?
A: It is a layered structure where each layer contains modules with specific functionalities,
like OS, COM, and MEM.
Example: The COM stack handles signal transmission between ECUs.
5. Functionality of Each Layer
Q: What is the role of each AUTOSAR layer?
A: The Application Layer contains user logic, RTE enables communication, and BSW
provides services and hardware drivers.
Example: ADC drivers are part of the BSW and accessed via RTE.
6. Software Component Description
Q: What is a Software Component in AUTOSAR?
A: It encapsulates functionality and communicates via ports. Described in ARXML files.
Example: An SWC for cruise control reads vehicle speed and controls throttle.
7. ECU Resource Description
Q: What is ECU Resource Description?
A: It provides details of an ECU’s available resources like memory, cores, and peripherals.
Example: Describes flash size and communication interfaces for mapping SWCs.
8. System Description
Q: What does the System Description contain?
A: It integrates ECU descriptions, SWC mappings, and connections between components.
Example: Shows how the brake ECU communicates with ABS and stability control.
9. VFB
Q: What is the Virtual Functional Bus (VFB)?
A: VFB abstracts communication between SWCs, making it independent of physical ECU
location.
Example: Two SWCs can exchange data even if they are mapped to different ECUs.
10. SWC
Q: What is an SWC in AUTOSAR?
A: A Software Component implements a specific functionality in the Application Layer and
interacts via RTE.
Example: Engine Speed Monitor SWC processes RPM data.
11. Ports
Q: What are Ports in AUTOSAR?
A: Ports are communication endpoints used by SWCs to send and receive data or service
requests. They can be required or provided.
Example: A Sensor SWC provides data via a provide port to a Control SWC.
12. Interface
Q: What is an Interface in AUTOSAR?
A: An Interface defines how data or services are exchanged between ports. Types include
Sender-Receiver and Client-Server.
Example: A Client-Server interface defines operations like 'GetSpeed()'.
13. Access Point
Q: What is an Access Point in AUTOSAR?
A: An Access Point is a RTE-generated interface through which SWCs access BSW modules
or services.
Example: A Diagnostic SWC uses an access point to invoke services from the Diagnostic
Communication Manager.
14. Function Call Point
Q: What is a Function Call Point?
A: It represents a location in the SWC where a function is called via the RTE using a Client-
Server interface.
Example: A SWC might call a 'ReadTemperature()' function of another SWC.
15. RTE Events
Q: What are RTE Events?
A: RTE events trigger execution of SWC runnables based on conditions like data reception,
timing, or operation invocation.
Example: A 10ms periodic RTE event triggers a speed monitoring runnable.
16. API - Types of Interface
Q: What are the types of API interfaces in AUTOSAR?
A: APIs include Sender-Receiver, Client-Server, Mode Switch, and Trigger interfaces for
various communication models.
Example: Client-Server API allows function calls like 'GetBrakeStatus()' between
components.
17. RTE
Q: What is RTE in AUTOSAR?
A: The Run-Time Environment (RTE) connects SWCs to each other and to BSW modules,
acting like middleware.
Example: RTE transfers data from a sensor SWC to an actuator SWC.
18. Contract Phase
Q: What happens in the Contract Phase in AUTOSAR?
A: In this phase, interface contracts between SWCs and the RTE are defined before code
generation.
Example: It validates that each required port is matched with a compatible provided port.
19. Generation Phase
Q: What happens in the Generation Phase in AUTOSAR?
A: The Generation Phase uses ARXML files to generate RTE code and configurations.
Example: Tools like DaVinci Developer generate the actual C code used by ECUs.
20. RTOS
Q: What is an RTOS in the context of AUTOSAR?
A: An RTOS (Real-Time Operating System) manages task scheduling, timing, and resource
control in automotive ECUs.
Example: AUTOSAR uses OSEK/VDX compliant RTOS like ERIKA or Tresos.
21. Hard Real Time System
Q: What is a Hard Real Time System?
A: A system where missing a deadline causes failure. Timing constraints must always be
met.
Example: Airbag deployment must occur within milliseconds on crash detection.
22. Soft Real Time System
Q: What is a Soft Real Time System?
A: A system where occasional deadline misses are tolerable but degrade performance.
Example: Multimedia infotainment system where slight delay in video is acceptable.
23. Single Tasking System
Q: What is a Single Tasking System?
A: Only one task is executed at a time; no preemption or concurrent tasks.
Example: An 8-bit MCU running a sensor polling loop without OS support.
24. Multi Tasking System
Q: What is a Multi Tasking System?
A: Multiple tasks run either concurrently or in preemptive/non-preemptive fashion.
Example: An ECU runs diagnostics, sensor polling, and communication tasks concurrently.
25. Scheduler or Kernel
Q: What is the role of a Scheduler in RTOS?
A: The Scheduler decides which task to execute next based on priority and availability.
Example: Round Robin and Priority-based scheduling are common.
26. Superloop
Q: What is a Superloop?
A: A simple scheduling technique using a continuous loop to call tasks in sequence.
Example: Main() calls sensor_read(), process_data(), and send_data() repeatedly.
27. ISR
Q: What is an ISR in embedded systems?
A: ISR (Interrupt Service Routine) is a function triggered by hardware/software interrupts.
Example: Timer ISR toggles an LED every 1 second.
28. Preemption
Q: What is Preemption in RTOS?
A: Preemption allows a higher-priority task to interrupt and execute over a lower-priority
task.
Example: Emergency braking task preempts regular speed monitoring.
29. Non Preemption
Q: What is Non Preemption?
A: In non-preemptive systems, a running task cannot be interrupted until it finishes.
Example: A diagnostic task runs fully before allowing another task to start.
30. Binary Semaphore
Q: What is a Binary Semaphore?
A: A synchronization mechanism that controls access to shared resources using a binary flag
(0 or 1).
Example: Used to control access to a CAN transmit buffer.
31. Basic Task
Q: What is a Basic Task in AUTOSAR OS?
A: Basic tasks cannot wait; they run to completion once started.
Example: A startup task initializes peripherals at boot.
32. Extended Task
Q: What is an Extended Task?
A: Extended tasks can wait for events and be blocked or resumed.
Example: A communication task waits for a CAN receive event.
33. Communication Stack
Q: What is the AUTOSAR Communication Stack?
A: It manages data exchange over buses like CAN, LIN, Ethernet, handling signals, PDUs, and
transport.
Example: Includes COM, PDU Router, CAN TP, and CAN Driver modules.
34. Module of COM Stack
Q: What are key modules of COM Stack in AUTOSAR?
A: Modules include COM, PDU Router, CAN TP, and CAN Interface and Drivers.
Example: COM packs signals into PDUs for transmission.
35. Types of Managers
Q: What are types of managers in AUTOSAR?
A: Managers include COMM, NVRAM Manager, Diagnostic Event Manager, etc.
Example: COMM Manager controls bus communication modes.
36. COMM
Q: What is the function of the COMM module?
A: COMM manages the communication states like No Communication, Silent, and Full
Communication.
Example: Switches ECU to Full Communication when ignition is ON.
37. Bus State Manager
Q: What is the Bus State Manager?
A: It controls the physical state (on/off/sleep) of the communication controller.
Example: Transitions CAN controller to sleep mode during vehicle shutdown.
38. Generic Network Manager
Q: What is the Generic Network Manager?
A: Manages coordinated network wake-up and shutdown for multiple ECUs.
Example: Controls wake-up pattern on FlexRay cluster.
39. Bus Network Manager
Q: What is the Bus Network Manager?
A: Specific to a bus type, it manages network availability and coordination.
Example: CAN NM controls when ECUs join or leave the CAN network.
40. IPDU
Q: What is an IPDU?
A: Interaction Protocol Data Unit is a unit of transmission containing packed signals.
Example: An IPDU may contain speed, rpm, and gear position.
41. NPDU
Q: What is NPDU?
A: Network Protocol Data Unit includes data and protocol-specific control info.
Example: CAN TP uses NPDUs for segmented transport of large data.
42. Filter Algorithms
Q: What are filter algorithms in AUTOSAR COM module?
A: They determine whether a received signal value should be forwarded to the application.
Example: E.g., F_MaskedNewEqualsX forwards only if (New & Mask) == X.
43. F_Always
Q: What does F_Always filter algorithm do?
A: F_Always always forwards the received signal value regardless of its content.
Example: Useful for logging or diagnostics where every signal change matters.
44. F_Never
Q: What does F_Never filter algorithm do?
A: F_Never never forwards the received signal, effectively disabling updates.
Example: Used in testing or when signal updates are irrelevant.
45. F_MaskedNewEqualsX
Q: What is F_MaskedNewEqualsX filter?
A: Forwards signal only if (NewValue & Mask) == X.
Example: If mask=0xF0 and X=0xA0, only values with high nibble A are accepted.
46. F_MaskedNewDiffersX
Q: What is F_MaskedNewDiffersX filter?
A: Forwards signal if (NewValue & Mask) != X.
Example: Detects changes in specific bits by comparing masked values.
47. F_MaskedNewMaskedOld
Q: What does F_MaskedNewMaskedOld filter do?
A: Forwards signal when (NewValue & Mask) != (OldValue & Mask).
Example: Triggers only when the selected bit(s) actually change.
48. F_NewIsWithin
Q: What is F_NewIsWithin filter?
A: Forwards signal if the new value lies within a defined range.
Example: Useful for accepting values between 10-100 only.
49. F_NewIsOutside
Q: What is F_NewIsOutside filter?
A: Forwards signal if new value is outside a predefined range.
Example: Can trigger error handling if sensor goes out of range.
50. F_OneEveryN
Q: What does F_OneEveryN filter do?
A: Forwards every Nth occurrence of a signal.
Example: If N=5, every 5th signal is sent to reduce bus load.
