The illustration below shows the MICROSAR packages in different colors and the additional Base Modules.
Basically, there are defined 5 packages.
Some are single packages only, other packages like MOP or MPP exist more than once as there are different modules for different OEMs or hardware platforms. The 5 packages are:
Package | Description |
|---|---|
| MICROSAR Core Package – MCP The MICROSAR Core Package includes the MICROSAR Core stack, i.e. means the modules for Communication, System, Memory Management, Bus Management, etc. The modules of the MCP are independent of an OEM and drivers are not included. |
| MICROSAR Base Package – MBP The MICRSOAR Base Package includes general modules like a generation framework and core libraries. |
| MICROSAR OEM Package – MOP The MICROSAR OEM Package comprises all OEM-dependent modules and the available OEM-specific extensions. |
| MICROSAR EXT Package – MEP The MICROSAR External Package comprises drivers for external devices as transceivers (TRCV) or system basis chip (SBC). |
| MICROSAR Platform Package – MPP The MICROSAR Platform Package(s) are platform-specific modules providing the required MCAL and different Platform Support Packages (PSP) and is available for specific hardware and the Vector vVIRTUALtarget. |
If the Supply folder in the ThirdParty/<Mcal_µC> folder is not included in your BSW Package, the MCAL must be integrated. Vector supports you with the tool 3rd Party MCAL Integration Helper.