How to fix the CDF termOrder mismatch

To prevent this problem from happening in the future, set:

envSetVal("auCore.misc" "updateCDFtermOrder" 'boolean t)

in your .cdsinit. This will prompt you to update the CDF term order any time the pins are changed in the symbol. There is another env var:

envSetVal("auCore.misc" "queryCDFtermOrder" 'boolean t)

that controls whether it prompts you. The default is that it prompts you - set this second var to nil if you don't want to be asked (but do want it to update automatically).

If you want to update your code to work on a category, you'd need to use the ddCat.* functions to read what's in a category. For example, ddCatGetCatMembers - search for that in the documentation.

Regards,

Andrew.

Hi, Andrew,

Thank you very much for the envSetVal suggestion which is the best and the simplest one to get rid of this problem in the future. I think my code can still be used to fix the existing termOrder mismatch problem. I will set this env var as well so it can prevent a simulation from running with existing cells with this problem.

envSetVal("asimenv.netlist" "updateCDFtermOrder" 'bool t)

Is there a SKILL function to check if a cell or a lib has the termOrder mismatch problem? It would be nice to see which cells have this problem before I blindly fix them in a lib.

TJ

envSetVal("asimenv.netlist" "updateCDFtermOrder" 'bool t) is not valid. Sorry for posting this before I try it out first. I was reading the Cadence Help version 02.10-p00:

    Virtuoso Analog Design Environment -> Virtuoso Analog Design Environment L User Guide -> Environment Variables -> ADE Simulation Environment .

There are 2 updateCDFtermOrder env vars in this section and the second one does not say which tool it belongs.

updateCDFtermOrder

If set to t, ADE L will automatically update the CDF termOrder when symbol changes that affect the terminal order are made. This will display additional dialog boxes asking you to accept or reject the change to the CDF termOrder.

 
Variable Type boolen
Default Value nil
Acceptable Values t, nil

After I dumped all env vars, I still can not figure out which tool.partition I should use. Which tool.partition should I use?

Thanks,
TJ

TJ,

The fact that the same env var appears twice is just a typo on the doc - one says "boolen" rather than "boolean" for some reason.

However, I don't know why you used "asimenv.netlist" as the tool.partition. I didn't say that in my earlier post - I said "auCore.misc" which is what it says in the documentation. Prior to IC5141 (e.g. in IC5033) it used to be in asimenv.misc (not asimenv.netlist), but certainly since IC5141 base release in 2004 it has been in auCore.misc - which is what the documentation and my earlier post says.

Also, the third argument should be 'boolean not 'bool (also look at what I wrote earlier).

I am not aware of any existing built-in function that determines whether the termOrder in the CDF is consistent with the current terminals. There is the function (which is private) which detects whether the current CDF is different from the cellView in the current window - but it's both private and also requires a window to be open. So probably not the best choice. Easy enough to write your own though which gets the termOrder from each of the simInfo in the CDF and compares with the terminals in the specified cellView.

Regards,

Andrew.

Hi, Andrew,

Thank you for making it clear that the second one is a typo.

I took asimenv.netlist from customizeTermOrder which is right below the second updateCDFtermOrder in the documentation. I realized I took the wrong one only after I tried it and it did not work. The descriptions of the two updateCDFtermOrder are different which made me think that the same env var can exists in two different tool.partitions to serve two different purposes specific to the tools themselves.

TJ