• 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. Encounter 8.1 vs 9.1 sdf generation

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 93
  • Views 16936
  • 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

Encounter 8.1 vs 9.1 sdf generation

MzQuarter
MzQuarter over 14 years ago

Hi,

I've used Encounter 8.1 for past projects to generate sdf back-annotation for simulation and it worked great. Now we've moved to Encounter 9.1, but the exact same 8.1 encounter project reloaded in 9.1 gives different results. First of all, the middle field ("typical", my guess) is no longer present, and when I load the sdf in a simulator the delays are all taken as 0 (no delays).  Second, the delays for interconnect are different, and quite often 0. Another difference I noticed is that in 8.1 the value triplets were always the same (which I thought odd), but not in encounter 9.1.

What am I missing? I'm almost sure it's just a setting, but I can't see where or how.

Thanks.

--------------------------------------------------------------------------------
Encounter 8.1:

(INTERCONNECT I_NCS U134/A (0.0037:0.0037:0.0037) (0.0037:0.0037:0.0037))
(INTERCONNECT I_SCLK Q_TRANSACTIONCOMPLETE_REG/CKN (0.0045:0.0045:0.0045) (0.0045:0.0045:0.0045))

Encounter 9.1:

(INTERCONNECT I_NCS U134/A  (0.003::0.004) (0.003::0.004))
(INTERCONNECT I_SCLK Q_TRANSACTIONCOMPLETE_REG/CKN  (0.000::0.000) (0.000::0.000))

  • Cancel
Parents
  • MzQuarter
    MzQuarter over 14 years ago

    Hi Diablo and Martinage,

    I had some time to come back to this problem, and found what I was looking for thanks to your help and pointers. Here is what I did:

    The project comes with wcbc already setup, so I added a typical view in MMMC by following the user guide chapter on MMMC (this thread: http://www.cadence.com/Community/forums/p/11116/13162.aspx).

    In the following lines, "default_mode_setup" and "default_mode_hold" already existed in  my project (bcwc), and point to the same .sdc file. "default_view_setup" and "default_view_hold" were also already defined.

    create_library_set -name typical_libraries -timing {tt_1p5v_25c.lib} -si {tt_1v50_c25.cdB}
    create_rc_corner -name typical_rc_corner -cap_table "typ.capTbl" -T -25 -qx_tech_file "typ.tch"                                                 
    create_delay_corner -name typical_delay_corner -library_set typical_libraries -rc_corner typical_rc_corner
    create_analysis_view -name typical_analysis_view -delay_corner typical_delay_corner -constraint_mode default_mode_setup

    then:
    set_analysis_view -setup {default_view_setup typical_analysis_view} -hold {default_view_hold typical_analysis_view}

    and lastly
    write_sdf -version 2.1 -typ_view typical_analysis_view -min_view default_view_hold -max_view default_view_setup test.sdf

    I quickly checked an entry in the sdf file before and after these, and the early/late entries are unchanged, with new entries in the center field that make sense to me, so I think at worst I didn't break anything.

    Again, thanks to both of you for your help.

    Mz

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • MzQuarter
    MzQuarter over 14 years ago

    Hi Diablo and Martinage,

    I had some time to come back to this problem, and found what I was looking for thanks to your help and pointers. Here is what I did:

    The project comes with wcbc already setup, so I added a typical view in MMMC by following the user guide chapter on MMMC (this thread: http://www.cadence.com/Community/forums/p/11116/13162.aspx).

    In the following lines, "default_mode_setup" and "default_mode_hold" already existed in  my project (bcwc), and point to the same .sdc file. "default_view_setup" and "default_view_hold" were also already defined.

    create_library_set -name typical_libraries -timing {tt_1p5v_25c.lib} -si {tt_1v50_c25.cdB}
    create_rc_corner -name typical_rc_corner -cap_table "typ.capTbl" -T -25 -qx_tech_file "typ.tch"                                                 
    create_delay_corner -name typical_delay_corner -library_set typical_libraries -rc_corner typical_rc_corner
    create_analysis_view -name typical_analysis_view -delay_corner typical_delay_corner -constraint_mode default_mode_setup

    then:
    set_analysis_view -setup {default_view_setup typical_analysis_view} -hold {default_view_hold typical_analysis_view}

    and lastly
    write_sdf -version 2.1 -typ_view typical_analysis_view -min_view default_view_hold -max_view default_view_setup test.sdf

    I quickly checked an entry in the sdf file before and after these, and the early/late entries are unchanged, with new entries in the center field that make sense to me, so I think at worst I didn't break anything.

    Again, thanks to both of you for your help.

    Mz

    • 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