Skip to content

Tighten gf12/coyote clock period - #4705

Open
jorge-ferreira-pii wants to merge 1 commit into
The-OpenROAD-Project:masterfrom
The-OpenROAD-Project-staging:secure-jorge-design-owner
Open

jorge-ferreira-pii wants to merge 1 commit into
The-OpenROAD-Project:masterfrom
The-OpenROAD-Project-staging:secure-jorge-design-owner

Conversation

@jorge-ferreira-pii

Copy link
Copy Markdown
Contributor
gf12/coyote (finish) master (4.0 ns) this branch (2.4 ns)
WNS (ns) +0.671 -0.043
TNS (ns) 0 -2.167
Violating endpoints 0 65

Scale the input and output delays with it, at half the period.

Signed-off-by: Jorge Ferreira <jorge.ferreira@precisioninno.com>
@jorge-ferreira-pii jorge-ferreira-pii self-assigned this Oct 20, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the SDC constraints for the Coyote design, reducing the clock period for both core_clk and vclk from 4.0 ns to 2.4 ns, and scaling down the input and output delays accordingly to 1.2 ns. The reviewer notes that this reduction leads to timing violations with negative slack. To resolve this, it is recommended to either slightly relax the clock period to 2.45 ns or apply further physical and synthesis optimizations to achieve clean timing closure.

Comment on lines +9 to +10
create_clock -name core_clk -period 2400 -waveform {0.0000 1200} [get_ports {clk_i}]
create_clock -name vclk -period 2400

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The proposed clock period of 2.4 ns (2400 ps) results in timing violations, as indicated in the pull request description (WNS of -0.043 ns, TNS of -2.167 ns, and 65 violating endpoints). To achieve clean timing closure (WNS >= 0), consider one of the following approaches:\n\n1. Slightly relax the clock period: Relaxing the clock period to 2.45 ns (2450 ps) would provide an additional 50 ps of slack, which should clear the -43 ps violation and result in zero violating endpoints (remember to also update the input/output delays to 1225 ps if keeping them at 50%).\n2. Further physical/synthesis optimization: If 2.4 ns is a strict target, additional optimization steps (such as useful skew, gate sizing, or logic restructuring) must be employed to close the remaining 43 ps of negative slack before merging.

@openroad-ci

openroad-ci commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

🔍 QoR check

Metrics reflect the PR merge build — i.e. what will land on the target branch.

Commit 2eae9ce · Jenkins build #2 · Baseline: build · View build on dashboard

62 design(s) checked — 0 with regression(s), 0 without a comparable baseline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants