Terms in Autosar -MemMap File / IDT / Ports & Port Interfaces
MemMap File
MemMap file is a header file (MemMap.h) used to map functions or variables to specific memory locations in Flash memory or RAM, to avoid wastage of RAM, and organize variables or function blocks as desired.
Reference:
https://autosartutorials.com/common-terms-used-in-autosar/
Implementation Data Type
This is analogous to typedef of C using which we can create a specific data type for suppose a signal of PDU.
Lets say we want to transmit signal named Alive and the range of the signal is expected between 0 to 255
so we will create a Implementation data type in Configuration software like DaVinci Developer.
Implementation Data type is used by Port interfaces which the ports follow while communicating with other entities. The structure of data and its tolerances and limits are all known at configuration time.
Ports And Port Interfaces
Ports
Every communication between SWC and lower layers is accomplished by using ports.
Port is a channel or connection using which data can be transferred between SWCs, or BSW modules.
As AUTOSAR aims in standardizing, the data which will be transferred between entities needs to be known at configuration time, so Ports are no exception.
Ports belong to exactly one SWC at a time. The port may or may not be connected to other end. There are two types of ports:
- Required Ports
- Provider Ports
Port Interfaces
Port Interfaces are interfaces which define the kind of information transmitted or received between two ports.
Port Interfaces are like blue prints of ports which defines a “protocol” to be followed by port of SWC.
Port interface is reusable
i.e. they can be used by multiple ports.
Port interface configuration is done at the time of system configuration.
AUTOSAR differentiates between three types of Port interfaces:
- AUTOSAR Interface: // TODO
- Standardized AUTOSAR Interface:
- Standardized Interface:
