Running the MODISTARC regression tests

From ErikaWiki

Jump to: navigation, search


MODISTARC regression tests: Objectives and results

The main goal of the MODISTARC project is to support the effort of the European car industry towards the development and standardisation of networking architectures. Through the OSEK/VDX consortium activities, the European industry has issued three new standards defining respectively the OSEK/VDX Operating System, Communication and Network Management. These specifications describe the applicable services and protocols and define the associated APIs. They intend to fulfil the two major goals of the OSEK/VDX initiative:

  • enable portability of applications to ECUs coming from different suppliers
  • enable interoperability of interconnected ECUs in a distributed automotive system
  • enable interoperability of interconnected ECUs in a distributed automotive system

The MODISTARC project aims to help the European car industry to keep its leading position in the network based car architectures by providing the relevant test methods and tools to assess the conformance of OSEK/VDX implementations.

For other info go to web site: OSEK portal

  • The following steps explain how to test the compilation procedure and kernel performances using the MODISTARC regression tests.

How to set up the MODISTARC regression procedure

  • Create in the path testcase a script to set the following environment variables:
    • RTDRUID_ECLIPSE_HOME (the path of the eclipse directory: e.g. C:/Evidence/Evidence/eclipse)
    • CLASSPATH (the class path: e.g. "$CLASSPATH;$ECLIPSE_HOME\\plugins\\$LAUNCHER_JAR"; this is for Nios II only)
  • Create in the path testcase\common a folder for the desired architecture. The folder should contain:
    • Files necessary to compile each test.
    • Files for configuring the debugger.
    • The file containing the main rules of the makefiles chain.
    • The main script for the debugger to run the regression tests;
  • Within each test folder to modify the following files:
    • code.c, the application file.
    •, the file containing the list of architectures supported by the test.
    • appl.oil, the OIL configuration file of the test (this file includes header files from the folder testcase\common\rtdruid_common, you have to create a new header file for the desired architecture).
Personal tools