Stats

  • Locked Locked
  • Replies 4
  • Subscribers 91
  • Views 15519
  • 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

optDesign removes fillers

Johann Glaser

HI!

I'm using the Foundation Flow for a flat design. While running all steps I find that "route" uses addFiller to fill the core area with filler cells. Opening the database with the GUI shows that it really contains these filler.

The next step "postroute" uses optDesign -postRoute which removes all fillers again. There is no later place where these fillers would be added again.

Could you please help me to persuade optDesign to let my fillers alone? :-)

Thanks

  Hansi

Parents

  • Hi!

    Thanks for the informative answer.

    I've also found the mentioned passage in the documentation of Encounter 8.1.

    I've verified the problem still exists by loading the data resulting from the "route" step and simply executing

    optDesign -postRoute

    from the command prompt. It still removes all filler cells but doesn't add new ones.

    Then I've tried Encounter 9.12, loaded the data from "route" and executed the very same command. It indeed adds filler cells after it is done. 

    **optDesign ... cpu = 0:00:02, real = 0:00:02, mem = 346.6M **
*INFO: Adding fillers to top-module.
*INFO:   Added 1 filler inst  (cell FILL25 / prefix FILL).
*INFO:   Added 12 filler insts (cell FILL10 / prefix FILL).
*INFO:   Added 19 filler insts (cell FILL5 / prefix FILL).
*INFO:   Added 36 filler insts (cell FILL2 / prefix FILL).
*INFO:   Added 47 filler insts (cell FILL1 / prefix FILL).
*INFO: Total 115 filler insts added - prefix FILL (CPU: 0:00:00.1).
*INFO: Checking for DRC violations on added fillers.
*INFO: Iteration 0-#1, Found 0 DRC violation  (real: 0:00:00.0).
*INFO: Adding fillers to top-module.
*INFO:   Added 0 filler inst of any cell-type.
*INFO: End DRC Checks. (real: 0:00:00.0 ).
*** Finished optDesign ***

    So it seems version 8.1 (v08.10-s273_1) really has a bug here, both in the 32 as well as the 64 bit version. :-(

    Thanks

      Hansi

Reply

  • Hi!

    Thanks for the informative answer.

    I've also found the mentioned passage in the documentation of Encounter 8.1.

    I've verified the problem still exists by loading the data resulting from the "route" step and simply executing

    optDesign -postRoute

    from the command prompt. It still removes all filler cells but doesn't add new ones.

    Then I've tried Encounter 9.12, loaded the data from "route" and executed the very same command. It indeed adds filler cells after it is done. 

    **optDesign ... cpu = 0:00:02, real = 0:00:02, mem = 346.6M **
*INFO: Adding fillers to top-module.
*INFO:   Added 1 filler inst  (cell FILL25 / prefix FILL).
*INFO:   Added 12 filler insts (cell FILL10 / prefix FILL).
*INFO:   Added 19 filler insts (cell FILL5 / prefix FILL).
*INFO:   Added 36 filler insts (cell FILL2 / prefix FILL).
*INFO:   Added 47 filler insts (cell FILL1 / prefix FILL).
*INFO: Total 115 filler insts added - prefix FILL (CPU: 0:00:00.1).
*INFO: Checking for DRC violations on added fillers.
*INFO: Iteration 0-#1, Found 0 DRC violation  (real: 0:00:00.0).
*INFO: Adding fillers to top-module.
*INFO:   Added 0 filler inst of any cell-type.
*INFO: End DRC Checks. (real: 0:00:00.0 ).
*** Finished optDesign ***

    So it seems version 8.1 (v08.10-s273_1) really has a bug here, both in the 32 as well as the 64 bit version. :-(

    Thanks

      Hansi

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.