What is the Arm memory map, and what are "DRAM holes"?
Short answer: Arm systems follow a recommended physical address map so that software and SoC designs are consistent: low addresses for boot ROM/flash and on-chip memory, a region for peripherals, and DRAM above that. Because the 32-bit address space (4 GB) is shared with peripherals, a system with lots of DRAM cannot place it all below 4 GB; the parts of the DRAM that would collide with peripheral space are remapped to higher addresses (above 4 GB, in the 36-bit and 40-bit extensions of the map). The gaps this leaves in the DRAM address ranges are the "DRAM holes".
Cortex-M fixed memory map (Armv7-M/v8-M)
| Range | Region | Typical content |
|---|---|---|
0x0000_0000–0x1FFF_FFFF |
Code | flash, boot ROM, ITCM |
0x2000_0000–0x3FFF_FFFF |
SRAM | on-chip RAM (bit-band region on M3/M4) |
0x4000_0000–0x5FFF_FFFF |
Peripheral | on-chip peripherals |
0x6000_0000–0x9FFF_FFFF |
External RAM | FMC/SDRAM |
0xA000_0000–0xDFFF_FFFF |
External device | |
0xE000_0000–0xFFFF_FFFF |
System | NVIC, SCB, SysTick, MPU, debug (PPB) |
Because the map is fixed, every Cortex-M part has the NVIC at 0xE000E100, the same SysTick address, and default memory attributes (e.g. the peripheral region is Device memory, execute-never).
Cortex-A systems (Arm's "Principles of Arm Memory Maps")
- The first 4 GB (32-bit) contains boot ROM, on-chip RAM, peripherals and the first 2 GB of DRAM (often from
0x8000_0000). - The 36-bit and 40-bit maps repeat the same structure, with large DRAM windows above 4 GB (e.g. starting at
0x8_8000_0000) and peripheral space reserved in each region. - A system with, say, 8 GB of DRAM therefore sees it as several non-contiguous ranges: 2 GB low and the remaining 6 GB high. The ranges reserved for peripherals and future use inside the DRAM windows are the holes.
Why a common map helps
- The same kernel and firmware work across SoCs with different memory sizes; devices are found from the device tree or ACPI, but DRAM placement follows predictable rules.
- 32-bit software (and 32-bit DMA masters) can still reach the low 2 GB of DRAM.
- Moving from 32-bit to 36/40-bit physical addresses (LPAE on Armv7, Armv8-A) does not force a redesign of where peripherals sit.
Practical consequences on Linux: the device tree /memory node lists several banks; DMA from 32-bit-only devices needs buffers in the low region (ZONE_DMA32) or an IOMMU/SMMU; and the kernel's memory zones reflect the holes.