loveuvm Posted August 12, 2012 Report Posted August 12, 2012 Hi, when using UVM_RGM with VCS, errors happen as attached. how to deal with these problem?[ATTACH]40[/ATTACH] Quote
loveuvm Posted August 12, 2012 Author Report Posted August 12, 2012 (edited) Hi, when using UVM_RGM with VCS, errors happen as attached. how to deal with these problem?[ATTACH]40[/ATTACH] ----------------------------------------------------- my script to run vcs is as below: vcs -sverilog \ +acc +vpi \ +incdir+$UVM_HOME/src $UVM_HOME/src/uvm.sv \ ./test_reg.sv \ +incdir+$UVM_HOME/src/uvm_pkg.sv \ $UVM_HOME/src/dpi/uvm_dpi.cc \ +incdir+$UVM_RGM_HOME/sv \ $UVM_RGM_HOME/dpi/rgm_set_hdl.c \ -CFLAGS "-DVCS" \ -l vcs.log ------------------------- Any one can help me? Thanks!!! Edited August 12, 2012 by loveuvm Quote
uwes Posted August 13, 2012 Report Posted August 13, 2012 are you using rgm with VHDL (as DUT)? if not you might want to define RGM_NO_VHPI during c code compile Quote
loveuvm Posted August 13, 2012 Author Report Posted August 13, 2012 Thanks, since adding +define+RGM_NO_VHPI to the script above is invalid, I have added the DEFINE statement in rdm_set_hdl.c instead. and it is ok for running. but i want to know if DUT is written in VHDL, how to deal with this case? Quote
uwes Posted August 13, 2012 Report Posted August 13, 2012 well, it just means that VCS isnt compatible with the vhpi header file/api used to access vhdl signals in $UVM_RGM_HOME/dpi/rgm_set_hdl.c. the options are simulator dependent Quote
loveuvm Posted August 13, 2012 Author Report Posted August 13, 2012 well, it just means that VCS isnt compatible with the vhpi header file/api used to access vhdl signals in $UVM_RGM_HOME/dpi/rgm_set_hdl.c. the options are simulator dependent uwes, thank you for your reply . Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.