• 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. Using pPar("") in AMS simulation

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 4141
  • 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

Using pPar("") in AMS simulation

designguy
designguy over 10 years ago

Hi,

I currently have a problem trying to pass instance parameters to a spectre model by using pPar("[parameter_name]") when I run AMS simulations.  My virtuoso version is virtuoso 6.1.6

Here are the 2 following scenarios:

1) If I set  the parameter_name = some number in my ADE-L state and run the simulation, the instance parameter with "parameter_name" is set to 0.

2) If I set the parameter_name = some number directly on the instance schematic in the Virtuoso schematic editor, the instance parameter is set correctly in the netlist.

This is a problem I only encounter while running AMS simulations.  I do not have the same problem when running a pure spectre simulation.

Please let me know what I can do to resolve this problem (is there a simple work around for using pPar with AMS). 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Hopefully you've contacted customer support by now, because I can't imagine what the problem might be without seeing the data. pPar() should work fine with AMS too.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Hopefully you've contacted customer support by now, because I can't imagine what the problem might be without seeing the data. pPar() should work fine with AMS too.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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