The MxVMC (sometimes called VMC) is used when you want to simulate the behavior of a microcontroller on the PC.  It provides the following capabilities:

•EEPROM emulation

•Input and Output ports

•A Scheduler and an OSEK operating system

•CAN buses

•Pseudo-interrupts

The MxVMC runs C or C++ code. Visual Studio or GCC is required. You can use one or more VMCs in a project.

The MxVMC is a Transform, but unlike other Transforms, it runs as a independent process, so an issue in your source code cannot take down MxVDev.

The µC Library provides an interface for using the simulated microcontroller functions.

The VMC is the primary Transform used for SIL testing of C code. The interface between the software component and the VMC is called the Harness and is defined an AppIF.c code file. There are three ways to create an AppIF.c. In some cases, you may use a combination of these methods:

•AUTOSAR - If your SWC is AUTOSAR-compliant and ARXML files are available, the VMC can automatically generate the Harness. See AUTOSAR Testing.

•Guided Harnessing - Use the Guided Harnessing tool to select the Signals to use for testing the SWC.

•Manually - The AppIF.c is a C code file and can be written or revised by a programmer. This may be the best way when working with an existing project or a non-standard interface. For details, see Port Registration.
 

Requirements

Be sure the required software is available before starting an MxVMC project:

 

Related Topics:

MxVMC C/C++ API

C Portability Guidelines

Token Charges