• 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. addFiller does not completely fill free area

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 91
  • Views 16492
  • 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

addFiller does not completely fill free area

kasyab
kasyab over 14 years ago

 Hi,

    I am seeing some strange behaviour with addFiller. It adds fillers on every alternate row and even then not everywhere. checkFiller duly reports gaps, but I am unable to change this behaviour inspite of turning on the -fitGap switch and trying '-util 1' with addFiller . I have checked that:

a) The list of filler cells is complete and ordered wider to narrower.

b) setFillerMode is not configured with anything wrong.

 

verifyGeometry, verifyConnectivity and verifyProcessAntenna all pass in Encounter, but I get errors related to p/n well continuity with the signoff DRC ruleset in Calibre.

 The version of encounter I am using is Encounter v09.10-p004_1.

 Any help is appreciated.

 Kasyab

  • Cancel
Parents
  • kasyab
    kasyab over 14 years ago

    Hi Kari,

    These are the warnings I got while trying to move the cell by hand. If you scroll down the list, you will see I tried various orientations as well.

    <CMD> selectInst FILLER_1030
    <CMD> uiSetTool move
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> setObjFPlanBox Instance FILLER_1030 2429.957 1406.399 2443.077 1411.319
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> placeInstance FILLER_1030 2430.07 1406.3 R0
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> placeInstance FILLER_1030 2430.07 1406.3 R0
    Instance FILLER_1030 is placed sideway.  Reset orientationto to R0.
    Flip instance FILLER_1030 to match row orient.
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> placeInstance FILLER_1030 2430.07 1406.3 R0
    <CMD> setObjFPlanBox Instance FILLER_1030 2430.847 1411.432 2443.967 1416.352
    <CMD> setObjFPlanBox Instance FILLER_1030 2430.89 1411.064 2444.01 1415.984
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> setObjFPlanBox Instance FILLER_1030 2430.268 1406.399 2443.388 1411.319
    <CMD> setObjFPlanBox Instance FILLER_1030 2431.003 1411.121 2444.123 1416.041
    <CMD> orientateInst FILLER_1030 MX
    Flip instance FILLER_1030 to match row orient.
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> setObjFPlanBox Instance FILLER_1030 2429.957 1406.088 2443.077 1411.008
    <CMD> orientateInst FILLER_1030 MX
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> orientateInst FILLER_1030 MY
    Flip instance FILLER_1030 to match row orient.
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.

     The LEF MACRO's for the filler cells do not have a site (or SITE) definition. They define the macros with a CLASS CORE instead. I am not familiar with the LEF/DEF syntax, but has the handling of LEF's changed in this version of EDI (as opposed to SOC-8.1 or SOC-7.1 )?

    Kasyab

     

    PS: I just looked at the technology LEF and that does have a SITE CORE definition with co-ordinates matching the numbers I gave earlier. However, it sefines the symmetry only as 'y'.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • kasyab
    kasyab over 14 years ago

    Hi Kari,

    These are the warnings I got while trying to move the cell by hand. If you scroll down the list, you will see I tried various orientations as well.

    <CMD> selectInst FILLER_1030
    <CMD> uiSetTool move
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> setObjFPlanBox Instance FILLER_1030 2429.957 1406.399 2443.077 1411.319
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> placeInstance FILLER_1030 2430.07 1406.3 R0
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> placeInstance FILLER_1030 2430.07 1406.3 R0
    Instance FILLER_1030 is placed sideway.  Reset orientationto to R0.
    Flip instance FILLER_1030 to match row orient.
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> placeInstance FILLER_1030 2430.07 1406.3 R0
    <CMD> setObjFPlanBox Instance FILLER_1030 2430.847 1411.432 2443.967 1416.352
    <CMD> setObjFPlanBox Instance FILLER_1030 2430.89 1411.064 2444.01 1415.984
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> setObjFPlanBox Instance FILLER_1030 2430.268 1406.399 2443.388 1411.319
    <CMD> setObjFPlanBox Instance FILLER_1030 2431.003 1411.121 2444.123 1416.041
    <CMD> orientateInst FILLER_1030 MX
    Flip instance FILLER_1030 to match row orient.
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> setObjFPlanBox Instance FILLER_1030 2429.957 1406.088 2443.077 1411.008
    <CMD> orientateInst FILLER_1030 MX
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.
    <CMD> orientateInst FILLER_1030 MY
    Flip instance FILLER_1030 to match row orient.
    **WARN: (ENCDB-2513):    Given orientation not legal, FILLER_1030 remains original orientation R0, check for SYMMETRY statement in the LEF file for the cell FILLERCELL32.

     The LEF MACRO's for the filler cells do not have a site (or SITE) definition. They define the macros with a CLASS CORE instead. I am not familiar with the LEF/DEF syntax, but has the handling of LEF's changed in this version of EDI (as opposed to SOC-8.1 or SOC-7.1 )?

    Kasyab

     

    PS: I just looked at the technology LEF and that does have a SITE CORE definition with co-ordinates matching the numbers I gave earlier. However, it sefines the symmetry only as 'y'.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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