Synopsys: Virtualizer¶

Vendor information

Vendor	Web page	Product name	Version
Synopsys, Inc.	https://www.synopsys.com	Virtualizer	tested with Version N-2017.12, T-2022.06

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”.

Properties 🛈¶

Name	Default value	Valid values	Type	Description
Path to setup.bat			string	Path to the setup.bat file that is used for initializing the simulation environment.
Command line parameters			string
Working directory			string
Interface description file			string	Path to the interface description file (absolute or relative to the base path of the host)
Domain		[‘<online query>’, ‘<no toollib start>’]	string	Name for the test domain from the interface description file.
Restore Simulation after test case	☑		bool	Restore the Virtualizer Simulation after every test case to ensure a clean test environment.
Timeout for tool call ❲in sec.❳	‘600’		string	Timeout after which a tool call is aborted.

Jobs 🛈¶

AttachToCosimDomain¶

Attaches Virtualizer to the co-simulation

Return value

Name	Available if	Default value	Valid values	Type	Description
result				object

DetachFromCosimDomain¶

Detaches Virtualizer from the co-simulation

Return value

Name	Available if	Default value	Valid values	Type	Description
result				object

RunFree¶

Releases the simulation time control and allows e.g. another tool connected to Virtualizer to control simulation time. Control will be retaken during the next wait test step.

Return value

Name	Available if	Default value	Valid values	Type	Description
result				object