Stats

  • Locked Locked
  • Replies 9
  • Subscribers 144
  • Views 21534
  • 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

how can i set environmental variables in .cdsenv file

venuuuuu

 hi all,

1) i trying to set some settings in my layout. Because of this i created a .cdsenv file in my home directory and write as following

layout  pinKeepFirstName    boolean      t
layout  pinDisplayPinName    boolean      t

When i starts icfb then following warning occurs. And variables what i need are not set. Iam using the version virtuoso 5141.

 *WARNING* envSetVal: Can't set the value of variable 'pinKeepFirstName', in tool[.partition] 'layout' - it has not been registered.

 *WARNING* envSetVal: Can't set the value of variable 'pinDisplayPinName',in tool[.partition] 'layout' - it has not been registered.

why it shows this warning.

2) what is the difference between graphic environment variables & layout environment variable.

please answer me if u know it.

Thank you

venu.

 

Parents

  • 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.

Reply

  • 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.

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.