Synopsys: Virtualizer

Legacy/internal identifier: VIRTUALIZER

Vendor information

Vendor

Web page

Product name

Version

Synopsys, Inc.

https://www.synopsys.com

Virtualizer

tested with Version N-2017.12

Categories

MDL 🛈

APL 🛈

BAN 🛈

BMA 🛈

SVC 🛈

DGN 🛈

FIU 🛈

EES 🛈

FCT 🛈

DBG 🛈

IMG 🛈

AUDIO 🛈

ENVSIM 🛈

ENVCOM 🛈

✓

✓

Platform

Operating system

Support

Windows

✓

Linux

Ports

Specifics

Prerequisites

In order to enable Virtualizer to be automated by ecu.test, an extension for providing a programming interface for ecu.test needs to be installed. This API extension has to be obtained directly from the vendor (Synopsys).

Configuration details

In order for making full use of the Virtualizer tool connection, it should be configured as described in the following:

  • In the test bench configuration, a MODELACCESS port is needed (for accessing the signals from the interface description file) and a APPLICATION port is needed (for accessing the quantities from the A2L file).

  • In the test configuration, a Model access must be configured and be associated with the MODELACCESS port.

  • IMPORTANT: In the Model access, the option Use as time base must be checked, in order that time based operations (such as Wait test steps) in ecu.test are executed in the time context of the Virtualizer simulation.

  • In the test configuration, the A2L file must be configured as Control unit access and be associated with the APPLICATION port.

Info

If a Wait test step is executed, time will only pass in Virtualizer, if the simulation is not halted (e.g., by a breakpoint in UDE).

Using Virtualizer together with UDE

In order for using an UDE instance in ecu.test that has been started by Virtualizer, the following steps are important:

  • In the test bench configuration, UDE should be set to start option Never and in the Debugger port the option Connect to running UDE instance should be activated.

  • If the configurations are started, first Virtualizer will be started and it will start a UDE instance.

  • Only then ecu.test may connect to the running UDE instance, either manually in the configuration window (Right click –> Connect tool) or via a Configuration change step in a project.

Info

Normally, if Virtualizer is closed, it will not close the UDE instance that has been started by it. For this purpose the UDE Debugger port has an option “Always close UDE instance”.