Repository navigation
Tighten gf12 swerv_wrapper clocks - #4674
eder-matheus merged 2 commits into
Conversation
Signed-off-by: LucasYuki <lucasyuki@yahoo.com.br>
Signed-off-by: LucasYuki <lucasyuki@yahoo.com.br>
There was a problem hiding this comment.
Code Review
This pull request updates the timing constraints in constraint.sdc for the swerv_wrapper design, reducing the clock periods for both the core clock and the JTAG clock from 1500 ps to 1000 ps, along with proportional adjustments to input and output delays. The review feedback correctly points out that treating the JTAG clock as synchronous to the core clock and tightening its period to 1 GHz is unrealistic and can negatively impact timing closure. The reviewer suggests keeping the JTAG clock at a realistic slower frequency (e.g., 100 MHz), defining the clock domains as asynchronous, and scaling the JTAG input/output delays accordingly.
🔍 QoR checkMetrics reflect the PR merge build — i.e. what will land on the target branch. Commit 62 design(s) checked — 0 with regression(s), 0 without a comparable baseline. |
Tighten gf12 swerv_wrapper clocks: 1500 ps → 1000 ps
File:
flow/designs/gf12/swerv_wrapper/constraint.sdccore_clock/vclk_core_clockperiodjtag_clock/vclk_jtag_clockperiodWhy
Results (full flow)
At 1000 ps the worst path is internal core logic (
lsu_lsc_ctl.addr_in_pic_dc3ff→pic_ctrl_inst.picm_wre_flop). The design's limit is about 1110–1155 ps.