Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
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.
17267 Discussions

Loading Flash with .pof & application cdoe/data on cyclone III board.

Altera_Forum
Honored Contributor II
‎12-29-2011 08:26 AM
1,215 Views

Hi friends, 

 

I am fresher & new to the FPGA platform. 

 

I have few doubts. 

 

In SOPC builder,I've given flash start address is :0x00000000 end address:0x00ffffff 

memory locations used for .pof file is: from 0x00020000 to 0x000CF6E9 (i got this from .map file) 

 

I have given reset vector as flash for cpu in sopc. 

So,my doubt is like excluding the memory locations used for  

(1)reset vector & 

(2).pof file 

other locations can be used for storing application code/data from NIOS II right? 

 

But,in NIOS II IDE ,I didn't observe any control to specify the address in Flash programmer. 

& also,they've given option to load fpga .sof file into the flash.this is for what?anyhow our fpga get configured by .pof from 0x20000. 

 

one more thing is about,remote update controller.I know the purpose of it.now,for this default configuration upon power power up,there is no need 

of including remote update controller in SOPC right? 

 

For loading .pof file to the flash,we get .map file,so that we can see where the .pof is going to sit.Similarly how to see,after programming software through "flash programmer" into flash. My concern is not to overwite the .pof file which is already written from 0x020000 to 0x000CF6E9. 

 

 

It's my pleasure if u help me resolving the above doubts. 

Thanks in advance. 

 

Regards, 

Raghavendra.S
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.