Thursday, January 08, 2009     Register | Login | Search | Contact Us
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Subject: avoid use of certain cells within a subdesign
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
mhkataoka
Posts: 1
Online: User is Offline
6/04/2008 10:27 AM  
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.
bougantp
Posts: 19
Online: User is Offline
6/04/2008 10:34 AM  
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.
Posting to forums is available to community members only.
Login or Register

Forums > Digital IC > Floorplanning, Place and route > avoid use of certain cells within a subdesign


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.