• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. DRC clean with encounter, DRC error with calibre

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 90
  • Views 18176
  • 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

DRC clean with encounter, DRC error with calibre

archive
archive over 18 years ago

    Hi,
I get a DRC clean and no DRC violation in my encounter log file after doing globaldetail routing and adding filler.
But as I am merging my design gds with stdcell gds and using calibre for DRC checking I get so many errors!
Could you please help me on the procedure i have to take to have a clean DRC using calibre?
can I load the DRC report of calibre and ask encounter to solve those DRC error?
As i am looking at most DRC error in my design are concern to filler. so basically I have so many empty area between nwells and has not been filled with fillers.

Thanks,

Houman


Originally posted in cdnusers.org by houmanh
  • Cancel
  • archive
    archive over 18 years ago

    Hello Houman,

    Glad to answer your question .

    Its very clear that Encounter cant fix such calibre reported violations for Nwell or Pwell spacing . As LEF file does not have such rule .

    You have to fix all of them manually and its very easy .

    Fixing procedure : and fill cell adding
    1. you should see that there are no empty site in the core area before adding filler (SUBCON ) cells .
    2. If you have any placement blockage please delete it manually ,as Encounter cannot delete placement blockages .
    3. Make sure that apart from Macro Block halo , there is no empty area.

    To load violation marker on to Soce .
    loadViolationReport -type Calibre -filename < File name drc.err >

    Hope this will help you ,

    Regards,
    Mohan



    Originally posted in cdnusers.org by mohanch007
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi Houman,

    The correct thing to do is to go back to SoC and understand why filler cell are not placed in the area they should. Once understand the cause, you can then know how to solve it.

    If you are sure that there is no issue with filler cell placement, then you may be the unlucky few that use std cell library that can have n-well or diffusion violation that are due to notches. So far, I am aware that only Apollo (not sure about the newer version) can fill up this type of gap. But there is always a workaournd. You can use custom layout to draw a continuous n-well for every cell row, or you can use custom layer in SoC to do this (please don't do this by hand. Use a script).

    From the question you post here, look like you are on the way to tape-out soon!

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    SOCE has the similiar command "fillNotch" for metal notch & well gap fill.

    li saing
    '


    Originally posted in cdnusers.org by lisiang
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi Li Siang,

    Thanks for point out. I did a "help well" and "help gap" but could not see related command. But I think I come across this command before in the command guide...

    But I think the issue is that usually layer lower than contact (or M1) are not usually in the LEF. For Apollo the database is like Virtuoso so the P&R view can keep the full GDS. From my memory (that is more than 5 years old..) the gap I need to fill at that time was some funny layer (not nwell , but something else).

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information