Forum Discussion

pp123's avatar
pp123
Icon for New Contributor rankNew Contributor
1 month ago
Solved

NIOS V/m dbg_reset_out signal (Q25.1 Std, MAX10)

Hello,

I have a problem with loading elf file.

Signal dbg_reset_out (used for resetting HDL components) is inactive (low) when I'm using "niosv-download -r -g exeFile.elf" command (Q25.1 Std, v25.2.1 Ashling GDB Server, Linux OS, MAX10 device, NIOS V variant m).
The same command for Q24.1 Std (previous version of Ashling GDB Server, the same OS and PC) works.

For me temporary solution is using additional option -o (OpenOCD instead of Ashling® RiscFree GDB Server). Is there any better solution?

Nios Cpu
  • LiangYuG_Altera's avatar
    LiangYuG_Altera
    19 days ago

    Hi pp123​ 

    pp123 wrote:

    Signal dbg_reset_out (used for resetting HDL components) is inactive (low) when I'm using "niosv-download -r -g exeFile.elf" command (Q25.1 Std, v25.2.1 Ashling GDB Server, Linux OS, MAX10 device, NIOS V variant m).
    The same command for Q24.1 Std (previous version of Ashling GDB Server, the same OS and PC) works.

    For me temporary solution is using additional option -o (OpenOCD instead of Ashling® RiscFree GDB Server).

    LiangYuG_Altera wrote:

    Please continue using OpenOCD.
    We have reported this failure to Ashling for investigation. 

    Ashling have responded to us, and fix their latest Ashling GDBServer in the upcoming RiscFree IDE v26.1.1-C in Quartus Prime Pro 26.1.1. Since you are using Quartus Prime Standard, you will need to wait for the Quartus Prime Standard 26.1 for the working Ashling GDBServer.

    Regards,
    Liang Yu

14 Replies

Show More
  • pp123's avatar
    pp123
    Icon for New Contributor rankNew Contributor
    1 month ago

    Would you mind sharing what is the incorrect reset connection?

    Yes, of course - dbg_reset_out output connected (indirectly) with reset input. It casued probably debug module reset and (sometimes) stranged behaviour.
    "Sometimes" because using niosv-download -r -g (Q24.1 Std) at Linux PC seems worked without problems.

    This connection also worked properly in our older projects using NIOS2.

  • LiangYuG_Altera's avatar
    LiangYuG_Altera
    Icon for Occasional Contributor rankOccasional Contributor
    1 month ago

    Thanks pp123​ 

    pp123 wrote:

    Yes, of course - dbg_reset_out output connected (indirectly) with reset input. It casued probably debug module reset and (sometimes) stranged behaviour.
    "Sometimes" because using niosv-download -r -g (Q24.1 Std) at Linux PC seems worked without problems.

    Oh ya, that is a thing to beware of.
    Resetting the debug module during "niosv-download" -r can cause un-deterministic behaviour. 
    In your words, "sometimes strange behaviour".

    It is mentioned here. But we should rewrite it more explicitly for future readers.

    pp123 wrote:

    This connection also worked properly in our older projects using NIOS2.

    The NIOS2 Debug Module is different from RISC-V Debug Module.
    We aimed to make them as similar as possible at the top-level. But there are slight difference between them.

    You may refer here for migration tips from NIOS2 to NIOSV.
    (Rewrite this more explicitly too)

    Regards,
    Liang Yu