AN 978: Nios® V Processor Migration Guidelines

Download PDF
ID 773196
Date 5/15/2024
Public
Document Table of Contents
Document Table of Contents x
1. Overview 2. Architecture Comparison 3. Processor Core Migration Mapping 4. Design Flow Comparison 5. Migration by Use Case 6. Document Revision History for AN 978: Nios® V Processor Migration Guidelines
2. Architecture Comparison x
2.1. Features Comparison 2.2. Ecosystem Comparison 2.3. Software Optimization
4. Design Flow Comparison x
4.1. Difference in the Design Flow 4.2. Design Migration from Nios® II Processor to Nios® V Processor
4.2. Design Migration from Nios® II Processor to Nios® V Processor x
4.2.1. Quartus® Prime Standard Edition 4.2.2. Quartus® Prime Pro Edition
4.2.1. Quartus® Prime Standard Edition x
4.2.1.1. Hardware Component 4.2.1.2. Software Component
4.2.2. Quartus® Prime Pro Edition x
4.2.2.1. Hardware Component 4.2.2.2. Software Component
5. Migration by Use Case x
5.1. Migrating Nios® II Processor to Nios® V Processor 5.2. Timer 5.3. Interrupt 5.4. Ethernet Stack 5.5. Bootloader 5.6. Data and Instruction Cache 5.7. Tightly Coupled Memory 5.8. Custom Instructions 5.9. Error Correction Code 5.10. Intel® HAL Settings 5.11. Micrium MicroC/OS-II BSP Settings 5.12. Software Packages
5.1. Migrating Nios® II Processor to Nios® V Processor x
5.1.1. Processor IP Instantiation in Platform Designer 5.1.2. Migrating Nios® II/e Processor to Nios® V/c Processor 5.1.3. Migrating Nios® II Processor to Nios® V/m Processor 5.1.4. Migrating Nios® II/f Processor to Nios® V/g Processor
5.1.2. Migrating Nios® II/e Processor to Nios® V/c Processor x
5.1.2.1. Nios® V Processor Hardware Migration 5.1.2.2. Nios® V Processor Software Migration
5.1.2.1. Nios® V Processor Hardware Migration x
5.1.2.1.1. Signal and Interface Mapping 5.1.2.1.2. IP Parameter Configuration 5.1.2.1.3. BSP Project Generation
5.1.2.2. Nios® V Processor Software Migration x
5.1.2.2.1. Command-Line Build Flow 5.1.2.2.2. IDE Build Flow
5.1.3. Migrating Nios® II Processor to Nios® V/m Processor x
5.1.3.1. Nios® V Processor Hardware Migration 5.1.3.2. Nios® V Processor Software Migration
5.1.3.1. Nios® V Processor Hardware Migration x
5.1.3.1.1. Signal and Interface Mapping 5.1.3.1.2. IP Parameter Configuration 5.1.3.1.3. BSP Project Generation
5.1.3.2. Nios® V Processor Software Migration x
5.1.3.2.1. Command-Line Build Flow 5.1.3.2.2. IDE Build Flow
5.1.4. Migrating Nios® II/f Processor to Nios® V/g Processor x
5.1.4.1. Nios® V Processor Hardware Migration 5.1.4.2. Nios® V Processor Software Migration
5.1.4.1. Nios® V Processor Hardware Migration x
5.1.4.1.1. Signal and Interface Mapping 5.1.4.1.2. IP Parameter Configuration 5.1.4.1.3. BSP Project Generation
5.1.4.2. Nios® V Processor Software Migration x
5.1.4.2.1. Command-Line Build Flow 5.1.4.2.2. IDE Build Flow
1. Overview
2. Architecture Comparison
3. Processor Core Migration Mapping
4. Design Flow Comparison
5. Migration by Use Case
6. Document Revision History for AN 978: Nios® V Processor Migration Guidelines

5.1.3.2.1. Command-Line Build Flow

Similar with Nios II Software Build Tools, you can create the Nios® V processor software project with Nios V Command Shell and Ashling* RiscFree* IDE for Intel® FPGAs.
Table 18.  CLI Build Flow Comparison
Flow Nios® V Processor Nios® II Processor
Invoke BSP Editor GUI
  • For Quartus® Prime Pro Edition software, use qsys-edit --1=.bsp.
  • For Quartus® Prime Standard Edition software, use niosv-bsp-editor .
  • For Quartus® Prime Pro Edition software, use nios2-bsp-editor or qsys-edit --1=.bsp.
    Note: The BSP Editor is integrated into the Platform Designer.
  • For Quartus® Prime Standard Edition, use nios2-bsp-edit.
    Note: The BSP Editor is not integrated as part of the Platform Designer.
Invoke Command Shell niosv-shell
  • In the Windows operating system, on the Start menu, point to Programs > Intel FPGA > Nios II EDS <version>,and click Nios II <version> Command Shell :.
  • In the Linux operating system, in a command shell, change directories to <Nios II EDS install path>, and type the command nios2_command_shell.sh.
Create a BSP niosv-bsp -c –p=<path to .qpf file> -s=<path to .qsys file> -t=<bsp type> [OPTIONS] settings.bsp nios2-bsp <bsp type> <bsp-dir> [<sopc>] [<override>]
Generate a BSP niosv-bsp –g [OPTIONS] settings.bsp
Update a BSP niosv-bsp –u [OPTIONS] settings.bsp
Examine a BSP niosv-bsp –q –E=<script name> [OPTIONS] settings.bsp nios2-bsp-query-settings --settings settings.bsp
Create an APP niosv-app -b=<bsp directory>-s=<source files directory> [OPTIONS] nios2-app-generate-makefile --bsp-dir <bsp directory> --src-file <source files directory> [<OPTIONS>]
Build an App cmake -B <build directory> -S <app directory> -G “Unix Makefiles”

make –C <build directory>

make
Download an ELF niosv-download <filename.elf> nios2-download <filename.elf>
Run an ELF niosv-download –g -r nios2-download –g -r
Open JTAG UART Terminal juart-terminal nios2-terminal
Level Two Title