Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 2225
  • 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

Update W/L number in instance property, but resistor "r "value isn't change accordingly

ringamp

Hi everyone

I am just using the PDK from the foundry.  I just followed its cdslib userguide. when I launch the virtuoso IC618 and create schematic. I add one instance of resistor using "add instance". in the "add instance" interface, I can adjust "W","L" value and the "Resistance" parameter (in gray) changed accordingly. 

But after I finished the placement of this resistor instance on the schematic, I clicked on its symbol and  pressed "Q". "Instance Property Editor" pop-up. It showed quite native interface: every parameter can be change (no gray area and "W" "L" shows in different places ).it was different from that of "add instance".  I changed "W" "L" and click "apply", the “W” “L” value changed displayed by symbol but the resistance value was the seem value. But CIW window give a warning "*WARNING* CDF parameter "r" reset to "6.0969K""

What I want is the resistance value display by the symbol also change after I modified "W" "L", and the "Instance Property Editor"  interface is in consistent with that of "add instance"

Parents
  • Andrew Beckett

    This sounds as if you have a rather strange set of bindkeys. The normal bind key for "q" would be schHiObjectProperty() whereas it sounds (from your description) that it is invoking the old (very low level) geQuerySelSet() function which doesn't really deal with CDF information which controls the edibility/readability and callbacks for interacting with various components.

    I suggest you take a look at Options->Bindkeys and for the Schematic application search for "q" in the search box at the top, and see what the bindkeys are set to. If it's geQuerySelSet() you might want to find out why it's been changed in your environment, because that is rather non-standard.

    You can probably just enter:

    load(prependInstallPath("samples/local/schBindKeys.il"))

    in the CIW to change back to a more standard default set.

    You didn't give any clue as to which foundry PDK you were using, so this is of course guesswork on my part...

    Andrew

Reply
  • Andrew Beckett

    This sounds as if you have a rather strange set of bindkeys. The normal bind key for "q" would be schHiObjectProperty() whereas it sounds (from your description) that it is invoking the old (very low level) geQuerySelSet() function which doesn't really deal with CDF information which controls the edibility/readability and callbacks for interacting with various components.

    I suggest you take a look at Options->Bindkeys and for the Schematic application search for "q" in the search box at the top, and see what the bindkeys are set to. If it's geQuerySelSet() you might want to find out why it's been changed in your environment, because that is rather non-standard.

    You can probably just enter:

    load(prependInstallPath("samples/local/schBindKeys.il"))

    in the CIW to change back to a more standard default set.

    You didn't give any clue as to which foundry PDK you were using, so this is of course guesswork on my part...

    Andrew

Children
  • ringamp
    in reply to Andrew Beckett

    Thanks Andrew, it is Global Foundry/IBM PDK(maybe it is not so welcome on its environment setting) . since there's limited number of foundry, I realize that this information is quite important. I check .il files provided by the foundry (both gfPdkBindkeys.il and gfPdkBindkeysCDS.il), they show the difference on <Key>q exactly as you mentioned. I changed to load gfPdkBindkeysCDS.il in .cdsinit, it is back to normal. Thanks again!

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.