Home > Community > Forums > Digital Implementation > avoid use of certain cells within a subdesign

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 avoid use of certain cells within a subdesign 

Last post Wed, Jun 4 2008 10:27 AM by archive. 1 replies.
Started by archive 04 Jun 2008 10:27 AM. Topic has 1 replies and 1291 views
Page 1 of 1 (2 items)
Sort Posts:
  • Wed, Jun 4 2008 10:27 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,910
    avoid use of certain cells within a subdesign Reply

    I've used create_library_domain+set_attribure avoid true... commands in RC to avoid instantiation of certain cells within a subdesign.

    Now I'm in Encounter. What is the best way to avoid optimization to replace cells and use those I didn't want?
    I've found some options
    a)setOptMode -noRestruct
    b)set_dont_touch on cells I don't want it to be replaced

    (a) is not desirable because it's a global option and  there are modules I'd like to let Encounter to optimize
    (b) is ok, but I would like to let Encounter  optmize(resize, restructu) whenever needed but just not using some types of cells.

    Do you suggest any other option?
    Thanks.


    Originally posted in cdnusers.org by mhkataoka
    • Post Points: 0
  • Wed, Jun 4 2008 10:34 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,910
    RE: avoid use of certain cells within a subdesign Reply

    No easy to undel that in Encounter...
    One possible workAround is to:
    1- Setup your restrictive dontUse list
    2- Run a full block optimization
    3- set a dontTouch on your specific module
    4- relax your dontUse list
    5- run incremental optimization

    For the step 2, you might have to specify a path_group (Someting available in 71), if your critical path is outside your special module, to force encounter to work for path within it.

    Pat.


    Originally posted in cdnusers.org by bougantp
    • Post Points: 0
Page 1 of 1 (2 items)
Sort Posts:
Started by archive at 04 Jun 2008 10:27 AM. Topic has 1 replies.