Forum Discussion

ove's avatar
ove
Icon for New Contributor rankNew Contributor
6 months ago
Solved

Nios-V on Cyclone IV

Hi all Trying to get a NÌOS-V running on Cyclone IV using, just the basics. Using Quartus 25.1. Just as a test I added just the neccessary components and the sysid as shows in the picture below. ...
Nios Cpu
  • tehjingy_Altera's avatar
    tehjingy_Altera
    5 months ago

    Hi ove 

     

     

    I managed to reproduce the issue on my end.

    It seems like this is a valid issue on the driver side to cause the error you are facing.

     

    A workaround currently is to limit the naming of the SystemID IP to "sysid".

     

     

    Could you possible to try that and see if it solves the issue?

     

WaiMunC_Altera's avatar
WaiMunC_Altera
Icon for New Contributor rankNew Contributor
6 months ago

Hi Ove,

Based on you steps. can you include the altera_avalon_sysid_qsys_regs.h

Regards,

WaiMun

  • ove's avatar
    ove
    Icon for New Contributor rankNew Contributor
    5 months ago

    I already did, but still compiles with "Unknown reference to alt_avalon_sysid_qsys_test"

    • tehjingy_Altera's avatar
      tehjingy_Altera
      Icon for Regular Contributor rankRegular Contributor
      5 months ago

      Hi ove 

       

      Is it possible that you could attached a full log of the command used?

      I tried the steps on the environment here but could not see the error you are facing.

      • Naji_Naufel_Arrow's avatar
        Naji_Naufel_Arrow
        Icon for Occasional Contributor rankOccasional Contributor
        5 months ago

        Hi ove,

        You have to establish an Ashling RiscFree project which uses the CMake flow.

        https://docs.altera.com/r/docs/726952/25.3.1/nios-v-embedded-processor-design-handbook/building-the-application-projects

        Command line flow:

        cmake -G "Unix Makefiles" -B software/app/build -S software/app

        make -C software/app/build

        Or, you can do it in the RiscFree IDE by creating a C/C++ project, selecting CMake empty file flow and pointing to the software/app folder which contains the source file.

    • tehjingy_Altera's avatar
      tehjingy_Altera
      Icon for Regular Contributor rankRegular Contributor
      5 months ago

      Hi ove 

       

       

      I managed to reproduce the issue on my end.

      It seems like this is a valid issue on the driver side to cause the error you are facing.

       

      A workaround currently is to limit the naming of the SystemID IP to "sysid".

       

       

      Could you possible to try that and see if it solves the issue?

       

      • ove's avatar
        ove
        Icon for New Contributor rankNew Contributor
        5 months ago

        Hi tehjingy_Altera​ 

        Nice that worked, can now use the sysid from the firmware

         

        Thanks for the quick assistance.

        Do I need to flag this somewhere else as an bug ?