• 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. Excluded pin during CTS

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 14968
  • 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

Excluded pin during CTS

archive
archive over 19 years ago

During CTS-run I've defined my clocktree as below:

AutoCTSRootPin TIMMCORE/u_core/u_coss/u_efc/u_fb_fs/f_wre_reg/Q
MaxDelay 7.0ns # set_clock_latency
MinDelay 6.7ns # default value
MaxSkew 300ps # set_clock_uncertainty
SinkMaxTran 900ps # set_clock_transition
BufMaxTran 900ps # set_clock_transition
Buffer dly1x3pdv dly2x3pdv dly2x8pdv dly3x3pdv
RouteType standard_clk
AddDriverCell cnbfx6pdv
PadBufAfterGate NO
NoGating NO
DetailReport YES
RouteClkNet YES
PostOpt YES
ExcludedPin
+ TIMMCORE/u_core/u_coss/u_efc/u_fb_fs/loc_tdo7_reg/TI
LeafPin
+ TIMMCORE/u_core/u_coss/u_efc/u_flash/WRE
END

But after CTS, the delay from the clock root to */TI
as same as the delay to the */WRE. My expecting is that the */TI pin should be excluded from the clocktree.

Ps. I'm using (cadence_fe 04.20-s315_1_USR2 )


Originally posted in cdnusers.org by DN
  • Cancel
  • archive
    archive over 19 years ago

    I've just found that when you define (SetDPinAsSync YES) in the CTS-configuration file then it works.

    From user guider
    SetDPinAsSync YES | NO
    Controls whether CTS automatically treats the D-pins of flip-flops as synchronous pins.

    D-pins include

    Data pins

    Enable pins

    Scan-in pins

    Scan-enable pins

    Synchronous set and reset pins

    Default: If you omit this statement, CTS treats the D-pins of flip-flops as excluded pins. That is, CTS does not treat the pins as synchronous pins.


    Originally posted in cdnusers.org by DN
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    Hi, Let me add few more comments on your topics,
    The alternative way other then adding in script file is by setting the same in CTSMode "setCTSMode -setDPinAsSync " before loading ctstch script file.

    Then this is global for all the other CTS trees.
    Its allways adviceble to set soft rule for Preferred layers like avalable top metals (M5 , M4 ) in setCTSMode command .
    like ( setCTSMode -topPreferredLayer M4  -bottomPreferredLayer M3 ) .
    BTW how was your correlation of skew and delay between clk- route only and post route phase.

    Regards,
    Mohan


    Originally posted in cdnusers.org by mohanch007
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    Hi, Let me add few more comments on your topics,
    The alternative way other then adding in script file is by setting the same in CTSMode "setCTSMode -setDPinAsSync " before loading ctstch script file.

    Then this is global for all the other CTS trees.
    Its allways adviceble to set soft rule for Preferred layers like avalable top metals (M5 , M4 ) in setCTSMode command .
    like ( setCTSMode -topPreferredLayer M4  -bottomPreferredLayer M3 ) .
    BTW how was your correlation of skew and delay between clk- route only and post route phase.

    Regards,
    Mohan


    Originally posted in cdnusers.org by mohanch007
    • 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