• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Error about Environment Variable settings

Stats

  • Locked Locked
  • Replies 17
  • Subscribers 143
  • Views 23472
  • 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

Error about Environment Variable settings

wgtkan
wgtkan over 6 years ago

Hello,

After doing an update to the new pdk I get the following error. I think It comes from my .csinit file. It is asking about the EV variable of GF_PDK_HOME not being set.

And many other errors that come from the .cdsinit.

Please see attached.

Thank you always.

  • Cancel
  • mbracht
    mbracht over 6 years ago in reply to wgtkan

    look at your .cdsinit above - you do not(!!) issue a setShellEnvVar(..) - you do

    if(gfPdkHome = getShellEnvVar("GF_PDK_HOME=/home/grps/ef-test/GLF8HP/130HPSIGE-8HP/") then...

    it is supposed to be:

    setShellEnvVar("GF_PDK_HOME=/home/grps/ef-test/GLF8HP/130HPSIGE-8HP/")
    if(gfPdkHome = getShellEnvVar("GF_PDK_HOME") then
    ...

    And better yet you set it in the bash ever before you launch virtuoso

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wgtkan
    wgtkan over 6 years ago in reply to mbracht

    Thank you so much for your help. I get it know.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wgtkan
    wgtkan over 6 years ago in reply to wgtkan

    What is the alternative in .cdsenv? How do we write the same command in .cdsenv?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to wgtkan

    There isn't an alternative to do this in the .cdsenv file, and there is no "command" you can use in the .cdsenv file. Mainly because it doesn't make sense because:

    • .cdsenv is a file containing the names and values of Cadence-specific variables. This is not "code" (it's not a programming language), and these variables are not UNIX environment variables - they are settings specifically for Cadence tools (in particular Virtuoso)
    • .cdsinit is a file containing SKILL code executed at startup. Because it's written using a programming language, you can perform a wide range of different operations, including interacting with UNIX environment variables as we've shown above.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wgtkan
    wgtkan over 6 years ago in reply to Andrew Beckett

    I see. 

    So before launching a virtuso I have to give either of the following commands at the unix prompt?

    Type this at the working directory

    1. For bash
    export GF_PDK_HOME=/home/grps/ef-test/GLF8HP/130HPSIGE-8HP/V1.8_1.1HP

    2. For csh

    setenv GF_PDK_HOME /home/grps/ef-test/GLF8HP/130HPSIGE-8HP/V1.8_1.1HP

    Thank you so much Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to wgtkan

    Of course, you could also set it wherever you're setting up the path for the software, the environment variables for the licensing and so on. That might be done in your ~/.cshrc, ~/.login or ~/.bashrc, or you might be using modules or something similar to configure your UNIX environment. You don't necessarily need to type it each time, and you could (as both Max and I have said) put a setShellEnvVar() call in your .cdsinit to set the environment variable there.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wgtkan
    wgtkan over 6 years ago in reply to Andrew Beckett

    Thank you very much indeed Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
<

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information