Continue to Site

Welcome to

Welcome to our site! 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.

[question] DRC fix in SOC Encounter

Not open for further replies.


Advanced Member level 4
May 4, 2004
Reaction score
Trophy points
the hole eletron left behind
Activity points
Hi, All,

it seems that SOC encounter doesn't have quite good capability to fix DRC, or?

In my run, a module around 2x2 has almost 800 DRC error, and most of them are apparently not difficult to get fixed.
I really go through every page of the User manual and Cadence website, and do not find anything regarding DRC fix in SOC Encounter. But I still don't believe Encounter will be so lousy in this aspect.

Can you give me some hint on this point?

Thanks a lot!

u must export the def file from encounter
and fix all DRC error in assura or calibre(mentor)
encounter wont fix DRC violation.


yes, this is what I am doing know, I load the gds into icfb and fixed them interactively with calibre drc rve. Luckily there are not some many DRC errors.



Encounter is weak on DRC related to the metal overhang for the power router.

Beside that, if both the LEF technology and LEF files are good, then I ould said not DRC should be expected. If you can show us the type of DRC errors that Encounter make, perhaps we can know what need to be fixed.

Eng Han

Hi, i have found many DRC problems after nano route. Such as open and antenna violations. Open Violation is the most frequent and I dont know what I have to do to solve this problem!! My doubt is, from when I can extract the GDSII and further files to solve this on Virtuoso? Can i solve this on virtuoso? What is the solution for my problem?

If your technology LEF file is provided with your std cell you should have no DRC visible by Encounter.
I never provide a gds with more than 10DRC errors for 100kgates design 75% std celle density, antenna could be more difficult when no place is available for routing and diode placement.

Well, LEF file is provided, you are talking about IMPORT DESIGN STAGE, right? if yes, anyway i got these DRC vios. What is the explanation about it? my design is simple, no hard macros, only the std cell block to floorplan i'm a noob (first big project) and design density is something about 75% or less. Another problem i've faced out is the congestion red diamonds after trial route, i can increase die area infinitely, they will reduce congestion diamonds but I will find some ones always!

Thank you!

Did you used no special option during the placement ?

neither pre nor in-place optimization.. this is the problem? What happen in in-place and pre-place optimization?
I will try this way, with both optimization.

you define high effort for congestion issue during pre-post placement

---------- Post added at 10:26 ---------- Previous post was at 10:25 ----------

if you already seen congestion violation after placement, there is an issue to solve before going forward.
you could also used padding feature on module/cell/instance..

Hi Rca,

Can you please explain me "congestion violation" after placement. I have many process antenna violations and dont know what to do then after trying many things in the soce guide.

Thank you for you time.


Not open for further replies.

Part and Inventory Search

Welcome to