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 2 and Version 3 of Software/Firmware/Framework/R3_arch/outline/mem_map


Ignore:
Timestamp:
Jun 18, 2010, 5:58:42 PM (12 years ago)
Author:
khanhle
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Software/Firmware/Framework/R3_arch/outline/mem_map

    v2 v3  
    11== Memory Map ==
    22
    3 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.
     3R3 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 1. Each address range gets its own chip select.
    44
    55For 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 Common Control RMAP real address == RMAP offset + 0x10000000 (base).   
     
    2121
    2222
    23 __Figure 2 - R3 Address Decoding__
     23__Figure 1 - R3 Address Decoding__
    2424[[BR]][[BR]]
    2525[[Image(r3_addr_dec.jpg)]]