Functional Overview
Block
Start Address
On-Chip Memory
Data Space
Prog Space
0x00 0000
M0 Vector − RAM (32 × 32)
(Enabled if VMAP = 0)
0x00 0040
0x00 0400
M0 SARAM (1K × 16)
M1 SARAM (1K × 16)
0x00 0800
0x00 0D00
Peripheral Frame 0
(2K × 16)
PIE Vector - RAM
(256 × 16)
Reserved
(Enabled if VMAP
= 1, ENPIE = 1)
0x00 0E00
0x00 2000
Reserved
Reserved
0x00 6000
0x00 7000
Peripheral Frame 1
(4K × 16, Protected)
Reserved
Peripheral Frame 2
(4K × 16, Protected)
0x00 8000
0x00 9000
0x00 A000
L0 SARAM (4K × 16, Secure Block)
L1 SARAM (4K × 16, Secure Block)
Reserved
0x3D 7800
OTP (or ROM) (1K × 16, Secure Block)
0x3D 7C00
0x3D 8000
0x3F 7FF8
Reserved (1K)
Flash (or ROM) (128K × 16, Secure Block)
128-Bit Password
0x3F 8000
0x3F A000
H0 SARAM (8K × 16)
Reserved
0x3F F000
0x3F FFC0
Boot ROM (4K × 16)
(Enabled if MP/MC = 0)
BROM Vector - ROM (32 × 32)
(Enabled if VMAP = 1, MP/MC = 0, ENPIE = 0)
LEGEND:
Only one of these vector maps—M0 vector, PIE vector, BROM vector, XINTF vector—should be enabled at a time.
NOTES: A. Memory blocks are not to scale.
B. Reserved locations are reserved for future expansion. Application should not access these areas.
C. Peripheral Frame 0, Peripheral Frame 1, and Peripheral Frame 2 memory maps are restricted to data memory only. User program
cannot access these memory maps in program space.
D. “Protected” means the order of Write followed by Read operations is preserved rather than the pipeline order.
E. Certain memory ranges are EALLOW protected against spurious writes after configuration.
Figure 3−3. F2811/C2811 Memory Map (See Notes A through E)
30
SPRS174L
April 2001 − Revised December 2004