01.08.2013 Views

Chapter 10 Memory Subsystem.pdf

Chapter 10 Memory Subsystem.pdf

Chapter 10 Memory Subsystem.pdf

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Public Version<br />

SDRAM Controller (SDRC) <strong>Subsystem</strong> www.ti.com<br />

• The out-of-band error signal generation using two out-of-band error signals<br />

Based on the fact that there is no way to prevent the debugger from generating firewall violations during<br />

debug, and that users cannot stop checking for functional violations, two out-of-band violation signals are<br />

set when:<br />

• A functional violation is detected<br />

• A debug violation is detected<br />

These signals are asserted on each error detection from a read, write, or posted write faulty access: they<br />

are deasserted when the software clears the error bit in the SMS_ERR_TYPE register.<br />

<strong>10</strong>.2.4.2 Module Power Saving<br />

Power-saving is managed through the SMS.SMS_SYSCONFIG register.<br />

The SMS_SYSCONFIG[4:3] SIDLEMODE field defines the power management strategy (force idle mode,<br />

no idle mode, or smart idle mode). See Section <strong>10</strong>.2.4.3 for more details about the system power<br />

management.<br />

By default, the internal interface clock gating strategy is enabled as the SMS_SYSCONFIG[0] AUTOIDLE<br />

bit is set to 0x1 after reset. When all FIFO queues are empty and no ongoing transactions remain, the L3<br />

interconnect clock is disabled inside the SMS thus reducing power consumption. The L3 interconnect<br />

clock can be disabled after a programmable delay defined in the SMS_POW_CTRL[7:0] IDLEDELAY bit<br />

field.<br />

When there is new activity on the interconnect interface, the interconnect clock is restarted without any<br />

latency penalty. It is recommended to enable this mode to reduce power consumption.<br />

There is an internal interface clock gating strategy within the SDRC. This power-saving feature is always<br />

active.<br />

<strong>10</strong>.2.4.3 System Power Management<br />

The SMS can be configured through the SMS.SMS_SYSCONFIG register to be in one of these idle<br />

modes:<br />

• No-idle mode (the SMS.SMS_SYSCONFIG[4:3] SIDLEMODE field is set to 0x1): The module never<br />

goes into idle state.<br />

• Force-idle mode (the SMS.SMS_SYSCONFIG[4:3] SIDLEMODE field is set to 0x0): The module goes<br />

into idle state immediately after receiving the request from the PRCM.<br />

• Smart-idle mode (the SMS.SMS_SYSCONFIG[4:3] SIDLEMODE field is set to 0x2): SidleAck is<br />

asserted once the module has confirmed there are no more outstanding transactions with the SDRC.<br />

<strong>10</strong>.2.4.4 SDRC<br />

The SDRC provides two configurable memory areas. Each supports mobile SDR SDRAM and low-power<br />

DDR SDRAM from 16 Mbits to 4 Gbits, depending on the memory organization.<br />

Flexible row/column addressing schemes are possible with 2-bank support for 16 Mbits and 32 Mbits<br />

memories, and 4-bank support for 64 Mbits, 128 Mbits, 256 Mbits, 512 Mbits, 1 Gbit, 2 Gbits, and 4 Gbits<br />

memories.<br />

Figure <strong>10</strong>-50 shows the architecture of the SDRC.<br />

2228 <strong>Memory</strong> <strong>Subsystem</strong> SPRUGN4L–May 20<strong>10</strong>–Revised June 2011<br />

Copyright © 20<strong>10</strong>–2011, Texas Instruments Incorporated

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!