User Auto-Refresh Conduit with hard memory Controller. Strange request behaviour?

Thanks four your reply.

Currently I am using a Cyclone V device. You need to keep in mind that this happens in simulation with ModelSim.

When my custom logic tells me that every request is passed to the controller, I assert the request. Kept watching for an acknowledgment for about 5000 clock cycles and still no acknowledgment.

If I use the oscillation on the request signal, which basically looks then like a half rate clock in the waveforms, I get the acknowledgment after 10 or 12 clock cycles.

To me it looks like the controller is ignoring the first refresh requests because it needs to deal with the read and write requests. And it looks like the controller only checks for rising edges on the local_refresh_req signal, otherwise there would be no different behaviour between a constant high signal, which never leads to an acknowledgment, and a oscillating singal, which leads to many rising and falling edges on the req signal until the acknowledgment is received.