6.9.1.2.1 Configuration Register (CONFIG)
The Configuration Register (CONFIG) contains the configuration value of the MPU. CONFIG is shown in Figure 6-19 and described in Table 6-42.
Figure 6-19 Configuration Register (CONFIG)
|
|
31 |
|
24 |
23 |
20 |
19 |
16 |
15 |
12 |
11 |
1 |
0 |
|
|
ADDR_WIDTH |
NUM_FIXED |
NUM_PROG |
NUM_AIDS |
Reserved |
ASSUME_ALLOWED |
Reset Values |
MPU0 |
R-0 |
R-0 |
R-16 |
R-16 |
R-0 |
R-1 |
MPU1 |
R-0 |
R-0 |
R-5 |
R-16 |
R-0 |
R-1 |
MPU2 |
R-0 |
R-0 |
R-16 |
R-16 |
R-0 |
R-1 |
MPU3 |
R-0 |
R-0 |
R-1 |
R-16 |
R-0 |
R-1 |
MPU4 |
R-0 |
R-0 |
R-16 |
R-16 |
R-0 |
R-1 |
Legend: R = Read only; -n = value after reset |
Table 6-42 Configuration Register (CONFIG) Field Descriptions
BIT |
FIELD |
DESCRIPTION |
31 – 24 |
ADDR_WIDTH |
Address alignment for range checking
- 0 = 1KB alignment
- 6 = 64KB alignment
|
23 – 20 |
NUM_FIXED |
Number of fixed address ranges |
19 – 16 |
NUM_PROG |
Number of programmable address ranges |
15 – 12 |
NUM_AIDS |
Number of supported AIDs |
11 – 1 |
Reserved |
Reserved. These bits will always reads as 0. |
0 |
ASSUME_ALLOWED |
Assume allowed bit. When an address is not covered by any MPU protection range, this bit determines whether the transfer is assumed to be allowed or not.
- 0 = Assume disallowed
- 1 = Assume allowed
|