Visible to Intel only — GUID: lco1690858869035
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 Processor — Using Custom Instruction
9. Nios® V Embedded Processor Design Handbook Archives
10. 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: lco1690858869035
Ixiasoft
7.3.6. Operating the RSU Client API
The RSU Client API performs the following operations:
- Trigger Intel FPGA device reconfiguration with selected image
- Update the application image
- Update the factory image
To display the Nios® V processor application messages, the example design utilizes the JTAG UART Intel FPGA IP. You can begin the display message by using the following command:
juart-terminal
The JTAG UART terminal displays the RSU message logs, followed by the RSU Menu. While the factory image provides the full list of operations, the application images can support status log acquisition and reconfiguration operations only. The RSU Menu offers the following options:
- Acquire RSU status log
- Acquire Decision Firmware Status Log
- Trigger reconfiguration with Factory Image
- Trigger reconfiguration with Application Images
- Application-0 Image
- Application-1 Image
- Add Application-1 Image
- Update the Factory Image
- Erase Decision Firmware
Note: For application image, the Menu options are only Options 1 to 4.