Happy to Help!

This website doesn't store cookies. Enjoy the experience, without worrying about your data!

Great, thanks!

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

  • Comasso,
  • K-Vector (DaVinci Configurator and Developer)
  • EB Tresos
  • autosar-migration

    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
  • Autosar-mbd-implementation

    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
  • Snow

    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) & Run-Time Environment (RTE)


    Customer FAQs About AUTOSAR MCAL, BSW, RTE and AUTOSAR Testing Services


      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. Embitel provides product engineering services for AUTOSAR BSW layer development. It includes configuration of memory stack (MemStack), AUTOSAR communication stack (COMStack like CAN, LIN, FlexRay) and DCM (Diagnostic Communication Manager).

      The configuration of the Operating System is also a part of the AUTOSAR BSW layer development.

      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 (Run-Time Environment), that serves as an interface between the application software module (SWC) and the AUTOSAR BSW.
      Ans. Yes, our AUTOSAR software development team has delivered projects on the latest versions of AUTOSAR ( from AUTOSAR 4.0 to AUTOSAR 4.3).

      We have also worked on projects based on earlier versions of AUTOSAR software.

      Ans. Yes. Our AUTOSAR software development team has successfully partnered with global OEMs’ and Suppliers for migration to AUTOSAR 4.3.

      We can share the success stories of our customers after signing the NDA agreement.

      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:

      1. Module Testing,- individual AUTOSAR modules are tested for various test-case scenarios. This is White Box testing

      3. 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

      5. 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

      What is AUTOSAR MCAL? Learn about the software module architecture and device drivers
    • What is AUTOSAR Communication Stack (ComStack)? Introduction to CAN Communication Stack
    • What is AUTOSAR Memory Stack | Software modules and device drivers
    • What is AUTOSAR development partnership and AUTOSAR MCAL Layer
    • Decoding the “Component Concept” of the Application Layer in AUTOSAR
    • Decoding the Implementation of UDS Vehicle Diagnostics in AUTOSAR Base Software Module


    AUTOSAR Development Customer Success Story

    • AUTOSAR Software for an Ambient Lighting ECU and Integration of UDS Protocol Stack


    Knowledge Bytes
      What is AUTOSAR MCAL?

      AUTOSAR MCAL is a software module that directly accesses on-chip MCU peripheral modules and external devices that are mapped to memory, and makes the upper software layer independent of the MCU.

      (Source – Renesas)

      What is AUTOSAR layered architecture?

      AUTOSAR uses a three-layered architecture:

      • Basic Software (AUTOSAR BSW): Basic Software is the standardized software layer, which provides services to the AUTOSAR Software Components and is necessary to run the functional part of the software. It does not fulfill any functional job itself and is situated below the AUTOSAR RTE (Runtime Environment). The Basic Software contains standardized and ECU specific modules.
      • Runtime environment (AUTOSAR RTE): Middleware which abstracts from the network topology for the inter- and intra-ECU information exchange between the application software components and between the Basic Software (BSW) and the applications.
      • Application Layer: application software components that interact with the runtime environment (RTE).

      Source – AUTOSAR.org

      Why migrate to AUTOSAR architecture from legacy software?

      AUTOSAR layered architecture ensures a clear demarcation between the application software and hardware platform and drivers with the help of RTE.

      This facilitates a shift in ECU design approach from coding to configuration


      (Source – RTC Magazine)

    Benefits of migrating to AUTOSAR architecture:

    • Improved reuse of ECUs in new car platforms and architectures
    • Improved use of pre-validated and tested software components (representing vehicle functions)
    • Reduced testing and safety certification costs
    • Reduction in downstream design errors—an AUTOSAR methodology allows functions to be defined and verified at an architectural level
    • Reduction in overall hardware cost by improved AUTOSAR network management and capacity utilization
    • Reduced costs in overall network architecture analysis and design reviews
    • Improved communication between OEMs and Tier 1 suppliers, by using a standardized digital exchange format (AUTOSAR XML or arxml)

    (Source – RTC Magazine)

      Which tools are used for AUTOSAR software development and AUTOSAR 4.3 Migration? What are their roles?
      A number of AUTOSAR tools are deployed to develop an AUTOSAR compliant software. These tools are also very important for projects involving migration to AUTOSAR 4.3 or other versions

      Here is a list of tools that our AUTOSAR software developers are expert in:

      1. COMASSO: COMASSO is a registered association that supports implementation of the AUTOSAR Architecture as per the common global standard. (Source- https://www.comasso.org/).

        COMASSO provides a technical platform to the AUTOSAR software developers in order to reduce the integration efforts in software exchange or re-use.

        COMASSO as a platform facilitates AUTOSAR developers to maintain and develop AUTOSAR BSW as part of a community, which is similar to an Open Source community.

        COMASSO technical platform also helps the developers exchange source code, information and experience to implement AUTOSAR BSW.

      2. K-SAR AUTOSAR: It is an AUTOSAR suite developed by Mathworks. It is used by AUTOSAR Software developers to configure and generate AUTOSAR BSW (Base Software) and AUTOSAR RTE (Run-time Environment).

        The tool comprises of basic AUTOSAR Software Stack and K-SAR Editor.

      3. DaVinci Developer Tool: It is a development tool for designing the architecture of software components, that need to be deployed in AUTOSAR based Electronic Control Systems.

        It is used in application development phase of AUTOSAR software development projects.

        One of the tool’s biggest advantage is its ability to link model based development (MBD) tools via ARXML (a file format introduced by AUTOSAR to contain data used in Electronic Control Unit(ECU) development as per the AUTOSAR Architecture)



    Contact Us


     I agree to allow this website to store my submitted data. This data can be used only for responding to my enquiry and/or send related information about technology services and solutions.