Nios® V Embedded Processor Design Handbook

Download PDF
ID 726952
Date 4/04/2022
Public

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

Document Table of Contents
Document Table of Contents x
1. About this Document 2. Introduction 3. Nios® V Processor Hardware System Design with Intel® Quartus® Prime Pro Edition and Platform Designer 4. Nios® V Processor Software System Design 5. Nios® V Processor Configuration and Booting Solutions 6. Nios® V Processor - Using the MicroC/TCP-IP Stack 7. Nios® V Processor Debugging, Verifying, and Simulating 8. Document Revision History for the Nios® V Embedded Processor Design Handbook
2. Introduction x
2.1. Overview on Intel® FPGA IP and Soft-Core Processors 2.2. Embedded System Design 2.3. Nios® V Processor Quick Start Guide
2.3. Nios® V Processor Quick Start Guide x
2.3.1. System Requirements 2.3.2. Nios® V/m Processor Example Design 2.3.3. Software Design Flow 2.3.4. Programming Nios® V/m into the FPGA Device
2.3.1. System Requirements x
2.3.1.1. Hardware and Software Requirements 2.3.1.2. Setting Up Open-Source Tools
2.3.2. Nios® V/m Processor Example Design x
2.3.2.1. Generating the Example Design Through Graphical User Interface 2.3.2.2. Generating the Nios® V/m Processor Example Design Using the Command-Line Interface
2.3.2.1. Generating the Example Design Through Graphical User Interface x
2.3.2.1.1. Generating the Nios® V/m Processor Example Design in Platform Designer 2.3.2.1.2. Generating the Nios® V/m Processor Example Design System in Platform Designer
2.3.3. Software Design Flow x
2.3.3.1. Generating the Board Support Package 2.3.3.2. Generating the Application Project File 2.3.3.3. Building the Application Project
2.3.3.1. Generating the Board Support Package x
2.3.3.1.1. Generating the Board Support Package using the BSP Editor GUI 2.3.3.1.2. Generating the Board Support Package using the Command-Line Interface
2.3.3.3. Building the Application Project x
2.3.3.3.1. Building the Application Project using Eclipse Embedded CDT 2.3.3.3.2. Building the Application Project using the Command-Line Interface
3. Nios® V Processor Hardware System Design with Intel® Quartus® Prime Pro Edition and Platform Designer x
3.1. Creating Nios® V Processor System Design with Platform Designer 3.2. Integrating Platform Designer System into the Intel® Quartus® Prime Project 3.3. Designing a Nios® V Processor Memory System 3.4. Clocks and Resets
3.1. Creating Nios® V Processor System Design with Platform Designer x
3.1.1. Instantiating Nios® V/m Processor IP Core 3.1.2. Defining System Component Design 3.1.3. Specifying Base Addresses and Interrupt Request Priorities
3.1.1. Instantiating Nios® V/m Processor IP Core x
3.1.1.1. Configure Nios® V Processor Parameters 3.1.1.2. Generate Nios® V processor example design from Platform Designer
3.1.1.1. Configure Nios® V Processor Parameters x
3.1.1.1.1. Debug Tab 3.1.1.1.2. Vectors Tab
3.2. Integrating Platform Designer System into the Intel® Quartus® Prime Project x
3.2.1. Instantiating the Nios® V Processor System Module in the Intel® Quartus® Prime Project 3.2.2. Connecting Signals and Assigning Physical Pin Locations 3.2.3. Constraining the Intel FPGA Design
3.3. Designing a Nios® V Processor Memory System x
3.3.1. Volatile Memory 3.3.2. Non-Volatile Memory 3.3.3. On-Chip Memory Configuration – RAM/ROM
5. Nios® V Processor Configuration and Booting Solutions x
5.1. Introduction 5.2. Linking Applications 5.3. Nios® V Processor Booting Methods 5.4. Introduction to Nios® V Processor Booting Methods 5.5. Nios® V Processor Booting from Configuration QSPI Flash 5.6. Nios V Processor Booting from On-Chip Memory (OCRAM) 5.7. Summary of Nios V Processor Vector Configuration and BSP Settings
5.2. Linking Applications x
5.2.1. Linking Behaviour
5.2.1. Linking Behaviour x
5.2.1.1. Default BSP Linking 5.2.1.2. Configurable BSP Linking
5.4. Introduction to Nios® V Processor Booting Methods x
5.4.1. Nios® V Processor Application Execute-In-Place from Boot Flash 5.4.2. Nios® V Processor Application Copied from Boot Flash to RAM Using Boot Copier 5.4.3. Nios® V Processor Application Execute-In-Place from OCRAM
5.4.1. Nios® V Processor Application Execute-In-Place from Boot Flash x
5.4.1.1. alt_load()
5.4.2. Nios® V Processor Application Copied from Boot Flash to RAM Using Boot Copier x
5.4.2.1. GSFI Bootloader 5.4.2.2. SDM Bootloader
5.5. Nios® V Processor Booting from Configuration QSPI Flash x
5.5.1. Nios V Processor Design, Configuration and Boot Flow (Control Block-based Device) 5.5.2. Nios V Processor Design, Configuration and Boot Flow (SDM-based Devices)
5.5.1. Nios V Processor Design, Configuration and Boot Flow (Control Block-based Device) x
5.5.1.1. Nios® V Processor Application Executes-In-Place from Configuration QSPI Flash 5.5.1.2. Nios® V Processor Application Copied from Configuration QSPI Flash to RAM Using Boot Copier (GSFI Bootloader) 5.5.1.3. GSFI Bootloader Example Design
5.5.1.1. Nios® V Processor Application Executes-In-Place from Configuration QSPI Flash x
5.5.1.1.1. Hardware Design Flow 5.5.1.1.2. Software Design Flow 5.5.1.1.3. Programming Files Generation 5.5.1.1.4. QSPI Flash Programming
5.5.1.2. Nios® V Processor Application Copied from Configuration QSPI Flash to RAM Using Boot Copier (GSFI Bootloader) x
5.5.1.2.1. Hardware Design Flow 5.5.1.2.2. Software Design Flow 5.5.1.2.3. Programming Files Generation 5.5.1.2.4. QSPI Flash Programming
5.5.2. Nios V Processor Design, Configuration and Boot Flow (SDM-based Devices) x
5.5.2.1. Nios V Processor Application Copied from Configuration QSPI Flash to RAM Using Boot Copier (SDM Bootloader) 5.5.2.2. SDM Bootloader Example Design
5.5.2.1. Nios V Processor Application Copied from Configuration QSPI Flash to RAM Using Boot Copier (SDM Bootloader) x
5.5.2.1.1. Hardware Design Flow 5.5.2.1.2. Software Design Flow 5.5.2.1.3. Software Design Flow (SDM Bootloader Project) 5.5.2.1.4. Software Design Flow (User Application Project) 5.5.2.1.5. Programming Files Generation 5.5.2.1.6. QSPI Flash Programming SDM
5.6. Nios V Processor Booting from On-Chip Memory (OCRAM) x
5.6.1. Nios V Processor Application Executes in-place from OCRAM
5.6.1. Nios V Processor Application Executes in-place from OCRAM x
5.6.1.1. Hardware Design Flow 5.6.1.2. Software Design Flow 5.6.1.3. Programming
6. Nios® V Processor - Using the MicroC/TCP-IP Stack x
6.1. Introduction 6.2. Software Architecture 6.3. Support and Licensing 6.4. MicroC/TCP-IP Example Designs 6.5. Development Flow 6.6. Operating the Example Designs 6.7. Optional Configuration 6.8. MicroC/TCP-IP Simple Socket Server Concepts
6.4. MicroC/TCP-IP Example Designs x
6.4.1. Hardware and Software Requirements 6.4.2. Overview 6.4.3. Acquiring the Example Design Files 6.4.4. Hardware Design Files 6.4.5. Software Design Files
6.4.5. Software Design Files x
6.4.5.1. MicroC/TCP-IP IPerf Example Design 6.4.5.2. MicroC/TCP-IP Simple Socket Server Example Design
6.5. Development Flow x
6.5.1. Hardware Development Flow 6.5.2. Software Development Flow 6.5.3. Device Programming
6.5.2. Software Development Flow x
6.5.2.1. Creating a BSP project 6.5.2.2. Configuring the BSP 6.5.2.3. Creating an Application Project 6.5.2.4. Building the Application Project 6.5.2.5. HEX File Generation
6.6. Operating the Example Designs x
6.6.1. Operating the MicroC/TCP-IP IPerf 6.6.2. Operating the MicroC/TCP-IP Simple Socket Server
6.7. Optional Configuration x
6.7.1. Configuring Hardware Name 6.7.2. Configuring MAC and IP Addresses 6.7.3. Configuring MicroC/TCP-IP Initialization 6.7.4. Configuring iPerf Server Auto-Initialization
6.7.3. Configuring MicroC/TCP-IP Initialization x
6.7.3.1. Network Task Configuration Default network task configuration in uc_tcp_ip_init.c 6.7.3.2. Network Interface Configuration
6.8. MicroC/TCP-IP Simple Socket Server Concepts x
6.8.1. MicroC/OS-II Resources 6.8.2. Error Handling 6.8.3. MicroC/TCP-IP Stack Default Configuration
7. Nios® V Processor Debugging, Verifying, and Simulating x
7.1. Debugging Nios® V Processor Software Designs 7.2. Debugging Tools 7.3. Additional Embedded Design Considerations 7.4. Simulating Nios® V Processor Designs
7.1. Debugging Nios® V Processor Software Designs x
7.1.1. OpenOCD and Eclipse Embedded CDT 7.1.2. Objdump File 7.1.3. Show Make Commands
7.3. Additional Embedded Design Considerations x
7.3.1. JTAG Signal Integrity 7.3.2. Additional Memory Space for System Prototyping
7.4. Simulating Nios® V Processor Designs x
7.4.1. Prerequisites 7.4.2. Setting Up and Generating Your Simulation Environment in Platform Designer 7.4.3. Creating Nios V Processor Software 7.4.4. Generating Memory Initialization File 7.4.5. Generating System Simulation Files 7.4.6. Running Simulation in the QuestaSim Simulator Using Command Line
7.4.2. Setting Up and Generating Your Simulation Environment in Platform Designer x
7.4.2.1. Using IP and Platform Designer Simulation Setup Scripts
7.4.3. Creating Nios V Processor Software x
7.4.3.1. Creating a Software Project using Platform Designer & Eclipse Embedded CDT 7.4.3.2. Creating a Software Project Using Command Line
1. About this Document
2. Introduction
3. Nios® V Processor Hardware System Design with Intel® Quartus® Prime Pro Edition and Platform Designer
4. Nios® V Processor Software System Design
5. Nios® V Processor Configuration and Booting Solutions
6. Nios® V Processor - Using the MicroC/TCP-IP Stack
7. Nios® V Processor Debugging, Verifying, and Simulating
8. Document Revision History for the Nios® V Embedded Processor Design Handbook

6.7.3.1. Network Task Configuration

In this example design, the µC/TCP-IP stack has three configurable tasks, the Receive task, the Transmit De-allocation task and the Timer task. Each task is configured with its own task priority and task stack size.

In order to place a task at higher priority, you have to register it with a lower value, and vice versa. The third-party vendor recommends configuring the task priorities as listed below for optimum performance.

  • Network Transmit (TX) De-allocation task (Highest priority)
  • Network timer task
  • Network Receive (RX) task (Lowest Priority)
As for the task stack size, it is dependent on the processor architecture and compiler used. Configuring the stack size to 4,096 bytes is deemed sufficient for most applications.
Table 17.  Network task configuration
Settings Description Default Value
TX_TASK_PRIO Network TX De-allocation Task Priority 1u
RX_TASK_PRIO Network RX Task Priority 3u
TMR_TASK_PRIO Network Timer Task Priority 5u
TX_TASK_SIZE Network TX De-allocation Task Stack Size 4096u
RX_TASK_SIZE Network RX Task Stack Size 4096u
TMR_TASK_SIZE Network Timer Task Stack Size 4096u

Default network task configuration in uc_tcp_ip_init.c 

#define TX_TASK_SIZE  (4096u)
#define RX_TASK_SIZE  (4096u)
#define TMR_TASK_SIZE (4096u)

static const unsigned TX_TASK_PRIO  = 1u;
static const unsigned RX_TASK_PRIO  = 3u;
static const unsigned TMR_TASK_PRIO = 5u;
Level Two Title