A newer version of this document is available. Customers should click here to go to the newest version.
1. About This Document
2. About the Nios® V Embedded Processor
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. Nios® V Embedded Processor Design Handbook Archives
9. Document Revision History for the Nios® V Embedded Processor Design Handbook
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
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
6.7.4. Configuring iPerf Server Auto-Initialization
Note: This configuration is only available for µC/TCP-IP IPerf Example Design.
The example design is capable of initializing the iPerf server using pre-determined arguments upon running the Nios V applications. This is developed for ease of use purpose, and it can be disabled if other iPerf utility is required.
To disable this feature, you need to provide the 0 argument to the App_IPerf_TaskTerminal(), and the iPerf terminal begins acquiring the custom iperf commands after iPerf is successfully initialized. The iperf command must end with an ENTER key to complete the acquisition process.
Figure 93. iPerf Terminal
iPerf server auto-initialization feature in main.c
//To enable auto-initialization
App_IPerf_TaskTerminal( 1 );
//To disable auto-initialization
App_IPerf_TaskTerminal( 0 );