Stats

  • Locked Locked
  • Replies 10
  • Subscribers 126
  • Views 21799
  • 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

Declaring global net in schematic composer

RFStuff

 Dear All,

I want to name a net as global so that it can be accessed in the hierarchy.

But also I want the same net should not be created as a PIN in layout.

Could anybody please tell how that can be achieved ?

Kind Regards,

Parents
  • Andrew Beckett

    Finally it's clear what you were asking. There doesn't appear to be any control to stop the *.PIN from being netlisted for each *.GLOBAL net. I'm not sure why it matters -  I don't think I've seen any reports about removing this.

    The one CCR that I found was that you can use the variable simPinGlobals=t which instead of adding *.GLOBAL it will add pins through the hierarchy - although it still outputs the *.PIN at the top level. I don't know whether that's an acceptable alternative.

    Anyway, if you want different behaviour (other than manually removing the *.PIN line yourself) then you'll need to contact customer support to request control of this in the auCdl netlister, with details as to why it's needed (what goes wrong if this is there).

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Finally it's clear what you were asking. There doesn't appear to be any control to stop the *.PIN from being netlisted for each *.GLOBAL net. I'm not sure why it matters -  I don't think I've seen any reports about removing this.

    The one CCR that I found was that you can use the variable simPinGlobals=t which instead of adding *.GLOBAL it will add pins through the hierarchy - although it still outputs the *.PIN at the top level. I don't know whether that's an acceptable alternative.

    Anyway, if you want different behaviour (other than manually removing the *.PIN line yourself) then you'll need to contact customer support to request control of this in the auCdl netlister, with details as to why it's needed (what goes wrong if this is there).

    Regards,

    Andrew.

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.