Typical design flow, Software requirements, Typical design flow –2 – Altera Nios II C2H Compiler User Manual

Page 24

Advertising
background image

2–2

9.1

Altera Corporation

Nios II C2H Compiler User Guide

November 2009

Typical Design Flow

Typical Design
Flow

A typical design flow using the C2H Compiler to accelerate a function
involves the following steps:

1.

Develop and debug your application or algorithm in C targeting a
Nios II processor system.

2.

Profile the code to identify the areas that would benefit from
hardware acceleration.

3.

Isolate the code you want to accelerate into an individual C
function.

4.

Specify the function you want to accelerate in the Nios II IDE.

5.

Rebuild the project in the Nios II IDE.

6.

Profile the results in hardware, or observe estimates from the C2H
report in the Nios II IDE.

7.

If the results do not meet the design requirements, modify the C
source code and system architecture (for example, the memory
topology).

8.

Return to Step 5, and iterate.

The typical C2H Compiler design flow is an iterative process of
accelerating a function, comparing the performance to design
requirements, and modifying C code to improve results. If you start with
C code that is not optimized for the C2H Compiler, the first iteration of
acceleration might not dramatically improve performance. Further
iterations, modifying the C code for optimal hardware structure, often
improve the final results significantly over the first pass results.

f

This tutorial does not describe techniques for optimizing hardware
accelerator performance. For further information on optimizing
C2H Compiler results, refer to the

Accelerating Nios II Systems with the

C2H Compiler Tutorial

.

Software Requirements

The C2H Compiler in evaluation mode is installed as part of the Altera

®

Quartus

®

II Complete Design Suite. You can download the Quartus II

Complete Design Suite free from the Altera website. Visit

www.altera.com

and click Download.

Advertising