1      DEVELOPMENT BACKGROUND

With the rapid development of the automotive industry, automotive electronics have become a revolutionary sign in the process of automotive technology development. To cope with the increasing system complexity in automotive electronic software development, improve software consistency and reusability, the AUTOSAR standard was proposed in 2003 and quickly gained widespread recognition in the industry. After the development tool providers in the industry launched development tool chains and solutions that conform to the AUTOSAR standard, some developers established the ARTOP organization to solve the problem of data interaction between development tools from different manufacturers and the multi-version issues of the AUTOSAR meta-model, aiming to better promote the implementation of the AUTOSAR development method in the development of automotive electronic software.

Among them, some internationally renowned companies have provided AUTOSAR development tool chains based on their original development tool products, and were the first in the industry to launch the Artop architecture of AUTOSAR Builder. These development tools all include the function of ECU configuration, but most of these ECU configuration functions only provide support for the implementation of the company's own basic software modules, and cannot support the configuration and code generation of the basic software implemented by other companies.

Compared with the solutions of international giants, there are very few domestic software development platforms and ECU configuration tools that conform to the AUTOSAR development method, and the development capability of basic software is also very weak. Therefore, developing and implementing a set of development tools that conform to the AUTOSAR standard development process, providing an ECU configuration environment that supports the implementation of basic software from multiple manufacturers and platforms, is of great significance to the development of China's automotive electronic software.

ZC.MuNiu configuration tool is an ECU development solution that conforms to the domestic automotive electronic system architecture standard. The solution is compatible with the mainstream AUTOSAR standard in the industry, including a series of tools from system function design, ECU function mapping and component configuration, to automatic code generation of the runtime environment, providing a set of practical and reusable ECU application software development foundation.

2      FUNCTIONAL DESCRIPTION

ZC.MuNiu configuration tool is based on the latest ARTOP architecture and supports the latest AUTOSAR 4.4.0 standard. It has realized the full process of ECU configuration from configuration, verification to code generation according to the ECU configuration steps defined in the AUTOSAR development method. The main advantages can be summarized in the following aspects:

The implementation of the full process of configuration, verification, and code generation fully realizes the development requirements of the ECU configuration phase in the AUTOSAR development method.

It supports the design and implementation of a system that is easy to expand with pluggable module information related to the manufacturer's implementation. Different manufacturers can easily integrate the implementation of the basic module into the BSW Builder in ZC.MuNiu configuration tool, which is dynamically loaded during the startup process of the BSW Builder and has good scalability.

The implementation of the dynamic generation method of the configuration interface based on the viewer framework. Based on the basic functions of the EMF framework, the BSW Builder decouples the view layer from the model layer and designs and implements the BSW Builder viewer, combining the BSW Builder parameter definition model and configuration value model to dynamically generate the configuration interface.

2.1     Product Feature

ZC.MuNiu configuration tool integrates a development environment with the following features:

Ø  Based on the Eclipse platform and Artop architecture, it is developed in a plug-in manner, offering strong extensibility.

Ø  Supports configuration for various modules of the AUTOSAR 4.4.0 standard.

Ø  Supports customized development of complex driver configuration tools.

Ø  Supports consistency verification of configuration data.

Ø  Product-level automatic code generation.

Ø  Supports data exchange in ARXML format.

Ø Flexible configuration and trimming of functional components according to customer needs.

Ø  Powerful error checking and prompt correction mechanism.

Ø  Supports the import of various format data files.

2.2     Technical Architecture

 ZC.MuNiu configuration tool is developed based on the latest architecture of the AUTOSAR configuration tool.

Ø   Eclipse Oxygen.3a Release (4.7.3a)

Ø   ARTOP-SDK-4.13.0 (supports the latest AUTOSAR releases R21-11)

Ø   ARTEXT-SDK-1.7.2 1.6.0.

Ø   CDT 8.1.2     

ZC.MuNiu Configuration Tool Architecture Diagram

2.3     Run Environment

3      Introduction to Use

3.1     Create a New Project

Select "New" in the "File" menu, then choose "Project" ---> "AUTOSAR" ---> "AUTOSAR Project" to open the following interface for project creation.

Create a New Project

3.2     Select Platform

Click "Next," and you can open the following interface to select the platform that needs to be configured.

CREATE PLATFORM

3.3     添加模块Add Module

In the main interface of the software, click on "Basic Editor" to view the modules included under this platform.

Right-click on a module and select "Add" to add a new module.

OPEN THE MODULE SELECTION INTERFACE

In the interface, all modules supported under the platform are listed for selection based on your needs.

By clicking on the arrow to the left of the module, you can view the configuration structure it contains. To add configurations where needed, right-click and select 'Add'. After clicking on a specific configuration, you can see each configuration item.

ADD CONFIGURATION

CONFIGURATION ITEM

3.4     Verification and Generation

       For modules that have been configured, you can perform verification to check if the configuration is reasonable. Any problematic configuration items will be highlighted with prompts.

VERIFY CONFIGURATION

     Verification of the configuration can be carried out after the setup is complete. Once the verification is done, you can proceed to the code generation step. You can observe the process and outcome of the generation right within the interface.

  GENERATE CODE

Here is an example of a generated header file:

AUTOMATICALLY GENERATED HEADER FILE EXAMPLE

3.5     Import DBC Files

（1）As shown in the figure, after creating the project and setting up the platform, click the "Import Communication Data" button and select "Import DBC file" to start importing the DBC file.

IMPORT DBC FILES

（2）Select the appropriate DBC file and the required ECU nodes.

ELECT ECU NODE:

 （3）Bind the COM module, DIAG mode, and CAN Controller module:

BIND CONTROLLER

    （4）The final generated effect is shown in the figure below.

THE CONFIGURATION GENERATED AFTER IMPORTING THE DBC FILE.

3.6     Import LDF File

（1）Select to import the LDF file

（2）Select the file path

（3）The generated effect is as follows:

3.7     Import ODX File

（1）As shown in the figure, after creating the project and setting up the platform, click the "Import Diagnostic Data" button and select "Import ODX File" to start importing the ODX file.

Import odx file

（2）Select ODX File

Select ODX File

（3）Select the ECU node:

Select the ECU node:

（4）Finally, generate the configuration. The effect is shown in the figure below.

Generate the configuration after importing the ODX file.

3.8     Import DEXT(ARXML) File

（1）As shown in the figure, after creating the project and setting up the platform, click the "Import Diagnostic Data" button and select "Import Dext File" to start importing the Dext file.

DEXT File Import Entry

    （2） Select DEXT File：

  Select DEXT File

   （3）Finally, generate the configuration. The effect is shown in the figure below.

Generate the configuration after importing the DEXT file.

3.9     Import OIL File

（1）As shown in the figure, after creating the project and setting up the platform, click "Import OS Data" to start importing the OIL file.

Merge with the existing modules or not

（2）Finally, generate the configuration. The effect is shown in the figure below.

ZC.MuNiu configuration tool is developed based on the latest ARTOP architecture and supports the latest AUTOSAR 4.4.0 standard for basic software configuration tools, providing a full set of BSW configuration and RTE generation functions. Currently, ZC’s AUTOSAR standardized BSW, complex drivers, SafetyLibrary, SafetyFrame, CryptoLibrary, and other basic software products all use this configuration tool. The solution is compatible with mainstream industry standards, including system functional design, ECU function mapping and component configuration, and a suite of tools for automatic code generation in the runtime environment. It provides a set of practical and verified foundations for developing reusable ECU application software, which can be used in conjunction with tools from Vector, EB, and others.

Features of ZC.MuNiu Configuration Tool Product:

Ø Based on the Eclipse platform framework, it adopts the development philosophy of plugin-based and modular design, offering cross-platform operation, component-based architecture, and excellent scalability.

Ø Provides a complete integrated development environment, supporting intelligent code editing, compilation, linking, and debugging functions.

Ø Supports the AUTOSAR development methodology and process, offering a full set of BSW configuration and RTE generation tools.

Ø Developed based on the latest ARTOP architecture, it supports the latest AUTOSAR 4.4.0 standard.

Ø  Supports BSW consistency and integrity verification.

Ø  Supports the import of DBC and ODX format files.

Ø  Compatible with various mainstream automotive ECU chips,

ZC.MuNiu Configuration Tool offers a user-friendly interface for the development of ECU (Electronic Control Unit) controller software. It supports the configuration of standardized AUTOSAR basic software code modules and the development of configuration interfaces for complex drivers. It is currently mainly applied in the following scenarios:

Ø  ZC.MuNiu Basic Software Platform Standard AUTOSAR Module Configuration

Ø  ZC.MuNiu Basic Software Platform Complex Driver Module Configuration

        u SAFETY FRAME

        u CRYPTO LIBRARY

        u BCCIC

        u SBC

Ø  Collaborate with chip companies to provide configuration tools for MCU MCAL

MUNIU SOFTWARE COPYRIGHT REGISTRATION CERTIFICATE

Click to download the product manual