CDF simulation parameters do not update accordingly?

I forget to mention: I am using IC 5.1.0

 There is a nice SourceLink Solution #11123666 for that.

http://support.cadence.com/wps/myportal/cos/COSHome/viewsolution/!ut/p/c5/dY1LboMwAAXPkgMgG5OAWToOEGOg_BQ-G2QBTQnEhjS0Uk9fcoDMW46eBtRgmxQ_w1U8ByXFBEpQm42OPKrzPbQ_aIQhw2bE04sDN0DxepgNfAOBoAK19fII6RjanpsfIaOc-dgyEOQmuEj1uG-lHJR-Ox9PI_l1SJkwiGTdsigIM61bYjsZvrJe4gwdujPbw3SNHzoKr81aEW0VziHwjZ4aMue3gS_CSau1W57KPIkqLqok0D41aypa-8a9ifrfTairkc2tmFzcehSpHYjO6t6DeZR_Lia7f_19frU!/dl3/d3/L2dBISEvZ0FBIS9nQSEh/

Bernd

Sorry I am a graduate student and have no access to this link. I use the school's Cadence and have no idea how to apply for the access of support.cadence.com

Is there any other link I can refer to?  Or could you briefly describe hwo to do it?

Million thanks !!

 Sorry I was not aware the people who have acces to this form do not have acces to the

Cadence support page.

If you update the pins in the symbol directly, for the defaults settings, the CDF simInfo 

is not updated acordingly.

This can be workaround by creating a new symbol form the schematic view, but

chosing the modify option and let the CDF been update.

Also the default behaviour can be change by setting the env variable:

in the .cdsenv:

auCore.misc updateCDFtermOrder boolean t

OR place following in .cdsinit file:

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

 You may look for this variable in the documentation.

Bernd

PS: Andrew if you track this is there good a way to enter  the postings in plain text

and get them well formated, rahter than this ugly html style?

You mean to solve my problem now I have to create every symbol view again?!   Wow .......

One question: you mentioned that the CDF information will not be updated if I change the pin in the symbol directly? But the real case is that I did change the pin name in the schematic, too.  Will this schematic update not update the CDF information accordingly?

Thank you !

The point is that if you update the pins on the schematic, you're going to have to update the symbol anyway because netlisting will fail if there's a mismatch between the symbol and schematic pins. So having the CDF update based on the symbol makes sense - that's what is going to be used to control netlisting.

Note that these are warning messages. If it detects that the termOrder information is wrong, it tells you, and discards the information and netlists using a built-in default order algorithm. It just warns you so that you know the order in the netlist is not what it was specified in the CDF, because that's wrong.

I don't particularly want to post the whole solution here (you should be able to get access to this somehow even as a university), but you could just use:

artGenerateHierSymbolCDF(geGetEditCellView())

from your schematic (schematic's best, because this will ensure any pPar() expressions in your schematic also populate the parameters section in the CDF). You could even have this on a bindkey if you need to do it a lot.

Regards,

Andrew.