Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14323
  • 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 an Additional Subcircuit Parameter for a Mos Model

Trail Animal

I thought this was a no-brainer...but after a couple of hours of frustration, I have no brain!?!?

 I'm just trying to pass an additional parameter to a mos model so I can do selective monte carlo sims.  I'm using an integer as a boolean "on/off" switch in the mmvtho & mmbeta definitions.  I've modified the model and edited the "base" cdf to use this new parameter, but I can't get the netlister to include it in the subcircuit call.  It shows up on the edit properties dialog, but it just gets ignored when netlisted!?!?  If I modify the netlist directly, it works fine, but that's too much work to do evrytime I need to re-netlist!

 I've searched the related user guides and tried various ways to define the variable (integer, string, etc..), but I'm at a loss??? 

 Any thoughts would be appreciated...

Thanks

-Rob

  • First thing to do is check the Base CDF for this component and make sure you've included the parameter name in the simulator's simInfo - instParameters list. Andrew.

  • Andrew...Genius!!!  Works perfectly now!  I only saw the terminals listed in the general CDF form under simInfo and didn't realize if I selected the edit, all the other parameters were there!?!?  I modified both the spectre and the hspiceS versions, even though I'm using spectre...I noticed that the macroArgumentStyle is hspiceS and that there isn't a spectre option!?!?

     Thanks again...

    Rob

  • Each netlister has its own special needs, so you'll see variety between simInfo. Just wait until you get to the LVS stage and have to figure out the subtle differences between auCdl (used by Calibre) and auLvs (used by Assura). Also, start getting familiar with hspiceD - when you move on to the IC6.1.x environment you'll find all the 'S' variants of netlisters are completely gone.

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.