• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. creatnetlist does not netlist transistors correctly

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 13682
  • 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

creatnetlist does not netlist transistors correctly

naderi
naderi over 14 years ago

 Hello,

 I am using following set of ocean commands when icfb is in -nograph mode. However, the final netlist.scs is not correct. The transistor model is set to subcircuit while it should be nfet or pfet in this technology. Is there any fix for the problem?

Thanks, Ali

ocnWaveformTool( 'wavescan )
simulator( 'spectre )
resultsDir( "..../simulation/amp_test/spectre/schematic" )
modelFile(
    '("/kits/cmosp13.V1.7.0.0DM/IBM_PDK/cmrf8sf/V1.7.0.2DM/Spectre/models/design.scs" "")
    '("/kits/cmosp13.V1.7.0.0DM/IBM_PDK/cmrf8sf/V1.7.0.2DM/Spectre/models/allModels.scs" "tt")
)
design( "Mylib" "amp_test" "schematic")
createNetlist()

RESULT:

Netlisting Statistics:
    Number of components:   22

    Elapsed time:          3.0s (7.33/s)
Errors: 0    Warnings: 0
      ...successful.
compose simulator input file...
      ...successful.

 

 

The netlist.scs:

 // Generated for: spectre
// Generated on: Feb 15 10:52:10 2011
// Design library name: Mylib
// Design cell name: amp_test
// Design view name: schematic
simulator lang=spectre
global 0 vssd! vdda! vssa! vddd!
include "/kits/cmosp13.V1.7.0.0DM/IBM_PDK/cmrf8sf/V1.7.0.2DM/Spectre/models/design.scs"
include "/kits/cmosp13.V1.7.0.0DM/IBM_PDK/cmrf8sf/V1.7.0.2DM/Spectre/models/allModels.scs" section=tt

// Library name: Mylib
// Cell name: amp
// View name: schematic
subckt amp in ip outp
    C1 (bp1 vssa!) capacitor c=500.0f
    C0 (bp2 vssa!) capacitor c=500.0f
    I0 (bp2 vssa!) isource dc=pPar("I0")
    T26 (net039 net039 vssa! vssa!) subcircuit l=240.0n \
        w=pPar("mn")*160.0n nf=1 m=1 par=1 ngcon=1 \
        ad=(pPar("mn")*160.0n*5.5e-07) as=(pPar("mn")*160.0n*5.5e-07) \
        pd=(2*pPar("mn")*160.0n+2*5.5e-07) \
        ps=(2*pPar("mn")*160.0n+2*5.5e-07) nrd=2.2e-07/pPar("mn")*160.0n \
        nrs=2.2e-07/pPar("mn")*160.0n rf_rsub=1 lstis=1 lnws=0 rgatemod=0 \
        rbodymod=0
...

  • Cancel
  • skillUser
    skillUser over 14 years ago

     Hi Ali,

    I would guess that you are using IC5141 since you mentioned "icfb -nograph" - since icfb/virtuoso performs the netlisting it is quite important to mention the version, and probably the exact subversion too, since issues like this might crop up and then later get fixed...

    Does the device instance model say "pfet" or "nfet", and what does the cell CDF for either P or N instance look like for the spectre simulator in the simulation information section?

    A quick search in our database did not yield anything, but additional details would be helpful.  Have you considered entering a ticket with IBM's PDK support?  Or a Service Request with Cadence Customer Support?

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • naderi
    naderi over 14 years ago

    Hello Lawrence, 

    Thanks for your reply.

    I am using IC5141 on a Linux OS. I just realized there should two changes to fix the problem.

    First, the script produced by ADE (in graphical env.) had two "\n" at the end of lines of the model file defenition.Therefore, the modelFile command were not entered correctly.

    Second, I had to run icms -nograph rather than icfb -nograph. I still don't know what difference is betwenn icfb and icms, but trial on icms produces the correct netlist and uses the model files for the transistors.

    I also have another question and appriciate your help.

    In this case after running a transient analysis successful in icms -nograph, I like to plot voltage of a node. I used following commands, and got two t as results. However no window orplot pops out, and no furthur message.

    ocnWaveformTool( 'wavescan )
     plot( VT("/outp") )

     Is it due to the ocean commands for plot, or there is something wrong out of icms in my environment setting?

     

     Thanks,,

    Ali

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 14 years ago

    Hi Ali,

    If the plot is being done inside a -nograph session then there will be no windows or forms etc. opened, since you are running in non-graphical mode.  If you wish to run a batch type simulation session with plot windows etc. then you can run the "ocean" executable, but this cannot perform any netlisting itself, but it can use the netlist result that you created in an earlier session such as the one you just did.  You can run ocean from the command line and type interactive commands in, or load a file.

    I hope that this answers your questions.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • naderi
    naderi over 14 years ago

     Thank you very much,

    Ali

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 14 years ago

    Hi Ali,

    I meant to add that "icms" is an acronym for IC Mixed Signal and "icfb" is an acronym for IC Front-to-Back; the latter contains layout (and verification) tools and can be considered a superset of the icms executable.  If you only need to perform netlisting, simulation, schematic and symbol design, then icms might be a good choice, but generally these days most users would just run "icfb" since there is not really much overhead in doing so.  The netlisting in icfb should be the same as in icms - you might want to report this issue through a Service Request to see if this is a known issue with a solution or workaround.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information