cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
7,359 Views
Registered: ‎08-13-2007

How to set up timing analyzer when using both edges of the clock in a S3A device

I'm using both edges of a clock from a DCM ( I'm not using the CLK180 due to lack of BUFGs) the datasheet refers to DCM and Clock tree Duty cycle distortion. These figures don't appear to be taken into account in the timing analyzer ( 10.1SP3). Is the best way just to increase the clock rate to effectively take it into account or have I missed something?

 

0 Kudos
2 Replies
Highlighted
Xilinx Employee
Xilinx Employee
7,338 Views
Registered: ‎11-28-2007

Re: How to set up timing analyzer when using both edges of the clock in a S3A device

Dear,

 

the tools automatically take rising and falling edge clocks into account.

there are no dual-clock FFs in the FPGA fabric except in the Input-Output-Block, so I assume you refer to these FFs.

 

timing analyzer should be correct and you don't use one of the 2 edges of the clock.

if you don't see it in timing analyzer, try to increase the reported amount of paths.

 

maybe you will find the following whitepapers of interest:

http://www.xilinx.com/support/documentation/white_papers/wp257.pdf (about period constraints)

http://www.xilinx.com/support/documentation/white_papers/wp237.pdf (about offset constraints and DDR-FF offset constraints)

 

 

best regards,

Dries

--------------------------------------------------------------------------------------------------------------------
Please mark the Answer as "Accept as solution" if the information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented by clicking the star next to the post.
0 Kudos
Highlighted
Adventurer
Adventurer
7,328 Views
Registered: ‎08-13-2007

Re: How to set up timing analyzer when using both edges of the clock in a S3A device

My question was about clock distortion. The clock out of the DCMs isn't 50:50 ( it will be close but not exact) and after is has gone though buffers and clock tree it will be worse. The datasheet says the distortion in my case may be upto 410ps. This figure appears to be missing from the Timing Analyzer report.

 

dp11 

0 Kudos