cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
bennie123
Visitor
Visitor
9,787 Views
Registered: ‎01-12-2014

Question on From-To

Hi, Experts

 

Now my quesiton is the constraint on the From-to is a constant delay or only a maximum delay when I give a constranit in th UCF or editor. For instance, when I give a 10ns delay for a constraint on 'PAD to FF', the timing report only told me MAX Delay is 6.423ns. Therefore I am very confused. Is 10ns  a constant value or maximum value? Or if when the gate-logic is less than 10ns, some man-made delay will be added, won't it?

If indeed it is a constant delay, who can't tell me how to read the timing report?

 

Maybe this is not big problem to you, experts. Please provide some points to me. :)

Thanks.

0 Kudos
5 Replies
graces
Moderator
Moderator
9,786 Views
Registered: ‎07-16-2008

The value is maximum delay. The tool will make effort to obey the constraint so that the path delay doesn't exceed 10 ns.

The max delay shown in timing report is the performance that the tool can achieve. There's some margin (positive slack) here.

 

ISE timing doesn't support minimum delay.

-----------------------------------------------------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
If starting with Versal take a look at our Versal Design Process Hub and our Versal Blogs.
-----------------------------------------------------------------------------------------------------------------------
0 Kudos
bennie123
Visitor
Visitor
9,783 Views
Registered: ‎01-12-2014

Thank you for your quick response.
I also see many points in the reference. It is said that this constaint can help designer implement some fixed delay. Especailly in some cases such as 2 different clock domani or case 'from pad to pad', it could achieve some functionality effectively. If it is only a maximum value, I believe it will be difficult to match the designer's strange idea.
For example when I hope some fix delay from one pad to another which must be able to match a timing delay of another group of logic, how can only a maximum delay configuraiton do it? As we know, usually in this case over-long or over-short both cause timing error finally.
OK. In another word, if as you said, could you tell me how to achieve my purpose with ISE tools?
Thank you very much.
0 Kudos
graces
Moderator
Moderator
9,779 Views
Registered: ‎07-16-2008

There's no way to implement a fixed delay in FPGA. Considering the PVT variation, the path delay will vary between a range in hardware.

 

For a PAD TO FF path, the most viable way to get a consistent path delay is to place the FF in IOB. Of cousre the FF needs to be I/O register (i.e. there's no combinatorial logic between pad and FF). This ensures dedicated routing resource to be utilized.

-----------------------------------------------------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
If starting with Versal take a look at our Versal Design Process Hub and our Versal Blogs.
-----------------------------------------------------------------------------------------------------------------------
0 Kudos
bennie123
Visitor
Visitor
9,777 Views
Registered: ‎01-12-2014

In doc ug612, the segment 'Pad-to-Pad path' of P77 tell us that the expection slow path is likely to be achieved. How to understand this segement?
My project need to transfer LVDS to TTL, and then transfer DDR to SDR. So it seems impossible to implement FF in IOB.
0 Kudos
graces
Moderator
Moderator
9,760 Views
Registered: ‎07-16-2008

The slow exception section gives another method to define multi-cycle constraints.

The path between FFs that have CE pin can have requirement of 2 or more cycles rather than a single cycle.

 

Anyway the delay value is a guided max delay for implementation tool. It will by no means result in a fixed delay.

You can preserve the routing delay as much as possible by locking down the associated components and apply directed routing constraint (DIRT).

-----------------------------------------------------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
If starting with Versal take a look at our Versal Design Process Hub and our Versal Blogs.
-----------------------------------------------------------------------------------------------------------------------
0 Kudos