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

multiple NIOS instanses on a single FPGA

Altera_Forum
Honored Contributor II
‎05-13-2010 07:37 AM
1,477 Views

Hi 

 

does anyone has experience with 2 (different) NIOS processors on the same FPGA? how for example the JTAG connects to the processors? 

any other problems? (assuming 2 RAMs as well)? 

 

thanks in advance
0 Kudos

Link Copied

3 Replies
Altera_Forum
Honored Contributor II
‎05-13-2010 08:12 AM
543 Views

just to make my question a little more complicated, I mean 2 SOPC systems which at least one of them will be located in a QXP imported partition.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎05-13-2010 10:26 AM
543 Views

There's no basic restriction of the Quartus software, that wouldn't allow it. The JTAG communication is e.g. using Alteras virtual JTAG protocol, that allows for multiple instances of each type. But you should check, if the respective tools are supporting selection of multiple instances.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎05-14-2010 03:53 AM
543 Views

Yes. You can instantiate and debug multiple NIOS processors within a single FPGA. I have done projects with as many as 5 NIOS processors within one FPGA. 

 

Jake
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.