Post Go back to editing

Constraints

Thread Summary

The user asked about the meaning and necessity of specific CMOS clock latency constraints (2 ns early, 5 ns late) for the ADRV9001 on a Zedboard. The final answer explains that these values account for PCB trace delays and component propagation delays, and advises recalculating these values for a custom board. The accompanying answer clarifies that these constraints ensure the design meets setup and hold timing requirements.
AI Generated Content
Category: Hardware
Product Number: adrv9001

In the example project of ADRV9001 for zedboard, the CMOS constraint file have the following constraint. 

set_clock_latency -source -early 2 [get_clocks rx1_dclk_out]
set_clock_latency -source -early 2 [get_clocks rx2_dclk_out]

set_clock_latency -source -late 5 [get_clocks rx1_dclk_out]
set_clock_latency -source -late 5 [get_clocks rx2_dclk_out]

Can someone explain these? Also, do I need to add these on my project?
I am using adrv9001 on a custom board with a Zynq7000 soc. 

Thread Notes

  • Hello AliAhmad,

    Those constraints are used to define a range for clock arrival uncertainty for 2 clocks: rx1_dclk_out and rx2_dclk_out. Basically, it defines an early arrival (2 ns delay) or a late arrival (5 ns delay), which are then used by the timing analyzer to check for timing violations.
    The timing analyzer uses these bounds to check both setup timing (data capture) against the late case and hold timing (data stability) against the early case, ensuring your design can handle the worst-case clock arrival scenarios.
    If you are using a custom board, you might need to modify these values based on your board design, as they model real-world delays such as PCB trace lengths, clock buffer propagation delays, and jitter from the clock source.

    I hope this answers your question!

  • Where do the values of 2 and 5 come from? How may I calculate these values for my own board? Also, the difference of 2 and 5 seems very excessive. 

  • The values of 2 and 5 ns (early and late corners) have been calculated by taking into account the real physical lengths of the PCB traces as well as any delays introduced by other components on the signal path. For your custom board you need to calculate the PCB trace delay (depends on the type of dielectric used in the PCB, typically ~6 inches/ns in FR4) and the component propagation delay for components sitting on the signal path, you should find this information in the datasheets of the components you used.

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.