Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 1796
  • 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

SPICEIN for importing netlisting with pPar expressions

PSKR

I want to generate a schematic using SPICE IN. The CDL netlist of the component would look like this. Need the schematic to be generated with these following expression in the property form(CDF). When i import this netlist , i get these errors

.subckt LDMOS_101 BTWO D S G SUB
*.PININFO BTWO:B D:B S:B G:I SUB:I 
 XQ0 ISO1 SUB SUB S PNP4 model=pPar("pnpModel") area=pPar("pL")*pPar("tank_area")) mi=pPar("miX")

 XQ1 S ISO1 ISO1 D NPN4 bypass=SVER, Assura, auLvs, auCdl, calibre mi=pPar("miX") area=pPar("adasNum") model=NPN_LDMOS_101
.ends LDMOS_101

ERROR (SPICEIN-102): Spice In failed to parse the cdl netlist file cdl'. You may read log file 'lvsrpt.wrn'

 ERROR (AVLVSNN-10134) : CDL parser encountered error in file 'cdl' on line 76: Error: Unknown Function type.

XQ0 is line 76

The purpose is to create a schematic for multiple components(from one component) which have similar sub-ckt and batch process and import them. Is it possible through spicein.

  • Putting pPar() expressions in the netlist doesn't make sense - that's not legal SPICE (or CDL, or Spectre) syntax. Not sure why would expect that to work. Also, that bypass=SVER, Assura... won't work either (as that doesn't look legal).

    You can have parameters in the netlist - e.g. area=pL*tank_area m=miX - but you should also define the parameters (via .PARAM) within the subckt. However, if you do this, the SPICE import converts them to NLP parameter rather than CDF (pPar) parameters. I have some SKILL code to deal with that (not sure I want to post it here because I don't know how robust it is to deal with general cases - it's been used by a few customers here and there to solve specific problems, but I don't think I've done enough widespread testing to be sure it covers everything). It would be better to contact customer support (submit a case after logging in) and then mention this post and the AE can contact me for more details.

    Andrew

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.