• 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 SKILL
  3. How to access global signals cds_globals

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 142
  • Views 5074
  • 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

How to access global signals cds_globals

FormerMember
FormerMember over 8 years ago

Hello everyone,

I have a cellview that has both inherited connections that can be called with this command dbGetCellViewInheritedSig and other global signals that do not show up with it. However, all of them appear in the cds_globals module after the netlisting.

I want to figure out this global "hidden" signal without running the netlister. Like is there a way in skill to get the name of this signal?

Thanks,

Sherif

  • Cancel
Parents
  • FormerMember
    FormerMember over 8 years ago

    Thanks Andrew for your reply. The thing I myself don't know what actually that signal is to describe it properly. I mean it should be a global signal since it has the ! attached to it and it ends up in the cds_globals module. But to describe it a bit clearer, I will try and approach it like this:

    So a top cell has a main voltage source that is defined as nsub!, it goes all the way down with the hierarchy with each cell. Whenever you define a source and give it the name nsub, it will be hooked up to this global signal. However, every other block/CV will have its own inherited connections. If you apply this line to the cv: dbGetSigNetExpr(id) where the id is the id of the schematic view, you will get the inherited connections in this block. And although you can still access nsub from within that block, you cannot find it between the signals or the inherited connections. Now if you run the netlister from the AMS options menu, you will see the nsub with the other inherited connections listed there.

    My problem is that I want to get this nsub from within that small block.

    I hope I did it right this time :)

    Sherif

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • FormerMember
    FormerMember over 8 years ago

    Thanks Andrew for your reply. The thing I myself don't know what actually that signal is to describe it properly. I mean it should be a global signal since it has the ! attached to it and it ends up in the cds_globals module. But to describe it a bit clearer, I will try and approach it like this:

    So a top cell has a main voltage source that is defined as nsub!, it goes all the way down with the hierarchy with each cell. Whenever you define a source and give it the name nsub, it will be hooked up to this global signal. However, every other block/CV will have its own inherited connections. If you apply this line to the cv: dbGetSigNetExpr(id) where the id is the id of the schematic view, you will get the inherited connections in this block. And although you can still access nsub from within that block, you cannot find it between the signals or the inherited connections. Now if you run the netlister from the AMS options menu, you will see the nsub with the other inherited connections listed there.

    My problem is that I want to get this nsub from within that small block.

    I hope I did it right this time :)

    Sherif

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information