Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
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.
12748 Discussions

beginnign trouble

Altera_Forum
Honored Contributor II
‎03-21-2007 02:08 PM
1,052 Views

Hello, sorry but my english is not so good. 

I am developding a project, it is: 

Using a program, for example an ordinance algorithm, on the NIOS memory. 

Build the project.  

After configure the cache. 

Run NIOSII simulation. 

Export to QuartusII in order to do the power estimation of the project.  

I obtained build and run the project, but I didn't know how to configure the cache, on the NIOSII IDE, following the support structions I have to open the QuartusII, build a system in the SOPC builder, then open the NIOSII IDE and build the project. I would like to configure the cache on the NIOSII IDE, using the *.ptf given as example and not having to construct an other system. 

Another thing, after run the project, what could I do, to do the power estimation of the system. Please, be detailed, I have some experience on QuartusII, but I am beginning on NIOSII IDE.
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.