Specifications

1. Right-click the application project.
2. Point to Make targets and click Build to open the Make Targets dialog box.
3. Select mem_init_install.
4. Click Build. The makefile generates a separate file (or files) for each memory device. The makefile
inserts the memory initialization files directly in the Quartus II project directory for you.
5. Recompile your Quartus II project.
Related Information
Hardware Reference
For information about working in the stand-alone flow.
Memory Initialization Files for User-Defined Memories
Generating memory initialization files requires detailed information about the physical memory devices,
such as device names and data widths. Normally, the Nios II SBT extracts this information from
the .sopcinfo file. However, in the case of a user-defined memory, the .sopcinfo file does not contain
information about the data memory, which is outside the system. Therefore, you must provide this
information manually.
You specify memory device information when you add the user-defined memory device to your BSP. The
device information persists in the BSP settings file, allowing you to regenerate memory initialization files
at any time, exactly as if the memory device were part of the hardware system.
Specify the memory device information in the Advanced tab of the Add Memory Device dialog box.
Settings in this tab control makefile variables in mem_init.mk. On the Advanced tab, you can control the
following memory characteristics:
• The physical memory width. The device’s name in the hardware system.
• The memory initialization file parameter name. Every memory device can have an HDL parameter
specifying the name of the initialization file. The Nios II ModelSim launch configuration overrides the
HDL parameter to specify the memory initialization filename. When available, this method is
preferred for setting the memory initialization filename.
• The Mem init filename parameter can be used in Nios II systems as an alternative method of specifying
the memory initialization filename. The Mem init filename parameter directly overrides any filename
specified in the HDL.
• Connectivity to processor master ports. These parameters are used when creating the linker script.
• The memory type: volatile, CFI flash or EPCS flash.
• Byte lanes.
• You can also enable and disable generation of the following memory initialization file types:
• .hex file
• .dat and .sym files
• .flash file
Related Information
Publishing Component Information to Embedded Software on page 13-1
For more information about this parameter, refer to "Embedded Software Assignments".
Specifying the Memory Device Information in the Advanced Tab
Specify the memory device information in the Advanced tab of the Add Memory Device dialog box.
Settings in this tab control makefile variables in mem_init.mk.
2-32
Memory Initialization Files for User-Defined Memories
NII5V2
2015.05.14
Altera Corporation
Getting Started with the Graphical User Interface
Send Feedback