AR# 57669

AXI BFM simulation with ModelSim fails because the .do script generated by Vivado points to a 64-bit version of the DLL which is incompatible wth 32-bit ModelSim


The following error is seen when launching ModelSim simulation for an AXI BFM core from Vivado.

 vsim -L unisims_ver -L unimacro_ver -L secureip -lib work -voptargs=\"+acc\" -pli G:/xbuilds/2013.1_0305_1/installs/nt64/Vivado/2013.1/ids_lite/ISE/lib/nt64/libxil_vsim.dll -t 1ps cdn_axi_bfm_0 glbl
# ** Note: (vsim-3812) Design is being optimized...
# ** Note: (vsim-3865) Due to PLI being present, full design access is being specified.
# Loading G:/xbuilds/2013.1_0305_1/installs/nt64/Vivado/2013.1/ids_lite/ISE/lib/nt64/libxil_vsim.dll
# ** Error: (vsim-3193) Load of "G:/xbuilds/2013.1_0305_1/installs/nt64/Vivado/2013.1/ids_lite/ISE/lib/nt64/libxil_vsim.dl
l" failed: Bad DLL format.
# ** Error: (vsim-PLI-3002) Failed to load PLI object file "G:/xbuilds/2013.1_0305_1/installs/nt64/Vivado/2013.1/ids_lite/ISE/lib/nt64/libxil_vsim.dl

ModelSim is run in 32-bit mode so the DLL it points to is incompatible, resulting in this error.

Is it possible to let the tool know that ModelSim/Questa is in 32-bit mode so that the DO script points to a 32-bit version of the DLL?


In 2013.3, if you have both 32- and 64-bit versions of the ModelSim toolset installed, Vivado will call the 64-bit executable on a 64-bit platform.

The integration has no way of automatically knowing when a 32-bit version of ModelSim is being used.

You can control this manually by setting the following property:

set_property MODELSIM.64BIT 0 [current_fileset -simset] 

Linked Answer Records

Associated Answer Records

Answer Number Answer Title Version Found Version Resolved
59667 Vivado/ModelSim - ModelSim fails on PLI (AXI BFM) with "Error: (vsim-3193)" and "Error: (vsim-PLI-3002)" N/A N/A
AR# 57669
Date 12/16/2014
Status Active
Type General Article