AUTOSAR MCAL, BSW, RTE Integration And Migration to AUTOSAR 4.3
Automotive Open System Architecture: A Global Partnership for AUTOSAR Architecture in ECU Software
The founding principle of AUTOSAR consortium is to create one common standard, accepted by global OEMs’, for in-vehicle networking and automotive ECU development. The charter states – “Cooperate on standards, compete on implementation”
Partner with Embitel Technologies, a CMMI Level 3 organization, for robust and quality implementation of your AUTOSAR 4.x/AUTOSAR 3.x projects
Partner with us for AUTOSAR MCAL, CDD, BSW, RTE and ISO 26262 compliance:
AUTOSAR MCAL Development, Code Generation, Testing
Development of Eclipse based Configuration tool and Perl/Python based Code Generation Tool
In-depth expertise in customization of the configuration tool, as per your requirements
Our team can also deliver a standalone executable (.exe) package (code generation tool).
This .exe file can be easily integrated and configured with any Configuration Tool, as per the project requirement.
MCAL Driver development, as per ISO 26262 Standard
Creation of Test Environment (Test Applications, BSW stubs and Simple Scheduler), for testing each MCAL component.
AUTOSAR RTE and BSW Configuration & Integration
Integration of AUTOSAR BSW stack (basic software) with the Application Layer.
Integration of AUTOSAR RTE (Run-time environment) with the Application Layer.
We have delivered projects on BSW, RTE configuration and integration by leveraging our expertise in the following AUTOSAR tools
K-Vector (DaVinci Configurator and Developer)
Migration to AUTOSAR 3.X or 4.X
Technical and business workshops to analyze your product roadmaps and assessment of migration to AUTOSAR 4.3 or AUTOSAR 3.X, across the product lines
Model Based Development of the Application Layer
Model-Based Development (AUTOSAR, DaVinci Developer) and logic implementation for Application layer of the AUTOSAR Software Stack
ISO 26262 Compliant CDD Development and Integration
Development of ISO26262 compliant CDD
Creation of test environments, to validate CDD
Integration of CDD with existing configuration
A Handbook on AUTOSAR & ISO26262 Compliant MCAL
Learn about AUTOSAR Architecture of MCAL, Configuration & Code Generation Tools, MCAL Driver Development and Testing
Meet Our Automotive Leaders
A Handbook on AUTOSAR BSW & RTE
Learn about AUTOSAR Architecture and Configuration process of the Base Software (BSW) & Real-Time Environment (RTE)
Ans. Our AUTOSAR Software developers have in-depth expertise and project experience in AUTOSAR MCAL driver development.
We have partnered with automotive leaders for the development of microcontroller drivers such as GPT driver and MCU driver; Communication drivers like CAN, LIN, FlexRay and MOST and I/O drivers like ICU, PWM, ADC, Flash, and EEPROM.
Our AUTOSAR software development team has partnered with customers for the development of static file of the microcontroller driver and the AUTOSAR MCAL driver configuration.
Ans. It is a non-AUTOSAR component which has access to the services of the AUTOSAR MCAL and also has an interface with the AUTOSAR compliant Application Layer.
A CDD is designed to access the AUTOSAR application layer and AUTOSAR MCAL layer without having to communicate via the BSW and RTE Layers.
It is commonly used to integrate additional hardware components to AUTOSAR compliant Electronic Control Units (ECU).
Ans. We provide support in development of ISO 26262 Functional safety compliant CDD.
We support in validating the CDD by creating Test environment which includes Test Application, MCAL Drivers and AUTOSAR OS.
In case of non-availability of MCAL Drivers or OS; we can support in CDD validation by
- Creation of stubs that replicate MCAL Driver
- Deploying a Simple Scheduler to replicate AUTOSAR OS.
We also provide support in integration of CDD with existing configuration.
Ans. Yes, we provide support for configuration of diagnostic messages according to the project requirements.
The configuration sequence details are discussed in detail during the AUTOSAR Technology Workshops as part of our SLA.
Ans. Yes, we provide support for the configuration of the interface layer as per your project/application requirement.
Ans. Yes, our AUTOSAR software developers have expertise in the configuration of the AUTOSAR RTE (Real Time Environment), that serves as an interface between the application software module (SWC) and the AUTOSAR BSW.
Ans. We have delivered projects on configuration and code generation based on AUTOSAR tools like Comasso, Vector, ECU Spectrum, KSAR AUTOSAR.
We also have experience in working with design tool DaVinci Developer and scripting tools based on Pearl and Python.
Ans. As part of our AUTOSAR Testing suite, following testing services are included:
- Module Testing,- individual AUTOSAR modules are tested for various test-case scenarios. This is White Box testing
- Integration test – after integration of individual AUTOSAR modules, we perform integration testing based on relevant test-case scenarios. This is also a White Box Testing
- System level testing (end application layer testing). – This is Black Box testing where we test the entire product/embedded system
Write to us to know more detailed information about our testing services.
Ans. Yes. The application development can be done based on the specification of the project. We have expertise in both manual coding and tool-based code generation.
Our team of software development engineers has extensive experience in manual coding implemented in Embedded C
We also have expertise and experience in working with the code generation tools like Matlab, Vector, Comasso and much more.
Blogs on AUTOSAR Architecture: Learn about AUTOSAR MCAL, AUTOSAR Communication Stack and more