CoreLink DDR2 Dynamic Memory Controller (DMC-341) Technical Reference Manual: 3.3.2. Memory Controller Command Register

3.3.2. Memory Controller Command Register

The memc_cmd Register characteristics are:

Purpose: Controls the operating state of the DDR2 DMC.
Usage constraints: Not accessible in the Reset or Power On Reset (POR) state.
Configurations: Available in all configurations of the DDR2 DMC.
Attributes: See the register summary in Table 3.1.

Figure 3.9 shows the memc_cmd Register bit assignments.

Figure 3.9. memc_cmd Register bit assignments

Table 3.3 shows the memc_cmd Register bit assignments.

Table 3.3. memc_cmd Register bit assignments

Bits Name Function

[31:3] - Undefined, write as zero.

Bits	Name	Function
[31:3]	-	Undefined, write as zero.
[2:0]	memc_cmd	Use the following commands to change the state of the DDR2 DMC: `0b000` = Go `0b001` = Sleep `0b010` = Wakeup `0b011` = Pause `0b100` = Configure `0b111` = Active_Pause. If the controller receives a command to change state and a previous command to change state has not completed then it holds pready LOW until the new command can be carried out. See Figure 2.13 for more information about the state transitions.

[2:0]

memc_cmd

Use the following commands to change the state of the DDR2 DMC:

0b000 = Go

0b001 = Sleep

0b010 = Wakeup

0b011 = Pause

0b100 = Configure

0b111 = Active_Pause.

If the controller receives a command to change state and a previous command to change state has not completed then it holds pready LOW until the new command can be carried out.

See Figure 2.13 for more information about the state transitions.

Note

Active_Pause command puts the DDR2 DMC into the Paused state without draining the arbiter queue. This enables you to move the controller to the Low_power state, to change configuration settings such as memory frequency or timing register values, without requiring co-ordination between masters in a multi-master system.
If you use the Active_Pause command to put the controller in the Low_power state then you must not remove power from the controller because this results in data loss and violation of the AXI protocol.
The controller does not issue refreshes when in the Config state. Therefore, ARM recommends that you make register updates with the controller in Low_power state because this ensures that the memory is put into self-refresh mode, rather than the Config state when the memory contains valid data.

Copyright © 2007, 2009-2010 ARM Limited. All rights reserved.	ARM DDI 0418E
Non-Confidential	ID080910
PDF version