how can i set environmental variables in .cdsenv file

Venu,

I can find no record of either of those cdsenv variables, in any release. They're certainly not current in either IC5141 or IC615, and there's no mention of them in any CCR or Service Request. I even checked in some older releases in the documentation (e.g. IC446), but nothing.

So that's why you get the warnings - these are meaningless variables as far as the tool is concerned. The closest I have found are these:

layout keepFirstTermName boolean ni
graphic displayPinNames boolean t
layout displayPinNames boolean nil

The graphic/layout bit is where there is a generic capability for all graphic editors, and then a layout variable is specifically for maskLayout views - so is more specific and will override any graphic setting.

Regards,

Andrew.

hi  Andrew,

Yes as u said i didnot found that commands in my Directory/IC5141/tools.lnx86/dfII/samples/.cdsenv file. But in my layout when i select  create pin option then a window  appears and there is need to ON the buttons of Keep First Name and Display Pin Name in that window. I want to on these buttons automatically when i start icfb. But i dont know how to achieve it.

Thank you

Venu.

Venu,

The env vars are keepFirstTermName and createPinLabel (both under "layout"), but the form is not initialized with keepFirstTermName - createPinLabel does however have an effect (this is for IC5141). In IC615, both cdsenv variables can be used to seed the form - so it's a limitation of IC5141.

You can then use:

envSetVal("layout" "keepFirstTermName" 'boolean t)
envSetVal("layout" "createPinLabel" 'boolean t)

Regards,

Andrew.

 hi,

yes i got  that variables what i need. Now my problem is Cut Spacing(via to via space) of contacts are as 0. But i need 0.28 between that contacts.

Thankyou

venu

Was that a further question? Or simply a comment? If it was a question, there wasn't really enough information to be able to answer it.

Regards,

Andrew.

Clearly nobody reads the forum guidelines... (appending a question onto a only loosely related 4 year old thread is not the best strategy for it being answered)

It's not weAutoDropViasForOverlaps() anyway. It's envSetVal("layout" "weAutoDropViaForOverlaps" 'boolean t) (so it's an environment variable, and there's no "s" after Via).

This works provided that the wire being routed and the pathSeg being crossed are on the same net. It doesn't drop vias on any random nets that you happen to cross over...

Of course, you could define a bind key that toggles this:

hiSetBindKey("Layout" "ShiftCtrl<Key>a" "envSetVal(\"layout\" \"weAutoDropViaForOverlaps\" 'boolean !envGetVal(\"layout\" \"weAutoDropViaForOverlaps\"))")

This also requires IC616 ISR5 or later.

Regards,

Andrew.

Thank u, andrew 

My problem solved. Initially I was using "ui" instead of "layout" (in envSetVal("layout" "weAutoDropViaForOverlaps" 'boolean t)). Actually when we have to use that "ui".