RHSResearchLLC / NiteFury-and-LiteFury

Public repository for Litefury & Nitefury
273 stars 72 forks source link

What should be the constraints on sys_clk_clk_p and _n #36

Closed mayureshw closed 1 year ago

mayureshw commented 1 year ago

I see IOSTANDARD property for sys_clk_clk_p and _n in normal.xdc

What are the PACKAGE_PIN and create_clock constraints needed on these ports?

The comment in the xdc suggests, MIG might be setting those. But I am not using MIG in my design.

###############################################################################
# DDR
###############################################################################
# Note: Most of the pins are set in the constraints file created by MIG
set_property IOSTANDARD LVDS_25 [get_ports sys_clk_clk_p]
set_property IOSTANDARD LVDS_25 [get_ports sys_clk_clk_n]
vogma commented 1 year ago

Hi @mayureshw,

correct, the PACKAGE_PIN and create_clock constraints are set by the MIG Constraint File. You can find this file in the Vivado GUI under Sources -> IP Sources Tab -> Synthesis -> Top_mig_7series_0_0 -> Top_mig_7series_0_0.xdc or in the project structure under project.gen/sources_1/bd/Top/ip/Top_mig_7series_0_0_1/Top_mig_7series_0_0/user_design/constraints

Hope this helps. Marco

mayureshw commented 1 year ago

Ok