How to disable those envSetVal warnings when calling ocean scripts?

I've never seen those warnings before. probeList is not a variable for any Cadence simulators - do you maybe have a third-party (non-Cadence) simulator integration in your environment which is maybe interfering with things? This shouldn't happen, but maybe it's not defined  properly? Or maybe the OCEAN script is for a third-party simulator and it's not being loaded properly? You didn't share the OCEAN script so it's hard to know...

Regards,

Andrew

Hi Andrew,

It is a simple ocean script.
I commanded out the simulator('spectre) when I posted the thred. But now even I enable the first sentense, the warnings are still there. Nothing changed.
This script does nothing important, but merely fetch the Gain value calculated from /psf data and saved it into a result file. No simulation is involved because the simulation was finished before.

By the way, I even tried to measure Gain in the ADE window, and simply saved the operation into a auto_gen.ocn script. Then I went to the command line and execute the saved auto_gen.ocn, those warnings are there as well.

Any hint on where I should go and check some setups to try to find out certain improper settings?

The original testSpectre.ocn:
;simulator( 'spectre )
openResults("/home/abc/simulation/Opamp_tb/spectre/schematic/psf/")

p=outfile("/home/abc/simulation/Opamp_tb/spectre/schematic/psf/resultsSpectre.txt" "w")
fprintf(p, "Hello!\n" )
selectResult('ac)

fprintf(p, "Gain:\n" )
Gain=value(dB20(-(VF("/Vout") / (VF("net3") - VF("/net5")))) 1 )
fprintf(p,"%f\n" Gain)

close(p)
printf("\n---End---\n")

Thanks,
Alex

Alex,

You didn't really answer my questions about third-party simulators, so I'm not sure.

Do the problems occur if you run virtuoso and then load the OCEAN script?

It's probably best if you contact customer support, and then one of the team can have a webex to look at the problem with you. Otherwise we'll be stabbing around in the dark.

Regards,

Andrew.

Hi Andrew,

I did not manually set using a different simulator. It should be Spectre by default.

Anyway, I have found something interesting.

I have three source file, the .cshrc, .cshrc_5d1, and .cshrc_6d16. The .cshrc will be automatically sourced when log in our linux server.

For runing different tools with different technologies, I will source different source files.

For 0.18um tech. tsmc tool, I source the 5.1 version, and for the 65nm tech tsmc tool, I source 6.16 version. Now my post is about ocean script runing for operation in tsmc65nm.

So I sourced the .cshrc_6d16 incrementally on the default .cshrc. And the warnings in the original thread post appeared following the mentioned source manner.

If I changed the source file, from 6.16 to 5.1, then I do not have any of these warnings. Problem seems solved, but I cannot get correct Gain value. I guess I have to use IC6 version to work with 65nm tool.

This is a conflict:     .cshrc_5d1 is good without any warning but bad in getting data or running simulation by using ocean script; 

.cshrc_6d14 is bad with warnings but good in fetching data and runing simlation.

Could you please look at the three source files, and to see if you can see some tricks or mistake I made. 

If still you feel I need to contact a customer support to look at this, please keep suggesting it again. Thanks in advance.

---------------------------------------------------------------------------------

.cshrc:
###: Default .cshrc will be automatically sourced when log in. 
setenv HOME /home/abc

setenv LM_LICENSE_FILE 6055@cmcstc01.ca
setenv CDS_LICENSE_FILE 6055@cmcstc01.ca
setenv SNPSLMD_LICENSE_FILE 6055@cmcstc01.ca
setenv MGLS_LICENSE_FILE 8056@cmcstc01.ca

setenv CDS_Netlisting_Mode "Analog"
setenv CDS_AUTO_64BIT NONE
setenv LD_LIBRARY_PATH ""

source /CMC/scripts/cadence.icc.11241.usr5.csh
#: Cadence nc-stuff is located here.
source /CMC/scripts/cadence.ius08.20.024.csh
#: Synopsys dc_shell stuff is located here.
source /CMC/scripts/synopsys.2010.03.csh
set path = (/usr/bin $path /local/bin ./)
----------------------------------------------------------------------------------------------------------
.cshrc_5d1:
###: Cadence ICFB version 5.1.0 for 0.18um tech.   //  [No such warning version]

setenv LM_LICENSE_FILE 6055@cmcstc01.ca
setenv CDS_LICENSE_FILE 6055@cmcstc01.ca
setenv SNPSLMD_LICENSE_FILE 6055@cmcstc01.ca
setenv MGLS_LICENSE_FILE 8056@cmcstc01.ca

source /CMC/scripts/cadence.ic.5141.usr6.csh
source /CMC/scripts/cadence.icc.11241.usr5.csh
source /CMC/scripts/cadence.mmsim.72.109.csh
setenv LD_LIBRARY_PATH $CDSHOME/tools/lib:$LD_LIBRARY_PATH
----------------------------------------------------------------------------------------------------------------------
.cshrc_6d14:
###: Cadence Virtuoso 6.16 for 65nm tech. is located here. //  [Have such warning version]

setenv LM_LICENSE_FILE 6055@cmcstc01.ca.
setenv CDS_LICENSE_FILE 6055@cmcstc01.ca
setenv SNPSLMD_LICENSE_FILE 6055@cmcstc01.ca
setenv MGLS_LICENSE_FILE 8056@cmcstc01.ca

source /CMC/scripts/cadence.ic06.16.090.csh
#source /CMC/scripts/cadence.ic06.14.005.csh
source /CMC/scripts/mentor.calibre.2011.4.csh
source /CMC/scripts/cadence.mmsim07.20.109.csh
setenv LD_LIBRARY_PATH $CDSHOME/tools/lib:$LD_LIBRARY_PATH

Regards,

Alex

Alex,

This doesn't really tell me anything useful. For a start there are scripts which are being sourced that you don't show, plus the difference may well be in the .cdsinit used for the particular versions. It may just be that there's a third party integration that isn't being loaded in IC5141. Or it might be something else - who knows?

As I said before, customer support is probably the best channel to be able to help you out here - we'll have to observe your set up to find out what is causing this.

Regards,

Andrew.