RZhen11
Occasional Contributor
2 years agoHow to constrain the transceiver Rx data path?
Dear support,
I used to only constrain XCVR with the reference clock and expect the Quartus tool to derive all the generated constraints.
Recently I found adding logics to the Rx data path is causing timing failure, and the path is not constrained.
Leaving this path unconstrained, please let me know if this is intentional or I am missing something from my project.
report_timing -from [get_keepers {my_mdl:\My_Rx:0:My_Rx_Serdes|My_Rx_Serdes_altera_xcvr_native_a10_221_2q4miaq:xcvr_native_a10_0|twentynm_xcvr_native:g_xcvr_native_insts[0].twentynm_xcvr_native_inst|twentynm_xcvr_native_rev_20nm3:twentynm_xcvr_native_inst|twentynm_pcs_rev_20nm3:inst_twentynm_pcs|gen_twentynm_hssi_rx_pld_pcs_interface.inst_twentynm_hssi_rx_pld_pcs_interface~pld_rx_data_fifo.reg}] -setup -npaths 10 -detail full_path -panel_name {Report Timing} -multi_corner Report Timing: No setup paths were found
Hello,
How about sharing through email?
I'm dropping you an email, you may send your design through there.
The reason I am requesting your design is to check if the connection/usage of the IP is correct. From there, we can tell if it is a usage problem or timing constraint problem.
Regards,
Nurina