Stats

  • Locked Locked
  • Replies 4
  • Subscribers 66
  • Views 20621
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

passing IRUN command-line arguments into vsif file?

xzhao

Hi,

I use command-line arguments in my script and it looks like this

irun ... +define+MY_ARG ...

I can run stand-alone simulation with different MY_ARG to different tests.

How can I reuse my script in a vsif to launch regression of all tests? Is there a way to define an attribute so I can specify MY_ARG in vsif, for example

...

test my_test1 { my_arg_attr : 2};

test my_test2 {my_arg_attr : 3};

... 

Thanks for help.

Xing 

  • Hi Xing,

    Did you work out how to do this - I want to do the same thing - basically pass testname to my run_sim script.

    Thanks,

    Steven

  • You can pass attribute valuesto your run script using the $ATTR(<name>) or $RUN_ENV(<envvarname>) in theVSIF.

    Look in the cdnshelp tool for more information about attributes, how to deine them and pass them around.
    Here's a small example from the SoC Verification Kit labs that ship with Incisive:

    group apb_ss_tests {
      run_script: "irun -R -nclibdirname $DIR(chain)/INCA_libs +UVM_TESTNAME=$ATTR(test_name)_test -covtest $ATTR(test_name)";
      scan_script: "vm_scan.pl shell.flt uvm.flt ius.flt";
     
      count : 5;              // Default run count
      sv_seed: random;       // Random seed selection

      test apb_subsystem { };
      test apb_gpio_simple { };
      test apb_spi_simple {  };
      test apb_uart_simple { };
    };
     

  •  Hi Stephen,

     Thanks -exactly what I was looking for.

    Steven

  • in reply to StephenH

    Hi Steven, Could you provide me with an example on how to send attributes other than test_name. For example, my run script in standalone mode accepts -opts

     ../scripts/run.sh -test i2c_basic_trans_test -opts "+VSEQ=HP_RD" 

    While running another test I want to change "+VSEQ=HP_RD" to "+VSEQ=LP_RD" 

    Thanks in advance.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.