Our Solutions
AUTOSAR Products & Solutions
Reusable software products and turnkey services to make your drivers portable, your modules AUTOSAR-compliant and your integration faster.
Reusable software products and turnkey services to make your drivers portable, your modules AUTOSAR-compliant and your integration faster.
Reduce the cost and risk of AUTOSAR software, from the microcontroller up to the complete ECU
One MCAL architecture, portable across microcontrollers.
Discover → 02Make your existing modules AUTOSAR-compliant.
Discover → 03From your ARXML or text requirements to an integrated ECU configuration.
Discover → 04A tailored platform to develop one module, N modules or the whole ECU.
Discover →An MCAL driver is built on four layers. In the MAS Generic MCAL, the three upper layers are generic and microcontroller-independent. Only the Low Level Driver (LLD) is specific to the target MCU.
Porting the MCAL to a new microcontroller, or to a new derivative of the same family, means writing and validating the LLD only. The API, handler and driver logic stay unchanged, as does everything built on top of them.
Supporting a new MCU means rewriting only the LLD, which cuts porting effort and time-to-market.
The same API and behavior on every target: upper BSW and application software are not impacted by an MCU change.
Tests, reviews and quality evidence of the generic layers are reused from one project to the next. Only the LLD needs full re-verification.
Switching or dual-sourcing the microcontroller becomes realistic, reducing dependency on a single silicon vendor.
One code base for the upper layers: a fix or an improvement benefits every supported microcontroller.
The same configuration approach across targets, so your teams build know-how once and reuse it.
MAS makes your software modules AUTOSAR-compliant, so they can be configured, generated and integrated in any standard AUTOSAR toolchain.
You have MCAL modules or low-level drivers and need to deliver them as AUTOSAR MCAL to your customers.
You own specific modules (proprietary drivers, CDDs, middleware) that must fit into an AUTOSAR ECU.
Give us your ARXML files, or even your requirements in plain text. We integrate them on any AUTOSAR platform, respecting the ECUC parameter definitions of each AUTOSAR vendor.
System / ECU extract ARXML, communication matrices, or textual specifications.
Consistency checks, gap analysis and translation of text requirements into AUTOSAR configuration.
Configuration on your vendor stack, compliant with its ECUC ParamDefs (Vector, Elektrobit, ETAS…).
Generated and built configuration, integration report and traceability to your inputs.
You have an AUTOSAR ECU and want to develop your own modules? MAS provides a tailored AUTOSAR platform so your teams can focus on their software, not on the integration.
A ready-to-use environment around the module you develop, with its surrounding BSW configured.
A shared platform for several modules or teams, with a common baseline and integration rules.
A complete AUTOSAR baseline for your ECU: BSW, OS and RTE configured, ready for application development.
Tell us about your microcontroller, your modules or your ECU project. We will propose the solution that fits your needs.
Contact Us