Build errors on helloworld tutorial

Looking at your screenshot, there are two distinct failure categories here, and at least one has a documented root cause.

1. niosv-stack-report failure (line 73/180 — helloworld.elf.stack_report] Error 2)

This is a known issue in Quartus Prime Pro Edition Software version 22.2 when building Nios V processor software in RiscFree IDE. The error chain you see — make: *** [Makefile:91: all] Error 2, CMakeFiles/niosv-stack-report.dir/all] Error 2, and the stack_report target failure — occurs because the niosv-stack-report utility is only present in Quartus Prime Pro Edition, and is missing when RiscFree IDE is installed as a standalone development tool (e.g., paired with only the Quartus Prime Programmer). Why does niosv-stack-report return error during Nios® V build flow in RiscFree* IDE for Intel® FPGAs?

To resolve this, make sure you are running RiscFree IDE with a full Quartus Prime Pro installation (not just the Programmer), so that niosv-stack-report is available on the PATH.

2. onchip_memory2_0.hex] Error 2 (line 73, create-hex)

This failure in the create-hex target is most likely a cascade from the niosv-stack-report failure above — once that target fails, the overall make job aborts related targets as well. Fixing the stack-report issue should resolve this one too.

General checklist:

• Confirm you are launching RiscFree IDE from within a full Quartus Prime Pro installation, not as a standalone tool.
• Make sure you open the Nios V Command Shell to run niosv-app and related utilities Nios V Processor Software Developer Handbook — if your PATH is not set correctly in the IDE environment, utilities like niosv-stack-report and elf2hex won't be found.
• Before importing the project to Ashling RiscFree IDE for Altera FPGAs, ensure you have the generated BSP package and application package already created via the command-line flow. Nios V Processor Software Developer Handbook

If you are on Quartus Prime Pro 22.2 specifically, upgrading to a later version would be the cleanest fix, as the underlying issue is version-specific.

Note: To continue using AI Responder, please start your next inquiry with ai_responder

Disclaimer (Beta): The AI Responder is currently provided as a beta feature. AI-generated responses may contain errors or omissions. Please verify technical guidance with official Altera documentation before implementation.

Thank you very much.