Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 8373
  • 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

parametrizing input port for rapid IP3

TommasoF

Hi all,

in my TB I have a variable called "NF_inp_port" which correspond for a given input I'd like to use on a specific corner simulation. This variable I use when running the NF simulation.

Now I would like to do the same also for the rapid IP3. So here below  I would like to parametrize the "Input Sources 1 and 2" such that for a given path I get the PORT name I desire. I tried to use some variables, then also  with VAR("variable_name") , but it didn't work out. Is there a way to parametrize this input ?

Thanks 
Tommaso

  • Dear TommasoF,

    TommasoF said:
    I tried to use some variables, then also  with VAR("variable_name") , but it didn't work out. Is there a way to parametrize this input ?

    I did not try it, but did you happen to view the Troubleshooting article at URL:

    https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O3w00000AEFWHEA5&pageName=ArticleContent

    This article provides a method that will vary the port in the simulation as part of a corners simulation in Assembler. From my understanding of your description, it is different than what you tried.

    Shawn

  • in reply to ShawnLogan

    Tommaso,

    This does not appear to be possible currently. The Input Sources 1/2 appear to be treated literally (other than a mapping from schematic names to netlist names) and you cannot put a variable name in the field (I'd have expected that you'd need to use VAR("myport") to distinguish it from a literal port name, but it netlists the VAR() syntax).

    You'll need to contact customer support to request support for this .

    I tried this with Rapid IP3 with an AC analysis (i.e. for an amplifier); my guess is that it works (or rather doesn't work) similarly for a single tone hbac RapidIP3 analysis too.

    Andrew

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.