• 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. High-Level Synthesis
  3. Genus Synthesis Timing Report does not make any sense

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 22
  • Views 18132
  • 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

Genus Synthesis Timing Report does not make any sense

saw235
saw235 over 5 years ago

I don't understand how timings are calculated in genus. Below is the synthesis timing report of one of my design, it mentions that critical path is met with 0 slack but the calculation does not make any sense to me because the datapath is 567 ps and the capture time is at 350 ps. So how is it that the timing is met? Usually there are some kind of negative slack if the timing is not met. 

There seems to be some ambiguity going on here when one flop is launched at rising edge and captured at the falling edge. 

I am targeting 1 GHz, hence target clock period is constrained to 1000ps. 

============================================================
Generated by: Genus(TM) Synthesis Solution 17.20-p003_1
Generated on: Jan 03 2020 05:55:41 pm
Module: top
Operating conditions: TT_0P80V_0P00V_0P00V_0P00V_25C (balanced_tree)
Wireload mode: enclosed
Area mode: timing library
============================================================


Path 1: MET (0 ps)
Group: l2clk
Startpoint: (R) lsu_stbuf/stbuf_fwdbyteen_lo_dc3ff_dout_reg[1]/CLK
Clock: (R) l2clk
Endpoint: (R) dec_decode_illegal_any_ff_clkhdr_clkhdr_en_ff_reg/D
Clock: (F) l2clk

Capture Launch
Clock Edge:+ 500 0
Src Latency:+ 0 0
Net Latency:+ 0 (I) 0 (I)
Arrival:= 500 0

Uncertainty:- 150
Required Time:= 350
Launch Clock:- 0
Data Path:- 567
Slack:= 0

  • 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