Visible to Intel only — GUID: xtp1646032164861
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: xtp1646032164861
Ixiasoft
5.5.2.5. HEX File Generation
A .hex file must be generated from the .elf file so that the .hex file can be used for memory initialization.
- Launch the Nios V Command Shell.
- Use the following command line to convert the .elf to .hex for your application. This command creates the application (app.hex) file.
elf2hex software/app/build/app.elf -o app.hex \ -b <base address of OCRAM> -w <data width of OCRAM> \ -e <end address of OCRAM>
- Recompile the hardware design to memory-initialize the app.hex into the On-Chip RAM.
Note: You must ensure that the .hex filename is exactly the same as configured in the system memory for a successful recompilation.