Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 20910
  • 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

when is .cdsinit.local loaded?

SteveRFIC

I have a questions on .cdsinit.local file

I did some customization (bindkeys etc.) in .cdsinit.local file and I put the file in my cadence working directory.

When I start cadence, when is .cdsinit.local loaded?

What I found is that some of the customization gets overwritten by scripts loaded later from the project/company environment. As a results, I have to load again my bindkeys after cadence fully starts.

Is there a way to put .cdsinit.local at the end of the list of files loaded when cadence starts, so that it won't get overwritten?

Or is there a way to use the pop up window (like the what's new window)  to trigger the loading of some skill code?

Thanks! 

Parents

  • There are two SKILL files that get loaded - .cdsinit and .simrc. However, ,simrc is only loaded when netlisting is performed, and customisations in their should be limited to just those related to netlisting (it's also loaded multiple times per session).

    There's another file, libInit.il, which lives in a library and is loaded the first time that a library is accessed. That's normally intended for library-specific actions.

    So in general I'd say you should sort out with your CAD team a way of loading customisation in the order you need.

    In general, the rules for loading the .cdsinit are:

    1. If there is no csfLookupConfig file which has an 'INCLUDE .cdsinit' line in it, the search order is:
      1. <ICinstDir>/tools/dfII/local/.cdsinit
      2. ./.cdsinit
      3. ~/.cdsinit
    2. If csfLookupConfig has been defined, it searches using the "setup.loc" order. You can check this with:
      cdswhich -lookupconfig .cdsinit
      This will tell you if .cdsinit has been configured to be found via CSF (cdswhich csfLookupConfig will check the file and you can look at the contents) and if so, which path was found. The order can be found by looking at the contents of whatever "cdswhich setup.loc" returns.

    In both situations, whichever file is found first in the search sequence is the only one loaded (by virtuoso). It does not load any later files in the sequence (unless that has been coded into the first .cdsinit file it loads).

    Regards,

    Andrew.

Reply

  • There are two SKILL files that get loaded - .cdsinit and .simrc. However, ,simrc is only loaded when netlisting is performed, and customisations in their should be limited to just those related to netlisting (it's also loaded multiple times per session).

    There's another file, libInit.il, which lives in a library and is loaded the first time that a library is accessed. That's normally intended for library-specific actions.

    So in general I'd say you should sort out with your CAD team a way of loading customisation in the order you need.

    In general, the rules for loading the .cdsinit are:

    1. If there is no csfLookupConfig file which has an 'INCLUDE .cdsinit' line in it, the search order is:
      1. <ICinstDir>/tools/dfII/local/.cdsinit
      2. ./.cdsinit
      3. ~/.cdsinit
    2. If csfLookupConfig has been defined, it searches using the "setup.loc" order. You can check this with:
      cdswhich -lookupconfig .cdsinit
      This will tell you if .cdsinit has been configured to be found via CSF (cdswhich csfLookupConfig will check the file and you can look at the contents) and if so, which path was found. The order can be found by looking at the contents of whatever "cdswhich setup.loc" returns.

    In both situations, whichever file is found first in the search sequence is the only one loaded (by virtuoso). It does not load any later files in the sequence (unless that has been coded into the first .cdsinit file it loads).

    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.