Timing violation when enable 'Extra Timing Report Clock' in DDR3 UniPHY based controller

You may see timing violation when you disable DQS tracking in DDR3 controller following the steps in this KDB solution:
http://www.altera.com/support/kdb/solutions/rd01062012_793.html

The timing violation happens when the controller is named with the string “controller“.   

The workaround for this issue is by changing the “controller” to “alt*controller” in <instance>_p0_report_timing_core.tcl

Change:

To:

if { ! } {
        set controller_regs [get_registers | *alt*controller_*inst|*]
        set inst_other_if
    } else {
        set controller_regs [get_registers |*:* alt*controller _*inst|*]
        set inst_other_if
    }

This issue will be fixed in a future release of Quartus® II software.