• 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. Digital Implementation
  3. Getting an xls file after generating the qor in RTL

Stats

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

Getting an xls file after generating the qor in RTL

Electronic Guy
Electronic Guy over 14 years ago

 Hi,

 

Is there any way to get an xls with all the qor reports of our syntheis in RTL compiler? In the DC using the dump_metrics command helps in creating an xls .. is there any way to do what in RTL compiler?

 

Thanks

  • Cancel
  • mclarke
    mclarke over 14 years ago

    Hi E. Guy,

       Yes RC has a very flexable and user configurable statistics capturing/reporting mechanism. Control is through the statistics command and a few statistics attributes. Multiple runs can be stored in the same db, then this db can be reload, compared or exported as text (for import to xls). The RC documentation covers the basic but contact me if you would like a working example.

    Cheers, Mike

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Electronic Guy
    Electronic Guy over 14 years ago

     Hi Mike,

     

    Can you provide me with a working example please??

     

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • grasshopper
    grasshopper over 14 years ago

     Hi Electronic Guy,

     here is a quick example

     . . .

    ## Optional Attributes
    set_attribute statistics_run_id statsdb_run /
    set_attribute statistics_run_description "This is a sample run of statsDB" /
    set_attribute statistics_db_file emac.stats_db /

    include lib_incl.tcl
    include ple_incl.tcl ;# This file is empty if no PLE was used

    include hdl_incl.tcl
    elaborate ${topDesign}

    if [file exists design.sdc] { read_sdc design.sdc }
    set sdcErrorFile [open ${runName}_error.info w]
    puts $sdcErrorFile $::dc::sdc_failed_commands
    close $sdcErrorFile

    ## User defined statsDB stage
    statistics log -stage_id constraints
    statistics write -to_file design.stats_db


    ##User defined metric
    #statistics add_metric -name effort_level -function get_effort_level
    #proc get_effort_level {} {get_attribute synthesize_effort_level /}

    synthesize -to_generic -effort low ${designName}
    synthesize -to_mapped -effort low -no_incr ${designName}
    synthesize -to_mapped -effort low -no_incr ${designName}

    ## Final report
    statistics report -run_id statsdb_run

    and this commands/attributes should be documented in the manuals as well

      hope this helps,

    gh-

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mclarke
    mclarke over 14 years ago
    Could you send youy contact info directly to mclarke@cadence.com. Since my email direct to you bounced.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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