AN 978: Nios® V Processor Migration Guidelines

Download PDF
ID 773196
Date 5/15/2024
Public
Document Table of Contents
Document Table of Contents x
1. Overview 2. Architecture Comparison 3. Processor Core Migration Mapping 4. Design Flow Comparison 5. Migration by Use Case 6. Document Revision History for AN 978: Nios® V Processor Migration Guidelines
2. Architecture Comparison x
2.1. Features Comparison 2.2. Ecosystem Comparison 2.3. Software Optimization
4. Design Flow Comparison x
4.1. Difference in the Design Flow 4.2. Design Migration from Nios® II Processor to Nios® V Processor
4.2. Design Migration from Nios® II Processor to Nios® V Processor x
4.2.1. Quartus® Prime Standard Edition 4.2.2. Quartus® Prime Pro Edition
4.2.1. Quartus® Prime Standard Edition x
4.2.1.1. Hardware Component 4.2.1.2. Software Component
4.2.2. Quartus® Prime Pro Edition x
4.2.2.1. Hardware Component 4.2.2.2. Software Component
5. Migration by Use Case x
5.1. Migrating Nios® II Processor to Nios® V Processor 5.2. Timer 5.3. Interrupt 5.4. Ethernet Stack 5.5. Bootloader 5.6. Data and Instruction Cache 5.7. Tightly Coupled Memory 5.8. Custom Instructions 5.9. Error Correction Code 5.10. Intel® HAL Settings 5.11. Micrium MicroC/OS-II BSP Settings 5.12. Software Packages
5.1. Migrating Nios® II Processor to Nios® V Processor x
5.1.1. Processor IP Instantiation in Platform Designer 5.1.2. Migrating Nios® II/e Processor to Nios® V/c Processor 5.1.3. Migrating Nios® II Processor to Nios® V/m Processor 5.1.4. Migrating Nios® II/f Processor to Nios® V/g Processor
5.1.2. Migrating Nios® II/e Processor to Nios® V/c Processor x
5.1.2.1. Nios® V Processor Hardware Migration 5.1.2.2. Nios® V Processor Software Migration
5.1.2.1. Nios® V Processor Hardware Migration x
5.1.2.1.1. Signal and Interface Mapping 5.1.2.1.2. IP Parameter Configuration 5.1.2.1.3. BSP Project Generation
5.1.2.2. Nios® V Processor Software Migration x
5.1.2.2.1. Command-Line Build Flow 5.1.2.2.2. IDE Build Flow
5.1.3. Migrating Nios® II Processor to Nios® V/m Processor x
5.1.3.1. Nios® V Processor Hardware Migration 5.1.3.2. Nios® V Processor Software Migration
5.1.3.1. Nios® V Processor Hardware Migration x
5.1.3.1.1. Signal and Interface Mapping 5.1.3.1.2. IP Parameter Configuration 5.1.3.1.3. BSP Project Generation
5.1.3.2. Nios® V Processor Software Migration x
5.1.3.2.1. Command-Line Build Flow 5.1.3.2.2. IDE Build Flow
5.1.4. Migrating Nios® II/f Processor to Nios® V/g Processor x
5.1.4.1. Nios® V Processor Hardware Migration 5.1.4.2. Nios® V Processor Software Migration
5.1.4.1. Nios® V Processor Hardware Migration x
5.1.4.1.1. Signal and Interface Mapping 5.1.4.1.2. IP Parameter Configuration 5.1.4.1.3. BSP Project Generation
5.1.4.2. Nios® V Processor Software Migration x
5.1.4.2.1. Command-Line Build Flow 5.1.4.2.2. IDE Build Flow
1. Overview
2. Architecture Comparison
3. Processor Core Migration Mapping
4. Design Flow Comparison
5. Migration by Use Case
6. Document Revision History for AN 978: Nios® V Processor Migration Guidelines

5.6. Data and Instruction Cache

Nios® II/f and Nios® V/g processors support cache.

Table 29.  Cache Comparison Between Nios® V and Nios® II Processors
Cache Nios® V/g Processor Nios® II/f Processor
Instruction Cache
  • 1KB 3
  • 2KB
  • 4KB
  • 8KB
  • 16KB
  • 04
  • 512B
  • 1KB
  • 2KB
  • 4KB
  • 8KB
  • 16KB
  • 32KB
  • 64KB
Data Cache
  • 1KB
  • 2KB
  • 4KB
  • 8KB
  • 16KB
  • 0
  • 512B
  • 1KB
  • 2KB
  • 4KB
  • 8KB
  • 16KB
  • 32KB
  • 64KB
Cache Bypass Method Peripheral Regions
  • Bit-31 cache bypass
  • Cache bypass instructions
  • Peripheral Regions
The processors use the peripheral regions to defined non-cacheable transaction for peripherals such as UART, PIO, DMA, and others. Both Nios® II/f and Nios® V/g processors support peripheral regions. Nios® V/g processor supports two separate peripheral regions, and Nios® II/f processor supports only one.
  • For Nios® II/f processor (with caches enabled), it is optional to use a peripheral region when using peripherals.
  • For Nios® V/g processor, you must place your peripherals in a peripheral region. Failure to do so can cause the processor system to malfunction.

If you do not define the peripherals regions, Platform Designer prompts the following warning message:

No peripheral regions have been defined. If your design contains any peripherals such as UART, PIO, DMA, etc, they must be placed within a peripheral region.

3 Nios® V/g processor requires a minimum allocation of 1KB cache size.
4 You can disable the cache in the Nios® II/f processor.
Level Two Title