Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 15608
  • 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

auCdl netlist subckt missing parameters

Paulux

Hi,
In auCdl netlist generation, I want to generate the netlist shown below
XI1 net16 gnd! / rnpoly2 rl=20 rw=2
.SUBCKT rnpoly2 MINUS PLUS rl=2 rw=2
RR0 PLUS MINUS 190*rl/(rw-6.2e-3) $[NS] $W=rw $L=rl
.ENDS

But the generated CDL out file (File->Export->CDL) is
XI1 net16 gnd! / rnpoly2 M=1
.SUBCKT rnpoly2 MINUS PLUS rl=2 rw=2
RR0 PLUS MINUS 190*rl/(rw-6.2e-3) $[NS] $W=rw $L=rl
.ENDS

The auCdl setting is given below
cdfId->simInfo->auCdl = '( nil
dollarEqualParams nil
dollarParams nil
netlistProcedure ansCdlSubcktCall
instParameters (rl rw m)
componentName rnpoly
termOrder (PLUS MINUS)
propMapping (nil L rl W rw)
namePrefix "X"
modelName "rnpoly"

Details can be found below
The cdf file is attached for reference

Thank you in advance for your help

The CDF settings are

let( ( libId cellId cdfId )
    unless( cellId = ddGetObj( LIBRARY CELL )
        error( "Could not get cell %s." CELL )
    )
    when( cdfId = cdfGetBaseCellCDF( cellId )
        cdfDeleteCDF( cdfId )
    )
    cdfId  = cdfCreateBaseCellCDF( cellId )

    ;;; Parameters
    cdfCreateParam( cdfId
        ?name           "model"
        ?prompt         "Model name"
        ?defValue       "rnpoly"
        ?type           "string"
        ?display        "t"
        ?editable       "nil"
        ?parseAsCEL     "yes"
    )
    cdfCreateParam( cdfId
        ?name           "macro"
        ?prompt         "Hspice Model name"
        ?defValue       "iPar(\"model\")"
        ?type           "string"
        ?display        "nil"
        ?editable       "nil"
        ?parseAsCEL     "yes"
    )
    cdfCreateParam( cdfId
        ?name           "macroArgumentStyle"
        ?prompt         "macro arg style"
        ?defValue       "hspiceS"
        ?type           "string"
        ?display        "nil"
        ?parseAsCEL     "yes"
    )
    cdfCreateParam( cdfId
        ?name           "r"
        ?prompt         "Resistance"
        ?units          "resistance"
        ?defValue       "190"
        ?type           "string"
        ?editable       "cdfgData->entryMode->value == \"Resistance&Width\""
        ?callback       "preswl_1Si()"
        ?parseAsNumber  "yes"
        ?parseAsCEL     "yes"
    )
    cdfCreateParam( cdfId
        ?name           "tr"
        ?prompt         "Total resistance"
        ?units          "resistance"
        ?defValue       "190"
        ?type           "string"
        ?display        "deGetEditCellView()->cellViewType != \"maskLayout\""
        ?editable       "nil"
        ?parseAsNumber  "yes"
        ?parseAsCEL     "yes"
    )
    cdfCreateParam( cdfId
        ?name           "entryMode"
        ?prompt         "Entry Mode"
        ?defValue       "Length&Width"
        ?choices        '("Length&Width" "Resistance&Width")
        ?type           "cyclic"
    )
    cdfCreateParam( cdfId
        ?name           "rl"
        ?prompt         "Length"
        ?defValue       "2"
        ?type           "string"
        ?editable       "cdfgData->entryMode->value == \"Length&Width\""
        ?callback       "presr_1Si()"
        ?parseAsCEL     "yes"
    )
    cdfCreateParam( cdfId
        ?name           "rw"
        ?prompt         "Width"
        ?defValue       "2"
        ?type           "string"
        ?display        "artParameterInToolDisplay('w)"
        ?callback       "presr_1Si()"
        ?parseAsCEL     "yes"
    )
    cdfCreateParam( cdfId
        ?name           "m"
        ?prompt         "Multiplier"
        ?defValue       1
        ?type           "int"
        ?display        "deGetEditCellView()->cellViewType != \"maskLayout\""
        ?editable       "deGetEditCellView()->cellViewType != \"maskLayout\""
        ?callback       "presm_1Si()"
    )

  • berndf

     I believe the issue is related to your propMapping.
    You do a "propMapping (nil L rl W rw)" in the auCdl simInfo, but
    in the parameter section you have defined "rl" and "rw".

    Bernd

  • Paulux

    Thanks Bernd.

    After I modify from "propMapping (nil L rl W rw)" to propMapping (nil)" and generate new auCdl netlist, the parameters are still missing.

    XI1 net16 gnd! / rnpoly2 M=1
    .SUBCKT rnpoly2 MINUS PLUS rl=2 rw=2
    RR0 PLUS MINUS 190*rl/(rw-6.2e-3) $[NS] $W=rw $L=rl
    .ENDS

    Could you/anyone please suggest how to modify propMapping so that auCdl can generate "XI1 net16 gnd! / rnpoly2 M=1 rl=20 rw=2"?

    Thanks in advance for your help

  • skillUser

    Hi Paulux,

    I think that you may want to look at the ansCdlPrintInstParams or ansCdlPrintInstProps functions in the documentation - set the auCdl netlist procedure to ansCdlHnlPrintInst and then you will be able to customize how the device is written to the netlist. Put any procedure definitions in your .simrc file, if you need to overwrite the default implementations.

    Hope this helps.

    Lawrence.

  • Paulux

     Hi Lawerence,

     Thank you very much for your reply.

    Could you/anyone give an example in.simrc such that the "rl=" "rw=" appear in the line "XI1 net16 gnd! / rnpoly2"

    XI1 net16 gnd! / rnpoly2 M=1
    .SUBCKT rnpoly2 MINUS PLUS rl=2 rw=2
    RR0 PLUS MINUS 190*rl/(rw-6.2e-3) $[NS] $W=rw $L=rl
    .ENDS

    Also, the problem is more series in capacitor subcircuit because only capacitance equation is printed in the auCdl netlist as shown below!

    XI2 in1 gnd! / umim

    .SUBCKT umim MINUS PLUS

    CC0 PLUS MINUS 1.5e-4*cw*cl $[CA]

    .ENDS

     ******************************************************************************************

    How could the above capacitor parameters in auCdl netlist be added as shown below
    XI2 net17 gnd! / umim cl=15 cw=15

    .SUBCKT umim MINUS PLUS  cl=10 cw=10

    CC1 PLUS MINUS 1.5e-4*cw*cl $[CA] $L=cl $W=cw

    .ENDS

    Thanks in advance for your help.

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.