Stats

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

 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.

 

Parents

  • Happy Days!

     Item 1:
    I'm currently using (for now) a formInitProc in the cdf (to stuff all the W/L's with default values so that the symbols are technology independent) and I was unable to put the code for the procedure into that field - it would *only* hold the NAME of a procedure. The procedure itself needed to be in a file that I had to load (in fact, that's the current thorn in my approach). I'd have thought doneProc would be the same way. In fact, by setting the doneProc as you suggest, I see this in the icfb window all the time:

    *WARNING* icInstMoveTrigFunc: '{if(cdfParseFloatString(cdfgData->WN1->value)==cdfParseFloatString(cdfgData->WN2->value) && cdfParseFloatString(cdfgData->LN1->value)==cdfParseFloatString(cdfgData->LN2->value) cdfgData->flag->value=0 cdfgData->flag->value=1)}' is not a function.

    Item 2:
    In every callback, I currently have:

      evalstring(cdfgData->flag->defValue) \

    and I was relying on that to deal with evaluating the flag parameter (in the same way that I also evalstring all the other parameters like size1, size2 etc). However, I have defined flag as per my recent post, and I'm seeing errors in the callbacks. This is presumably because I'm doing an evalstring on flag but flag (unlike the rest) is declared as an int instead of a string. It's defValue being a string is messing things up. So I declared flag as string and set it to "0" & "1" instead. I also modified the ILLabel if statement to test for "1" instead of 1 and ... it works!!!

    At this point I am a very happy camper :-). Thank you (all of you) very much for your help. But wait - there's more...

    Going back to item 1 for a moment, I'd be in hog heaven if I could find ANY way to stuff the code I need into formInitProc instead of referencing a file that people must load. Is there any back door way to do this?

    and is there a more compact way to define the ILLabel expression below other than reducing the size of the parameter names. This is to keep effective size of the instantiated cell to a minimum.

    {if(ilInst~>flag=="1" ilInst~>name ilInst~>size1)}

Reply

  • Happy Days!

     Item 1:
    I'm currently using (for now) a formInitProc in the cdf (to stuff all the W/L's with default values so that the symbols are technology independent) and I was unable to put the code for the procedure into that field - it would *only* hold the NAME of a procedure. The procedure itself needed to be in a file that I had to load (in fact, that's the current thorn in my approach). I'd have thought doneProc would be the same way. In fact, by setting the doneProc as you suggest, I see this in the icfb window all the time:

    *WARNING* icInstMoveTrigFunc: '{if(cdfParseFloatString(cdfgData->WN1->value)==cdfParseFloatString(cdfgData->WN2->value) && cdfParseFloatString(cdfgData->LN1->value)==cdfParseFloatString(cdfgData->LN2->value) cdfgData->flag->value=0 cdfgData->flag->value=1)}' is not a function.

    Item 2:
    In every callback, I currently have:

      evalstring(cdfgData->flag->defValue) \

    and I was relying on that to deal with evaluating the flag parameter (in the same way that I also evalstring all the other parameters like size1, size2 etc). However, I have defined flag as per my recent post, and I'm seeing errors in the callbacks. This is presumably because I'm doing an evalstring on flag but flag (unlike the rest) is declared as an int instead of a string. It's defValue being a string is messing things up. So I declared flag as string and set it to "0" & "1" instead. I also modified the ILLabel if statement to test for "1" instead of 1 and ... it works!!!

    At this point I am a very happy camper :-). Thank you (all of you) very much for your help. But wait - there's more...

    Going back to item 1 for a moment, I'd be in hog heaven if I could find ANY way to stuff the code I need into formInitProc instead of referencing a file that people must load. Is there any back door way to do this?

    and is there a more compact way to define the ILLabel expression below other than reducing the size of the parameter names. This is to keep effective size of the instantiated cell to a minimum.

    {if(ilInst~>flag=="1" ilInst~>name ilInst~>size1)}

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.