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

bin2flash, offset is larger than flash memory span

Altera_Forum
Honored Contributor II
‎03-22-2010 06:16 AM
1,106 Views

Hi, 

I'm using the flash programmer to download a binary raw image file to the epcs4 flash. 

 

When I set the offset as 2048(which is the total page number of epcs4, 512K/256) or a larger value, a error reported: 

"offset is larger than flash memory span". 

 

And when I change the offset to 2047, no error was reported. So, the offset seems to use the pages other than bytes as its unit.  

 

However, by analyzing the obtained s-record file, it uses bytes as unit indeed. 

 

now, my question is: 

How can I save my binary file to an address higher than 2048 in epcs4 with flash programmer? 

 

To supplement, my quartus and nios ide version is 9.1 sp1. 

 

regards!
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎04-27-2010 10:30 AM
385 Views

Hi, have you resolved your question? I have the same problem, unable to program a binary file at offsets larger than 2047. 

One thing I know, is that 2048 is address span of the epcs_controller module, 

and the programmer takes it as flash memory span. 

 

When I was using version 8.0, there were no such problems. I am considering to return to 8.0.
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.