Forum Discussion

BrendenB's avatar
BrendenB
Icon for New Contributor rankNew Contributor
2 years ago
Solved

RiscFree debugging fails after first debug

I have a simple Nios V system that prints "Hello World" on a DE-10. The design is generated using Quartus Std Lite 23.1.1. The first time I try to debug, everything is fine. The second time I try to ...
Nios Cpu
  • tehjingy_Altera's avatar
    tehjingy_Altera
    2 years ago

    Hi


    Sorry in that cause you will need to wait for the release of Quartus Standard 24.1 in Q1 next year.


    Regards

    Jingyang, Teh


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

I just wanted to mention a work around I have been using for debugging. I have been using OpenOCD running externally from the RiscFree IDE.

  1. Terminal: openocd-cfg-gen debugger.cfg
  2. Terminal: openocd -f debugger.cfg
  3. IDE: Create "GDB OpenOCD Debugging Launcher"
  4. IDE: On Main Configure executable.
  5. IDE: Setup to compile the program before launch.
  6. IDE: On Debugger tab Uncheck "Start OpenOCD locally". I'm running it externally to make things easier. I guess you can launch it from here if you wanted.
  7. IDE: Executable name ${eclipse_home}/../toolchain/riscv32-unknown-elf/bin/riscv32-unknown-elf-gdb. This was automatically filled.
  8. IDE: Commands: set mem inaccessible-by-default off. Again automatically filled.
  9. IDE: Remote Target Host: localhost Port: 3333. Again automatically filled.
  10. IDE: I left the other settings at their defaults.

This seems to be pretty reliable to me (but slower).