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

FileI/O in NIOSII IDE

Altera_Forum
Honored Contributor II
‎03-05-2007 05:28 AM
1,026 Views

I've got a question about FileI/O in NIOSII IDE. 

I'm working on open source JPEG running on NiosII processor. 

 

Mostly, I'm working on NiosII IDE. I'm using Advanced project in NiosII IDE which I required to create/ manage 'makefile' to compile the project. 

 

After successful compilation, NiosII IDE generated excuteable. 

And I need to run it with parameters. For example, 

'jpeg' is the excutable name. And it requires two parameters. 

 

=> jpeg [input file] [output file] 

jpeg testorig.jpg myoutput.jpg 

 

But when I clicked "run", it run "jpeg" only. How can I do this task? 

input file is existing file and output file is non existing file/expected to be generated when it run successfully. 

 

Could you give me guidance how to deal with this task, please? 

Or is there any document/tutorial which related to file I/O in NiosII IDE? 

 

 

Thanks in advance, 

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