Honored Contributor
Honored Contributorthepancake
I think I figured out how to stall the streaming core. I count lines and pixels going in so I know when all my data has been used. I am also counting lines and fft data out so I know when I have gotten all the required data. I push 3 extra lines in making sure I end the last extra line with the eop and immediately drop the sink_valid. The core flushes out the last 2+ lines of data and then keeps going for another 2+ lines before dropping source_valid. Since I count the output data, I only capture valid info. It looks like the core might flush itself if I am careful about ending input with an eop and not generating an extra sop. This is what the verilog testbench produced by the core generator shows. I'll try pulling it in later today to see what happens. I have an awful lot of processing to do in the freq. domain after the 2D fft and this is an imaging system so frame rate is key here. Shaving off unnecessary clock cycles is always a good thing. Since I can stream lines of video in from memory, seems like the streaming versions of the core gets me the fastest processing. If you think burst might be better, I'm all ears. I'm new to this core. Most of what I've done is spatial processing.
