• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Mixed-Signal Design
  3. Defining a string parameter in a systemverilog model as...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 63
  • Views 19526
  • 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

Defining a string parameter in a systemverilog model as a design variable

Soner
Soner over 12 years ago

Hi, I have a systemverilog module with a string parameter:

parameter string filename = "default_name"; 

When I instantiate this module and edit its object properties, I see the filename property. Whatever I write into this field is passed as a string to the module. Is it possible to define a design variable (which value I can control in ADE) and pass this design variable to this field? 

The motivation is to be able to provide a unique filename in a parametric analysis. Otherwise, the file will be overwritten for each simulation.

 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    I think so - although I've not tested this. You'd have to ensure that the parameter is defined in the CDF as parseAsCEL=yes though. If that doesn't work, please contact customer support (I'm assuming AMS is the simulator).

    KInd Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Soner
    Soner over 11 years ago

    Hi Andrew,

    Here is a workaround: 

    1) Ensure that the parameter is defined in the CDF as parseAsCEL=yes

    2) Edit object properties of the instance, type pPar("myVariable")

    myVariable shows up as a design variable in ADE XL. Is it possible to make step #1 above automatic, just like parameters of type real?

    Regards,

    Soner Yaldiz 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information