• 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. Defining power supply symbols

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 18147
  • 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

Defining power supply symbols

markbeck
markbeck over 14 years ago

I'm trying to do something which is common in BiPolar analog design, but not as much in CMOS design.  I'm trying to figure out how to create a symbol which will allow me to define a net's connectivity when placed upon that net. 

For example:
I have a schematic and symbol which have VCC and VEE defined as ports (Note: they are defined as ports to make power supply modeling easier).  To make the schematic more readable, I wish to place instance symbols which represent VCC and VEE inside the schematic which will connect those nets to the actual VCC and VEE power ports.

I know that it is possible, and I think that it was done in the past using netset, but I can't seem to find any information about netset which doesn't pertain to defining a global power and ground supply (something that I do NOT want).

Any ideas?
Mark

 

  • Cancel
Parents
  • markbeck
    markbeck over 14 years ago

    Ok, while the above method worked, I was still getting warnings in the CIW when netlisting.

    I found that the nlAction = ignore needed to be added as a property to the schematic (It has no real effect inside the CDF parameters).  Then everything worked as desired (as far as I can tell today)

     sigh...

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • markbeck
    markbeck over 14 years ago

    Ok, while the above method worked, I was still getting warnings in the CIW when netlisting.

    I found that the nlAction = ignore needed to be added as a property to the schematic (It has no real effect inside the CDF parameters).  Then everything worked as desired (as far as I can tell today)

     sigh...

     

    • 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