Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
As described in AN 351: Simulating Nios II Embedded Processor Designs, Qsys and Nios II Software Build Tools (SBT) for Eclipse can automatically generate an RTL simulation environment for Nios II designs. This guide shows how to handle issues specific to designs in which program memory is stored on external flash memory and runs from external SSRAM memory. This guide is presented using Verilog, but the process is similar for designs using VHDL.
This guide assumes that you have prior experience using Qsys as well as a familiarity with Nios II SBT and the ModelSim simulator. In order to simulate the Nios II design using the instructions in this guide, you must have the following software installed:
The design used for this guide is a complete Qsys system that includes a Nios II processor, connections to external flash and SSRAM memory, and PIOs for buttons and LEDs. The example software running on the NIOS II system tests a range of addresses in SSRAM and signals possible write/read failures by turning on the LEDs. Additionally, messages are sent to the console via the JTAG UART to confirm success or failure of each address.
This section summarizes the process of generating the simulation files. A more detailed explanation can be found in AN 351: Simulating Nios II Embedded Processor Designs .
The software used for this guide will test a range of address in SSRAM and signal success and failure with the LEDs and the JTAG UART. If a read/write failure occurs, the LEDs with turn on. Otherwise, the LEDs will remain off. With each test, messages are sent to the console via JTAG UART to confirm success or failure. To create and build the software project, perform the following steps:
When simulating Nios II systems that use external memory, it is often desirable to skip the simulation of the transfer of program code from non-volatile storage to RAM. Nios II SBT provides a simulation optimization option that skips this step and preloads the RAM with program code. To enable this optimization:
1. Right-click on niosii_with_external_memory_bsp in the Project Explorer and select Nios II > BSP Editor…. As shown in Figure 1, the BSP Editor will open with the Main tab selected and Settings > Common selected from the hierarchy on the left side of the window.
Figure 1 – Selecting "enable_sim_optimize" to optimize the simulation for external memory. 4/4d/Ext_mem_bsp_editor.png
2. As shown in Figure 1, check the box next to the enable_sim_optimize option.
3. Click Generate.
4. When the BSP generation has completed, click Exit to return to the main Nios II SBT window.
Important note: when the enable_sim_optimize option is turned on, the BSP cannot run on hardware. To run your project on hardware, disable the enable_sim_optimize option by unchecking the box in the BSP Editor.
Due to a known issue with the SSRAM and flash memory bus functional models (BFMs), a slight change must be made to the automatically generated testbench file before you run your simulation. For this guide, the testbench file, niosii_system_tb.v, is located in:
<project directory>/niosii_system/testbench/niosii_system_tb/simulation
In general, this file will be located in:
<project directory>/<Qsys system name>/testbench/<Qsys system name>_tb/simulation
For this example design, you can either make the modifications to the test bench file yourself, or you may copy the completed code into the testbench file from the niosii_system_tb.v file, which is located in <project directory>/modified_files directory.
To make the modifications, open the automatically generated testbench file in an editor of your choice and complete the following steps:
1. As shown below, add a new wire called system_clk and connect it to the system_clk port of the Nios II system:
// CHANGE: add system_clk wire and connect to system_clk port of Nios II system
wire system_clk;
niosii_system_tb_niosii_system_inst niosii_system_inst (
.osc_clk (niosii_system_inst_osc_clk_clk_in_bfm_clk_clk),
.system_clk (system_clk),
…
2. As shown below, connect the system_clk wire to the clk input of the SSRAM BFM (in place of the ext_ssram_external_mem_bfm_clk_bfm_clk_clk).
// CHANGE: connect the system_clk wire to the clk input of the SSRAM BFM (in place of ext_ssram_external_mem_bfm_clk_bfm_clk_clk(
…
) ext_ssram_external_mem_bfm (
.clk (system_clk),
…
3. Next, connect the system_clk wire to the clk input of the flash memory BFM (in place of the ext_flash_external_mem_bfm_clk_bfm_clk_clk).
// CHANGE: connect the system_clk wire to the clk input of the flash memory BFM (in place of ext_flash_external_mem_bfm_clk_bfm_clk_clk(
…
) ext_flash_external_mem_bfm (
.clk (system_clk),
…
4. Save the niosii_system_tb.v file.
Now that you have finished fixing the testbench file, go back the Nios II SBT and right-click again on “lower_level_qsys” in Project Explorer, and select Run As > Nios II ModelSim. This command will start the ModelSim software and create the remaining simulation files.
Once ModelSim has finished loading the simulation files, load signals into the waveform viewer by selecting File > Load… and browsing to the <project directory>/wave.do waveform script file. Begin the simulation by typing “run 2 ms”. As shown in Figure 2, the software tests several SSRAM address and displays success messages for each test. The active-low LEDs remain off (0x1111) for the duration of the test to indicate that all of the tests have been successful.
Figure 2 – Simulating the niosii_with_external_memory design. 8/8d/Ext_mem_modelsim.png
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.