Stats

  • Locked Locked
  • Replies 4
  • Subscribers 63
  • Views 15094
  • 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

how to prevent the use of specific library cells for some instance in the design?

diablo

how to prevent the use of specific library cells for some instance in the design?

I tried

set_attribute_avoid true {TLAT*} top_design/inst1

but this prevent this cell to be used from entire design instead of just inst1.

Thanks for your time.

Regards. 

 

 

 

  • grasshopper

     The same technology used for top-down MSV called libray domains, enables this. Library domains are a simple yet incredibly powerful concept in RC. Basically you would do something like

    create_library_domain withLat
    create_library_domain withoutLat

    set_attr library_domain {my_lib} [find / -library_domain withLat]
    set_attr library_domain {my_lib} [find / -library_domain withoutLat]

    set_attr avoid true [find [find / -library_domain withoutLat] -libcell LAT*]

    set_attr default true [find / -library_domain withLat]
    set_attr libray_domain withoutLat <blocks with latch avoided>

    An interesting blog discussing the use of the same technology for accurate power modelling can be found at

     http://www.cadence.com/community/blogs/ld/archive/2009/03/31/dont-let-power-kill-your-project.aspx

    good luck,

    gh-

  • diablo

     Thanks gh for your suggestion and sharing the interesting blog about library domain. I appreciate your help. 

  • sudhirjain

    Gh, Is similar possible in SOC Encounter as well?

    I want to restrict some instances for be optimized with one set of libs and rest of the instances with all the libs.

     

    thanks and regards

    Sudhir

  • dacyace24

     Got the same problem..thanks for answering and sharing what you know grasshopper, this is a good source of information, just lucky to read some ideas here..

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.