Confused by setup and recent changes in software

[Stefan Joeres]

Hi altogether,

our university is dealing with different Design Kits from industry partners
(e.g. ST, Infineon, Atmel,...). The setup for each Project is done by the
use of the module-package for linux (FC 4).

Actually we're getting more and more confused from the setups of the current
IC, IUS and MMSIM releases.

Can you state and explain your individual setup of

Environment Variables ( CDSHOME, CDS_INST_DIR, IC_INST_DIR,
CDS_Netlisting_Mode, PATH & LD_LIBRARY_PATH,...)

and your settings for the cds.lib (and hdl.var if necessary) ?

Desired releases here would be IC 5.10.41.USR4, MMSIM 61 & 60, IUS 54 to
58.2P2, ASSURA 3.14

The target applications include
transistor level design & layout of mixed signal ICs
behavioural modelling using SysVerilog, VAMS, VHDL and matlab/simulink
coupling.

Maybe there's a good howto on the setup ? The documentation from cadence
itself typically doesn't cover the combination of the different tools (at
least as far as I've found them ...) .

Regards,

Stefan Joeres

 

[Bernd Fischer]

Dear Stefan,

The setup for each Project is done by the
use of the module-package for linux (FC 4).

We use the module package too.

Actually we're getting more and more confused from the setups of the current
IC, IUS and MMSIM releases.

That's nothing new ;-)

Can you state and explain your individual setup of
Environment Variables ( CDSHOME, CDS_INST_DIR, IC_INST_DIR,
CDS_Netlisting_Mode, PATH & LD_LIBRARY_PATH,...)

Try to

CDS_INST_DIR
- Cadence Design Framework II Configuration Guide, says
In 4.4.5 and later, Cadence executables ignore this environment variable.
Use prior to 4.4.5 only.
- We don't use this variable

CDSHOME
- Also have a look at Cadence Design Framework II Configuration Guide,
it's a replacement for CDS_INST_DIR but not necessarily to use, it's
more intent to make live easier. Points to 'yourInstallDirPath'
- we use DFIIHOME

IC_INST_DIR
- Never heard of, not aware of.

CDS_Netlisting_Mode
- Virtuoso Analog Design Environment User Guide, says
the CDS_Netlisting_ModeGo to next match variable controls
how parameter values on components that use CDF and AEL are
interpreted during netlisting
- We have set it to "Analog" per default.

PATH & LD_LIBRARY_PATH
Excerpt from our module files:

- For DFII
append-path PATH $env(DFIIHOME)/tools/bin
append-path PATH $env(DFIIHOME)/tools/dfII/bin
append-path LD_LIBRARY_PATH $env(DFIIHOME)/tools/lib

- For MMSIM
append-path PATH $env(MMSIMHOME)/tools/bin
append-path LD_LIBRARY_PATH $env(MMSIMHOME)/tools/lib
append-path LD_LIBRARY_PATH $env(MMSIMHOME)/tools/ultrasim/lib

- For IUS
append-path PATH $env(LDVHOME)/tools/bin
append-path LD_LIBRARY_PATH $env(LDVHOME)/tools/lib

-For Assura
append-path PATH $env(ASSURAHOME)/tools/assura/bin


Where every variable *HOME, except ASSURAHOME is just to see like explained for
CDSHOME above.

Hope this helps.

Bernd

 

[Pete nospam Zakel]

In article <4p71cpFhjev2U1@individual.net> Bernd Fischer <bernd.fischer@xignalerif.r'4054-50];p5.de> writes:

CDS_INST_DIR
- Cadence Design Framework II Configuration Guide, says
In 4.4.5 and later, Cadence executables ignore this environment variable.
Use prior to 4.4.5 only.
- We don't use this variable

To be more accurate, CDS_INST_DIR can be used in cds.lib and other setup
files to indicate the Cadence install directory. It is a predefined keyword
starting in the 4.4.5 release and it's value is not affected by defining an
environment variable of the same name. It will always be defined internally
by the application for the installation directory the application is being
run from.

Note in later releases there is a new syntax for indicating the installation
hierarchy directory.

-Pete Zakel
(phz@seeheader.nospam)

"Computers are not intelligent. They only think they are."