Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronic Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

Xlinix/constraints Multicycle Paths (FROM/THRU/TO)

Status
Not open for further replies.

cmos babe

Full Member level 4
Joined
Jan 15, 2005
Messages
209
Helped
11
Reputation
22
Reaction score
0
Trophy points
1,296
Location
Dubai
Activity points
1,899
xilinx multicycle multiplier

Can someone show me an example of how this constraint is used?

According to the constraints guide :
Multicycle Paths (FROM/THRU/TO)
Definition
Establishes a maximum acceptable time delay between groups of elements relative to
another timing specification.
When should this constraint be used? For example in my design the ALU is by far the worst-case path , how can multicycle path constraint be used in this situation ? and how will it affect the overall behavior of the design? THANKS
 

vomit

Full Member level 2
Joined
Jun 14, 2002
Messages
148
Helped
14
Reputation
28
Reaction score
4
Trophy points
1,298
Activity points
1,527
xilinx multicycle paths

For your example: suppose you have a 10 ns clock period and a multiplier that takes 13 ns to calculate the answer.

If you make your control path that it launches the multiplication at clock edge @ time = 0 ns.
If you don't clock (clock enable=false) what's coming out of the multiplier at time = 10ns, and clock the result in at time = 20 ns, you have created a "multicycle path". The path itself seems 10 ns (because it is between 2 flipflops that are attached to a 10 ns clock period. But as you (human) know (by design) that one of the clocks is never enabled one in 2 clock edges, and the effective data flow only is 20 ns, this is a fake constraint. So you have to relax it by telling the Xilinx optimisation tools that they only need to take 20 ns as constraint if going THRU the multiplier.

Hope this was helpful. Look in the Xilinx Answers Database for training on this and other constraints.
 

    cmos babe

    points: 2
    Helpful Answer Positive Rating

drwho78

Full Member level 3
Joined
Dec 31, 1999
Messages
163
Helped
10
Reputation
20
Reaction score
5
Trophy points
1,298
Activity points
1,143
multicycle path xilinx

Refer to this file for timing constaints:
 

    cmos babe

    points: 2
    Helpful Answer Positive Rating
Status
Not open for further replies.
Toggle Sidebar

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Top