close
Warning:
Can't synchronize with repository "(default)" (/common/SVN/crkit does not appear to be a Subversion repository.). Look in the Trac log for more information.
- Timestamp:
-
Jun 17, 2010, 4:15:06 AM (13 years ago)
- Author:
-
khanhle
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v31
|
v32
|
|
| 49 | 49 | === Global Memory Map === |
| 50 | 50 | |
| 51 | | R3 global memory map is divided into multiple regions as shown in Table 1. The total number of address bits are 32-bit, but we will only use the lower 16-bits per region e.g. 65Kbytes per region. Therefore, bit31-28 are used for region address decoding between the individual regions as illustrated in figure 2. Each address range gets its own chip select. For detailed definition for each RMAP, click on provided links under ''Instance'' column in Table 1. Note that the RMAP addresses are offsets, and must be added to Base addresses to get the correct address pointer to RMAP register. |
| | 51 | R3 global memory map is divided into multiple regions as shown in Table 1. The total number of address bits are 32-bit, but we will only use the lower 16-bits per region e.g. 65Kbytes per region. Therefore, bit31-28 are used for region address decoding between the individual regions as illustrated in figure 2. Each address range gets its own chip select. For detailed definition for each RMAP, click on provided links under ''Instance'' column in Table 1. Note that the RMAP addresses are given as offsets, and must be added to Base address to get the correct address pointer to RMAP register. Example - Common control base address == 0x10000000, hence RMAP real address == RMAP offset + 0x10000000 (base). |
| 52 | 52 | |
| 53 | 53 | __Table 1 - R3 Global Memory Map__ |
