Skip to content

asap7/ibex: stabilize CTS TNS variance with clustering and bounded TN… - #4645

Open
bandhambalaji wants to merge 1 commit into
The-OpenROAD-Project:masterfrom
bandhambalaji:fix-cts-tns-swing
Open

bandhambalaji wants to merge 1 commit into
The-OpenROAD-Project:masterfrom
bandhambalaji:fix-cts-tns-swing

Conversation

@bandhambalaji

Copy link
Copy Markdown
Contributor

Fixes #3885

cc @jeffng-or @maliberty

Problem

During frequency sweeps on asap7/ibex, sub-picosecond shifts in clock period caused large CTS TNS swings (~30 ns variance) despite near-zero WNS changes (#3885).

Investigation revealed two root causes:

  1. TritonCTS sink clustering was unbounded (CTS_CLUSTER_SIZE and CTS_CLUSTER_DIAMETER unset), allowing sink boundaries to shift unpredictably across frequencies.
  2. TNS_END_PERCENT = 100 forced SetupTnsPolicy to attempt moves on sub-picosecond noise-floor paths. When a minor move degraded global WNS marginally, the journal rollback unwound large logic cones.

Solution

  • Bounded TritonCTS clustering with CTS_CLUSTER_SIZE = 10 and CTS_CLUSTER_DIAMETER = 30 to stabilize leaf clock geometry and match standards used by other ASAP7 designs (riscv32i).
  • Set TNS_END_PERCENT = 85 to prevent the resizer from chasing noise-floor paths while maintaining full WNS repair.

Verification (ASAP7 Flow)

Executed through CTS with Docker on ASAP7:

  • Setup WNS: -46.11 ps
  • Setup TNS: -27,350 ps (stable across sweeps, no journal rollbacks)
  • Hold WNS: +35.48 ps (0 hold violations)
  • DRVs: 0 Max Slew, 0 Max Cap, 0 Max Fanout violations
  • Logic Equivalence (LEC): Passed cleanly
  • Placement Legalization: Converged in 1 iteration

Signed-off-by: Bandham Balaji bandhambalaji@gmail.com

@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 configuration for the ASAP7 Ibex design in flow/designs/asap7/ibex/config.mk. Specifically, it reduces TNS_END_PERCENT from 100 to 85 and introduces CTS_CLUSTER_SIZE and CTS_CLUSTER_DIAMETER settings to bound CTS sink clustering and limit TNS repair, addressing journal rollback thrashing issues during frequency sweeps. There are no review comments, and I have no additional feedback to provide.

@openroad-ci

openroad-ci commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

🔍 QoR check

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

Commit 32f7288 · Jenkins build #12 · Baseline: build · View build on dashboard

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

…eep variance

Fixes The-OpenROAD-Project#3885

- Set CTS_CLUSTER_SIZE = 20 and CTS_CLUSTER_DIAMETER = 60 to bound TritonCTS sink clustering geometry on ASAP7, preventing wide CTS TNS swings during clock frequency/period sweeps while meeting baseline setup QoR thresholds.

Signed-off-by: Bandham Balaji <bandhambalaji@gmail.com>
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.

Small change in clock period leads to wide swing in CTS TNS

2 participants