Problem in Analog environnement

Dear All,

I have a problem in cadence Analog Environnement, it can not be opened
and this message appear in CIW:
*Error* sevFullMenuItem: extra arguments or keyword missing - (!
_spectreCheckFeature('spectre_analysisRF_TaskManager) then
("Parametric Analysis" ?callback sevParametricTool('sevSession1) ?form
t ... ) ("Corners" ?callback ((UartLoadPcfFiles) &&
sevCornersTool(&)) ?form t ... ) ("Monte Carlo" ?callback
sevMonteCarloTool('sevSession1) ?form t ... ) ... )
*WARNING* A Skill error occurred in function artMenuTrigger

Could you help me please!?

Regards,

Karim.

 

karim wrote, on 05/18/10 10:26:

Hi Karim,

It sounds as if you have somethng in your environment which is customizing the
ADE menus files, and the code is bad.

Try typing "cdswhich menus" and then looking inside any resulting directories
for spectre.menus, simui.menus, etc.

Quite possibily you are using a menus file not suited to the version of the
Cadence IC tools you're using?

Regards,

Andrew.

 

Yes I get the same error when booting up the HCMOS 9GP process from ST
Microelectronics. All other HitKits work fine (AMS, UMC etc)
Any help on getting this running would be great.
Ed

 

How exactly does one do a "cdswhich"? In icfb and my terminal I get
'unknown command'. Under Desgn Kit --> Design Kit Unix Interface I
only get ST microelectronics layout verification settings and not a
unix terminal.

Under the HCMOS9GP installed directory (not the working directory) we
have ArtistKit_4.6/menus which contains spectre.menus eldo.menus and
all the others.

One question I have is that although my new working directory for the
HCMOS9GP run is entirely in a different directory, it seems to still
be referencing files in my personal working directory. It seems my
upper level user home directory also contains menus/spectre.menu etc.
Could it be that my personal working directory is getting bogged down
with too many files. The problem is that even if you start cadence in
a particular working directory it seems to create and change files
higher up in the directory structure.

I have no idea where to go from here, apart from a back up and nuclear
option.
Ed

 

How exactly does one do a "cdswhich"? In icfb and my terminal I get
'unknown command'. Under Desgn Kit --> Design Kit Unix Interface I
only get ST microelectronics layout verification settings and not a
unix terminal.

Under the HCMOS9GP installed directory (not the working directory) we
have ArtistKit_4.6/menus which contains spectre.menus eldo.menus and
all the others.

One question I have is that although my new working directory for the
HCMOS9GP run is entirely in a different directory, it seems to still
be referencing files in my personal working directory. It seems my
upper level user home directory also contains menus/spectre.menu etc.
Could it be that my personal working directory is getting bogged down
with too many files. The problem is that even if you start cadence in
a particular working directory it seems to create and change files
higher up in the directory structure.

I have no idea where to go from here, apart from a back up and nuclear
option.
Ed

 

How exactly does one do a "cdswhich"? In icfb and my terminal I get
'unknown command'. Under Desgn Kit --> Design Kit Unix Interface I
only get ST microelectronics layout verification settings and not a
unix terminal.

Under the HCMOS9GP installed directory (not the working directory) we
have ArtistKit_4.6/menus which contains spectre.menus eldo.menus and
all the others.

One question I have is that although my new working directory for the
HCMOS9GP run is entirely in a different directory, it seems to still
be referencing files in my personal working directory. It seems my
upper level user home directory also contains menus/spectre.menu etc.
Could it be that my personal working directory is getting bogged down
with too many files. The problem is that even if you start cadence in
a particular working directory it seems to create and change files
higher up in the directory structure.

I have no idea where to go from here, apart from a back up and nuclear
option.
Ed

 

Edward Fisher wrote, on 06/01/10 14:13:

Ed,

Sorry, overlooked this.

cdswhich probably doesn't work because you've got some environment which wraps
the Cadence commands and so doesn't put them in your UNIX path by default.

In the CIW you could do:

ddGetStartupAll("menus")

This is often controlled by a "setup.loc" file which says where to look for
files, and that may get overridden by your design environment, maybe in the
wrapper by which you're starting the Cadence tools.

Even in the standard setup.loc file, it would look in $HOME. If you look in:

<instDir>/share/cdssetup/setup.loc

you'll see it references $HOME.

For more info on cdswhich, setup.loc and the Cadence Search File method, look in:

<ICinstDir>/doc/caiuser/caiuser.pdf

Regards,

Andrew.