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

 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

Parents

  • Hi Kari,

    Are there std cells on the rows where fillers aren't getting added?

    Yes. There are. I can forward pictures if so necessary. There are a large number of memory macros and the rows are cut in that area (including the placement blockage region for the macros), but if the rows are cut it should not influence the placement of thefillers in anyway,should it?

    Is the row definition correct?

    Can you explain a little more about what you mean by this? The rows match the std cell height of 4.92u (ST 130nm lib). However, I do get a warning during routing (CTS initially since I have routing turned on during CTS). That is pasted below:

     #NanoRoute Version v09.10-p020 NR091118-1115/USR62-UB
    #Using multithreading with 4 threads.
    #WARNING (NREX-28) The height of the first routing layer M1 is 0.000000. It should be larger than 0.000000
    #WARNING (NREX-30) Please also check the height and metal thickness values for the routing layers heigher than routing layer M1

     

    I am not sure they are related.

    Can you place a filler cell there by hand without errors?

    I tried this briefly yesterday but got warnings about the orientation. Itried moving one of the placed fillers to a row below but got warnings about  orientation violations. I was not able to change the orientation by editing the properties (FIXED -> PLACED, R0 -> MX).

     

    Hope this helps. I'm still looking for a solution.

     

    Thanks,

    Kasyab

Reply

  • Hi Kari,

    Are there std cells on the rows where fillers aren't getting added?

    Yes. There are. I can forward pictures if so necessary. There are a large number of memory macros and the rows are cut in that area (including the placement blockage region for the macros), but if the rows are cut it should not influence the placement of thefillers in anyway,should it?

    Is the row definition correct?

    Can you explain a little more about what you mean by this? The rows match the std cell height of 4.92u (ST 130nm lib). However, I do get a warning during routing (CTS initially since I have routing turned on during CTS). That is pasted below:

     #NanoRoute Version v09.10-p020 NR091118-1115/USR62-UB
    #Using multithreading with 4 threads.
    #WARNING (NREX-28) The height of the first routing layer M1 is 0.000000. It should be larger than 0.000000
    #WARNING (NREX-30) Please also check the height and metal thickness values for the routing layers heigher than routing layer M1

     

    I am not sure they are related.

    Can you place a filler cell there by hand without errors?

    I tried this briefly yesterday but got warnings about the orientation. Itried moving one of the placed fillers to a row below but got warnings about  orientation violations. I was not able to change the orientation by editing the properties (FIXED -> PLACED, R0 -> MX).

     

    Hope this helps. I'm still looking for a solution.

     

    Thanks,

    Kasyab

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.