Stats

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

dbOpenPanicCellView does not work in 'w' mode correctly.

shane park

Hello, I am sangyeon park.

I am using a virtuoso version 6.1.7 (or 6.1.8) and has used the command 'dbOpenPanicCellView' for a long time when I create some cells.

But, suddenly, this program does not work well, and I figured out that 'dbOpenPanicCellView' command with 'w' t_mode worked wired.

As I know, If the cell veiw does not exist, it is creaded, but It doesn't. It works only the cell exist.

I can share the message fro CIW when I used that command.

WARNING* (DB-270211): dbOpenCellViewByType: Cannot open cellview 'SIM_SHANE/cont2vdd/schematic' in 'w' mode because it does not exist or viewTypeName required to create a new cellview is not specified. Ensure that the cellview exists or to create a new cellview by specifying viewTypeName. Valid values for viewTypeName are "netlist", "schematic", "schematicSymbol" and "maskLayout

 

I am trying to resolve this issure finding various site. but I coudn't

Please help me

Thank you.

  • This makes no sense - why would you use dbOpenPanicCellView in "w" mode? The whole point of this function is to allow you to open the data which was saved automatically when a crash occurred - so that you can recover it. If you have unsaved edits then (if possible) Virtuoso will save a panic cellView and leave a message such as this in the terminal:

    A panic file has been created for cellview 'mylib/testpanic/layout' at:
    (/export/home/myuser/support/playGPDK45/mylib/testpanic/layout/layout.oa-)
    To open the cellview with the recovered data:
    cellview = dbOpenPanicCellView("mylib" "testpanic" "layout")

    Panic files have been created for cellviews that were opened in edit mode.
    For details on these panic files, see
    '/export/home/myuser/panic.log.lnx-myuser-76.116844'

    If you open it with SKILL, you can then open it in the editor and look at it. If you were to open this in "w" mode, it would erase the contents which rather defeats the point of having saved the panic data!)

    It sounds as if you might be trying to misuse this function to open a new cellView. You should use dbOpenCellViewByType instead:

    cv=dbOpenCellViewByType("mylib" "mycell" "schematic" "schematic" "w")

    (the fourth argument is the viewType you want to create, e.g. schematic, maskLayout etc).

    Andrew

  • in reply to Andrew Beckett

    Hi Andrew, 

    I has used 'dbOpenCellViewByType' beacause I am developing some program using skill language for CIW, so I don't want to open editor, actually.

    I want create a new cellview no matter the file existence.

    I has used the command like below, 
    cv_contvdd   = dbOpenCellViewByType(LibName center_Name   "schematic" nil "w")

    but, I realized that I should put "schematic" instead nil in that code, and It works very well. Slight smile

    ( Honestly, In the past, even I put it as 'nil' It had worked, but not now.)

    Thanks a lot.

    Sangyeon park.

  • in reply to shane park

    Sangyeon,

    I realised you were trying to do this batch and not open the editor - my point was that dbOpenPanicCellView was not the right API to be using.

    With dbOpenCellViewByType, the fourth argument can be nil if and only if the cellView already exists. In that case, it already knows what the viewType of the cellView is. If the cellView does not exist already (on disk) then you must tell it the viewType (this has been the case since the function was introduced in 4.4 (in 1996)).

    Regards,

    Andrew

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.