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

Two cpu's with one JTAG UART

Altera_Forum
Honored Contributor II
‎05-11-2005 06:11 AM
1,107 Views

Hi All 

 

I've just upgraded from Quartus 4.2 and Nios 1.1 to Quartus 5.0 and NiosII v5.0. 

One of the first projects I've tried to convert has two processors in it using the same Jtag Uart (so that I can debug either one of them through the IDE). This was perfectly ok in SOPC builder 4.2 but the new SOPC Builder complains that I can't have two masters on the same JTAG Uart. 

 

Is this a bug or is there a way around this problem ?  

 

Regards 

Nir
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎05-11-2005 03:40 PM
376 Views

You can have multiple JTAG Uarts in a system and the IDE will support it if you create seperate hardware configurations then run in multiprocessor mode. This document shows a different way to go about this where multiple masters communicate to a single master that talks to the JTAG Uart 

 

http://www.altera.com/literature/tt/tt_nio...or_tutorial.pdf (http://www.altera.com/literature/tt/tt_nios2_multiprocessor_tutorial.pdf) 

 

Hope that helps.
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.