• 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. A rather unconventional schematic symbol question/issue

Stats

  • Locked Locked
  • Replies 25
  • Subscribers 126
  • Views 10977
  • 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

A rather unconventional schematic symbol question/issue

Composter
Composter over 16 years ago

 Hi,

 I'm using Cadence 5.1 and am trying to make some schematic symbols that display context dependent information when instantiated. Onthe symbol itself, I have several ILLabels such as "ilInst~>myvar" and I have edited the cdf such that "myvar" contains some skill code that evaluates to the string of what I want displayed on the symbol. I'm accessing the data about the selected instance through expressions like "cdfgData->width->value". Much of this is based on code I've seen used elsewhere and I've just adapted it to suit my needs.

 

So I'm running aground because I don't know how to access the instance name (as opposed tthe cell name) within an expression. I've already tried cdsName() but that does not return the current instance name of the selected instance. Can anybody out there please provide me with the skill magic to do this. I figure it has to be available via cdfgData but I don't the access name. Many thanks in advance.

 

  • Cancel
Parents
  • Composter
    Composter over 16 years ago

     I've been trying to hold back what I deem to be extraneous details because I didn't want to complicate the issue and scare away responders, and that turned out to be a mistake. Your solution, while I'm sure it works, requires all users of this cell to have a procedure loaded. Virtually all of the people in the company I work for do not want to deal with ANY special file loading - even if it's just a .cdsinit. Sigh. I'm looking for a solution that "just works", and that's why everything is embedded in the cdf parameters (because that's what I've been shown so far).

    I feel really bad that you spent time on a solution I can't use because of information I omitted. However, at this point I believe all the constraints have been mentioned.

    Now I'm starting to see why you chose that avatar ;-)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Composter
    Composter over 16 years ago

     I've been trying to hold back what I deem to be extraneous details because I didn't want to complicate the issue and scare away responders, and that turned out to be a mistake. Your solution, while I'm sure it works, requires all users of this cell to have a procedure loaded. Virtually all of the people in the company I work for do not want to deal with ANY special file loading - even if it's just a .cdsinit. Sigh. I'm looking for a solution that "just works", and that's why everything is embedded in the cdf parameters (because that's what I've been shown so far).

    I feel really bad that you spent time on a solution I can't use because of information I omitted. However, at this point I believe all the constraints have been mentioned.

    Now I'm starting to see why you chose that avatar ;-)

    • 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