For the benefit of the casper list
From: Andrew Vdb [mailto:avd...@gmail.com]
Sent: 19 September 2016 14:19
To: Michael D'Cruze
Subject: Re: [casper] Spectrum woes
Hi Michael,
Sure - it's the FFT BRAM optimization. The coefficient bug was that we were
incorrectly applying the coefficients
from ‘Area’ to ‘Speed’. No other changes were made,
>> so, I think this is the former case?
>>
>> BW
>> Michael
>>
>>
>>
>> *From:* Jack Hickish [mailto:jackhick...@gmail.com]
>> *Sent:* 18 September 2016 22:27
>> *To:* Michael D'Cru
Sent:* 18 September 2016 22:27
> *To:* Michael D'Cruze; casper@lists.berkeley.edu
> *Subject:* Re: [casper] Spectrum woes
>
>
>
> Hi Michael,
>
>
>
> Is this actually the optimisation parameter of the xilinx bram block, or
> an optimisation of a casper block wh
Hi Michael,
Is this actually the optimisation parameter of the xilinx bram block, or an
optimisation of a casper block which completely changes some underlying
circuit (eg by doing a bunch of fanout control and instantiating multiple
small brams instead of one big one)?
If the latter, are you
Dear all,
I've been chasing the cause of some nasty artefacts in my spectra recently. The
first turned out to be a known bug in the Xilinx compiler, activated when the
BRAM_sharing optimisation in the FFT is checked, however the artefacts I'm
seeing since seem to be activated by the RAM blocks
5 matches
Mail list logo