• 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 SKILL
  3. Finding ViewTypes

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 16814
  • 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

Finding ViewTypes

ddr71m
ddr71m over 13 years ago

 Hi,

 i intend to copy verilog view of a schematic.....to do so i am using dbopenCellViewByType() but i don't know the view type for the same(for schematic--schematic,layout--maskLayout,symbol--schematicsymbol)....then i am using dbCopyCellView() but 

 Scell_veri=dbOpenCellViewByType("LibName" "CellName" "veriloga" "<ViewType>")

inplace of ViewType i used "verilog", "veriloga","VerilogA" but it returns --

WARNING* (DB-270208): dbOpenCellViewByType: unrecognized database viewType 'veriloga'

 

Now, i am in a fix...

 

Thanks

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    If your aim is to copy the cellView, using dbOpenCellView/dbCopyCellView is the wrong way to do it for textual views. The db functions are purely for opening cellViews with a database (i.e a CDB or OA database). Now in fact there is a database in the veriloga view, sometimes known as the "shadow" database, which is used to store information about hierarchy and terminals. However, this is not the master data for this cellView, so if you were to open it (leaving the viewType as "") and copy it, you would not get the textual representation as well.

    You should use ccpCopy to copy such views.

    Regards,

    Andrew.

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

    Thanks  Andrew

    your reply was immensely helpful,i was able to copy verilog view

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

    Hi Andrew,

    ccpcopy works fine if i am copying cells from lib1 to lib2 if both are attached to same technology libraries but if they are attached to two different technologies then copy doesn't happens...is there any option to force the copy by ccpcopy.

    Regards,

    ddr71m

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

    You may have to use this UNIX env var:

    setenv CCP_DISABLE_DFII_CHECKER all

    before starting virtuoso.

    Regards,

    Andrew.

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

    Hi,

     

    I want  to copy cells(having views as schematic.bckup..etc) with only those views which i specify as a collection of strings in a list using ccpcopy and i am not able to copy, also can you please tell what is the difference between----

    [ l_copyViewTypeList ]

    [ l_copyViewNameList ]

    Also,ccpcopy checks out 111 licensce each time copy is done is there any way to skip this check....

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

    View types are the type of the data (e.g. maskLayout, schematicSymbol etc) where as the view name is what the view is actually called. This way you can get it to copy all of a particular view type regardless of what the view names are called - or vice versa.

    Is this the same question as in the comp.cad.cadence newsgroup question - http://goo.gl/b4SwX

    If so, I suggested creating a service request for the reason why it takes a 111 license each time (that surprises me).

    Regards,

    Andrew.

     

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

     Thanks Andrew, I faced the issue of ccp copy checking the 111 license and as suggested i will raise a service request for this

    • 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