Ah,
I would guess what happens is that you have delay stages being implemented
in bram where the stage delay is fewer clock cycles than the bram latency,
causing an initialization implosion. I suspect if you changed the "minimum
delay implemented in bram" (or whatever it's called) parameter to be
Hi Michael,
If the initialisation script fails half way through drawing then often
you'll be left with a bunch of blocks half connected, so I think that's
(probably) a symptom rather than a cause of the issue. Are you using the
latest casper-astro branch? Do you remember what FFT parameters you
Hi all,
I had an odd problem while messing about with the FFT block today - on setting
a new combination of parameters and attempting a new compile, an error came up
which I've never seen before. Something along the lines of an initialisation
error in the FFT. On inspection, the component
Hi Jack,
After cycling through the settings I think I’ve isolated the issue. I was a bit
quick to declare a solution….i was able to repeat the problem. The problem
occurs when the BRAM latency is set to >10. I appreciate this may seem
excessive in any case however as you know I’m messing with
Hi Casper,
While we're talking weird FFT problems...
I have experienced an interesting problem with the FFT libraries when
compiling for ROACH2, that I'm hoping someone might be able to explain.
I have tried multiple versions of the libraries, and various branches
(latest CASPER, SKA-SA, SMA),
5 matches
Mail list logo