fbochud 2 Report post Posted August 19, 2013 Hi, I'm running v.13.10.001 of ncsim. It doesn't look like it supports uvm command line argument uvm_set_config_int like: ncsim <flags> work.my_tb +UVM_TESTNAME=tb_m00308_default_test +uvm_set_config_int=*,<my_variable1>,<my_value> Is that correct? Quote Share this post Link to post Share on other sites
uwes 17 Report post Posted August 19, 2013 hi, im sure ius supports that. what are your symptoms and have you escaped the "*" in order to avoid shell expansion? /uwe Quote Share this post Link to post Share on other sites
fbochud 2 Report post Posted August 19, 2013 hi Uwe, I've tried now with escaped * and full path, without success: ncsim <flags> work.my_tb +UVM_TESTNAME=tb_m00308_default_test +uvm_set_config_int=uvm_test_top,<my_variable1>,<my_value> ncsim <flags> work.my_tb +UVM_TESTNAME=tb_m00308_default_test +uvm_set_config_int=\*,<my_variable1>,<my_value> A similar issue, when trying to trace the config db, I write ncsim <flags> work.my_tb +UVM_TESTNAME=tb_m00308_default_test +uvm_set_config_int=*,<my_variable1>,<my_value> +UVM_CONFIG_DB_TRACE I do not get any trace at all, even though I have other config overriding in my test. However, choosing different tests from the command line is working. Quote Share this post Link to post Share on other sites
fbochud 2 Report post Posted August 20, 2013 Note that these commands all work with vcs, which we currently are using. Quote Share this post Link to post Share on other sites
uwes 17 Report post Posted August 20, 2013 hi, this sounds strange to me. i just rechecked 13.10 and its working as expected. btw have you set +UVM_VERBOSITY to NONE ? if you do then the UVM_CONFIG_DB_TRACE messages are NOT emitted since they are printed with UVM_LOW verbosity. /uwe Quote Share this post Link to post Share on other sites
fbochud 2 Report post Posted August 21, 2013 Now it works. The problem was that we didn't compiled the uvm_dpi library. Thank you for your help anyway. Quote Share this post Link to post Share on other sites