Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Calibre/Virtuoso: Context/Hierarchy question.

Status
Not open for further replies.

polygonslinger

Newbie level 3
Joined
Jan 14, 2010
Messages
4
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Location
Texas
Activity points
1,309
I am fixing DRC's on a full chip run using Calibre/Virtuoso with most of the errors are located in subcells. I edit in place to fix an error and when I click highlight the next error in RVE I am forced to save the cell, return to the top before zooming to the next error (usually to find out it is in the same cell that I was just editing).

Fixing 50 errors in subcells equals 50 extra saves and 50 extra returns. I am fairly certain that there is a better way than this. I can't find anything in Virtuoso/RVE to allow viewing of the errors from any level in the hierarchy and I know it is possible - anybody know how?
 

polygonslinger said:
I know it is possible - anybody know how?
First run DRC on each subcell and fix the errors! Or kindly ask the subcell's layouter to tidy up before delivering ;-)
SCNR
 

erikl said:
polygonslinger said:
I know it is possible - anybody know how?
First run DRC on each subcell and fix the errors! Or kindly ask the subcell's layouter to tidy up before delivering ;-)
SCNR

Nice idea - but this is revwork. We have a new flow, new drc's and an existing product. It is much more efficient to run a single calibre job and do the edit in place fixes than run 300 individual jobs.
 

polygonslinger said:
It is much more efficient to run a single calibre job and do the edit in place fixes than run 300 individual jobs.
polygonslinger said:
Fixing 50 errors in subcells equals 50 extra saves and 50 extra returns.
This doesn't fit together well: If you always have to climb through the full hierarchy - and I'm sure you have to, with the full hierarchy DRC job, I think it would be more efficient to DRC-clean the subcells before.

There's a work-around: Copy the full chip, flatten the copied view until just before the subcell hierarchy, run the DRC, clean all DRC subcell errors in the flattened view, then continue with the original view. By this you have to climb through just 1 hierarchy level.
 

i had a similar problem.cleanning up the hierarchy was a easier solution I saw.Or keeping the topview and the below hierarchy view side by side and editing it(in case you have a large screen)
 

erikl said:
polygonslinger said:
This doesn't fit together well: If you always have to climb through the full hierarchy - and I'm sure you have to, with the full hierarchy DRC job, I think it would be more efficient to DRC-clean the subcells before.

I might agree with you if this was 1995 - the drc job runs fast enough that there is more overhead running multiple jobs than running a single job and using edit in place. The overhead I am experiencing relates to being forced back to the top level (and save) each time I pan to the next error.

I've never had this issue before - drc has always let me pan to the next error regardless of my current position in the hierarchy. I am just trying to find out what is different in my current set up that is not allowing me to do this.
 

polygonslinger said:
I might agree with you if this was 1995
You're right: my experience was with Diva & Assura; then the DRC error backAnnotation into the layout only worked on top level.

polygonslinger said:
I've never had this issue before - drc has always let me pan to the next error regardless of my current position in the hierarchy. I am just trying to find out what is different in my current set up that is not allowing me to do this.
May be there's a Calibre option for the error backAnnotation scheme which enables you to jump directly to the affected cell? Good luck for finding it! Pls. report back in this case!
 

If anybody is interested -

3 things need to be done to accomplish this:

In Virtuoso: Calibre=>Setup=>RVE=>Edit in place while highlighting (t)
In RVE: Highlight=>Highlight in Context (t)

In the Calibre flow this statement must be present:DRC CELL NAME YES CELL SPACE XFORM
 

Thank you for telling us!
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top