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:12:00 AM (14 years ago)
- Author:
-
khanhle
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v30
|
v31
|
|
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. |
| 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. |
52 | 52 | |
53 | 53 | __Table 1 - R3 Global Memory Map__ |
54 | 54 | ||'''Instance''' ||'''Base Address'''||'''Size''' ||'''Description'''|| |
55 | 55 | ||''Reserved'' ||0x00000000-0x0FFFFFFC||- ||Future use|| |
56 | | ||''Common Control'' ||0x10000000-0x1000FFFC||65K ||Control Plane register map e.g. SPI, LEDs, and board level IO|| |
| 56 | ||''[source:/doc/trunk/architecture/R3/rmap_cmn_ctl.xls Common Control]'' ||0x10000000-0x1000FFFC||65K ||Control Plane register map e.g. SPI, LEDs, and board level IO|| |
57 | 57 | ||''Common INTC'' ||0x10010000-0x1001FFFC||65K ||Interrupt Controller map. Individual interrupt lines from all RMAPs are consolidated in a single location. Once an interrupt is set by HW, a status messaging packet is sent to Host. Host shall read the INTC status register to identify which of the RMAP regions has triggered an interrupt e.g. coarse parsing, followed by fine parsing|| |
58 | 58 | ||''Timing Control'' ||0x10020000-0x1002FFFC||65K ||address range for timing controller|| |