MC-Checker : MBD Model/Code Back-to-Back Test Tool

Overview

MC-Checker is an embedded code verification tool for automotive model-base development. It’s primary function is to compare the MATLAB/Simulink specification model with the target code. MC-Checker performs a Back-to-Back test between the model and code compliant with the ISO26262 Automotive Functional Safety Standard.

Features

Automotive ECU Software Model/Code Back-to-Back Test Tool

MC-Checker is a model & code back-to-back test tool for automotive software model-based development. It compares the MATLAB/Simulink specification model blocks (subsystems) with the embedded target code as required by the automotive functional safety standard ISO 26262.

Processor code level (PIL) simulation

MC-Checker performs model/code back-to-back testing using a MIL simulation for MATLAB/Simulink specification models, and a PIL simulation for the embedded target code.

During the PIL simulation the actual target code is executed in order to meet ISO 26262 test environment requirements.

MIL : Model In the Loop
PIL : Processor In the Loop

Import test data from other tools

MC-Checker uses general CSV format files for data input and output. In this way model or code coverage test cases may be imported from other model based development tools or GAIO's unit test tool CoverageMaster winAMS.

Supports both unit level and integration level model/code verification as required by ISO 26262

MC-Checker is capable of performing verifications on both the unit level and integration level. Unit level verifications compare the minimum unit sub-system (model) to the corresponding C-functions using MBD tool generated coverage test cases. Integration level verifications compare function unit Simulink blocks (models) with the corresponding C-functions using actual road test data or simulated fault injection data.

MC-Checker Type	Code / Model	Test Cases
Unit Level Verification	[Model]: Minimum unit sub-system [Code]: Corresponding C-function	Model/Code coverage test cases generated by MBD tools.
Integration Level Verification	[Model]: Function unit Simulink block [Code]: Corresponding C-functions	Road test data from actual automobile or simulated fault injection test cases.

Integrated file management

Necessary files (resources) used during model/code verification such as model files, compiled target code, and test data files may be managed from within the MC-Checker interface.

Easily setup tests using test items added to the test environment

Test queries such as model execution (MIL simulation) and/or code execution (S-PIL simulation) can be easily configured using test items added to the test environment. This allows the user to setup a variety of tests by selecting different combinations of models, target code and test data.

Import test data file from other MBD tools, Uses CSV files for input/output test data

MC-Checker uses general CSV format files for data input and output. Model or code coverage test cases may be imported from other model base development tools such as:

 

Automatically compares model and code execution results with user-defined allowable error range

Errors detected during the model and code comparison will be displayed on the dedicated graphical view. An allowable error range may be specified by the user to be used during the comparison.
The model/code simulation results and comparison results will also be automatically output to a CSV file.

Supported Processor List

MC-Checker Supported Processor List

 

System Requirements

PC: PC/AT Compatible

OS： WindowsXP Profesional SP3 / Windows7 (32bit/64bit)

Software:

MathWorks MATLAB/Simulink (32bit only):

Copyright(c) 2013 GAIO TECHNOLOGY CO., LTD. All Rights Reserved