Closed enjoy-digital closed 8 years ago
What's the current status on that?
There are two things:
We could do 2) without 1) but we still have to fix 1) since I'm not sure timings constraints are correcly applied when building with Vivado (the Vivado log should show it when applying the XDC constraints, is there a log somewhere?)
Could this be the reason for the Ethernet bugs we are seeing with some switches?
Not sure but possible:
WARNING: [Vivado 12-507] No nets matched 'eth_clocks_rx'. [/var/lib/buildbot/slaves/debian-stretch-amd64-2/miniconda/conda-bld/work/misoc_nist_clock_kc705/gateware/top.xdc:1027] CRITICAL WARNING: [Vivado 12-4739] create_clock:No valid object(s) found for '-objects [get_nets eth_clocks_rx]'. [/var/lib/buildbot/slaves/debian-stretch-amd64-2/miniconda/conda-bld/work/misoc_nist_clock_kc705/gateware/top.xdc:1027]
Done.
To be done when we'll figure out a reliable way to apply constraint on signals with Vivado ("dont_touch" signal attribute?)