Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
21615 Discussions

SOPC not updated with Accelerated function

Altera_Forum
Honored Contributor II
‎12-01-2009 02:17 PM
1,096 Views

Hi , 

 

It is expected that NIOS needs to updates the mapping in the SOPC once we compile the Source in NIOS , but this doesnt happen it just updates the component list and doesnt update the pin mappings with the memory . 

 

*** This is expected *** But doesnt happen**** 

" 

Build the application project again. As part of the build process, the Nios II IDE performs the following 

steps: 

● Analyzes the function to be accelerated, determining the mapping from C constructs to hardware, and 

computing performance metrics 

Optimizing the FFT 

Altera Corporation 11 

August 2008 Accelerating Nios II Systems with the C2H Compiler Tutorial 

● Integrates the accelerator into the SOPC Builder system 

● Generates the HDL 

● Compiles the system in Quartus II 

● Creates a wrapper function to invoke the accelerator 

● Compiles the software executable 

 

 

 

Does anyone had such an experience ? so what was the solution adopted ?? 

Regards, 

Rav's
0 Kudos

Link Copied

0 Replies
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.