How do I address hold time violations for paths where the destination register is implemented inside a dedicated DSP block in Arria® V devices? - How do I address hold time violations for paths where the destination register is implemented inside a dedicated DSP block in Arria® V devices? Description Due to a problem in the Quartus® II software version 13.1 and earlier, you may see hold violations in Arria® V designs for paths where the source register is implemented using a standard core register and the destination register is implemented as a dedicated DSP input register. Resolution To work around this problem, overconstrain the hold requirements during the fitting process by adding this constraint to your Synopsys Design Constraints (.sdc) file: if {($::quartus(nameofexecutable) == "quartus_map") || ($::quartus(nameofexecutable) == "quartus_fit")} { set_min_delay -from [get_keepers {<sourece register>}] -to [get_keepers {<destination register>}] 0.1 } If the violations you are seeing are greater than 100 ps, then the over-constraint value can be increased. This issue has been fixed starting Quartus® II software version 13.1.2 Related Articles How do I fix small hold time violations in Arria 10 designs? Custom Fields values: ['novalue'] Troubleshooting 2205808937 False ['DSP'] ['FPGA Dev Tools Quartus II Software'] 13.1.2 13.1 ['Arria® V GT FPGA', 'Arria® V GX FPGA', 'Arria® V ST FPGA', 'Arria® V SX FPGA'] ['novalue'] ['novalue'] ['novalue']