Ashling* RiscFree* Integrated Development Environment (IDE) for Intel® FPGAs User Guide

ID 730783
Date 7/26/2024
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

3.3. Setting Run Configuration to Download Nios® V Processor Project

You can download and run Nios® V processor software project on the targeted Intel FPGA using the RiscFree* IDE for Intel® FPGAs. To run the project, follow these steps:

  1. Right-click the project folder (application or BSP) in the project explorer and select Run As > Run configurations.
  2. Select Ashling RISC-V Hardware Debugging > <Project Name>. Ensure the Project and C/C++ Application match your project name and your project .elf file, respectively.
  3. In the Main tab, for C/C++ Application, browse to select the application build .elf file. For example: hello.elf.
    Figure 10. Run Configurations for Nios V Processor—Main Tab
  4. Under the Debugger tab, set these settings:
    • Debug probe: Agilex SI/SoC Dev Kit (Name of the FPGA board/development kit)
    • Transport type: JTAG
    • JTAG frequency: 16 MHz
    Figure 11. Run Configurations for Nios® V Processor—Debugger Tab
  5. Click Auto-detect Scan Chain to automatically detect JTAG scan chain information of the target device. Select the options from Device/Tap selection and Core selection.
  6. Based on the OS you use, configure the OS Awareness settings as follows:
    • Intel HAL: No OS Awareness configuration is required.
    • Other OS: Under the OS Awareness tab, turn on Enable OS Aware Debugging, and select the OS version applicable to you as listed below:
      • OS: μC/OS-II and Version: 2.93.0
      • OS: FreeRTOS and Version: 10.5.0
      • OS: Zephyr and Version: 3.2.0
        Note: Nios® V processor does not support Linux OS.
    Figure 12. Enabling OS Aware Run in RISC-V Hardware Debugging
  7. Click Run. RiscFree* IDE for Intel® FPGAs downloads the program to the target and you can find the console prints as shown in the following diagram.
    Figure 13. Console Prints after Run Connection is Successful