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

boot loader creation problem

Altera_Forum
Honored Contributor II
‎05-12-2010 09:03 PM
985 Views

Hello NIOS users, 

I am trying to follow the AN458 instructions and to create new boot rom for the purpose of putting multiple SW images in EPCS (on IDE 8.1 and quartus 8.1) I have tried both example standard NIOS CPU build (cyclone II_2c35_standard) and my own cyclone III based NIOS platform. in both cases I added boot_rom, and built BSP after altering the predefined build-bsp script. when I created boot_rom.hex I got empty hex files (all zeros except first line). I guess this is not what I should have got.  

Important note shall be that since in the parameters of the default BSP creation there was reference to cycloneIII_2c35_standard i changed it, and another issue was that the bootcopier_bsp_settings_boot_onchip.tcl gave me error messages so I used the bsp-set-defaults.tcl instead.  

 

Can anyone please give good advice how to advance forward?  

 

Thanks, 

A.G.
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.