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

Altera RO zip file system problem with latest IDE

Altera_Forum
Honored Contributor II
‎02-23-2011 09:57 AM
1,038 Views

Hi 

 

I have used this component for years now. Lately I finally upgraded my old NIOSII IDE 7.2 environement to flashy new 10.1 and several problems occured: 

 

Back in 7.2 the output was a file called filesys.flash. I am no longer able to create filesys.flash when using 10.1, even when using the web server app example. 

 

In fact, I can't even find where to put the name of the zip file archive?  

 

The BSP editor asks for 3 parameters only: Mount point, Base address and Offset. Thats ok, but BSP editor does not ask for the name of the zip file? 

 

In the web server app example, the zip file is named r0_zipfs.zip and is put in subdir .\system. For me its like its never included into the make, because nothing happens if I remove or rename the file ? 

 

Read the UM but didn't help much. 

 

Anyone having a clue? 

 

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