• 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. Timing Engine isues **ERROR: (TA-152) complaining about...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 91
  • Views 18877
  • 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

Timing Engine isues **ERROR: (TA-152) complaining about generated clock edges (was: an Error during placement?)

icmaple
icmaple over 15 years ago

During placement, it  issue below Error hint , and placement continues.....

**ERROR: (TA-152): A latency path from the 'Fall' edge of the master clock  at source pin 'clk_adc_in' to the 'Fall' edge of generated clock 'clk18' at pin 'u_center_ctrl/u_clk_gen/u_clkmx2x8m_46/Y' cannot be found. You must modify your create_generated_clock constraint to be consistent with the network topology. The analysis will continue using 0ns source latency for generated clock 'clk18'. For backward compatibility with earlier releases or to remove the edge-to-edge sufficiency checking, you should set the global 'timing_enable_genclk_edge_based_source_latency' to false

Note:  In my sdc file, clk18 defined below:

create_generated_clock -name "clk18"    -edges {1 6 11}  -source [get_ports clk_adc_in]   [get_pins u_center_ctrl/u_clk_gen/clk_tuner_anatv]

Is the clk18 defined incorrectly?

 

  • Cancel
Parents
  • icmaple
    icmaple over 15 years ago

    thank you very much,BobD.

    I learnt much from your example.  as for my issue, i found the reason which was a wrong definition of generated clock. it should be -edge { 1 5 11}.   so it is inconsistent with logic topology.  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • icmaple
    icmaple over 15 years ago

    thank you very much,BobD.

    I learnt much from your example.  as for my issue, i found the reason which was a wrong definition of generated clock. it should be -edge { 1 5 11}.   so it is inconsistent with logic topology.  

    • 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