e200z1 Core (Z1)
MPC5510 Microcontroller Family Reference Manual, Rev. 1
Freescale Semiconductor
10-13
Preliminary
10.3.3
e200z1 Core Complex Features Not Supported on the MPC5510
The MPC5510 implements a subset of the e200z1 core complex features. The e200z1 core complex
features that are not supported in the MPC5510 are described in
.
10.4
e200z1 Memory Management Unit
The e200z1 Memory Management Unit is a 32-bit Power Architecture Book E compliant implementation,
with the following feature set:
•
EIS MMU architecture compliant
•
Translates from 32-bit effective to 32-bit real addresses
•
8-entry fully associative TLB with support for eleven page sizes (4K, 16K, 64K, 256K, 1M, 4M,
16M, 64M, 256M, 1G, 4G)
•
Hardware assist for TLB miss exceptions
•
Software managed by
tlbre
,
tlbwe
,
tlbsx
,
tlbsync
, and
tlbivax
instructions
10.4.1
Effective to Real Address Translation
10.4.1.1
Effective Addresses
Instruction accesses are generated by sequential instruction fetches or due to a change in program flow
(branches and interrupts). Data accesses are generated by load, store, and cache management instructions.
The e200 instruction fetch, branch, and load/store units generate 32-bit effective addresses. The MMU
translates this effective address to a 32-bit real address which is then used for memory accesses.
The Power Architecture Book E architecture divides the effective (virtual) and real (physical) address
space into pages. The page represents the granularity of effective address translation, permission control,
and memory/cache attributes. The MMU supports eleven page sizes (4 KB, 16 KB, 64 KB, 256 KB,
1 MB, 4 MB, 16 MB, 64 MB, 256 MB, 1GB, 4GB). In order for an effective to real address translation to
exist, a valid entry for the page containing the effective address must be in a Translation Lookaside Buffer
(TLB). Addresses for which no TLB entry exists (a TLB miss) cause Instruction or Data TLB Errors.
Table 10-2. e200z1 Features Not Supported on the MPC5510 Family
Description
Function/Category
The less significant halfword of the Processor Version Register (PVR) provides the revision
level which is comprised of the following three bit fields:
Reserved = 0x00
Revision = 0x0
ID = 0x0
The more significant halfword of the Processor Version Register (PVR) provides the
processor type and version number (see
PVR Value
Nexus registers are not accessible by code running in User or Supervisor mode. Nexus
registers can be accessed only by external tools via the Nexus port.
Debug