T5.1.1 Restore the Same-Edge Hold Check

MediumFix25 minOpenROAD · serverReview the topic

Keep the two-cycle setup allowance while restoring the intended same-edge hold relationship.

Hardware context: Enable-controlled two-cycle datapath. Keep the intended setup and same-edge hold relationships.

The supplied enable toggles every cycle, so the selected datapath registers transfer on alternate edges. The existing setup multiplier is justified, but its default hold relationship is wrong.

Choose the setup and hold multipliers for only the supplied source and destination register groups. Ordinary single-cycle paths stay timed. External output timing is outside this internal-path exercise.

Requirements

RequirementLimitUnit
Cycles permitted by the enable protocol= 2count
Hold multiplier error from setup − 1= 0count
Maximum slack≥ 0.1ns
Minimum slack≥ 0.2ns

Live analysis: Live TT OpenSTA at a 1 ns clock on the two-cycle datapath from T5.1. Only the authored endpoint-specific multicycle constraints may change.

Full specification
JSON fieldAllowed valuesMeaning
setup_cycles1, 2, 3The transfer protocol permits two clock cycles.
hold_cycles0, 1, 2Zero omits the explicit hold adjustment; positive values apply it to the same endpoints.

Live TT OpenSTA at a 1 ns clock on the two-cycle datapath from T5.1. Only the authored endpoint-specific multicycle constraints may change.

Numeric checks use inclusive bounds. A missing measurement always fails. Only the documented fields are accepted.

Examples

Example 1

Matched Multipliers
Input
A candidate configuration for the fixed circuit and stated environment.
Output
Cycles permitted by the enable protocol: 2
Hold multiplier error from setup − 1: 0
Maximum slack: 0.2419 ns
Minimum slack: 0.2863 ns

The protocol and edge relationship must be correct as well as the reported slack.

Example 2

Setup Adjustment Alone
Input
{
  "setup_cycles": 2,
  "hold_cycles": 0
}
Output
Cycles permitted by the enable protocol: 2
Hold multiplier error from setup − 1: 1
Maximum slack: 0.2419 ns
Minimum slack: -0.3389 ns

The protocol and edge relationship must be correct as well as the reported slack.

Example 3

One-Cycle Setup
Input
{
  "setup_cycles": 1,
  "hold_cycles": 0
}
Output
Cycles permitted by the enable protocol: 1
Hold multiplier error from setup − 1: 0
Maximum slack: -0.7581 ns
Minimum slack: 0.2863 ns

The protocol and edge relationship must be correct as well as the reported slack.

Submission Rules

  • Submit one JSON object with every documented configuration field. The supplied circuit and external environment stay fixed.
  • Run measures your configuration. Submit applies the same requirements and records the result.
  • The stated stage and cell corner define this exercise; passing does not establish full chip sign-off.

Hints

Hint 1

A setup multiplier also changes the default hold edge.

Hint 2

Use matching source and destination groups for both exceptions.

Hint 3

An extra hold cycle can conceal a requirement even when the worst slack looks unchanged.

What is checked: Live TT OpenSTA at a 1 ns clock on the two-cycle datapath from T5.1. Only the authored endpoint-specific multicycle constraints may change.

Run and Submit use the same measured requirements. Run is a preview; Submit records an attempt. The fixed circuit and allowed settings use the pinned OpenROAD/OpenSTA engine.

More problems on this topic

Report a problem with this page

Your configuration JSONSaved locally
Ln 1, Col 1Ctrl/⌘ + Enter runs
Not run yet

Run your configuration to inspect the result.

OpenROAD · server