EasyManuals Logo

Xilinx MicroBlaze Reference Guide

Xilinx MicroBlaze
316 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #132 background imageLoading...
Page #132 background image
MicroBlaze Processor Reference Guide 132
UG984 (v2018.2) June 21, 2018 www.xilinx.com
Chapter 2: MicroBlaze Architecture
Data and Instruction Address Extension
MicroBlaze has the ability to address up to 16EB of data controlled by the parameter
C_ADDR_SIZE, and also supports a physical instruction address up to 16EB when the MMU
Physical Address Extension (PAE) is enabled by setting
C_USE_MMU = 3 (Virtual).
The parameter C_ADDR_SIZE can be set to the following values:
There are a number of software limitations with extended addressing:
The GNU tools only generate ELF files with 32-bit addresses, which means that program
instruction and data memory must be located in the first 4GB of the address space. This
is also the reason the instruction address space does not provide an extended address
unless PAE is enabled.
With PAE enabled, the majority of the program instruction and data can be located at
any physical address, but all software running in real mode must be located in the first
4GB of the address space. The MMU UTLB must also be initialized to set up the virtual
to physical address translation by software running in real mode, before virtual mode is
activated.
Because all software drivers use address pointers that are 32-bit unsigned integers, it is
not possible to access physical extended addresses above 4GB without modifying the
driver code, and consequently all AXI peripherals should be located in the first 4GB of
the address space.
With PAE enabled, AXI peripherals can be located at any physical address, provided that
the virtual address remains in the first 4GB of the address space.
The extended address is only treated as a physical address, and the MMU cannot be
used to translate from an extended virtual address to a physical address.
This also means that without PAE support, Linux can only use the data address extension
through a dedicated driver operating in real mode.
°
NONE 4 * 1024
3
bytes 32-bit address, no extended address instructions or PAE
°
64GB 64 * 1024
3
bytes 36-bit address
°
1TB 1024
4
bytes 40-bit address
°
16TB 16 * 1024
4
bytes 44-bit address
°
256TB 256 * 1024
4
bytes 48-bit address
°
4PB 4 * 1024
5
bytes 52-bit address
°
16EB 16 * 1024
6
bytes 64-bit address
Send Feedback

Table of Contents

Other manuals for Xilinx MicroBlaze

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Xilinx MicroBlaze and is the answer not in the manual?

Xilinx MicroBlaze Specifications

General IconGeneral
Architecture32-bit RISC
CacheConfigurable Instruction and Data Cache
CategorySoft Processor Core
Data Width32-bit
Memory Management Unit (MMU)Optional
Floating Point Unit (FPU)Optional
Interrupt ControllerConfigurable
Memory ManagementOptional MMU
ConfigurabilityHighly Configurable
Pipeline Stages3-stage
FPGA IntegrationXilinx FPGAs
Bus InterfacePLB
Debug InterfaceJTAG
Typical Clock SpeedVaries depending on FPGA and configuration (e.g., 100-400+ MHz)
ImplementationSoft core (synthesized logic)
Maximum PerformanceVaries with FPGA and configuration
Debug SupportIntegrated Debug Module

Related product manuals