Professional Documents
Culture Documents
Global Timing Constraints: PDF Created With Pdffactory Pro Trial Version
Global Timing Constraints: PDF Created With Pdffactory Pro Trial Version
Outline
Instead, the implementation tools try to meet your performance expectations Timing constraints improve the design performance by placing logic closer together so shorter routing resources can be used Note that when we discuss using the Constraints Editor, we are referring to the Xilinx Constraints Editor
Note the logical structure of the placement and pins This design has a maximum system clock frequency of 50 MHz
This is the same design with three global timing constraints entered with the Constraints Editor It has a maximum system clock frequency of 60 MHz Note that most of the logic is placed closer to the edge of the device, where the pins have been placed
Tight timing constraints will increase your compile time Unrealistic constraints will cause the implementation tools to stop Use the synthesis report or the Post-Map Static Timing Report to determine whether your constraints are realistic
After implementing, review the Post-Place & Route Static Timing Report to determine whether your performance objectives were met
If constraints were not met, use the Timing Report to determine the cause
I/O pads Synchronous elements (flip-flops, latches, and RAMs) Step 1: Create groups of path end points Step 2: Specify a timing requirement between the groups All flip-flops, all I/O pads, etc.
Skills Check
Review Questions
A single global constraint can cover multiple delay paths If the arrows are constrained paths, what are the path end points in this circuit? Do all of the registers have anything in common?
FLOP1 D Q FLOP2 D Q FLOP3 D Q
ADATA
CLK BUFG
OUT1
FLOP4 D Q
FLOP5 D Q
OUT2
CDATA
Answers
FLOP1, FLOP2, FLOP3, FLOP4, and FLOP5 They share a clock signal. A constraint that references this net could constrain all delay paths between all of the registers in the design
FLOP1 D Q FLOP2 D Q FLOP3 D Q
ADATA
CLK BUFG
OUT1
FLOP4 D Q
FLOP5 D Q
OUT2
BUS [7..0]
CDATA
Outline
The PERIOD constraint covers paths between synchronous elements clocked by the reference net The PERIOD constraint does NOT cover paths from input pads to output pads (purely combinatorial), from input pads to synchronous elements, or from synchronous elements to output pads
ADATA
CLK BUFG
FLOP4 D Q FLOP5 D Q FLOP1 D Q FLOP2 D Q FLOP3 D Q
OUT1
OUT2
BUS [7..0]
CDATA
The PERIOD constraint uses the most accurate timing information so it can automatically account for:
Clock skew between the source and destination flip-flops Synchronous elements clocked on the negative edge Unequal clock duty cycles Clock input jitter
FF1
FF2
Assume:
CLK 50-percent duty signal on CLK BUFG INV PERIOD constraint of 10 ns Because FF2 will be clocked on the falling edge of CLK, the path between the two flip-flops will actually be constrained to 50% of 10 ns = 5 ns
Clock input jitter is one source of clock uncertainty Clock uncertainty is subtracted from:
PERIOD constraint setup paths OFFSET IN constraint setup paths PERIOD constraint hold paths OFFSET IN constraint hold paths OFFSET OUT constraint paths
Purely combinatorial delay paths do not contain any synchronous elements Purely combinatorial delay paths start and end at I/O pads and are often left unconstrained
Skills Check
Review Questions
Which paths are constrained by a PERIOD constraint on CLK1? Which paths are constrained by a pad-to-pad constraint?
FLOP D Q
LATCH D G Q
OUT1
RAM D
OUT2
Answers
OUT1
OUT2
From input pads to synchronous elements (OFFSET IN) From synchronous elements to output pads (OFFSET OUT) OFFSET OUT
FLOP D Q FLOP D Q FLOP D Q
OFFSET IN
ADATA
CLK BUFG
FLOP D Q FLOP D Q
OUT1
OUT2
BUS [7..0]
CDATA
= Combinatorial Logic
The OFFSET constraint automatically accounts for the clock distribution delay
Provides the most accurate timing information Increases the amount of time for input signals to arrive at synchronous elements (clock and datapaths are in parallel) Reduces the amount of time for output signals to arrive at output pins (clock and datapaths are in series) Uses the jitter defined on the associated PERIOD constraint
Clock Delay
Both the datapath delay and the clock distribution delay are used to calculate OFFSET constraints
Clk OFFSET-IN
T_clk_Out OFFSET-OUT
Skills Check
Review Question
Which paths are constrained by an OFFSET IN and an OFFSET OUT constraint in this circuit?
PADA
FLOP D Q
LATCH D G Q
OUT1
OUT2 PADC
Answer
Which paths are constrained by an OFFSET IN and an OFFSET OUT constraint in this circuit?
OFFSET IN: PADA to FLOP and PADB to RAM OFFSET OUT: LATCH to OUT1, LATCH to OUT2, and RAM to OUT1
PADA
FLOP D Q LATCH D G Q
OUT1
OUT2 PADC
Outline
In the Processes for Source window, expand User Constraints Double-click Create Timing Constraints
The PERIOD and pad-topad constraints can be made on the Global tab Double-click here to make a PERIOD constraint Global pad-to-pad constraint Constraints can be deleted by selecting the constraint in the text window and pressing <Delete>
Active clock edge Duty-cycle Useful for designs with multiple clock signals Can define both frequency and phase relationships
Input jitter
Global OFFSET IN/OUT constraints can also be made on the Global tab
Pad to setup = OFFSET IN
Outline
Review Question
Given the system diagram below, what values would you put in the Constraints Editor so that the system will run at 100 MHz?
3 ns
Answer
Given the system diagram below, what values would you put in the Constraints Editor so that the system will run at 100 MHz?
Upstream Device Downstream Device
7 ns
3 ns
10 ns
8 ns
2 ns
Summary
Performance expectations are communicated with timing constraints The PERIOD constraint covers delay paths between synchronous elements The OFFSET constraint covers delay paths from input pins to synchronous elements and from synchronous elements to output pins The Constraints Editor allows you to create timing constraints
Documentation Technical Tips Timing & Constraints Getting Started The Timing Presentation