•L1P Memory Controller•Both EMACs (EMAC0 and EMAC1) Share
•L1D Memory Controller
•L2 Memory Controller
– Time Stamp Counter
– One 64-Bit General-Purpose/Watchdog Timer
• Shared Peripherals and Interfaces
– EDMA Controller
(64 Independent Channels)
– Shared Memory Architecture
•Shared L2 Memory Controller
•768K-Byte of RAM
•Boot ROM
– Three Telecom Serial Interface Ports (TSIPs)
•Each TSIP is 8 Links of 8 Mbps per
Direction
– 32-Bit DDR2 Memory Controller (DDR2-533
SDRAM)
•256 M-Byte x 2 Addressable Memory
Space
– Two 1x Serial RapidIO®Links,
v1.2 Compliant• Only 625-MHz Device Offered in GTZ Package
•1.25-, 2.5-, 3.125-Gbps Link Rates
•Message Passing, DirectIO Support,
Error Management Extensions, and
1
Please be aware that an important notice concerning availability, standard warranty, and use in critical applications of Texas
Instruments semiconductor products and disclaimers thereto appears at the end of this data sheet.
PRODUCT PREVIEW information concerns products in the formative
or design phase of development. Characteristic data and other
specifications are design goals. Texas Instruments reserves the right
to change or discontinue these products without notice.
The SM320C6472 devices are designed for a package temperature range of 0°C to 85°C (commercial
temperature range) or -40°C to 100°C (extended temperature range).
Extended temperature (A) range is available only on 500-MHz and 625-MHz devices.
The SM320C6472 device is a Texas Instruments next-generation fixed-point digital signal processor
(DSP) targeting high-performance computing applications, including high-end industrial, mission-critical,
high-end image and video, communication, media gateways, and remote access servers. This device was
designed with these applications in mind. A common key requirement of these applications is the
availability of large on-chip memories to handle vast amounts of data during processing. With 768K-Byte
of shared RAM and 608K-Byte local L2 RAM per C64x+ Megamodule, the SM320C6472 device can
eliminate the need for external memory, thereby reducing system power dissipation and system cost and
optimizing board density.
The SM320C6472 device has six optimized TMS320C64x+™ megamodules, which combine high
performance with the lowest power dissipation per port. The TMS320C6472 device includes three different
speeds: 500 MHz, 625 MHz, and 700 MHz. The C64x+ megamodules are the highest-performance
fixed-point DSP generation in the TMS320C6000™ DSP platform. The C64x+ megamodule is based on
the third-generation high-performance, advanced VelociTI™ very-long-instruction-word (VLIW) architecture
developed by Texas Instruments (TI), making devices like SM320C6472 an excellent choice for
applications including video and telecom infrastructure, imaging/medical, and wireless infrastructure (WI).
The C64x+™ devices are upward code-compatible from previous devices that are part of the C6000™
DSP platform.
The C64x+ megamodule core employs eight functional units, two register files, and two data paths. Like
the earlier C6000 devices, two of these eight functional units are multipliers or .M units. Each C64x+
megamodule core .M unit doubles the multiply throughput versus the C64x core by performing four
16-bit x 16-bit multiply-accumulates (MACs) every clock cycle. Thus, eight 16-bit x 16-bit MACs can be
executed every cycle on the C64x+ core. At a 500-MHz clock rate, this means 4000 16-bit MMACs can
occur every second. Moreover, each multiplier on the C64x+ megamodule core can compute one
32-bit x 32-bit MAC or four 8-bit x 8-bit MACs every clock cycle.
SM320C6472-EP
SPRS696–SEPTEMBER 2010
The C64x+ megamodule integrates a large amount of on-chip memory organized as a two-level memory
system. The level-1 (L1) program and data memories on this C64x+ megamodule are 32KB each. This
memory can be configured as mapped RAM, cache, or some combination of the two. When configured as
cache, L1 program (L1P) is a direct mapped cache where as L1 data (L1D) is a two-way set associative
cache. The level 2 (L2) memory is shared between program and data space and is 608K-Byte in size. L2
memory can also be configured as mapped RAM, cache, or some combination of the two. The C64x+
megamodule also has a 32-bit peripheral configuration (CFG) port, an internal DMA (IDMA) controller, a
system component with reset/boot control, interrupt/exception control, a power-down control, and a
free-running 32-bit timer for time stamp.
The peripheral set includes: three Telecom Serial Interface Port (TSIPs); an 16/8 bit Universal Test and
Operations PHY Interface for Asynchronous Transfer Mode (ATM) Slave [UTOPIA Slave] port; two
10/100/1000 Ethernet media access controllers (EMACs), which provide an efficient interface between the
C6472 DSP core processor and the network; a management data input/output (MDIO) module (shared by
both EMACs) that continuously polls all 32 MDIO addresses in order to enumerate all PHY devices in the
system; a Serial RapidIO®with two 1x lanes and support for packet forwarding; a 32-bit DDR2 SDRAM
interface; 12 64-bit general-purpose timers; an inter-integrated circuit bus module (I2C); 16
general-purpose input/output ports (GPIO) with programmable interrupt/event generation modes; and a
16-bit multiplexed host-port interface (HPI16).
The C6472 device has a complete set of development tools which includes: a C compiler, an assembly
optimizer to simplify programming and scheduling, and a Windows®debugger interface for visibility into
source code execution.
Table 2-1. Characteristics of the C6472 Processor (continued)
HARDWARE FEATURESC6472
Product Status
Device Part NumbersSM320C6472
(1) PRODUCT PREVIEW information concerns products in the formative or design phase of development. Characteristic data and other
specifications are design goals. Texas Instruments reserves the right to change or discontinue these products without notice.
(1)
Product Preview (PP), Advance Information (AI),
or Production Data (PD)
(For more details on the C64x+™ DSP part
numbering, see Figure 2-13)
2.2CPU (DSP Core) Description
The C64x+ Central Processing Unit (CPU) consists of eight functional units, two register files, and two
data paths as shown in Figure 2-1. The two general-purpose register files (A and B) each contain
32 32-bit registers for a total of 64 registers. The general-purpose registers can be used for data or can be
data address pointers. The data types supported include packed 8-bit data, packed 16-bit data, 32-bit
data, 40-bit data, and 64-bit data. Values larger than 32 bits, such as 40-bit-long or 64-bit-long values are
stored in register pairs, with the 32 LSBs of data placed in an even register and the remaining 8 or
32 MSBs in the next upper register (which is always an odd-numbered register).
The eight functional units (.M1, .L1, .D1, .S1, .M2, .L2, .D2, and .S2) are each capable of executing one
instruction every clock cycle. The .M functional units perform all multiply operations. The .S and .L units
perform a general set of arithmetic, logical, and branch functions. The .D units primarily load data from
memory to the register file and store results from the register file into memory.
SPRS696–SEPTEMBER 2010
PP
The C64x+ CPU extends the performance of the C64x core through enhancements and new features.
Each C64x+ .M unit can perform one of the following each clock cycle: one 32 x 32 bit multiply, two
16 x 16 bit multiplies, two 16 x 32 bit multiplies, four 8 x 8 bit multiplies, four 8 x 8 bit multiplies with add
operations, and four 16 x 16 multiplies with add/subtract capabilities (including a complex multiply). There
is also support for Galois field multiplication for 8-bit and 32-bit data. Many communications algorithms
such as FFTs and modems require complex multiplication. The complex multiply (CMPY) instruction takes
four 16-bit inputs and produces a 32-bit real and a 32-bit imaginary output. There are also complex
multiplies with rounding capability that produce one 32-bit packed output that contains 16-bit real and
16-bit imaginary values. The 32 x 32 bit multiply instructions provide the extended precision necessary for
audio and other high-precision algorithms on a variety of signed and unsigned 32-bit data types.
The .L or Arithmetic Logic Unit now incorporates the ability to do parallel add/subtract operations on a pair
of common inputs. Versions of this instruction exist to work on 32-bit data or on pairs of 16-bit data
performing dual 16-bit add and subtracts in parallel. There are also saturated forms of these instructions.
The C64x+ core enhances the .S unit in several ways. In the C64x core, dual 16-bit MIN2 and MAX2
comparisons were only available on the .L units. On the C64x+ core they are also available on the .S unit
which increases the performance of algorithms that do searching and sorting. Finally, to increase data
packing and unpacking throughput, the .S unit allows sustained high performance for the quad 8-bit/16-bit
and dual 16-bit instructions. Unpack instructions prepare 8-bit data for parallel 16-bit operations. Pack
instructions return parallel results to output precision including saturation support.
Other new features include:
•SPLOOP - A small instruction buffer in the CPU that aids in creation of software pipelining loops where
multiple iterations of a loop are executed in parallel. The SPLOOP buffer reduces the code size
associated with software pipelining. Furthermore, loops in the SPLOOP buffer are fully interruptible.
•Compact Instructions - The native instruction size for the C6000 devices is 32 bits. Many common
instructions such as MPY, AND, OR, ADD, and SUB can be expressed as 16 bits if the C64x+
compiler can restrict the code to use certain registers in the register file. This compression is
performed by the code generation tools.
•Instruction Set Enhancements - As noted above, there are new instructions such as 32-bit
multiplications, complex multiplications, packing, sorting, bit manipulation, and 32-bit Galois field
multiplication.
•Exception Handling - Intended to aid the programmer in isolating bugs. The C64x+ CPU is able to
detect and respond to exceptions, both from internally detected sources (such as illegal op-codes) and
from system events (such as a watchdog time expiration).
•Privilege - Defines user and supervisor modes of operation, allowing the operating system to give a
basic level of protection to sensitive resources. Local memory is divided into multiple pages, each with
read, write, and execute permissions.
•Time-Stamp Counter - Primarily targeted for Real-Time Operating System (RTOS) robustness, a
free-running time-stamp counter is implemented in the CPU which is not sensitive to system stalls.
For more details on the C64x+ CPU and its enhancements over the C64x architecture, see the following
documents:
•SM320C64x/C64x+ DSP CPU and Instruction Set Reference Guide (literature number SPRU732)
•SM320C64x+ DSP Cache User's Guide (literature number SPRU862)
•SM320C64x+ DSP Megamodule Reference Guide (literature number SPRU871)
•SM320C64x Technical Overview (literature number SPRU395)
•SM320C64x to SM320C64x+ CPU Migration Guide (literature number SPRAA84)
A.On .M unit, dst2 is 32 MSB.
B.On .M unit, dst1 is 32 LSB.
C. On C64x CPU .M unit, src2 is 32 bits; on C64x+ CPU .M unit, src2 is 64 bits.
D. On .L and .S units, odd dst connects to odd register files and even dst connects to even register files.
Table 2-2 shows the memory map address ranges of the C6472 device. This table provides a combined
view of both local and global addresses. The C64x+ megamodule local memories have both local and
global addresses. The megamodule registers only have local addresses. Local addresses can only be
resolved within the megamodule. They cannot be accessed from outside the megamodule. All of the other
addresses listed in this table are global addresses. Global addresses can be accessed from any bus
master including all six C64x+ megamodules, the transfer controllers within the EDMA3 block, and any
peripheral that can master the bus.
Note: 1K = 1024, 1M = 1024K.
MEMORY BLOCK DESCRIPTIONBLOCK SIZE (BYTES)HEX ADDRESS RANGE
The boot sequence is a process by which the DSP's internal memory is loaded with program and data
sections and the DSP's internal registers are programmed with predetermined values. The boot sequence
is started automatically after each power-on, warm, and system reset. For more details on the initiators of
these resets, see Section 7.7, Reset Controller.
SPRS696–SEPTEMBER 2010
There are several methods by which the memory and register initialization can take place. Each of these
methods is referred to as a boot mode. The boot mode to be used is selected at reset through the
BOOTMODE[3:0] pins.
2.4.1Boot Modes Supported
The SM320C6472 has a dedicated Boot Controller, which is responsible for managing the boot process
for single and multiple C64x+ megamodule core boots. There are two types of resets on the C6472
device:
1. Device-level Resets (Global Resets)
– Power-on Reset; initiated by POR
– Chip-level Warm Reset (or Device Reset); initiated by RESET
– System Reset; initiated by a watchdog timeout or emulation
– Local reset of the C64x+ megamodule initiated by on-chip Reset Controller
– Power Sleep Controller initiated by local C64x+ megamodule reset
After POR and RESET asserted resets, the boot controller selects the boot mode based on the status of
BOOTMODE[3:0] pins. When a system reset occurs, the boot mode used is determined by the
BOOTMODE field in the DEVSTAT register. All possible bootmodes are listed in Table 2-3. For a detailed
explanation of this operation, see the SM320C645x/C647x Bootloader User's Guide (literature number
SPRUEC6).
Following a device-level reset, each C64x+ megamodule core can set its boot mode choice for
subsequent local resets using the registers BOOTMODE0 through BOOTMODE5 to either immediate boot
mode or host boot mode. The default values of these registers are set to immediate boot mode.
•Immediate boot
When immediate boot is selected after global reset, the C64x+ megamodule core executes directly
from the internal L2 SRAM address programmed in the DSP_BOOT_ADDRx register. Note: device
operation is undefined if invalid code is address programmed in the DSP_BOOT_ADDRx register.
Executing invalid code may prevent connection by an emulator.
The default start addresses for megamodule core 0-5 boot are listed in Table 2-4.
Megamodule0x0080_00000x0010_00000x0010_0000, if the device
Core 0reset was boot mode 2-15;
Megamodule0x0080_00000x0080_00000x0080_0000
Core 1
Megamodule0x0080_00000x0080_00000x0080_0000
Core 2
Megamodule0x0080_00000x0080_00000x0080_0000
Core 3
Megamodule0x0080_00000x0080_00000x0080_0000
Core 4
Megamodule0x0080_00000x0080_00000x0080_0000
Core 5
For boot mode 1, these addresses can be modifed by the host before it releases each megamodule
core from reset; for details, see Section 3.9.5. For boot mode 2-15, it is possible to have megamodule
core 0 modify the default address of megamodule core 1-5 before it releases each megamodule core
from reset; for details, see Section 2.4.1. For local reset, if all cores are required to begin from a
particular address, the default addresses have to be modified. One example is that only the
megamodule core 0's default address is modified to match megamodule core 1-5.
•Host boot
If host boot is selected after global reset, all C64x+ megamodule cores are internally "held in reset"
while the remainder of the device (including all memory subsystems of the C64x+ megamodule) is
released from reset. During this period, an external host can initialize the C6472 device memory space
(shared memory as well as the C64x+ megamodule memory), as necessary through an HPI interface,
including internal configuration registers such as those that control the DDR2 or other peripherals.
Once the host is finished with all necessary initialization, it must write a 1 to bit fields BC0 through BC5
of the BOOT_COMPLETE_STAT register (inside the Boot Controller) indicating boot complete of the
corresponding C64x+ megamodule. This transition causes the Boot Controller to bring the C64x+
megamodule core out of the "held-in-reset" state. The CPU then begins execution from the internal L2
SRAM address programmed in the DSP_BOOT_ADDRx register. All memory may be written to and
read by the host. This allows for the host to verify what it sends to the DSP, if required.
For the C6472 device, only the Host Port Interface (HPI) peripheral can be used for host boot. PLL1,
which provides CPU/6 clock to the HPI module, will initially be running in bypass mode. Therefore, the
HPI interface will be very slow and HRDY must be observed. Initial HPI accesses can configure PLL1
for full-speed operation to make HPI accesses shorter.
•Master I2C boot
After global reset, the C64x+ megamodule core 0 comes out of RESET and starts executing the
shared ROM code from the address provided by the Boot Controller based on the I2C boot mode
selection. Then C64x+ megamodule core 0 configures I2C and acts as a master to the I2C bus and
copies data from an I2C EPROM or a device acting as an I2C slave to the DSP using a predefined
boot table format. The destination address and length are contained within the boot table. After
initializing the on-chip memory to the known state and initializing the start address of the other C64x+
megamodule cores, C64x+ megamodule core 0 brings the other cores out of reset by writing a 1 to bit
fields BC1 through BC5 of the BOOT_COMPLETE_STAT register. After this, C64x+ megamodule
cores 1 through 5 start executing from the start address provided by C64x+ megamodule core 0.
•Slave I2C boot
A Slave I2C boot is also implemented, which programs the DSP as an I2C slave. A DSP in I2C slave
mode will never transmit on the I2C bus. The slave DSP must first receive a three-word transmission
from the master. This transmission includes a 16-bit length field (length is in bytes, should be 6 for this
block), a 16-bit checksum field for which a value of zero means ignore the checksum, and the 16-bit
options field described in the boot parameter table for standard I2C boot. This option field informs the
slave what information is contained in the next data blocks. Typically, the option field is set to 1 to
indicate boot tables will be received next. Only core 0 is active during the boot process. Using the
slave I2C boot, a single DSP or device acting as an I2C master can simultaneously boot multiple slave
DSPs connected to the same I2C bus. Note that the master DSP may require booting via an I2C
EEPROM before acting as a master and booting other DSPs.
•Ethernet MAC boot
When BOOTMODE [3:0] = 1001 is selected, Ethernet MAC boot is initiated on EMAC0 with the mode
specified by the MACSEL0[2:0] pins. Alternately, when BOOTMODE [3:0] = 1010 is selected, Ethernet
MAC boot is initiated on EMAC1 with the mode specified by the MACSEL1[1:0] pins.
After reset, the C64x+ megamodule core 0 comes out of RESET and starts executing the shared ROM
code from the address provided by the Boot Controller based on the Ethernet boot mode selection
(1001b or 1010b). The C64x+ megamodule core 0 configures the appropriate Ethernet MAC and
brings the code image into the on-chip memory via the protocol defined. After initializing the on-chip
memory to the known state and initializing the start address of the other C64x+ megamodule cores (1
through 5), C64x+ megamodule core 0 brings the other cores out of reset by writing a 1 to bit fields
BC1 through BC5 of the BOOT_COMPLETE_STAT register. After this, C64x+ megamodule cores 1
through 5 start executing from the start address provided by C64x+ megamodule core 0.
•Serial RapidIO boot
After reset, the C64x+ megamodule core 0 comes out of RESET and starts executing the shared ROM
code from the address provided by the Boot Controller based on the Serial RapidIO boot mode
selection (1011b, 1100b, 1101b, or 1110b). The C64x+ megamodule core 0 configures Serial RapidIO
and EDMA, if required, and brings the code image into the on-chip memory via the protocol defined by
the boot method (SRIO bootloader). After initializing the on-chip memory to the known state and
initializing the start address of the other C64x+ megamodule cores (1 through 5), C64x+ megamodule
core 0 brings the other cores out of reset by writing a 1 to bit fields BC1 through BC5 of the
BOOT_COMPLETE_STAT register. After this, the C64x+ megamodule cores 1 through 5 start
executing from the start address provided by C64x+ megamodule core 0.
After local resets, the C6472 device supports two boot modes via BOOTMODE0-BOOTMODE5
device-level registers:
•Immediate boot
•Host boot
SM320C6472-EP
SPRS696–SEPTEMBER 2010
After reset, the C64x+ megamodule core 0 comes out of RESET and starts executing the shared ROM
code from the address provided by the Boot Controller based on the UTOPIA boot mode selection
(0101b, 0110b, 0111b, 1000b). The C64x+ megamodule core 0 configures the UTOPIA and brings the
code image into the on-chip memory via the protocol defined. After initializing the on-chip memory to
the known state and initializing the start address of the other C64x+ megamodule cores (1 through 5),
C64x+ megamodule core 0 brings the other cores out of reset by writing a 1 to bit fields ofBC1 through
BC5 the BOOT_COMPLETE_STAT register. After this, C64x+ megamodule cores 1 through 5 start
executing from the start address provided by C64x+ megamodule core 0.
When immediate boot is selected after global reset, the C64x+ megamodule core (x) executes directly
from the internal L2 SRAM address programmed in the DSP_BOOT_ADDRx register upon being given
a local reset. Note: device operation is undefined if invalid code is address programmed in the
DSP_BOOT_ADDRx register. Executing invalid code may prevent connection by an emulator.
If host boot is selected after global reset, the C64x+ megamodule core (x) is internally "held in reset"
while the remainder of the C64x+ megamodule is released from reset upon being given a local reset.
During this period, an external host can initialize the C64x+ megamodule (x) memory space, as
necessary, through an HPI interface. Once the host is finished with all necessary initialization, it must
write a 1 to the corresponding bit field BCx of the BOOT_COMPLETE_STAT register (inside the Boot
Controller) indicating boot complete of the corresponding C64x+ megamodule. This transition causes
the Boot Controller to bring the C64x+ megamodule core out of the "held-in-reset" state. The core (x)
then begins execution from the internal L2 SRAM programmed in the DSP_BOOT_ADDRx register. All
memory may be written to and read by the host. This allows for the host to verify what it sends to the
DSP, if required.
2.4.2BOOTACTIVE
The output pin, BOOTACTIVE, is asserted upon reset and de-asserted on boot complete. In the case of
BOOTMODE 0, all cores are released from reset immediately. BOOTACTIVE also goes low within a small
number of cycles, as all cores are out of reset and running. In the case of BOOTMODE 1, the host needs
to write to the boot complete bit in the BOOT_COMPLETE_STAT register corresponding to each C64x+
megamodule that is to be taken out of reset. BOOTACTIVE will be high if any cores are held in reset. In
the case of any other boot, core 0 comes out of RESET immediately, but all other cores are still in
RESET,soBOOTACTIVEwillbehigh.TheROMcodewillnotwritetoeitherthe
BOOT_COMPLETE_STAT or the BOOT_ADDRESS register unless explicitly directed to do so by the data
provided in the boot process. Any active core can set bits in BOOT_COMPLETE_STAT at any time to
begin code execution on inactive cores. BOOTACTIVE will go low after the boot complete bit (BCx) in the
BOOT_COMPLETE_STAT register is set for all six cores. For a detailed explanation of this operation, see
the SM320C645x/C647x Bootloader User's Guide (literature number SPRUEC6).
A.The SYSCLKOUTEN pin is muxed with GP[15]. For more details, see Section 3.
B.These CONFIG pins are muxed with the GPIO peripheral pins. For more details, see Section 3.
C. These BOOTMODE pins are muxed with the GPIO peripheral pins. For more details, see Section 3.
D. These pins are muxed with GPIO peripheral pins. For more details, see Section 3.
The terminal functions table (Table 2-5) identifies the external signal names, the associated pin (ball)
numbers along with the mechanical package designator, the pin type (I, O/Z, or I/O/Z), whether the pin
has any internal pullup/pulldown resistors and a functional pin description. For more detailed information
on device configuration, peripheral selection, multiplexed/shared pins, and debugging considerations, see
LENDIANAH4IIPU0 = System operates in Big-Endian mode
MACSEL1[0]AF5IIPD
MACSEL1[1]AH5IIPD
DDRENE20IIPD0 = disabled (only use this mode if DDR is not powered)
RIOENU26IIPD0 = disabled (only use this mode if RapidIO is not powered)
HOUTAH23O/ZIPUHost event output.
GP00/HPI_ENM1I/O/ZIPDoff.
GP01/UTOPIA_ENN5I/O/ZIPDturned off.
GP02/TSIP0_ENM3I/O/ZIPDGeneral-purpose input/output pin [4:2] multiplexed with TSIP[2:0]
GP03/TSIP1_ENK5I/O/ZIPD
GP04/TSIP2_ENM5I/O/ZIPD
GP05/EMAC1_ENN4I/O/ZIPDturned off.
Table 2-5. Terminal Functions
(1)
TYPE
GENERAL-PURPOSE INPUT/OUTPUT PINS
IPD/IPU
CONFIGURATION PINS
(2) (3)
Device Endian pin.
1 = System operates in Little-Endian mode (default)
EMAC1 configuration select pin (for details, see Table 3-1).
DDR2 Memory Controller enable
1 = enabled
RapidIO enable
1 = enabled
HOST EVENT PINS
General-purpose input/output pin 0 multiplexed with HPI internal
pulls enable/disable
0 = Internal pulls on HPI IO are enabled and buffers are turned
1 = Internal pulls on most HPI IO are disabled and all buffers are
turned on.
For more detail about internal pull options, see Section 3.3.1.
General-purpose input/output pin 1 multiplexed with UTOPIA
internal pulls enable/disable
0 = Internal pulls on UTOPIA IO are enabled and buffers are
1 = Internal pulls on UTOPIA IO are disabled and buffers are
turned on.
For more detail about internal pull options, see Section 3.3.1.
internal pulls enable/disable
0 = Internal pulls on TSIPx IO are enabled and buffers are turned
off.
1 = Internal pulls on TSIPx IO are disabled and buffers are turned
on.
For more detail about internal pull options, see Section 3.3.1.
General-purpose input/output pin 5 multiplexed with EMAC1
internal pulls enable/disable
0 = Internal pulls on EMAC1 IO are enabled and buffers are
1 = Internal pulls on EMAC1 IO are disabled and buffers are
turned on.
For more detail about internal pull options, see Section 3.3.1.
www.ti.com
DESCRIPTION
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = Internal pulldown, IPU = Internal pullup. (These IPD/IPU signal pins feature a 30-kΩ IPD or IPU resistor. To pull up a signal to the
opposite supply rail, a 1-kΩ resistor should be used.)
General-purpose input/output pin [9:6] multiplexed with
BOOTMODE selection pin [3:0] (for details, see Table 3-1 and
Section 2.4).
General-purpose input/output pin [14:10] multiplexed with
configuration selection pin [4:0].
General-purpose input/output pin 15 multiplexed with
SYSCLKOUT enable.
0 = SYSCLKOUT is disabled (default)
1 = SYSCLKOUT is enabled
•Decoded from the low-order address bits. The number of
address bits or byte enables used depends on the width of
external memory.
•Byte-write enables for most types of memory.
•Can be directly connected to SDRAM read and write mask
signal (SDQM).
Memory Controller is enabled, it first sets these pins low. Then as
accesses occur to the DDR2 memory, only the chip select
corresponding to the accessed DDR2 memory is low.