Matrickz AUTOSAR Lab
Our AUTOSAR experts have deep understanding of the complex architecture and have extensive experience in the configuration and integration of the AUTOSAR Basic Software (BSW), the Application Software (ASW) and the AUTOSAR Runtime Environment (RTE). Moreover, our “Safety & Security by Design” principle allows us to offer safety and security compliant architecture (e.g., Secure Onboard Communication), design and process definition for AUTOSAR (Versions .3.xx and 4.xx) based ECUs. We have expertise with all common AUTOSAR applications and the bootloader stack configuration. Thus, we develop and assemble the appropriate design, concept and suitable tool-chain based on the specific project and customer needs.
We offer:
- AUTOSAR configuration
- BSW integration:
- Creation and integration of new modules.
- Optimize resources such as memory and runtime
- Communication Stack:
- Configuration of CAN Driver, FlexRay Driver, CANIf / FlexRayIf
- Configuration of Com, Com Client (PDUR, CANTP, FlexRayTP)
- Memory Stack:
- NVM blocks
- EEPROM, FEE
- Diagnostic Communication Manager & Diagnostic Event Manager
- Configuration of different services for DCM modules
- Configuration of error analysis
- Complex Device Driver (CDD)
- Specification and implementation, e.g. driver
- We use the following tools to configure and validate the basic software:
- Vector GENy TEST
- DaVinci Developer
- DaVinci Configurator
- EB Tresos
- DSpace System desk test
AUTOSAR basic software
- BMW AUTOSAR Core 4 (Rel.2)
- Daimler SLP 10
- Audi MLBevo Standard Software 7
- GM Global B
- Elektrobit AutoCore 7.4
- Vector MICROSAR

We use the following tools to configure and validate the basic software:
- Vector GENy TEST
- DaVinci Developer
- DaVinci Configurator
- EB Tresos
- DSpace System desk test
AUTOSAR basic software
- BMW AUTOSAR Core 4 (Rel.2)
- Daimler SLP 10
- Audi MLBevo Standard Software 7
- GM Global B
- Elektrobit AutoCore 7.4
- Vector MICROSAR