Work out how much logic delay each half-cycle path of the block can hold at a 42.5 % duty cycle.
Hardware context: Rising-edge and falling-edge flops in a half-cycle chain. Budget the logic delay of each half-cycle path at a stated duty cycle.
The block half has a rising-edge flop fr, a falling-edge flop fn and a rising-edge flop fr2. One inverter sits between each pair. The clock is 2 ns, but its high phase is only 0.85 ns: a 42.5 % duty cycle.
A designer will replace the inverter between each pair of flops with new logic. For each path, give the largest total logic delay, including the inverter already on the path, that still meets setup. That is the time from the launch flop's Q changing to the latest moment D may arrive. Use the waveform in the full specification; each answer must be within 5 ps of the live report.
Requirements
| Requirement | Limit | Unit |
|---|---|---|
| Budget error, fr to fn (rise to fall) | ≤ 0.005 | ns |
| Budget error, fn to fr2 (fall to rise) | ≤ 0.005 | ns |
Live analysis: Live OpenSTA at tt_025C_1v80 on the half block with the stated 42.5 % clock, ideal, no wires. The budget is the required time minus the launch flop's Q time on each setup path. Other logic would change the setup time slightly, and the 5 ps tolerance covers that.
Full specification
create_clock -name clk -period 2.0 -waveform {0 0.85} [get_ports clk]
set_clock_transition 0.1 [all_clocks]
| JSON field | Allowed values | Meaning |
|---|---|---|
| rise_to_fall | 0 to 3 | Largest logic delay from fr/Q to fn/D, in ns. |
| fall_to_rise | 0 to 3 | Largest logic delay from fn/Q to fr2/D, in ns. |
Live OpenSTA at tt_025C_1v80 on the half block with the stated 42.5 % clock, ideal, no wires. The budget is the required time minus the launch flop's Q time on each setup path. Other logic would change the setup time slightly, and the 5 ps tolerance covers that.
Numeric checks use inclusive bounds. A missing measurement always fails. Only the documented fields are accepted.
Examples
Example 1
The Full Period- Input
Give each path the whole 2 ns period minus clock-to-Q and setup
- Output
Budget error, fr to fn (rise to fall): FAIL Budget error, fn to fr2 (fall to rise): FAIL
Each path gets one phase of the clock, not the whole period.
Example 2
The Slack Alone- Input
Copy the two setup slacks
- Output
Budget error, fr to fn (rise to fall): FAIL Budget error, fn to fr2 (fall to rise): FAIL
The slack is what is left after the inverter that is already there. The budget includes that inverter.
Example 3
The 50 % Edges- Input
Use the default waveform, with the fall at 1 ns
- Output
Budget error, fr to fn (rise to fall): FAIL Budget error, fn to fr2 (fall to rise): FAIL
The fall comes at 0.85 ns, so the high phase loses 0.15 ns and the low phase gains it.
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
Write the clock with -waveform {0 0.85} in the Try it of T3.2 and read both setup paths.
Hint 2
The launch flop's Q line gives the time the logic may start. The required time is when it must end.
Hint 3
One phase is 0.85 ns and the other 1.15 ns. Check which path gets which.
What is checked: Live OpenSTA at tt_025C_1v80 on the half block with the stated 42.5 % clock, ideal, no wires. The budget is the required time minus the launch flop's Q time on each setup path. Other logic would change the setup time slightly, and the 5 ps tolerance covers that.
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