Visible to Intel only — GUID: uhz1645762417774
Ixiasoft
1. About the Nios® V Embedded Processor
2. Nios® V Processor Hardware System Design with Intel® Quartus® Prime Software and Platform Designer
3. Nios® V Processor Software System Design
4. Nios® V Processor Configuration and Booting Solutions
5. Nios® V Processor - Using the MicroC/TCP-IP Stack
6. Nios® V Processor Debugging, Verifying, and Simulating
7. Nios® V Processor — Remote System Update
8. Nios® V Embedded Processor Design Handbook Archives
9. Document Revision History for the Nios® V Embedded Processor Design Handbook
4.1. Introduction
4.2. Linking Applications
4.3. Nios® V Processor Booting Methods
4.4. Introduction to Nios® V Processor Booting Methods
4.5. Nios® V Processor Booting from Configuration QSPI Flash
4.6. Nios V Processor Booting from On-Chip Memory (OCRAM)
4.7. Summary of Nios® V Processor Vector Configuration and BSP Settings
6.4.1. Prerequisites
6.4.2. Setting Up and Generating Your Simulation Environment in Platform Designer
6.4.3. Creating Nios V Processor Software
6.4.4. Generating Memory Initialization File
6.4.5. Generating System Simulation Files
6.4.6. Running Simulation in the QuestaSim Simulator Using Command Line
Visible to Intel only — GUID: uhz1645762417774
Ixiasoft
5.4.4. Hardware Design Files
Despite the example designs functioned differently, they share similar hardware design and BSP settings. The only difference lies in their respective Nios V application source code, one for the Simple Socket Server application, while the other for the iPerf 2 application.
The µC/TCP-IP example designs are developed using the Platform Designer. The hardware files can be generated using the build_sof.py Python script. The example design consist of:
- Nios® V Processor Intel FPGA IP
- On-Chip Memory II Intel FPGA IP for System Memory and Descriptor Memory
- JTAG UART Intel FPGA IP
- System ID Peripheral Intel FPGA IP
- Parallel I/O Intel FPGA IP (PIO)
- Modular Scatter-Gather DMA Intel FPGA IP (mSGDMA)
- Triple-Speed Ethernet Intel FPGA IP (TSE)
Figure 80. Hardware Block Diagram
Note:
- (1) The first n bytes are reserved for mSGDMA descriptor buffers, where n is the number of bytes taken by the configured RX or TX buffers. Applications must not use this memory region.
- (2) For MAC variations without internet FIFO buffers, the transmit and receive FIFOs are external to the MAC function.
- (3) Only one buffer type (RX or TX buffers) can reside in the descriptor memory.