Critical Issue
The Efficiency Monitor and Protocol Checker counts read latencies incorrectly for Avalon burst counts equal to 1; this causes the EMIF Toolkit to report incorrect values for minimum and maximum read latencies.This issue occurs if you measure efficiency with the example design driver; however, if you use your own custom driver that does not issue an Avalon burst count size equal to 1, the error will not occur.
The workaround for this issue is to use a custom driver that does not issue an Avalon burst count equal to 1.