List of Basic Software Modules, V1.0.0

List of Basic Software Modules, V1.0.
Module short AUTOSAR

AUTOSAR name of function / name (API Module ID Service AUTOSAR SW Number of
module service prefix) (uint16) Functional description (yes/no) Layer instances
CAN Driver Can 80 The CAN Driver provides services for initiating transmissions and callback no Communication 1 (indexed) or
functions for notifying receive events, independently from the hardware. Drivers several (code
doubled) possible
FlexRay Driver Fr 81 The FlexRay Driver is used to abstract the hardware related differences of no Communication 1 (indexed) or
different FlexRay Communication Controllers. All mandatory features according to Drivers several (code
the FlexRay Protocol Specification of the Communication Controllers are doubled) possible
encapsulated and can only be accessed by a uniform interface. The API provides
abstract functional operations that are mapped to a sequence of hardware
accesses depending on the actual supported CC
LIN Interface LinIf 62 LIN Master Communication Stack no Communication HW 1
Communication services for LIN communication: Abstraction
- Schedule table handling
- Transmission of LIN frames (confirmation with flag and function interface)
- Reception of LIN frames (indication with flag and function interface)
- Sleep and wakeup handling
- Error handling of protocol errors
- Timeout observation of LIN frames
- Transport protocol for diagnostic
For R2.0 this moduile also includes the LIN NM (not compatible with Autosar NM),
LIN TP (with different prefix "LinTp") and LIN transceiver driver.
LIN Driver Lin 82 Low level driver for performing LIN communication via the internal standard no Communication 1 (indexed) or
asynchronous serial communication interface of the µC (SCI/UART): Drivers several (code
- Initialization of the SCI hardware doubled) possible
- API for generating an original "LIN synch break"
On Chip LIN devices are not supported.

SPI Handler Driver Spi 83 The SPI Handler/Driver provides services for reading from and writing to devices no Communication 1
connected via SPI busses. It provides access to SPI communication to several Drivers
users (e.g. EEPROM, Watchdog, I/O ASICs). It also provides the required
mechanism to configure the onchip SPI peripheral.
Internal / External EEPROM Eep 90 The EEPROM driver provides services for reading, writing, erasing to/from an no Memory Drivers 1
Driver EEPROM. It also provides a service for comparing a data block in the EEPROM
with a data block in the memory (e.g. RAM).
Internal / External Flash Driver Fls 92 The flash driver provides services for reading, writing and erasing flash memory no Memory Drivers 1
and a configuration interface for setting/resetting the write/erase protection if
supported by the underlying hardware.
- AUTOSAR confidential -
List of Basic Software Modules, V1.0.0

Port Driver Port 124 This module shall provide the service for initializing the whole PORT structure of no I/O Drivers 1
the microcontroller.
DIO Driver Dio 120 The DIO Driver provides services for reading and writing to/from no I/O Drivers 1
• DIO Channels (Pins)
• DIO Ports
• DIO Channel Groups
PWM Driver Pwm 121 The driver provides services for initialization and control of the microcontroller no I/O Drivers 1
internal PWM stage (pulse width modulation).
ICU Driver Icu 122 The ICU driver (Release 1) provides services for signal edge and level no I/O Drivers 1
notification. Furthermore it provides services to control Wake-up interrupts.
The ICU driver (Release 2) provides services for periodic signal time
measurement, services for Edge timestamping, usable for the acquisition of non-
periodic signals and services for Edge counting with or without hardware gating.
ADC Driver Adc 123 Driver for initialization and control of the µC internal ADC (analog to digital no I/O Drivers 1
converter)
There are two variants planned:
1. Basic ADC Driver with basic functionality for body applications
2. Enhanced ADC Driver with additional enhanced functionality for PowerTrain
applications (e.g. streaming)
GPT Driver Gpt 100 Driver for internal general purpose timer no Microcontroller 1
Provision of periodic timer interrupts for use in timer services Drivers
Two modes are provided:
- resolution mode (module tries to perform the desired number of alls)
- period mode (module tries to maintain the specified period time)
MCU Driver Mcu 101 Driver Responsible to provide the following services: no Microcontroller 1
- SW initiated µC reset Drivers
- selection of µC power mode (STOP, SLEEP, HALT, …)
- configuration of Wake-up
- Handling of the internal PLL clock unit (Initialization and frequency setting, mode
selection, detection of clock disturbance, crystal loss, ...)
Internal / external Watchdog Wdg 102 Mode selection and triggering of µC internal watchdog no Microcontroller
Driver Drivers
Contraints: Trigger routine is called by watchdog manager
RAM Test RamTst 93 Functional test of µC internal RAM cells no Memory Drivers 1
- complete test during start-up/shutdown cycle
- complete test, triggered by diagnostic command
- cyclic test during normal operation mode (block by block or cell by cell)

Flash Check FlsTst 104 Check of data consistency of flash contents (via checksums) no System Services 1
- complete check during start-up/shutdown cycle
- complete check, triggered by diagnostic command
- cyclic check during normal operation mode (block by block)
Autosar Phase 2
Core Test CoreTst 103 Test of CPU registers and instruction set during start-up cycle (similar to BIST no Microcontroller 1
[build in self test] Drivers
Autosar Phase 2
Complex Drivers no prefix 255 A high number of different drivers for complex sensor evaluation and actuator no, but direct Complex Drivers 1
(AUTOSAR control with direct access to the µC using specific interrupts and/or complex µC RTE access
interface) peripherals (like PCP, TPU), e.g.
- injection control
- electric valve control
- incremental position detection
I/O Hardware Abstraction no prefix 254 Abstraction of signal path of the ECU hardware (Layout, µC Pins, µC external no, but direct I/O HW Abstraction 1
(AUTOSAR devices like I/O ASIC) RTE access
interface) - Provides signal based interface
- static normalization/inversion of values according to their physical representation
at the inputs/outputs of the ECU hardware (compensation of static influences
caused withing the path between ECU I/O and µC pin, e.g. voltage divider,
hardware inversion)
Important note: no filtering, debouncing, range checking etc.

Watchdog Interface WdgIf 43 The Watchdog Interface provides equal mechanisms to access µC internal and no Onboard Device 1
external Watchdog devices. It abstracts from the location of peripheral Watchdog Abstraction
devices (internal or external) and the number of Watchdog devices.
EEPROM Abstraction Ea 40 The EEPROM Interface provides equal mechanisms to access µC internal and no Memory HW 1
external EEPROM devices. It abstracts from the location of peripheral EEPROM Abstraction
devices (internal or external), the ECU hardware layout and the number of
EEPROM devices.
CAN Interface CanIf 60 The CAN Hardware Interface provides equal mechanisms to access a CAN bus no Communication HW 1
channel regardless of it‘s location (µC internal/external). It abstracts from the Abstraction
location of CAN controllers (onchip/onboard), the ECU hardware layout and the
number of CAN drivers.

FlexRay Interface FrIf 61 The FlexRay Interface provides equal mechanisms to access a FlexRay bus no Communication HW 1
channel regardless of it‘s location (µC internal/external). It abstracts from the Abstraction
location of CAN controllers (onchip/onboard), the ECU hardware layout and the
number of CAN drivers.
Crypto Routines Crypto 200 Routines for authentification and signature to protect against download of yes System Services - 1
unauthorized software Std Lib
Autosar Phase 2
CRC Routines Crc 201 calculation of CRC16, CRC32 etc. yes System Services - 1
Optimized for size (runtime calculation) or speed (table based) Std Lib
Interpolation Routines Ipo 203 Conversion of data types (e.g. real32 to uint16), 2D interpolation yes System Services - 1
Std Lib
Autosar Phase 2
Bit Routines Bit 204 Optimized setting, clearing and checking of single bits and bit masks System Services - 1
Std Lib
Autosar Phase 2
Operating System Os 1 OSEK operating system plus extensions: no, but direct System Services - 1
- memory protection RTE access OS
- Deadline monitoring
- schedule tables
- enhanced counter structure
Communication Manager ComM 12 Controlls the states of all communication channels attached to the ECU no, but direct System Services 1 ( but one state
RTE access machine for each
channel)
ECU State Manager EcuM 10 ECU power and mode Management yes System Services 1
- e.g. Start-up, Pre-Start, Normal Operation, Limp Home, Pre-Sleep, Shut down
- control of network management
- control of watchdog manager
- control of NVRAM manager
- control of power relevant modules (e.g. bus tranceiver drivers)
- ...
Management of (maybe parallel) ECU states
- Global States
- Local States (Implementation by User)
Activation of software parts dependent on active state(s)

Development Error Tracer Det 15 Supports software debugging. yes System Services 1
Provides interface for reporting development errors:
Dbg_ReportError(Module-ID, API-ID, Error-ID)
Behind this API errors can be traced, logged, counted etc.

Function Inhibition Manager FiM 11 Control of functionality yes System Services 1
- control (enable/disable) functionalities of SW components based on the
following inhibit conditions:
- faults
- signal qualities
- ECU and vehicle states
- diagnostic tester commands
- EOL configuration (function enabling/disabling in EEPROM)
- only in special cases for binary informations that are similar to reaction to
faults: driver demands (e.g. ESP on/off)
The Function Inhibition Manager shall use the information of dependencies
provided by the software components .
Watchdog Manager WdgM 13 Supervision of application functions yes System Services 1
- checking aliveness of applications (e.g. collecting flags, hand shaking and
protocols, question - answer)
- selection of watchdog mode
- triggering of internal and/or external watchdogs (via driver)
Generic NM Nm 30 Network management no Communication 1 per connected
- provision of common, network independent API Services network cluster
- agreement on network cluster wide shut down of communication system
- determination of network configuration at start-up
- monitoring of network configuration during operation
- provision of network status information
- one instance per network system required

CAN NM CanNm 31 Network management for CAN in interrupt mode no Communication 1 per connected
CAN specific synchronisation and monitoring algorithms Services CAN cluster
- synchronised transition to bus sleep
- error recovery after bus-off
- bus diagnostics

FlexRay NM FrNm 32 Network management for FlexRay no Communication 1 per connected
- synchronised transition to bus sleep Services FlexRay cluster
- error recovery after bus-off
- bus diagnostics

AUTOSAR COM Com 50 Management of internal and external messages no, but direct Communication 1
- Provision of signal oriented data interface for the application RTE access Services
- Communication control (start/stop)
- Sending of messages according to Transmission type (cyclic, event triggered)
- Checking of minimum distances between transmit messages
- Monitoring of receive messages (message timeout)
- Provision of FirstValue and Changed Flags
- Filter mechanisms for incoming and outgoing messages
- Byte ordering
- Different notification mechanisms
PDU Router PduR 51 Functionality 1: no Communication 1

Deploys IPDUs of OSEK COM to different communication systems. Services
The IPDU identifier decides on the network system type (e.g. CAN, LIN) and if a
transport layer has to be used or not.
The PDU Router abstracts from different underlying communication layers.
Functionality 2:
Frame based gateway. Simple routing of complete PDUs between equal (e.g.
CAN - CAN) or different (e.g. CAN - LIN) vehicle network systems.
- mapping of event triggered and cyclic frames
- queueing of frames
- sending of default values
This functionality is optional if there is no gateway required on an ECU (e.g. ECU
is connected only to 1 CAN bus)
CAN Tranceiver Driver CanTrcv 70 Driver for external CAN transceiver no Communication HW 1 per connected
- Control of wake-Up/sleep Abstraction CAN cluster
- Network diagnostic (short circuit, open line, ...)
- ...

FlexRay Tranceiver Driver FrTrcv 71 Driver for external FlexRay transceiver no Communication HW 1 per connected
- Control of wake-Up/sleep Abstraction FlexRay cluster
- Network diagnostic (short circuit, open line, ...)
- ...
CAN Transport Layer CanTp 35 Transport protocol on CAN according to ISO 15765-2 TPL no Communication 1 per connected
- segmentation of data in transmit direction Services CAN cluster
- collection of data in receive direction
- control of data flow
- detection of errors (message loss/doubling/sequence)
FlexRay Transport Layer FrTp 36 Transport protocol on FlexRay using the dynamic part of the communication no Communication 1 per connected
round Services FlexRay cluster
- segmentation of data in transmit direction
- collection of data in receive direction
- control of data flow
- detection of errors (message loss/doubling/sequence)
XCP Transport Layer on CAN CanXcp 210 Part 3 of XCP specification. no Communication 1
Transports the generic XCP protocol on CAN Services (it does not make
sense to have
Not part of any Autosar Specifications XCP access via
XCP Transport Layer on FrXcp 211 Part 3 of XCP specification. no Communication 1
FlexRay Transports the generic XCP protocol on FlexRay Services (it does not make
sense to have
Not part of any Autosar Specifications XCP access via
XCP Service Implementation Xcp -- Universal Calibration Protocol (according to ASAP2) yes Application 1
Measurement, calibration and control:
1. Synchronous data transfer
- data acquisition
- data stimulation
- bypassing
2. Online Calibration
3. Flash programming
- absolute access mode (address based)
- functional access mode (flash area based)
Not part of any Autosar Specifications

Diagnostic Communication Dcm 53 Diagnostic communication according to UDP - ISO14229 yes Communication 1
Manager - functional interface for diagnostic services Services
- handling of specific diagnostic requests (enable/disable normal message
transmission, tester present)
- reply of negative responses
- exception handling
- address handling
- support of ECU flash programming (Listen Only Mode)
Different authentication levels for diagnostic services

Diagnostic Event Manager Dem 54 Management of error data yes Communication 1
- Structuring of error data which shall be saved to the NVRAM Services
- Non volatile setting, counting, resetting and reading of errors
- Sampling and saving of general system environment data (not error specific)
- error specific environment data can be forwarded within the notification
MOST Application Socket MostNs -- MOST - Media Oriented System Transport no not mapped 1
Belongs to the MOST NetServices (Layer 2) and is required for implementing an
application. Services and function groups are
- MOST Command Interpreter
- NetBlock
- Network Master Shadow
- Adress Handler
- MOST Supervisor
- Notification Service.
Autosar Phase 2
MOST Basic Layer System MostNs -- MOST - Media Oriented System Transport no not mapped 1
Services Belongs to the MOST NetServices (Layer 1) with the following services:
- MOST Supervisor
- Control Message Service
- Synchronous Channel Allocation Service
- Transparent Channel Allocation Service
- Asynchronous Data Transmission Service
- Transceiver Control Service
Autosar Phase 2
Flash EEPROM Emulation Fee 21 Emulates EEPROM functionality using the flash memory no Memory Services 1

NVRAM Manager NvM 20 Management of non volatile data yes Memory Services 1
- immediate/queued/delayed writing
- data shadowing in RAM
- data encryption in NVRAM
- checksum calculation and validation
- distribution of write access ('walking blocks')
- redundant data storage
- read and write protection of data segments
- configuration of data segments and their attributes (memory location, kind of
data storage: single/multiple/distributed, autostore, encrypted)
- ...
Interface: logical (via RAM), direct (blockwise data programming)

MOST Network Master MostNm -- The responsibilities of the network master are: ??? not mapped 1
- Administration of the central registry holding the current system configuration,
i.e. the dynamic set of function blocks available at any point in time.
- Distribution of the configuration status by providing the interface of the network
master function block and by notifying the system of configuration change events.
There exists exactly one instance of the network master in every MOST network.
The network master uses the netblock function block to obtain the configuration
data.
Autosar Phase 2
MOST Power Master MostPm -- Function block of the network master node of a MOST cluster ??? not mapped 1
- start up and shut down
- overheat shut down
- error handling
There exists exactly one instance of the power master in every MOST network.
The power master uses the interface provided by the netblock function block.
Autosar Phase 2

MOST Connection Master MostCm -- The connection master administrates the use of the synchronous channel of the ??? not mapped 1
MOST network. It provides an interface, the connection master function block,
used to request synchronous connections. It handles the connection requests by
allocating the bandwidth needed and by controlling the sinks and sources
involved. It also stores all active connections and prohibits multiple allocations of
the same source, and deallocations of sources currently in use.
There exists exactly one instance of the connection master in every MOST
network.
Free Running Timer FRunTime 45 Provides read access to a free running timer. System Services
Autosar Phase 2
BSW Scheduler Module SchM 130 Provide scheduling of all BSW modules, e.g. assigns priority and memory System Services 1
protection to each BSW module used in an ECU.
Memory Abstraction Interface MemIf 22 Abstracts the memory interface for different memory devices. Memory Services 1
IPDU Multiplexer IPduMplex 52 Handles multiplexing of PDU's
CAN Transceiver Interface CanIf 72 Abstracts the CAN transceiver driver access
NM Gateway NmGw Handles Network management synchronisation between networks
34
Autosar Phase 2
LIN NM LinNm Handles LIN network states
63
Autosar Phase 2
Synchronization and Time ServiceSyncTime Provides synchronisation services for the module with respect to time.
46
Autosar R2.1

List of Basic Software Modules, V1.0.0

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

List of Basic Software Modules, V1.0.0

Încărcat de

Drepturi de autor:

Formate disponibile

List of Basic Software Modules, V1.0.

Module short AUTOSAR

On Chip LIN devices are not supported.

Module short AUTOSAR

Module short AUTOSAR

Important note: no filtering, debouncing, range checking etc.

Module short AUTOSAR

Module short AUTOSAR

Behind this API errors can be traced, logged, counted etc.

- one instance per network system required

- one instance per network system required

Module short AUTOSAR

- one instance per network system required

PDU Router PduR 51 Functionality 1: no Communication 1

The PDU Router abstracts from different underlying communication layers.

Module short AUTOSAR

Not part of any Autosar Specifications

Module short AUTOSAR

Different authentication levels for diagnostic services

Module short AUTOSAR

Interface: logical (via RAM), direct (blockwise data programming)

Module short AUTOSAR

S-ar putea să vă placă și