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

jtag-uart and software protocol

Altera_Forum
Honored Contributor II
‎11-16-2006 05:21 PM
1,163 Views

Hello all, 

 

For my project I need to use an uart with the software and hardware flow control. 

I see in nios2configtools that this configuration generates a conflict with Jtag uart “  

Jtag uart requires ! CYGOPT_IO_SERIAL_FLOW_CONTROL_SOFTWARE 

 

I don’t understand why there is a global restriction in ecos as in the driver structure there is a possibility to disable the xonxoff protocole for each uart. 

 

Did somebody get this problem before and how did you solve it ? 

 

Here below the way I used to jump over the restriction.  

In ecosconfigtool when I get Jtag uart requires ! CYGOPT_IO_SERIAL_FLOW_CONTROL_SOFTWARE 

I unselect the proposed solution and save anyway. 

 

Then I compiled the ecos library 

I got the error "The JTAG UART PC Software does not support Software flow control" from the altera_avalon_jtag_uart.c file. I removed the checking lines in this file.  

 

Then the Build and Compilation with application are fine. 

 

Are there any interdict to do this ? 

Thanks for advice.
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.