Stats

  • Locked Locked
  • Replies 7
  • Subscribers 67
  • Views 23144
  • 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 arguments from irun command line to top module

abhingp01

 Hi,

 I need to pass certain parameters to my top verilog module from irun command line.

Some thing like:

irun ------- argr1,agr2 

 

Is this possible ? 

Kindly give a small example if possible.

Thanking  you in advance.

 

Regards,

Abhishek

Parents
  • albas
    Uhm, interesting enough the example you are using is working correctly (tried on edaplayground.com), but this one does not work correctly:

    typedef enum bit {NO, YES} bool_t;

    module test;
    dut dut ();
    endmodule

    module dut ();
    parameter bool_t p = YES;

    initial $display ("p is %n", p);
    endmodule

    the -defparam options passed to incisive does not overwrite the locally defined parameter. Moreover I have the following situation www.edaplayground.com/.../ufn where the outcoming output of the parameter value is completely wrong.

    What is the main difference between these examples?

    Thanks for your support,

    Al
Reply
  • albas
    Uhm, interesting enough the example you are using is working correctly (tried on edaplayground.com), but this one does not work correctly:

    typedef enum bit {NO, YES} bool_t;

    module test;
    dut dut ();
    endmodule

    module dut ();
    parameter bool_t p = YES;

    initial $display ("p is %n", p);
    endmodule

    the -defparam options passed to incisive does not overwrite the locally defined parameter. Moreover I have the following situation www.edaplayground.com/.../ufn where the outcoming output of the parameter value is completely wrong.

    What is the main difference between these examples?

    Thanks for your support,

    Al
Children
No Data

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.