Stats

  • Locked Locked
  • Replies 4
  • Subscribers 127
  • Views 16264
  • 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

Specify a file path as a parameter type in Cadence VerilogAMS

uzzy

Hello,

        I am writing a verilogams module to be used in my spectre sims. When this module is instantiated in my schematic, it needs to take in a path to a pwl file as a parameter input to the verilogams instance and then incorporate this filename as the file type for the "vsource" instance defined inside the verilogams module. In short, this is something I want to do(syntax is incorrect) :

 parameter filename = "/projects/test.pwl";

 vsource #(.type("pwl"),.file(filename)) V1(p,n);

 I want to specify the particular pwl file to be used from the schematic and not by changing the verilogams code of the module. Any suggestions/comments will be greatly appreciated ?

Regards,

Uzzy 

Parents
  • Andrew Beckett

    Stephen,

    This works in both VerilogA and VerilogAMS:

    `include "disciplines.vams"

    module testpwl (plus,minus);

    inout plus,minus;
    electrical plus,minus;

    parameter filename="clock.pwl";

    vsource #(.type("pwl"),.file(filename)) V1(plus,minus);

    endmodule

    Spectre also works with:

     parameter string filename="clock.pwl";

    but this "string" keyword will not work in AMS Designer (Verilog AMS), so best to omit it in both.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Stephen,

    This works in both VerilogA and VerilogAMS:

    `include "disciplines.vams"

    module testpwl (plus,minus);

    inout plus,minus;
    electrical plus,minus;

    parameter filename="clock.pwl";

    vsource #(.type("pwl"),.file(filename)) V1(plus,minus);

    endmodule

    Spectre also works with:

     parameter string filename="clock.pwl";

    but this "string" keyword will not work in AMS Designer (Verilog AMS), so best to omit it in both.

    Regards,

    Andrew.

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.