Why does the Avalon interface of my DDR3 UniPHY-based memory controller use Avalon-MM signals instead of Avalon-ST signals?

Description

Due to a problem in the Quartus® II software version 11.1 and later, the DDR3 UniPHY-based memory controllers with the efficiency monitor enabled incorrectly use the Avalon®-MM signal names (e.g. avl_waitrequest) instead of Avalon-ST signal names (e.g. avl_ready). There is a problem during the generate stage of the controller where the Avalon-MM interface of the efficiency monitor is exported instead of the Avalon-ST interface of the controller.

Resolution

This issue is fixed in the Quartus II software version 12.1 and later.