Stats

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

Resetting SKILL IDE when debugging.

stephbur

I am currently taking a course on developing PCell using SKILL IDE.
I am looking for a way for rerunning a SKILL script after I made some changes.

As an example I might have the following routine:

procedure(test()
    cv = geGetEditCellView()
    rect = rodCreateRect(?cvId cv ?name "myrect" ?layer "poly" ?bBox list(1:1 4:4))
)

I run the function test and in the editor I will see the created rectangle.
Now I decide I want the rectangle starting in the origin and thus change the list for the bBox to list(0:0 3:3).
When rerunning the code there is an error as there already is a "myrect" in this cell view.

What is the easiest way to "reset" the environment such that the rectangle with the new parameters replaces the old one?
So far the only way I have found is to restart Virtuoso, which is obviously not ideal.

Parents

  • You may create as many rectangles as  you like - the problem is the ROD name which needs to be unique just like it was an instance name.

    Simply omit the ?name "myrect"  argument and the system will create a unique name

  • in reply to mbracht

    Thank you for your reply. I figured this much. But then the old rectangle will still be there, which is obviously not what I want. And since I want to use the skill code in production at some point I would really like to keep the name argument.
    In the end, I would like to have the code IDE and the layout view side by side, and on the press of the button have the corresponding layout in the layout view. This would somehow require that all objects will be removed from the execution context. A "start over" functionality so to speak.

  • in reply to stephbur

    Use dbReopen(cv "w") - this will erase everything in the cellView.

    Andrew

Reply Children
  • in reply to Andrew Beckett

    Thank you Andrew, that is exactly what I was looking for.  I have added a breakpoint and the dbReopen line as the last two lines of my procedure.
    Now an IDE button doing exactly this would be nice, I am surely not the only one looking for something like this. :)
    Thank you again and have a nice day!

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.