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 32 and Version 33 of crkit/Software/Firmware/Framework/R3_arch


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

--

Legend:

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

    v32 v33  
    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. 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).   
     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.
     52
     53Each 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).   
    5254
    5355__Table 1 - R3 Global Memory Map__