Handling of VerilogA Views

Discussion in 'Cadence' started by Guenther Sohler, Jun 8, 2005.

  1. Guenther Sohler

    Guenther Sohler Guest

    In our setup I have written an alternative copy script,
    which copies views hierarchically into a release library and also
    does the referencing correctly. This works fine, If I handle views like
    symbol, schematic,layout,abstract ...
    But it does not work for veriloga views(they are different in nature)

    during normal copying i use
    dbOpenCellViewByType
    v
    dbID
    v
    dbCopyCellViewByType

    these do not work for verilog a views because dbOpenCellViewByType
    cannot generate a dbID for them.
    Is there also a way to get a dbID for a veriloga
    view(its actually a file containing a veriloga behavioural description)


    rds
     
    Guenther Sohler, Jun 8, 2005
    #1
  2. Guenther Sohler

    Andrew Beckett Guest

    You should use the ccpCopy() function to copy things in general - this will
    cope with non-CDB views. The db functions are only for CDB (and OA) views.

    Regards,

    Andrew.
     
    Andrew Beckett, Jun 10, 2005
    #2
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Handling UCS and WCS

  2. Handling Arbitrary Keywords

  3. error handling problem

  4. How Does this Code Work: Error Handling

  5. Handling different prompts - plot command?

  6. list handling

  7. Error Handling

  8. inserting sketch dimensions from annotation views automaticaly into drawing views

Loading...