



Using 16K RAMB of Spartan-III?
by Unknown on Sep 17, 2004 |
Not available! | ||
Hi
Have anyone modified the PCI files to include the Spartan-III 16Kb RAMB?
Is it simply a mather of adding the definitions in the fifo RAM definitions
files, plus maybe changing some validations to include RAMB16.
Using 16K could lower the RAM block count from 3 to 2 per sides/interfaces
(by making 32 or 36-bit wide RAM). And at the same time, used shared RAM
while having even more depth than the 4Kb RAM (ex: shared memory having 256
bytes per directions, for a total on only four RAMB used, instead of 128
bytes per directions with 6 RAMB of 4Kb).
Spartan-III and Virtex-II are becoming popular, and would be nice to add
their native RAMB to the CVS.
Regards
Eric
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
|



