Greeting all,
I implemented my design in VHDL but i thought i would switch to impulse c if the answers to my question are positive, please any help in getting an answer would be appreciated.
1.
Is it possible to ensure that impulse c will use some of the space saving features. such as implementing a FIFO of arbitrary length in the smart ram (which has pre-built FIFO managers) instead of general ram or logic blocks?
2.
Also does it take advantage of the fact each CLB in the virtex 4 can be a 16 bit shift register and cascaded?
Thank you in advance
Rizgar Mella
Efficiency on the virtex 4
Started by rizgarmella, Sep 12 2008 11:26 AM
2 replies to this topic
#1
Posted 12 September 2008 - 11:26 AM
#2
Posted 15 September 2008 - 09:36 AM
QUOTE (rizgarmella @ Sep 12 2008, 01:26 PM) <{POST_SNAPBACK}>
Greeting all,
I implemented my design in VHDL but i thought i would switch to impulse c if the answers to my question are positive, please any help in getting an answer would be appreciated.
1.
Is it possible to ensure that impulse c will use some of the space saving features. such as implementing a FIFO of arbitrary length in the smart ram (which has pre-built FIFO managers) instead of general ram or logic blocks?
2.
Also does it take advantage of the fact each CLB in the virtex 4 can be a 16 bit shift register and cascaded?
Thank you in advance
Rizgar Mella
I implemented my design in VHDL but i thought i would switch to impulse c if the answers to my question are positive, please any help in getting an answer would be appreciated.
1.
Is it possible to ensure that impulse c will use some of the space saving features. such as implementing a FIFO of arbitrary length in the smart ram (which has pre-built FIFO managers) instead of general ram or logic blocks?
2.
Also does it take advantage of the fact each CLB in the virtex 4 can be a 16 bit shift register and cascaded?
Thank you in advance
Rizgar Mella
Hi,
Impulse C may influence synthesis only through the HDL it generates along with referenced HDL libraries, ultimately it is up to synthesis for implementation details some of which may be controlled via its settings. Impulse C generated HDL is mostly generic except for RAM generation which may be vendor specific (e.g. dual-port RAMs, block vs. distributed RAM, etc.) and the HDL libraries (co_* objects, etc.) also generally do not instantiate low-level primitives. If the user needs to excert finer control over implementation they may do so through the settings of the implementation tool, through the use of #pragma CO IMPLEMENTATION for external user provided primitive functions, and through the HDL libraries used.
Ed
Ed Trexel
Impulse Accelerated Technologies, Inc.
Impulse Accelerated Technologies, Inc.
#3
Posted 16 September 2008 - 03:49 PM
Thank You i will look into that
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












