The Designer's Guide Community Forum

The Designer's Guide Community Forum
https://designers-guide.org/forum/YaBB.pl
Design Languages >> Verilog-AMS >> verilog-ams variable in cadence calculator
https://designers-guide.org/forum/YaBB.pl?num=1273580425

Message started by Cri Azzolini on May 11^th, 2010, 5:20am

Title: verilog-ams variable in cadence calculator
Post by Cri Azzolini on May 11^th, 2010, 5:20am

Hi all,
can I pick up a verilog-ams variable from cadence caiculator?
I would like to plot its behaviour along with other signals (voltage/currents).
On the Calculator user-reference doc I was not able to find out how to do that.

Any hint?
Thanks,
Cristiano

Title: Re: verilog-ams variable in cadence calculator
Post by Marq Kole on May 12^th, 2010, 8:03am

Hi,

If you open the results browser from the calculator and go to the variable you want to use (assuming you have saved it to the PSF with the saveahdlvars option in Spectre) you can right-click the mouse button when you have selected it. This will bring up a drop-down menu where the bottom item is "calculator". Clicking on this will make the variable available in the calculator. You get an entry starting with "getData" - I'm not sure this is easily to reproduce in an OCEAN script but it will get you the data you need in the calculator.

Cheers,
Marq

Title: Re: verilog-ams variable in cadence calculator
Post by Cri Azzolini on May 12^th, 2010, 8:26am

Hi Marq,
actually I cannot see the Verilog-A variables there. I can see only the design variables (I checked the "saveahdlvars all" option).
Does it work for AHDL only?

Thanks,
Cristiano

Title: Re: verilog-ams variable in cadence calculator
Post by Marq Kole on May 14^th, 2010, 12:50am

Hi Cri,

Then I think you should first concentrate on getting the Verilog-A variables in the PSF. It has nothing to do with AHDL - that has been supported since Spectre 5.x. The saveahdlvars is really for Verilog-A variables.

Are you running a transient? I've seen this problem before - but I don't exactly remember how to solve it. You should probably check the log file and see if it tries to save stuff in SST2 format (which it does by default for transient-only). You could then try to force the use of PSFbin by a command-line option or by adding a DC analysis. If this doesn't work check with Cadence...

Marq