• 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 Design
  3. Why spectre generated-netlist always show the wrong subckt...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 2535
  • 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

Why spectre generated-netlist always show the wrong subckt name "unmos4_schematic" but not "unmos4" ?

Paulux
Paulux over 13 years ago

Hello,

I want to build a cell called unmos4 and hope the spectre-generated netlist showing as follows

.subckt unmos4 D G S B

parameters nw=1 nl=1

M1(D G S B) ne2 w=nw l=nl as=0.49*(nw) ad=0.49*(nw) pd=0.98+2*(nw) ps=0.98+2*(nw)

ends unmos4

MN0 (out net043 gnd gnd) unmos4 nw=3 nl=0.35

HOWEVER, the result shows that there is extra "_schematic" after unmos4

.subckt unmos4_schematic D G S B

parameters nw=1 nl=1

M1(D G S B) ne2 w=nw l=nl as=0.49*(nw) ad=0.49*(nw) pd=0.98+2*(nw) ps=0.98+2*(nw)

ends unmos4_schematic

MN0 (out net043 gnd gnd) unmos4_schematic nw=3 nl=0.35

 

May I know how to remove "_schematic" after unmos4?

 

The CDF is as follows

Component Parameters

model paramType=string, parseANumber=no, parseAsCEL=yes, storeDefault=no, name=model, prompt=unmos4

Simulation Information

Choose Simulator=spectre, otherParameters=model, instParameters= nw nl, componentName=unmos4, termOrder=d g s b

Same problem of extra "_schematic"  is also found when hspiceD netlisting for simulation.

 Choose Simulator=hspiceD, instParameters= nw nl, componentName=unmos4, namePrefix=X, termOrder=D G S B, termMapping= nil D \,D G\, G S \,S B \,B 

Thank you very much in advance for any help, feedback and comments

  • Cancel
  • Paulux
    Paulux over 13 years ago

    From Cadence Analog Design Environment User Guide (Product Version 5.0) p.135 (About Subcircuits and Macros), it mentioned

    "Whenever possible during hierarchical netlisting, subcircuit names are generated in the form _libName_cktName_schematic

    For example: .SUBCKT _mylib_bicomp_schematic n0 n1 hsbias out

    This name generation is not possible when a subcircuit is parameterized (that is, when it has parameter values passed in through macroArguments in the stopping cellview CDF). In this situation, subcircuits are named subX, where X is a unique number. For example:

    .SUBCKT sub3 D G S

    If you want to have nonparameterized subcircuits named in the subX style, add a dummy parameter to the macroArgument field of the CDF for the stopping cellview."

    My questions are 

    (1)Based on the above description, may I know how to change the instance name from  unmos4_schematic to unmos4?

    Or is this impossible? Or any other method that I can stop generating "_schematic" after the instance name unmos4?

    (2)Where can I set stopping cellview CDF?

    Thank you very much for your feedback/comments

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

     The macroArguments stuff is primarily for stopping views - it's if you want to reference an external subckt model - and it's for hspice - not spectre. Even then I think it's for hspiceS, not hspiceD.

    I believe that the _viewName will only get added if you have used a config and more than one view has been selected - In general it should just use the cellName as the subckt name.

    I'm not sure why it necessarily matters, if everything is consistent - but maybe the best thing is to provide your data (to customer support if you can't provide it here) so that somebody can take a look?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Paulux
    Paulux over 13 years ago

    Thanks Andrew very much for explanation.

    From your reply, _viewName exists due to (1)used a config and (2) more than one view has been selected.

    The libraries included in Library Manager are

    US_8ths, ahdlLib, analogLib, basic, cdsDefTechLib, functional, rfExamples, rfLib, my_chrt035

    I only build unmos4 in my_chrt035 library.

    If any more details are required, please kindly leave reply here.

    May I know where & how I can know what config I used? Or where/how can I know that more than one view has been selected? And how to fix this selection in order to remove _viewName?

     My Virtuoso Design Environment 5.10.41.500.5.96.

     

    Thank you very much in advance for any comments/feedbacks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Paulux
    Paulux over 13 years ago

    Thanks so much Andrew about "_viewName".

    May I know how I can view my config of my library my_chrt035 that generates "_viewName"?

    Or where I can see "more than one view has been selected"?

    May I know what data I should provide here to give further details for these questions?

    Thank you very much in advance for your kindness and feedback.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    If you don't know what a config view is, the chances are you didn't create one (you use the hierarchy editor for this).

    As I said, the best thing is to contact customer support on this, because then they can talk you through in a way that volunteers on this forum don't have time to do...

    Kind Regards,

    Andrew,

    • 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