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.

Changes between Version 30 and Version 31 of crkit/Software/Firmware/Framework/R3_arch


Ignore:
Timestamp:
Jun 17, 2010, 4:12:00 AM (12 years ago)
Author:
khanhle
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • crkit/Software/Firmware/Framework/R3_arch

    v30 v31  
    4949=== Global Memory Map ===
    5050
    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.
     51R3 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. 
    5252
    5353__Table 1 - R3 Global Memory Map__
    5454||'''Instance'''      ||'''Base Address'''||'''Size'''  ||'''Description'''||
    5555||''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||
    5757||''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||
    5858||''Timing Control''  ||0x10020000-0x1002FFFC||65K      ||address range for timing controller||