• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Logic Design
  3. RTL Compiler, Min Libraries and CPF

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 62
  • Views 14658
  • 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

RTL Compiler, Min Libraries and CPF

moogyd
moogyd over 13 years ago

Hi,

For synthesis (RTL compiler) I define a worst case libraries read_cpf -libraries, and in the CPF I use

define_library_set -name my_lib_set _librares {libA_slow.lib libB_slow.lib libC_worst.lib}

 i.e. I load multiple worst case librarie (there are actually about 15, from different vendors)

I then export the CPF for the backedn. This works, but....

My backend engineer  is complaining that the CPF file does not contain the min libraries.In principle, I just add then in the same way, but I need RTL compiler to ignore the min libraries.

How do people usually manage this issue ?

Thanks for suggestions/links

Steven

 

  • Cancel
Parents
  • grasshopper
    grasshopper over 13 years ago

     You have 2 choices. If using golden CPF as source to both RC and EDI, you can do

     . . .

    set_cpf_version 1.1

    define_library_set -name wcTim -libraries [concat $stdcell(timing,$pvt(cell,wcTim)) $memory(timing,$pvt(mem,wcTim))]
    define_library_set -name wcPow -libraries [concat $stdcell(timing,$pvt(cell,wcPow)) $memory(timing,$pvt(mem,wcPow))]

    if {[regexp -nocase {/(edi|encounter)$} [info nameofexecutable]]} {
        define_library_set -name bcTim      -libraries [concat $stdcell(timing,$pvt(cell,bcTim))  $memory(timing,$pvt(mem,bcTim))]
        define_library_set -name typ        -libraries [concat $stdcell(timing,$pvt(cell,typ))    $memory(timing,$pvt(mem,typ))]
    }
    . . .

    so certain library sets will only be enabled when read by tools of your choice

    If relying on RC generated CPF for downstream tools you can ready everything in and then in RC you can remove them or set avoids/dont_use in all cells from those set along the lines of

     

    set_attr avoid true *bcTim*/*

     

    gh-

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • grasshopper
    grasshopper over 13 years ago

     You have 2 choices. If using golden CPF as source to both RC and EDI, you can do

     . . .

    set_cpf_version 1.1

    define_library_set -name wcTim -libraries [concat $stdcell(timing,$pvt(cell,wcTim)) $memory(timing,$pvt(mem,wcTim))]
    define_library_set -name wcPow -libraries [concat $stdcell(timing,$pvt(cell,wcPow)) $memory(timing,$pvt(mem,wcPow))]

    if {[regexp -nocase {/(edi|encounter)$} [info nameofexecutable]]} {
        define_library_set -name bcTim      -libraries [concat $stdcell(timing,$pvt(cell,bcTim))  $memory(timing,$pvt(mem,bcTim))]
        define_library_set -name typ        -libraries [concat $stdcell(timing,$pvt(cell,typ))    $memory(timing,$pvt(mem,typ))]
    }
    . . .

    so certain library sets will only be enabled when read by tools of your choice

    If relying on RC generated CPF for downstream tools you can ready everything in and then in RC you can remove them or set avoids/dont_use in all cells from those set along the lines of

     

    set_attr avoid true *bcTim*/*

     

    gh-

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information