Visible to Intel only — GUID: xfu1638454752451
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: xfu1638454752451
Ixiasoft
4.2. Linking Applications
When you generate the Nios® V processor project, the BSP Editor generates two linker related files:
- linker.x: The linker command file that the generated application's makefile uses to create the .elf binary file.
- linker.h: Contains information about the linker memory layout.
Every Nios® V processor application contains the following linker sections:
You can add additional linker sections to the .elf file to hold custom code and data. These linker sections are placed in named memory regions, defined to correspond with physical memory devices and addresses. By default, BSP Editor automatically generates these linker sections. However, you can control the linker sections for a particular application.
Linker Sections | Descriptions |
---|---|
.text | Executable code. |
.rodata | Any read-only data used in the execution of the program. |
.rwdata | Stores read-write data used in the execution of the program. |
.bss | Contains uninitialized static data. |
.heap | Contains dynamically allocated memory. |
.stack | Stores function-call parameters and other temporary data. |