Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 14408
  • 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

residual cdf parameters after switching lib

DavidLou

hi exports,

I have a question about cadence. say we have two sets of libraries. libA has full set parameters for the cells while libB has less parameters for the same cells. 

once the design switched from libA to libB, the instances in the schematic would keep obsolete parameters from libA, even it's now associated with libB. 

how can we easily flush the obsolete parameters out (although I know I can always manually replace all the instances from the new lib). 

thanks,

David

Parents

  • Hi David

    I think this can be quite easily done using a SKILL script. E.g.

    procedure( CCSremoveParams(lib)
       let( (cv)
          foreach( cell ddGetObj(lib)~>cells
             foreach( view setof(x cell~>views pcreMatchp("schematic" x~>name)
                cv=dbOpenCellViewByType(lib cell~>name view~>name "" "a")
                ;;; do something ;;;
                schCheck(cv)
                dbSave(cv)
                dbClose(cv)
             ) ;foreach
          ) ;foreach
       ) ;let
    ) ;procedure


    Best regards
    Quek

Reply

  • Hi David

    I think this can be quite easily done using a SKILL script. E.g.

    procedure( CCSremoveParams(lib)
       let( (cv)
          foreach( cell ddGetObj(lib)~>cells
             foreach( view setof(x cell~>views pcreMatchp("schematic" x~>name)
                cv=dbOpenCellViewByType(lib cell~>name view~>name "" "a")
                ;;; do something ;;;
                schCheck(cv)
                dbSave(cv)
                dbClose(cv)
             ) ;foreach
          ) ;foreach
       ) ;let
    ) ;procedure


    Best regards
    Quek

Children
  • in reply to Quek

    thanks Quek,

    This seems to generate sub-lib from existing library by removing specific parameters. that's not what I want. we've already had such sub-lib. but when the schematic design updated to attach new lib, the instances in the schematic would keep past parameters, not automatically updated to have only parameters from the new library. so what I want is to remove obsolete parameters from the instances. 

    would there be easy way for that?

    thanks,

    David

  • in reply to DavidLou

    Hi David

    I am not sure if this can resolve your problem, hope that it will be helpful:

    procedure( CCSremoveParams(newLib)
       let( (cv cdfTable techLib baseCdf instCdf paramList)
          cdfTable=makeTable("cdfTable" nil)
          techLib=techGetTechFile(ddGetObj(newLib))~>libName
          foreach( cell ddGetObj(techLib)~>cells
             baseCdf=cdfGetBaseCellCDF(cell)
             cdfTable[cell~>name]=foreach(mapcar x baseCdf->parameters x->name)
          ) ;foreach

          foreach( cell ddGetObj(newLib)~>cells
             foreach( view setof(x cell~>views pcreMatchp("schematic" x~>name)
                cv=dbOpenCellViewByType(newLib cell~>name view~>name "" "a")
                foreach( inst setof(x cv~>instances x~>libName==techLib)
                   instCdf=cdfGetInstCDF(inst)
                   paramList=setof(x instCdf->parameters !member(x->name cdfTable[cell~>name]]))
                   apply('cdfDeleteParam paramList)
                ) ;foreach
                schCheck(cv)
                dbSave(cv)
                dbClose(cv)
             ) ;foreach
          ) ;foreach
       ) ;let
    ) ;procedure


    If it is not what you need, perhaps it might be best to file a case so that the local AE can assist you on the problem.


    Best regards
    Quek

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.