Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 10474
  • 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

different results from spice in

MReza123

Hi, 

I am trying to import a cdl netlist. When I use the GUI in virtuoso (ICADVM20.1), the generated schematic is correct. When I use the command line (spiceIn -param  with parameter file saved from the working GUI), the width and length of transistors are wrong. Interestingly, the spicein.log file is almost the same between the two.

Does anyone know what could be the source of discrepancy? My guess is the CDF callback is not automatically trigged after running spice-in from command line. If that is true, how should I resolve this?

CDL:

*.BIPOLAR
*.RESI = 0
*.RESVAL
*.CAPVAL
*.DIOPERI
*.DIOAREA
*.EQUATION
*.SCALE METER
*.MEGA
.PARAM

.SUBCKT inverter VDD VSS inp outp
*.PININFO inp:I outp:O VDD:B VSS:B
MM0 outp inp VSS VSS nch l=40n m=6 simM=2 Wfg=250.0n fingers=3
MM1 outp inp VDD VDD pch l=40n m=6 simM=2 Wfg=250.0n fingers=3
.ENDS

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

With GUI: wfinger=250n, l=40n, fingers=3, m=2  --> w=750n and total_m=6

With command line: wfinger=250n, l=40m, fingers=3, m=2 --> w=100n and total_m=1  which is very very weird!!!

----

  • Andrew Beckett

    Please contact customer support. I think we need to see this in the context of the actual PDK you're using.

    Andrew

  • MReza123
    in reply to Andrew Beckett

    Thanks Andrew. I realized that after running spicein from command line, CDF call back is not automatically triggered. 

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.