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

re-generate sopc system

Altera_Forum
Honored Contributor II
‎09-22-2011 10:44 AM
1,172 Views

Hi mates! 

 

I have a question about when it is necesary to re-generate my niosII system. 

 

I am writting my own component to connect it through Avalon to the uP NiosII. Every time I change the verilog/vhdl code is it necesary to re-generate the sopc-system? 

 

It is supposed that the changes in the code don't affect to the component interfaces. 

 

Many thanks.
0 Kudos

Link Copied

4 Replies
Altera_Forum
Honored Contributor II
‎09-22-2011 11:07 AM
491 Views

If there is no change to the interfaces then it should not be necessary to regenerate the SOPC system.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎09-22-2011 11:57 AM
491 Views

If there are no changes in top signals (e.g. new signals, signal removal, width change, etc), then the SOPC system can be left as it is, but You have to resynthesize the code.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎09-22-2011 12:04 PM
491 Views

re-synthesize means re-compile? 

 

Thank you
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎09-22-2011 12:12 PM
491 Views

basically - yes.

0 Kudos
Copy link
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.