10-23-2014 10:13 AM
I have configured an FFT core using Throttle Scheme: Real Time . After simulating the design, I realized that I needed to implement Throttle Scheme: Non Real Time. After changing to Non Real Time, my design simulation suddenly terminates after only 3 clock cycles. This was not the case with Real Time, where it executed for over 1000 clock cycles.
The only difference between the two FFT implementations from an instantiation/simulation point is the addition of the I/O signals: m_axis_status_tready, event_data_out_channel_halt and event_status_channel_halt in Non Real Time mode. I do not understand why changing throttle modes would casue the simulation to halt prematurely. Has anyone experienced this behavior before?
10-24-2014 02:22 PM