• 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. auCdl view and loading CDF port order through CIW?

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 15139
  • 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 view and loading CDF port order through CIW?

yayla
yayla over 11 years ago
Hi,

I have a netlist provided by a different team and my port order in Cadence doesn't match the provided netlist. What we are doing is that we are generating auCdl view from symbol. Then, we have a script to generate a cdf file(attached below)  and load into CIW in Cadence. From CIW=>Tools=>CDF, I can see the new correct port order but when I need to netlist, Cadence doesn't still use the new order.

I found this document but it didn't help me much. This suggests sth about “auCDFPinCtrl”  but don't know how to incorporate.

http://lost-contact.mit.edu/afs/rose-hulman.edu/cadence-0910/IC610/doc/anasimhelp/appC.html#938197

 

Thanks,

yayla

/****************************************************/
 LIBRARY = "test_lib"
 CELL    = "test_cell"
/****************************************************/

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           "macro"
        ?prompt         "Subcircuit Filename"
        ?defValue       "gv_pr"
        ?type           "string"
        ?display        "!cdfgData->template->value"
        ?editable       "nil"
        ?parseAsCEL     "yes"
    )

    ;;; Simulator Information
    cdfId->simInfo = list( nil )
    cdfId->simInfo->ams = '( nil )
    cdfId->simInfo->auCdl = '( nil
        namePrefix        "X"
        termOrder         ("a" "b" )
        componentName     "subcircuit"
        netlistProcedure  ansCdlSubcktCall
    )
    cdfId->simInfo->hspiceS = '( nil
        namePrefix        "X"
        termOrder         ("a" "b" )
        componentName     "subcircuit"
        macroArguments    nil
        netlistProcedure  ansSpiceSubcktCall
    )
    cdfId->simInfo->spectre = '( nil
        opParamExprList   nil
        stringParameters  nil
        propMapping       nil
        termMapping       nil
        instParameters    nil
        otherParameters   nil
        termOrder         ("a" "b")
        componentName     gv_pr
        netlistProcedure  nil
)
    cdfId->simInfo->spectreS = '( nil
        namePrefix        "X"
        termOrder         ("a" "b" )
        componentName     "subcircuit"
        macroArguments    nil
        netlistProcedure  ansSpiceSubcktCall
    )

    ;;; Properties
    cdfId->formInitProc            = ""
    cdfId->doneProc                = ""
    cdfId->buttonFieldWidth        = 340
    cdfId->fieldHeight             = 35
    cdfId->fieldWidth              = 350
    cdfId->promptWidth             = 175
    cdfId->paramLabelSet           = "-macro"
    cdfId->paramDisplayMode        = "parameter"
    cdfId->paramEvaluate           = "t nil nil nil nil"
    cdfId->instDisplayMode         = "cellName"
    cdfId->instNameType            = "schematic"
    cdfSaveCDF( cdfId )
)
  • Cancel
  • yayla
    yayla over 11 years ago

     Hi,

    I figured out how to solve the problem which is already at the link I have provided before but I didn't notice at that time. What you need to do is create a .simrc file and put auCdlCDFPinCntrl='t this line inside that file.

     thanks,

    yayla

    • 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