• 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. How to calculate 'Hold' time in the endpoint report?

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 1091
  • 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 calculate 'Hold' time in the endpoint report?

yamakazu
yamakazu over 9 years ago

Hi,

I want to know how to calculate 'Hold' time in the endpoint report to identify what is wrong. Could you give me the formula to calculate this? Is there any commands to list them up?

Path 1: VIOLATED Hold Check with Pin SW_SD_PAT_Gr_SW_SD_PAT1_M_SD_SEL32_FF_DTS_
KffF8_O1_reg_6/CK
Endpoint:   SW_SD_PAT_Gr_SW_SD_PAT1_M_SD_SEL32_FF_DTS_KffF8_O1_reg_6/D (v)
checked with  leading edge of 'CLK400M'
Beginpoint: SW_SB_RAM_M_U7076/A                                        (^)
triggered by  leading edge of 'CLK400M'
Path Groups: {reg2reg}
Analysis View: func_fhhb_sigrcmindp_erminus
Other End Arrival Time        208.536
+ Hold                        10787.407    <<=======  what is the formula to calculate this?
+ Phase Shift                   0.000
- CPPR Adjustment               9.873
- AOCV Adjustment               3.200
= Required Time               10982.870
  Arrival Time                402.334
  Slack Time                  -10580.536

  • Cancel
Parents
  • J2mh
    J2mh over 9 years ago

    Hi,


    That value is extracted from timing library. I think that value is very large because it is out of range so the tool has extrapolated to that value. Hence, there is a problem with the timing library or the design.

    Regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • J2mh
    J2mh over 9 years ago

    Hi,


    That value is extracted from timing library. I think that value is very large because it is out of range so the tool has extrapolated to that value. Hence, there is a problem with the timing library or the design.

    Regards.

    • 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