Embedded Computing Design - OpenSystems Media
Embedded Computing Design - OpenSystems Media
Embedded Computing Design - OpenSystems Media
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
arithmetic, implementing algorithms in<br />
FPGAs or ASICs gives the designer the<br />
ability to independently control the number<br />
of bits used to represent each number<br />
in the algorithm. Using too may bits can<br />
be costly – a 40% increase in the number<br />
of bits in a multiplier can double its area<br />
in silicon – but using too few can lead to<br />
overflows or instabilities. When choosing<br />
tools for implementing DSP algorithms<br />
in silicon, designers should evaluate tools<br />
that help automate this floating-point to<br />
fixed-point conversion process.<br />
6<br />
Rule #6<br />
Keep your options open<br />
with vendor-independent,<br />
technology-independent flow.<br />
As designers, we are all increasingly<br />
under pressure to cut costs, which often<br />
leads to having to select the supplier who<br />
can provide the lowest price, the best<br />
availability, etc. The tools available in the<br />
market fall into two categories.<br />
Vendor-supplied tools are available from<br />
companies offering FPGA devices for<br />
DSP and provide integrated environments<br />
spanning graphical design entry, IP<br />
block libraries, and RTL simulation and<br />
synthesis tools. But, these tools offer<br />
libraries of DSP functions that can only<br />
target a single vendor’s devices. To convert<br />
a design from one vendor’s tools to another<br />
is at best a time-consuming and errorprone<br />
process, leaving the designer at the<br />
mercy of the vendor in terms of the cost<br />
and availability.<br />
Vendor-independent tools provide a more<br />
flexible alternative. Once the design is<br />
captured, it can easily be retargeted from<br />
one device family to another from the<br />
same vendor, and can even be retargeted to<br />
an entirely different family of FPGAs. Yet<br />
another advantage of vendor-independent<br />
flows involves the need to retarget the same<br />
design to different silicon technologies.<br />
Companies find that they can meet their<br />
need for first silicon using FPGAs, and<br />
then incorporate structured ASICs or<br />
ASICs as they become available from<br />
product lines. While vendor-supplied tools<br />
provide IP that is only available for FPGA<br />
devices, vendor-independent tools allow<br />
designers to retarget the designs without<br />
changing the golden design source.<br />
7<br />
Rule #7<br />
Given the time, you can<br />
always make a design better<br />
– use design exploration.<br />
Almost invariably, getting the functionality<br />
of the design correct is just the beginning<br />
– then begins the pursuit of improving<br />
performance to make specs and trying<br />
to shrink to a smaller device or go to a<br />
slower speed grade to cut costs. Hardware<br />
engineers have an arsenal of tools and<br />
tricks at their disposal, but working at<br />
gate-level – even at RTL level – has its<br />
limits. Inserting intermediate registers<br />
can be difficult. Optimizing quantization<br />
throughout a design is particularly tedious<br />
and error-prone when changing at the RTL<br />
level. And, if the algorithm developer<br />
comes up with a brilliant new idea two<br />
weeks into the hardware design, chances<br />
are that the project manager will decide to<br />
stick with the old design rather than risk<br />
the entire project schedule.<br />
“To convert a design from<br />
one vendor’s tools to<br />
another is at best a<br />
time-consuming and<br />
error-prone process...”<br />
The greatest benefits can be realized<br />
by keeping the original floating-point<br />
MATLAB source file as the golden source<br />
for all design and using algorithmic<br />
synthesis tools that synthesize from<br />
MATLAB to RTL. Using architectural<br />
synthesis tools such as AccelChip DSP<br />
Synthesis, the algorithm designer can<br />
make changes to the design well into<br />
the flow, resynthesize to RTL, and work<br />
with the hardware designer to determine<br />
whether the design performance and<br />
device utilization has improved. Possible<br />
trade-offs given different levels of abstraction<br />
are shown in Figure 3.<br />
Figure 3<br />
Wrapping up<br />
Implementing DSP algorithms in silicon<br />
used to be a task reserved for only the<br />
most highly skilled and best equipped<br />
design teams. The demand for a more<br />
efficient path from algorithm to an ASIC<br />
or FPGA has given rise to a new breed of<br />
EDA companies, such as AccelChip, that<br />
bridge the gap between DSP algorithm<br />
development and silicon. Architectural<br />
synthesis tools such as this accelerate<br />
design and implementation by automatically<br />
synthesizing algorithms written<br />
in floating-point MATLAB model to<br />
synthesizable VHDL or Verilog models<br />
suitable for standard ASIC and FPGA<br />
design flows. AccelChip’s toolset also<br />
enables rapid design exploration targeting<br />
fidelity, performance, area, and cost<br />
tradeoffs for optimal results while using<br />
MATLAB as a golden source.<br />
Eric Cigan is the Product Marketing<br />
Manager for AccelChip Inc., and is<br />
responsible for product planning and<br />
promotion for the AccelChip product<br />
family. He has more than fourteen years’<br />
experience in the EDA industry.<br />
Reference:<br />
1. Xilinx, June 2003.<br />
2. Xilinx website.<br />
For further information, contact Eric at:<br />
AccelChip Inc.<br />
1900 McCarthy Blvd., Suite 204<br />
Milpitas, CA 95035<br />
Tel: 408-943-0700 • Fax: 408-943-0661<br />
E-mail: eric.cigan@accelchip.com<br />
Website: www.accelchip.com<br />
<strong>Embedded</strong> <strong>Computing</strong> <strong>Design</strong> Summer 2004 / 33