
HMS30C7202N
2004 MagnaChip Semiconductor Ltd. All Rights Reserved. Version 1.1
- 42 -
bus select the device to be initialized, as described in Table 6-3.
A25
Device selected
0
Device 0
1
Device 1
Table 6-3 SDRAM Device Selection
6.5
AMBA Accesses and Arbitration
The SDRAM controller bridges both the AMBA Main and Video buses. On the Main bus, the SDRAM appears
as a normal slave device. On the Video DMA bus, the SDRAM controller integrates the functions of the bus
arbiter and address decoder. Writes from the main bus may be merged in the quad word merging write buffer.
A Main/Video arbiter according to the following sequence arbitrates access requests from either the Main or
Video buses:
Highest Priority: LCD
Refresh request
Lowest Priority: Main bus peripheral (PMU, ARM, DMA)--order determined by Main bus arbiter.
Video SDRAM accesses always occur in bursts of 16 words. Once a burst has started, the SDRAM controller
provides data without wait states. Video data is only read from SDRAM, no write path is supported.
If a refresh cycle is requested, then it will have lower priority than the Video bus, but will be higher than any
other accesses from the Main bus. Assuming a worst-case BCLK frequency of 8MHz, the maximum, worst-
case latency that the arbitration scheme enforces is 11.5us before a refresh cycle can take place. This is
comfortably within the 16us limit. Note that the 2 external SDRAM devices are refreshed on 2 consecutive
clock cycles to reduce the peak current demand on the power source.
The arbitration of the Main bus is left to the Main bus arbiter. Data transfers requested from the Main bus
always occur as a burst of eight half-word accesses to SDRAM. The Main bus arbiter cannot break into
access requests from the Main bus. In the case where fewer than four words are actually requested by the
Main bus peripheral, the excess data from the SDRAM is ignored by the SDRAM controller in the case of read
operations, or masked in the case of writes. In the case where more than four words are actually requested by
the Main bus peripheral, the SDRAM controller asserts BLAST to force the ASB decoder to break the burst.
In the case of word/half-word/byte misalignment to a quad word boundary (when any of address bits [3:0] are
non-zero at the start of the transfer), BLAST is asserted at the next quad word boundary (bits 3, 2, 1 and 0
properly set 1 for each type) to force the ASB decoder to break the burst.
Sequential half word (or byte) reads are supported and the controller asserting BLAST at quad word boundary.
In the case of byte or half word reads, data is replicated across the whole of the ASB data bus.
Data bus for word access:
31 23 15 7 0
d31 d30 d29 d28 d27 d26 d25 d24 d23 d22 d21 d20 d19 d18 d17 d16 d15 d14 d13 d12 d11 d10 d9 d8 d7 d6 d5 d4 d3 d2 d1 d0
Data bus for half word access:
31 23 15 7 0
d15 d14 d13 d12 d11 d10 d9 d8 d7 d6 d5 d4 d3 d2 d1 d0 d15 d14 d13 d12 d11 d10 d9 d8 d7 d6 d5 d4 d3 d2 d1 d0
Data bus for byte access:
31 23 15 7 0
d7 d6 d5 d4 d3 d2 d1 d0 d7 d6 d5 d4 d3 d2 d1 d0 d7 d6 d5 d4 d3 d2 d1 d0 d7 d6 d5 d4 d3 d2 d1 d0
6.6
Merging Write Buffer
An eight word merging Write-Buffer is implemented in the SDRAM controller to improve write performance.
The write buffer can be disabled, but its operation is completely transparent to the programmer. The eight
words of the buffer are split into two quad words, the same size as all data transactions to the SDRAMs. The
split into two quad words allows one quad word to be written to at the same time as the contents of the other