• 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. Custom IC Design
  3. Aliasing net or shorting net of an extracted view

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 125
  • Views 15169
  • 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

Aliasing net or shorting net of an extracted view

sidm
sidm over 4 years ago

HI All,

I have a 3 terminal extracted view stitched in my schematic using a n2port. One of its terminal is GR

Is there a way I can alias this GR terminal of n2port with another net in my schematic so that they are connected like a short ?

I wish to connect the floating GR of the n2port to schematic gnd net.

regards

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    I have no idea what you're asking. n2port doesn't have a "GR" terminal - I just can't make sense of your question.

    A picture might help?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 4 years ago in reply to Andrew Beckett

    Thanks for the reply Andrew.

    Here is the image of the n2port where the 3rd terminal is a GR net.

    I wish to connect this to schematic ground net. As of now I am using a small resistor from analogLib to do this but is there a way to short these nets ?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to sidm

    Why don't you just wire them together (and not give the nets two different names)? If you really want to give them two different names, you could use the "patch" component from the basic library (or Create->Patchcord) to alias the two nets.

    There must something I'm missing here?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 4 years ago in reply to Andrew Beckett

    Thanks Andrew, the extracted view was generated from the layout with ground netname GR instead of gr (schematic ground net) so the n2port created after extraction has GR net in i.

    So GR net is coming automatically after extracted view is invoked.

    I can delete GR net and connect the 3rd terminal of n2port to gr directly but not sure if that will impact the functionality of the n2port s-parameter which was originally created with GR net ?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to sidm

    The s-parameter file has no node names - it just has ports (two ports in this case) - the node names are irrelevant. So you can safely change this without impacting the functionality (inserting the 1ohm resistor would however have a small impact).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 4 years ago in reply to Andrew Beckett

    Thanks Andrew, this is helpful information.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 4 years ago in reply to sidm

    Hi All,

    I am facing an issue in that the layout I have received is not in sync with the schematic in terms of the pin names and net names. for example the layout has pin name RFIN whereas the schematic has rfin so all the nets and pins in the layout have been put in capital letters.

    Is there an easy way I can rename the nets and pins in the layout to be the same as in the schematic ?

    Due to this pin name difference I am unable to generate the extracted view  post s-parameter simulation of the layout.

    Any workarounds will be great help.

    thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to sidm

    Presumably you're not using Layout XL? That said, if you did and did update Components and Nets, it would create new pins and you'd have to move them into place.

    It would probably be easiest to write some SKILL code to fix this, because it's a very specific requirement - that code would then be adapted to fix whatever was wrong. I suggest you contact customer support, because writing some code based on an incomplete description of possible mismatches is not going to be very helpful - it would be better to see this. If it's just a matter of converting the pin names to lower case, something like this may work (adapt to suit your needs):

    cv=geGetEditCellView()
    foreach(term cv~>terminals
      term~>name=lowerCase(term~>name)
      ; fix any attached labels
      foreach(pin term~>pins
        foreach(pinFig pin~>figs
          foreach(child pinFig~>children
            when(child~>objType=="label"
              child~>theLabel=lowerCase(child~>theLabel)
            )
          )
        )
      )
    )

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 4 years ago in reply to Andrew Beckett

    Thanks Andrew I will check this out , I am using Layout EXL mostly.

    • 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