Forum Discussion

anhnidnahp's avatar
anhnidnahp
Icon for New Contributor rankNew Contributor
2 years ago

DDR3 SDRAM Controller with Uniphy intel FPGA IP 22.1 failed

Hi Intel team,

Please see below for the error message when i am generating the DDR3 IP.

Info: p0: "mem_if_ddr3_emif_0" instantiated altera_mem_if_ddr3_phy_core "p0"
Info: m0: "mem_if_ddr3_emif_0" instantiated altera_mem_if_ddr3_afi_mux "m0"
Error: s0: Error during execution of "{C:/intelfpga_lite/22.1std/quartus/../nios2eds/Nios II Command Shell.bat} make all 2>> stderr.txt": child process exited abnormally
Error: s0: Execution of command "{C:/intelfpga_lite/22.1std/quartus/../nios2eds/Nios II Command Shell.bat} make all 2>> stderr.txt" failed
Error: s0: /mnt/c/intelfpga_lite/22.1std/quartus/bin64/uniphy_mcc.exe -ac_code sequencer_mc/ac_rom.s -inst_code sequencer_mc/inst_rom.s -ac_rom ../soc_system_mem_if_ddr3_emif_0_s0_AC_ROM.hex -inst_rom ../soc_system_mem_if_ddr3_emif_0_s0_inst_ROM.hex -header sequencer/sequencer_auto.h -vheader ../sequencer_auto_h.sv -ac_rom_init sequencer/sequencer_auto_ac_init.c -inst_rom_init sequencer/sequencer_auto_inst_init.c -DAC_ROM_USER_ADD_0=0_0000_0000_0000 -DAC_ROM_USER_ADD_1=0_0000_0000_1000 -DAC_ROM_MR0=0010001110001 -DAC_ROM_MR0_CALIB= -DAC_ROM_MR0_DLL_RESET=0010101110000 -DAC_ROM_MR1=0000000000000 -DAC_ROM_MR1_OCD_ENABLE= -DAC_ROM_MR2=0000000010000 -DAC_ROM_MR3=0000000000000 -DAC_ROM_MR0_MIRR=0010001101001 -DAC_ROM_MR0_DLL_RESET_MIRR=0010011101000 -DAC_ROM_MR1_MIRR=0000000000000 -DAC_ROM_MR2_MIRR=0000000001000 -DAC_ROM_MR3_MIRR=0000000000000 -DQUARTER_RATE=0 -DHALF_RATE=1 -DFULL_RATE=0 -DNON_DES_CAL=0 -DAP_MODE=0 -DGUARANTEED_READ_BRINGUP_TEST=0 -DMEM_ADDR_WIDTH=13 -DHARD_PHY=0
Error: s0: UniPHY Sequencer Microcode Compiler
Error: s0: Copyright (C) 2023 Intel Corporation. All rights reserved.
Error: s0: Info: Reading sequencer_mc/ac_rom.s ...
Error: s0: Info: Reading sequencer_mc/inst_rom.s ...
Error: s0: Info: Writing ../soc_system_mem_if_ddr3_emif_0_s0_AC_ROM.hex ...
Error: s0: Info: Writing ../soc_system_mem_if_ddr3_emif_0_s0_inst_ROM.hex ...
Error: s0: Info: Writing sequencer/sequencer_auto_ac_init.c ...
Error: s0: Info: Writing sequencer/sequencer_auto_inst_init.c ...
Error: s0: Info: Writing sequencer/sequencer_auto.h ...
Error: s0: Info: Writing sequencer/sequencer_auto.h ...
Error: s0: Info: Writing ../sequencer_auto_h.sv ...
Error: s0: Info: Microcode compilation successful
Error: s0: /mnt/c/intelfpga_lite/22.1std/quartus/../nios2eds/sdk2/bin/nios2-bsp hal sequencer_bsp .. --default_sections_mapping sequencer_mem --use_bootloader DONT_CHANGE
Error: s0: nios2-bsp: Using /mnt/c/intelfpga_lite/22.1std/nios2eds/sdk2/bin/bsp-set-defaults.tcl to set system-dependent settings.
Error: s0: nios2-bsp: Updating existing BSP because sequencer_bsp/settings.bsp exists.
Error: s0: Makefile:18: recipe for target 'setup' failed
Error: s0: child process exited abnormally
Error: s0: Cannot find sequencer/sequencer.elf
Error: s0: An error occurred while executing

Can you help to advise how to solve this issue?

I installed Windows Subsystem for Linux (WSL) and distro packages for NIOS.

Platform

7 Replies

  • AdzimZM_Altera's avatar
    AdzimZM_Altera
    Icon for Regular Contributor rankRegular Contributor
    2 years ago

    Hi


    Thank you for submitting your question in Intel Community.

    I'm Adzim, application engineer will assist you in this thread.


    May I know which Windows build version that you used?


    Have you verify that the Windows Subsystem for Linux option has been enabled in Windows Features?

    Restart required to apply the changes.


    If you have option enabled and already reboot but the error still exist, please try to remove the WSL and Ubuntu then reinstall it again.

    Please capture the installation process for verification purpose.


    Regards,

    Adzim


  • anhnidnahp's avatar
    anhnidnahp
    Icon for New Contributor rankNew Contributor
    2 years ago

    Hello Adzim, thank you for helping me with this issue. I have checked that all Windows Subsystem for Linux options are turned on and restarted the computer. However, it still doesn't work.

    So, I tried uninstalling everything and reinstalling following the steps below. I've listed them here for your easy reference.
    1. Enable the Windows Subsystem for Linux + Enable virtual machine feature::

    Result:

    2. Install Linux distribution Ubuntu18.04 LTS for WSL

    3. Install additional distro packages

    + sudo apt update

    + sudo apt install wsl

    + sudo apt install dos2unix

    + sudo apt install make

    + sudo apt install build-essential

    But it still appears as I mentioned initially.

  • AdzimZM_Altera's avatar
    AdzimZM_Altera
    Icon for Regular Contributor rankRegular Contributor
    2 years ago

    Hello


    Thank you for your feedback.


    The installation parts look normal based on the screenshots that you have provided.

    The windows build version also should be supported.


    There a few things that might be helpful to resolve this based on the use cases.

    1. There are some interruption that might happen during the installation progress if using VPN.
      1. Try to disconnect from VPN during the installation progress.
    2. Set the default version for WSL.
      1. You may run this command to set the default version: wsl --set-default-version 1
    3. Running application from NIOS II Command Shell.
      1. Try to run a command in the NIOS II Command Shell such as make or jtagconfig.exe.
      2. Link to NIOS II Handbook: https://www.intel.com/content/www/us/en/docs/programmable/683525/21-3/running-make.html
    4. Try to run the Quartus software in administrator privileges.


    Regards,

    Adzim


  • anhnidnahp's avatar
    anhnidnahp
    Icon for New Contributor rankNew Contributor
    2 years ago

    I'm sorry, Adzim, for responding just now. However, I've tried the methods you mentioned without success. Currently, I've switched to Quartus 18.1 and turned off WSL to serve my projec

  • AdzimZM_Altera's avatar
    AdzimZM_Altera
    Icon for Regular Contributor rankRegular Contributor
    2 years ago

    Hi,


    Thank you for your feedback.


    I understand your current situation.

    For the time being, you may use previous Quartus version.


    If you are able to debug this issue again in future, I suggest you to open a new thread with this tagging of this thread.

    I'm now closing this thread.


    Regards,

    Adzim