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

EPCS with 2 FPGA + NIOS Code

Altera_Forum
Honored Contributor II
‎09-19-2006 04:32 AM
1,074 Views

Hi folk! 

 

I see some usefull information in Topic Coverting/Combining SOF and ELF for EPCS. 

But I want to do something more complex/undocumented. 

I want two configure 2 Cyclones, one with a basic CPU (NIOS II). 

I generated a fpga.pof file with both FPGA configuration (build from fpga1.sof and fpga2.sof) than I programed the flash (EPCS16) with it. After that I read back the flash to find the end of the data. I look the code components/altera_nios2/sdk/src/boot_loader_sources/boot_loader_epcs_bits.S. 

than I found the offset where to put the .elf code ( I used elftoflash to convert it). 

But that didn't work ?  

 

I think I know why. I noticed that the offset produce by sof2flash is different from the one produce by the .pof generator. 

 

If someone has already did that or can help me to figure out what I have to do, I will be very happy. 

 

If I change the code (boot_loader_epcs_bits.S) to retrieve the software elsewhere but at a fix address do you thing that will be feasible ?
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.