Sign In

Don't have a Xilinx account yet?

  • Choose to receive important news and product information
  • Gain access to special content
  • Personalize your web experience on Xilinx.com

Create Account

Username

Password

Forgot your password?
XClose Panel
Xilinx Home
Reply
Contributor
403464238
Posts: 51
Registered: ‎08-08-2011
0

virtex5 timing constraints questions

Hi everyone!

    when  I did some timing constraints , setup time didn't meet requirement.I want to use OFFSET CONSTRAINT to meet setup time.However  the port isn't external pad but internal port .For a internal pin,How can I make it meet setup time requirement ? Thanks advance!  

Expert Contributor
rcingham
Posts: 2,010
Registered: ‎09-09-2010
0

Re: virtex5 timing constraints questions

What FPGA?
Which version of ISE?
Post the portion of Timing Report with the error message?

"For an internal signal, how can I make it meet setup time requirement?"

Generally, reduce the amount of logic between registers, which may require a technique known as pipelining, or else reduce the routing delay, by persuading the tool to place the registers close together. Perhaps the logic will permit a "multicycle" constraint to be used, but without seeing your logic, it is impossible to know.


------------------------------------------
"If it don't work in simulation, it won't work on the board."
Moderator
kren
Posts: 159
Registered: ‎08-21-2007
0

Re: virtex5 timing constraints questions

I suggest you use period constriant for this internal signal.

Contributor
403464238
Posts: 51
Registered: ‎08-08-2011
0

Re: virtex5 timing constraints questions

Thanks a lot ! In fact ,I tried  to use period constraint ,but  it can't meet setup time.Do you have other suggestions? Thanks advance! 

Contributor
403464238
Posts: 51
Registered: ‎08-08-2011
0

Re: virtex5 timing constraints questions

ISE version is 10.1. The device is xc5vfx70t-2ff1136.
Error  message as follows:

timing constraint: NET "tile0_rxusrclk0_i" PERIOD = 4 ns HIGH 50%;

 191 paths analyzed, 146 endpoints analyzed, 2 failing endpoints
 2 timing errors detected. (2 setup errors, 0 hold errors)
 Minimum period is   4.104ns.
--------------------------------------------------------------------------------
Slack:                  -0.104ns (requirement - (data path - clock path skew + uncertainty))
  Source:               inst_mydesign/tile0_mydesign_i/gtx_dual_i (HSIO)
  Destination:          inst_dff1/Qout_0 (FF)
  Requirement:          4.000ns
  Data Path Delay:      4.069ns (Levels of Logic = 0)
  Clock Path Skew:      0.000ns
  Source Clock:         tile0_rxusrclk0_i rising at 0.000ns
  Destination Clock:    tile0_rxusrclk0_i rising at 4.000ns
  Clock Uncertainty:    0.035ns

  Clock Uncertainty:          0.035ns  ((TSJ^2 + TIJ^2)^1/2 + DJ) / 2 + PE
    Total System Jitter (TSJ):  0.070ns
    Total Input Jitter (TIJ):   0.000ns
    Discrete Jitter (DJ):       0.000ns
    Phase Error (PE):           0.000ns

  Maximum Data Path: inst_mydesign/tile0_mydesign_i/gtx_dual_i to inst_dff1/Qout_0
    Location               Delay type         Delay(ns)  Physical Resource
                                                         Logical Resource(s)
    ---------------------------------------------------  -------------------
    GTX_DUAL_X0Y3.RXDATA00 Tgtxcko_RXDATA        1.433   inst_mydesign/tile0_mydesign_i/gtx_dual_i
                                                         inst_mydesign/tile0_mydesign_i/gtx_dual_i
    OLOGIC_X1Y127.D1       net (fanout=1)        2.284   tile0_rxdata0_i<0>
    OLOGIC_X1Y127.CLK      Todck                 0.352   inst_dff1/Qout<0>
                                                         inst_dff1/Qout_0
    ---------------------------------------------------  ---------------------------
    Total                                        4.069ns (1.785ns logic, 2.284ns route)
                                                         (43.9% logic, 56.1% route)
The clock "tile0_rxusrclk0_i" is internal clock,a recovery clock .
Thanks !

Xilinx Employee
ajmirg
Posts: 100
Registered: ‎05-14-2008

Re: virtex5 timing constraints questions

Hi,

 

Source is     GTX_DUAL_X0Y3 and destination is OLOGIC_X1Y127, both are fixed in your design and there is no placement flexibility for the tool, so it tries it's best with routing, but still fails to meet the requirement. 

 

Can you pipeline this path i.e add a registering stage between these two? Note that the latency will increase by 1 in doing so. Pipelining should reduce the routing path, which is currently net (fanout=1)        2.284   tile0_rxdata0_i<0>

 

If you do not pack the  inst_dff1/Qout_0 (FF), the path may improve, but I do not know if you have output path requirements to meet.

 

Cheers,

Xilinx Employee
chrisz
Posts: 85
Registered: ‎05-06-2008
0

Re: virtex5 timing constraints questions

Another suggestion is to use a FROM:TO constraint or multicycle constraint, to constrain this path.