•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
•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 concernsproducts in the formative
or design phase of development. Characteristic data and other
specifications are design goals. Texas Instruments reserves the right
to change ordiscontinue these products withoutnotice.
The TMS320C6472 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 TMS320C6472 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 TMS320C6472 device can
eliminate the need for external memory, thereby reducing system power dissipation and system cost and
optimizing board density.
The TMS320C6472 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 TMS320C6472 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.
TMS320C6472
SPRS612E–JUNE 2009–REVISED OCTOBER 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 NumbersTMX320C6472
(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)
PP
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.
www.ti.com
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
•Exception Handling - Intended to aid the programmer in isolating bugs. The C64x+ CPU is able to
•Privilege - Defines user and supervisor modes of operation, allowing the operating system to give a
•Time-Stamp Counter - Primarily targeted for Real-Time Operating System (RTOS) robustness, a
For more details on the C64x+ CPU and its enhancements over the C64x architecture, see the following
documents:
•TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide (literature number SPRU732)
•TMS320C64x+ DSP Cache User's Guide (literature number SPRU862)
•TMS320C64x+ DSP Megamodule Reference Guide (literature number SPRU871)
•TMS320C64x Technical Overview (literature number SPRU395)
•TMS320C64x to TMS320C64x+ CPU Migration Guide (literature number SPRAA84)
TMS320C6472
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
multiplications, complex multiplications, packing, sorting, bit manipulation, and 32-bit Galois field
multiplication.
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).
basic level of protection to sensitive resources. Local memory is divided into multiple pages, each with
read, write, and execute permissions.
free-running time-stamp counter is implemented in the CPU which is not sensitive to system stalls.
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.
Figure 2-1. TMS320C64x+™ CPU (DSP Core) Data Paths
Submit Documentation Feedback
Product Folder Link(s) :TMS320C6472
PRODUCTPREVIEW
www.ti.com
2.3Memory Map Summary
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.
www.ti.com
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 TMS320C6472 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 TMS320C645x/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.
selected
1PLLx20 mode of main PLLCTL is
selected
0PLLx10 mode of main PLLCTL is
selected
1PLLx20 mode of main PLLCTL is
selected
www.ti.com
MEGAMODULEADDRESSES FORADDRESSES FOR
CORE NAMEDEVICE RESET/DEVICE RESET/
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 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.
After local resets, the C6472 device supports two boot modes via BOOTMODE0-BOOTMODE5
device-level registers:
•Immediate boot
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.
•Host boot
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.
www.ti.com
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 TMS320C645x/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.
TMS320C6472
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
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.)
(3) IPU/IPD logic on some pins can be disabled based on configuration. For more information, see Section 3.3.1.
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.
UXCLAVH27O/ZIPD0 indicates a complete cell is NOT available for transmit.
UXADDR0W29
UXADDR1W28
UXADDR2W27IIPDUTOPIA transmit address bus
UXADDR3W26
UXADDR4W25
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
Table 2-5. Terminal Functions (continued)
(1)
TYPE
IIPD
IPD/IPU
(2) (3)
Source clock for UTOPIA receive driven by Master ATM
Controller.
Receive cell available status output signal from UTOPIA Slave.
0 indicates NO space is available to receive a cell from Master
1 indicates space is available to receive a cell from Master ATM
Controller.
UTOPIA 16-bit receive data bus (also supports 8-bit mode on pins
[7:0])
UTOPIA receive interface enable input signal. Asserted by the
Master ATM Controller to indicate to the UTOPIA slave to receive
one or more cells on the URDATA bus with URSOC active on the
first data cycle.
Receive start-of-cell signal. This signal is output by the Master
ATM Controller to indicate to the UTOPIA Slave that the first valid
byte of the cell is available to sample on the 16-bit Receive Data
Bus (URDATA[15:0]).
Source clock for UTOPIA transmit driven by Master ATM
Controller.
Transmit cell available status output signal from UTOPIA Slave.
1 indicates a complete cell is available for transmit.
GMDIOMDIO serial data input/output. Only active if MACSEL0[2:0] is any
GMDCLKMDIO serial clock output. Only active if MACSEL0[2:0] is any
RGMDIOMDIO serial data input/output. Only active if MACSEL0[2:0] = 011
RGMDCLKMDIO serial clock output. Only active if MACSEL0[2:0] = 011
MRXD00/RMRXD00/SRXD0AH11IIPURMII0 or Receive Data (RXD) for S3MII0. Pin function defined by
MRXD01/RMRXD01/SRXSYNC0AG12IIPURMII0 or Receive Sync (RXSYNC) for S3MII0. Pin function
MRXD02/SRXD1AJ11IIPUReceive Data (RXD) for S3MII1. Pin function defined by
MRXD03/SRXSYNC1AJ10IIPUReceive Sync (RXSYNC) for S3MII1. Pin function defined by
MRXD04/RMRXD10AH9IIPU(RXD0) for RMII1. Pin function defined by MACSEL0[2:0] and
MRXD05/RMRXD11AG7IIPU(RXD1) for RMII1. Pin function defined by MACSEL0[2:0] and
Table 2-5. Terminal Functions (continued)
(1)
TYPE
O/ZIPD
MANAGEMENT DATA INPUT/OUTPUT (MDIO)
AH10I/O/ZIPU
AG9O/ZIPU
AG18I/O
AF18O
ETHERNET MAC (EMAC0 and EMAC1) (MII0/GMII0/RMII[1:0]/S3MII[1:0])
IPD/IPU
(2) (3)
UTOPIA 16-bit transmit data bus (also supports 8-bit mode on
pins [7:0])
UTOPIA transmit interface enable input signal. Asserted by the
Master ATM Controller to indicate that the UTOPIA slave should
transmit one or more cells on the UXDATA bus with UXSOC
active on the first data cycle.
Transmit start-of-cell signal. This signal is output by the UTOPIA
Slave on the rising edge of the UXCLK, indicating that the first
valid byte of the cell is available on the 16-bit Transmit Data Bus
(UXDATA[15:0]).
value but 011 (RGMII).
value but 011 (RGMII).
(RGMII).
(RGMII).
EMAC Receive Data 0 (MRXD0) for MII0 [default], GMII0 and
MACSEL0[2:0] (see Table 3-1).
EMAC Receive Data 1 (MRXD1) for MII0 [default], GMII0 and
defined by MACSEL0[2:0] (see Table 3-1).
EMAC Receive Data 2 (MRXD2) for MII0 [default] and GMII0 or
MACSEL0[2:0] and MACSEL1[1:0] (see Table 3-1).
EMAC Receive Data 3 (MRXD3) for MII0 [default] and GMII0 or
MACSEL0[2:0] and MACSEL1[1:0] (see Table 3-1).
EMAC Receive Data 4 (MRXD4) for GMII0 or Receive Data 0
MACSEL1[1:0] (see Table 3-1).
EMAC Receive Data 5 (MRXD5) for GMII0 or Receive Data 1
MACSEL1[1:0] (see Table 3-1).
MRXD06/RMRXER1AJ13IIPU(RXER) for RMII1. Pin function defined by MACSEL0[2:0] and
MRXD07AJ6IIPU
MRCLK0/SRXCLK1AG10IIPUReceive Clock (RXCLK) for S3MII1. Pin function defined by
MRXDV0/RMCRSDV1AE12IIPU
MRXER0/RMRXER0/SRXCLK0AF12IIPURMII0 or Receive Clock (RXCLK) for S3MII0. Pin function defined
MCRS0/RMCRSDV0AF10IIPDGMII0 or Receive Carrier Sense/Data Valid (CRSDV) for RMII0.
GMTCLK0/REFCLK1/SREFCLK1AG6I/OIPUclock input (REFCLK) for RMII1 and S3MII1. Pin function defined
MTCLK0/REFCLK0/SREFCLK0AJ9IIPUor Reference clock input (REFCLK) for RMII0 and S3MII0. Pin
MTXD00/RMTXD00/STXD0AF8OIPURMII0 or Transmit Data (TXD) for S3MII0. Pin function defined by
MTXD01/RMTXD01/STXSYNC0AH7OIPURMII0 or Transmit Sync (TXSYNC) for S3MII0. Pin function
MTXD02/STXD1AG8OIPUTransmit Data (TXD) for S3MII1. Pin function defined by
MTXD03/STXSYNC1AF9OIPUTransmit Sync (TXSYNC) for S3MII1. Pin function defined by
MTXD04/RMTXD10/STXCLK1AE7OIPU
MTXD05/RMTXD11AJ7OIPU(TXD1) for RMII1. Pin function defined by MACSEL0[2:0] and
MTXD06/RMTXEN1AE11OIPU(TXEN) for RMII1. Pin function defined by MACSEL0[2:0] and
MTXD07/STXCLK0AG11OIPU(TXCLK) for S3MII0. Pin function defined by MACSEL0[2:0] (see
MTXEN0/RMTXEN0AF11OIPU
MCOL0AE8IIPD
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
Table 2-5. Terminal Functions (continued)
TYPE
(1)
IPD/IPU
(2) (3)
EMAC Receive Data 6 (MRXD6) for GMII0 or Receive Error
MACSEL1[1:0] (see Table 3-1).
EMAC Receive Data 7 (MRXD7) for GMII0. Pin function defined
by MACSEL0[2:0] (see Table 3-1).
EMAC Receive Clock (MRCLK) for MII0 [default] and GMII0 or
MACSEL0[2:0] and MACSEL1[1:0] (see Table 3-1).
EMAC Receive Data Valid (MRDV) for MII0 [default] and GMII0 or
Receive Carrier Sense/Data Valid (CRSDV) for S3MII1. Pin
function defined by MACSEL0[2:0] and MACSEL1[1:0] (see
Table 3-1).
EMAC Receive Error (MRXER) for MII0 [default], GMII0 and
by MACSEL0[2:0] (see Table 3-1).
EMAC Receive Carrier Sense (MCRS) for MII0 [default] and
Pin function defined by MACSEL0[2:0] (see Table 3-1).
EMAC Transmit Clock output (GMTCLK) for GMII0 or Reference
by MACSEL0[2:0] and MACSEL1[1:0] (see Table 3-1).
EMAC Transmit Clock input (MTCLK) for MII0 [default] and GMII0
function defined by MACSEL0[2:0] (see Table 3-1).
EMAC Transmit Data 0 (MTXD0) for MII0 [default], GMII0 and
MACSEL0[2:0] (see Table 3-1).
EMAC Transmit Data 1 (MTXD1) for MII0 [default], GMII0 and
defined by MACSEL0[2:0] (see Table 3-1).
EMAC Transmit Data 2 (MTXD2) for MII0 [default] and GMII0 or
MACSEL0[2:0] and MACSEL1[1:0] (see Table 3-1).
EMAC Transmit Data 3 (MTXD3) for MII0 [default] and GMII0 or
MACSEL0[2:0] and MACSEL1[1:0] (see Table 3-1).
EMAC Transmit Data 4 (MTXD4) for GMII0 or Transmit Data 0
(TXD0) for RMII1 or Transmit Clock (TXCLK) for S3MII1. Pin
function defined by MACSEL0[2:0] and MACSEL1[1:0] (see
Table 3-1).
EMAC Transmit Data 5 (MTXD5) for GMII0 or Transmit Data 1
MACSEL1[1:0] (see Table 3-1).
EMAC Transmit Data 6 (MTXD6) for GMII0 or Transmit Enable
MACSEL1[1:0] (see Table 3-1).
EMAC Transmit Data 7 (MTXD7) for GMII0 or Transmit Clock
Table 3-1).
EMAC Transmit Enable (MTXEN) for MII0 [default], GMII0 and
RMII0. Pin function defined by MACSEL0[2:0] (see Table 3-1).
EMAC Collision (MCOL) for MII0 [default]. Pin function defined by
MACSEL0[2:0] (see Table 3-1).
AG13connected directly to the 1.5-/1.8-V I/O supply (DV
D12When DDR is used, connect to DV
V5
(2) (3)
DESCRIPTION
Die-side core supply (CVDD) voltage monitor pin. The monitor pins
indicate the voltage on the die and, therefore, provide the best
probe point for voltage monitoring purposes. For more information
regarding the use of this and other voltage monitoring pins, see
the TMS320C6472/TMS320TCI6486 Hardware Design Guide
application report (literature number SPRAAQ4). If the CV
pin is not used, it should be connected directly to the die-side
core supply (CVDD).
Die-side 1.5-/1.8-V I/O supply (DV
monitor pins indicate the voltage on the die and, therefore,
) voltage monitor pin. The
DD15
provide the best probe point for voltage monitoring purposes. For
more information regarding the use of this and other voltage
monitoring pins, see the TMS320C6472/TMS320TCI6486Hardware Design Guide application report (literature number
SPRAAQ4). If the DV
DD15MON
pin is not used, it should be
NOTE: If the RGMII mode of the EMAC is not used, the DV
DV
can be NC or connected directly to VSS(GND) to save power.
DD15MON
, V
, PTV15P, PTV15N, and HHV15EN pins
REFHSTL
However, connecting these pins in this way will prevent
boundary-scan from functioning on the RGMII pins of the EMAC.
To preserve boundary-scan functionality on the RGMII pins, see
Section 7.3.3.
Die-side 1.8-V I/O supply (DV
monitor pins indicate the voltage on the die and, therefore,
) voltage monitor pin. The
DD18
provide the best probe point for voltage monitoring purposes. For
more information regarding the use of this and other voltage
monitoring pins, see the TMS320C6472/TMS320TCI6486Hardware Design Guide application report (literature number
SPRAAQ4). If the DV
connected directly to the 1.8-V I/O supply (DV
DD18MON
NC or connected to VSS, if DDR is not used
pin is not used, it should be
DD18
(1.8V)
DD18
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
and HHV18EN pins can be NC or connected directly to V
DD18MON
, V
REFSSTL
, AV
DD3
, AV
DD4
, CV
, PTV18P, PTV18N,
DD1
(GND) to save power. However, connecting these pins this way
prevents boundary scan from functioning on the DDR2 Memory
Controller pins. To preserve boundary-scan functionality on the
DDR2 Memory Controller pins, see Section 7.3.3.
Die-side 3.3-V I/O supply (DV
monitor pins indicate the voltage on the die and, therefore,
) voltage monitor pin. The
DD33
provide the best probe point for voltage monitoring purposes. For
more information regarding the use of this and other voltage
monitoring pins, see the TMS320C6472/TMS320TCI6486Hardware Design Guide application report (literature number
PTV18PC20Iand HHV18EN pins can be NC or connected directly to V
PTV18NC19I
PTV15PAF14I
PTV15NAE14I
TYPE
(1)
IPD/IPU
(2) (3)
PTV PINS
If DDR is used, connect to VSS(GND) via 200-Ω precision resistor
NC or connected to VSS, if DDR is not used
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
DD18MON
, V
(GND) to save power. However, connecting these pins this way
prevents boundary scan from functioning on the DDR2 Memory
Controller pins. To preserve boundary-scan functionality on the
DDR2 Memory Controller pins, see Section 7.3.3.
If DDR is used, connect to DV
resistor
NC or connected to VSS, if DDR is not used
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
and HHV18EN pins can be NC or connected directly to V
DD18MON
, V
(GND) to save power. However, connecting these pins this way
prevents boundary scan from functioning on the DDR2 Memory
Controller pins. To preserve boundary-scan functionality on the
DDR2 Memory Controller pins, see Section 7.3.3.
If RGMII is used, connect to VSS(GND) via 200-Ω precision
resistor
NC or connected to VSS, if RGMII is not used
NOTE: If the RGMII mode of the EMAC is not used, the DV
DV
can be NC or connected directly to VSS(GND) to save power.
DD15MON
, V
However, connecting these pins in this way will prevent
boundary-scan from functioning on the RGMII pins of the EMAC.
To preserve boundary-scan functionality on the RGMII pins, see
Section 7.3.3.
If RGMII is used, connect to DV
precision resistor
NC or connected to VSS, if RGMII is not used
NOTE: If the RGMII mode of the EMAC is not used, the DV
DV
can be NC or connected directly to VSS(GND) to save power.
DD15MON
, V
However, connecting these pins in this way will prevent
boundary-scan from functioning on the RGMII pins of the EMAC.
To preserve boundary-scan functionality on the RGMII pins, see
HHV15ENAF13Ican be NC or connected directly to VSS(GND) to save power.
HHV18END20Iand HHV18EN pins can be NC or connected directly to V
CV
DD
Table 2-5. Terminal Functions (continued)
AE10
C21
G19
G20
K15
K17
K19
L10
L12
L14
L16
L18
L20
M11
M13
M15
M17
M19
N10
N12
N14
N16
N18
P11
P13
P15
P17
R10
TYPE
(1)
IPD/IPU
SUPPLY VOLTAGE PINS
I
(2) (3)
When RGMII is used, connect to DV
Connected to VSS, if RGMII is not used
NOTE: If the RGMII mode of the EMAC is not used, the DV
DV
DD15MON
, V
However, connecting these pins in this way will prevent
boundary-scan from functioning on the RGMII pins of the EMAC.
To preserve boundary-scan functionality on the RGMII pins, see
Section 7.3.3.
When DDR is used, connect to DV
Connected to VSS, if DDR is not used
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
DD18MON
, V
(GND) to save power. However, connecting these pins this way
prevents boundary scan from functioning on the DDR2 Memory
Controller pins. To preserve boundary-scan functionality on the
DDR2 Memory Controller pins, see Section 7.3.3.
1-V (500-MHz device),
1.1-V (625-MHz device),
1.2-V (700-MHz device)
supply voltage for core logic
Iand HHV18EN pins can be NC or connected directly to V
K11
K13
N201-V (500-MHz device), 1.1-V (625-MHz device), 1.2-V (700-MHz
P19
R20
T19
IDV
U20
R241.2-V RapidIO analog supply voltage
U24
IDV
M29I1.8-V System PLL analog supply voltage
AG14I1.8-V EMAC PLL analog supply voltage
(2) (3)
DESCRIPTION
NC or connected to VSS, if DDR is not used
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
DD18MON
, V
REFSSTL
, AV
DD3
, AV
DD4
, CV
, PTV18P, PTV18N,
DD1
(GND) to save power. However, connecting these pins this way
prevents boundary scan from functioning on the DDR2 Memory
Controller pins. To preserve boundary-scan functionality on the
DDR2 Memory Controller pins, see Section 7.3.3.
device) supply voltage for SRIO core logic
NC or connected to VSS, if RapidIO is not used
NOTE: If the RapidIO interface is not used, the CV
, DV
DDR
, and AV
DDD
to VSS(GND) to reduce power use. However, connecting these
pins can be NC or connected directly
DDT
pins in this way prevents boundary scan from functioning on the
RapidIO pins. To preserve boundary-scan functionality on the
RapidIO pins, see Section 7.3.3.
NC or connected to VSS, if RapidIO is not used
Do not connect this SERDES supply to CV
NOTE: If the RapidIO interface is not used, the CV
, DV
DDR
, and AV
DDD
to VSS(GND) to reduce power use. However, connecting these
pins can be NC or connected directly
DDT
DD1
pins in this way prevents boundary scan from functioning on the
RapidIO pins. To preserve boundary-scan functionality on the
RapidIO pins, see Section 7.3.3.
B21IPTV18N pins can be NC or connected directly to VSS(GND) to
H41.8-V DDR analog supply voltage
A21
IPTV18N pins can be NC or connected directly to VSS(GND) to
T231.2-V RapidIO digital supply voltage
V23
IDV
R28I
A1
A19
B10
B14
B5
E1
E12
E16
E6
F15
F17IPTV18N pins can be NC or connected directly to VSS(GND) to
F19
G10
G12
G14
G16
G18
G6
G8
H7
J6
(2) (3)
DESCRIPTION
1.8-V DDR PLL analog supply voltage
NC or connected to VSS, if DDR is not used
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
DD18MON
, V
REFSSTL
, AV
DDA3
, AV
DDA4
, CV
DD1
, PTV18P, and
save power. However, connecting these pins this way prevents
boundary scan from functioning on the DDR2 Memory Controller
pins. To preserve boundary-scan functionality on the DDR2
Memory Controller pins, see Section 7.3.3.
NC or connected to VSS, if DDR is not used
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
DD18MON
, V
REFSSTL
, AV
DDA3
, AV
DDA4
, CV
DD1
, PTV18P, and
save power. However, connecting these pins this way prevents
boundary scan from functioning on the DDR2 Memory Controller
pins. To preserve boundary-scan functionality on the DDR2
Memory Controller pins, see Section 7.3.3.
NC or connected to VSS, if RapidIO is not used
Do not connect this SERDES supply to CV
NOTE: If the RapidIO interface is not used, the CV
, DV
DDR
, and AV
DDD
to VSS(GND) to reduce power use. However, connecting these
pins can be NC or connected directly
DDT
DD1
pins in this way prevents boundary scan from functioning on the
RapidIO pins. To preserve boundary-scan functionality on the
RapidIO pins, see Section 7.3.3.
1.5-V/1.8-V RapidIO regulator supply voltage
NC or connected to VSS, if RapidIO is not used
NOTE: If the RapidIO interface is not used, the CV
DV
, DV
DDR
, and AV
DDD
to VSS(GND) to reduce power use. However, connecting these
pins can be NC or connected directly
DDT
pins in this way prevents boundary scan from functioning on the
RapidIO pins. To preserve boundary-scan functionality on the
RapidIO pins, see Section 7.3.3.
1.8-V I/O supply voltage for DDR2 buffers
NC or connected to VSS, if DDR is not used
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
DD18MON
, V
REFSSTL
, AV
DDA3
, AV
DDA4
, CV
DD1
, PTV18P, and
save power. However, connecting these pins this way prevents
boundary scan from functioning on the DDR2 Memory Controller
pins. To preserve boundary-scan functionality on the DDR2
Memory Controller pins, see Section 7.3.3.
E10IPTV18N pins can be NC or connected directly to VSS(GND) to
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
Table 2-5. Terminal Functions (continued)
(1)
TYPE
IPD/IPU
IDV
(2) (3)
NC or connected to VSS, if RapidIO is not used
Do not connect this SERDES supply to CV
NOTE: If the RapidIO interface is not used, the CV
, DV
DDR
, and AV
DDD
to VSS(GND) to reduce power use. However, connecting these
pins in this way prevents boundary scan from functioning on the
RapidIO pins. To preserve boundary-scan functionality on the
RapidIO pins, see Section 7.3.3.
1.5-V/1.8-V supply voltage for RGMII HSTL buffers
NC or connected to VSS, if RGMII is not used
NOTE: If the RGMII mode of the EMAC is not used, the DV
DV
connected directly to VSS(GND) to save power. However,
DD15MON
, V
, PTV15P, and PTV15N pins can be NC or
REFHSTL
connecting these pins in this way will prevent boundary-scan from
functioning on the RGMII pins of the EMAC. To preserve
boundary-scan functionality on the RGMII pins, see Section 7.3.3.
0.75-V/0.9-V DV
NC or connected to VSS, if RGMII is not used
reference supply voltage
DD15
NOTE: If the RGMII mode of the EMAC is not used, the DV
DV
connected directly to VSS(GND) to save power. However,
DD15MON
, V
, PTV15P, and PTV15N pins can be NC or
REFHSTL
connecting these pins in this way will prevent boundary-scan from
functioning on the RGMII pins of the EMAC. To preserve
boundary-scan functionality on the RGMII pins, see Section 7.3.3.
DDR 0.9-V V
NC or connected to VSS, if DDR is not used
reference supply voltage
REFSSTL
NOTE: If the DDR2 Memory Controller is not used, the DV
DV
DD18MON
, V
REFSSTL
, AV
save power. However, connecting these pins this way prevents
boundary scan from functioning on the DDR2 Memory Controller
pins. To preserve boundary-scan functionality on the DDR2
Memory Controller pins, see Section 7.3.3.
For customers that will develop their own features and software on the C6472 device, TI offers an
extensive line of development tools for the TMS320C6000™ DSP platform, including tools to evaluate the
performance of the processors, generate code, develop algorithm implementations, and fully integrate and
debug software and hardware modules. The tool's support documentation is electronically available within
the Code Composer Studio™ Integrated Development Environment (IDE).
The following products support development of C6000™ DSP-based applications:
Software Development Tools: Code Composer Studio™ Integrated Development Environment (IDE)
including Editor, C/C++/Assembly Code Generation, and Debug plus additional development tools
scalable Real-Time Foundation Software (DSP/BIOS™), which provides the basic run-time target software
needed to support any DSP application.
HardwareDevelopmentTools: ExtendedDevelopmentSystem(XDS™)Emulators(support
C6000/C64x+ DSP multiprocessor system debug) and Evaluation Module (EVM).
2.8.2Device Support
2.8.2.1Device and Development-Support Tool Nomenclature
To designate the stages in the product development cycle, TI assigns prefixes to the part numbers of all
DSP devices and support tools. Each DSP commercial family member has one of three prefixes: TMX,
TMP, or TMS (e.g., TMX320C6472ZTZ). Texas Instruments recommends one of two prefix designators for
its support tools: TMDX and TMDS. These prefixes represent evolutionary stages of product development
from engineering prototypes (TMX/TMDX) through fully qualified production devices/tools (TMS/TMDS).
TMS320C6472
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
Device development evolutionary flow:
TMXExperimental device that is not necessarily representative of the final device's electrical
specifications
TMPFinal silicon die that conforms to the device's electrical specifications but has not completed
quality and reliability verification
TMSFully qualified production device
Support tool development evolutionary flow:
TMDXDevelopment-support product that has not yet completed Texas Instruments internal
qualification testing.
TMDSFully qualified development-support product
TMX and TMP devices and TMDX development-support tools are shipped with the following disclaimer:
"Developmental product is intended for internal evaluation purposes."
TMS devices and TMDS development-support tools have been characterized fully, and the quality and
reliability of the device has been demonstrated fully. TI's standard warranty applies.
Predictions show that prototype devices (TMX or TMP) have a greater failure rate than the standard
production devices. Texas Instruments recommends that these devices not be used in any production
system because their expected end-use failure rate still is undefined. Only qualified production devices are
to be used.
Blank = 0°C to +85°C (default commercial temperature)
°°
A = -40 C to +100 C (extended temperature)
DEVICE SPEED RANGE
(B)
Blank = 500 MHz
625 = 625 MHz
700 = 700 MHz
PACKAGE TYPE
(C)
ZTZ = 737-pin plastic BGA, with lead-free
solder balls
ZTZ
( )
( ) ( )
SILICON REVISION
Blank = silicon revision 1.0
B = silicon revision 1.1
C = silicon revision 1.2
D = silicon revision 2.0
(D)
TMS320C6472
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
TI device nomenclature also includes a suffix with the device family name. This suffix indicates the
package type (for example, ZTZ), the temperature range (for example, blank is the default commercial
temperature range), and the device speed range, in megahertz (for example, blank is 500 MHz).
Figure 2-13 provides a legend for reading the complete device name for any TMS320C64x+™ DSP
generation member.
For a complete list of all valid device part numbers and further ordering information for TMS320C6472 in
the ZTZ package type, see online ordering at www.ti.com or contact your TI sales representative. For
specific references to package symbolization as well as device errata and advisories, see the
TMS320C6472 Digital Signal Processor Silicon Errata (literature number SPRZ300).
www.ti.com
A.A (extended temperature) temperature range is available only on 500-MHz and 625-MHz devices.
B.Device Speed Range marking is placed in upper right hand corner of device.
C. BGA = Ball Grid Array
D. Silicon revision correlates to the lot trace code found on the second line of the package marking. For more
information, see the TMS320C6472 Digital Signal Processor Silicon Errata (literature number SPRZ300).
Figure 2-13. TMS320C64x+™ DSP Device Nomenclature (including the TMS320C6472 DSP)
2.8.2.2Documentation Support
The following documents describe the TMS320C6472 Fixed-Point Digital Signal Processor. Copies of
these documents are available on the Internet at www.ti.com. Tip: Enter the literature number in the
search box provided at www.ti.com.
The current documentation that describes the TMS320C6472, related peripherals, and other technical
collateral, is available in the C6000 DSP product folder at: www.ti.com/c6000.
User's Guides/Reference Manuals:
SPRZ300TMS320C6472 Digital Signal Processor Silicon Errata. This document describes the
silicon updates to the functional specifications for the TMS320C6472 digital signal processor.
SPRU732TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide. Describes the CPU
architecture, pipeline, instruction set, and interrupts for the TMS320C64x and TMS320C64x+
SPRU871TMS320C64x+ DSP Megamodule Reference Guide. Describes the TMS320C64x+ digital
On the C6472 device, boot mode and certain device configurations/peripheral selections are determined
at device reset. Following device reset, the software needs to enable and configure the desired peripheral
modules.
3.1Device Configuration at Device Reset
Table 3-1 describes the C6472 device configuration pins. The logic level of these pins is latched at reset
to determine the device configuration. The logic level on the device configuration pins can be set by using
external pullup/pulldown resistors or by using some control device (e.g., FPGA/CPLD) to intelligently drive
these pins. When using a control device, care should be taken to ensure there is no contention on the
lines when the device is out of reset. The RESETSTAT pin can be monitored for this purpose. The device
configuration pins are sampled during reset and may be driven after the reset is removed. At this time, the
control device should ensure it has stopped driving the device configuration pins of the DSP to avoid
contention.
Table 3-1. C6472 Device Configuration Pins
www.ti.com
CONFIGURATIONIPD/
PINIPU
GP[9:6]_BOOTMODE[3:0]IPU
GP[14:10]_CFGGP[4:0]IPDThese pins are used in S/W routines located in internal ROM for boot operations.
GP[15]_SYSCLKOUTENIPD0 - SYSCLKOUT is disabled (default)
MACSEL1[1:0]IPD
MACSEL0[2:0]IPD011 - RGMII
LENDIANIPU0 - System operates in Big Endian mode
DDRENIPD
RIOENIPD
(1) 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.)
NO.FUNCTIONAL DESCRIPTION
(1)
For more detailed information on the boot modes, see Section 2.4, Boot Mode
Sequence, of this document.
Configuration GPI (General-Purpose Inputs for Configuration purposes
CFGGP[4:0])
For more detailed information on the use of the configuration pins for boot
operation, see Section 2.4, Boot Mode Sequence, of this document.
Enable SYSCLKOUT
1 - SYSCLKOUT is enabled
EMAC Interface selection for EMAC 1 (EMAC1_EN in the DEVCTL register must
be a 1 for these to be functional)
00 - Reserved
01 - SS-SMII (SS Mode)
10 - RGMII
11 - RMII
EMAC Interface selection for EMAC 0
000 - MII
001 - RMII
010 - GMII
Device Endian mode (LENDIAN)
1 - System operates in Little Endian mode (default)
DDR2 Memory Controller enable (DDR2_EN)
0 - DDR2 Memory Controller module and pins are disabled (default)
1 - DDR2 Memory Controller module and pins are enabled
Note that this is a static configuration input from reset.
RIOEN RapidIO enable
0 - RapidIO module and pins are disabled (default)
1 - RapidIO module and pins are enabled
Note that this is a static configuration input from reset.
It is recommended that external connections be provided to device configuration pins, including all GPIO,
MACSEL, DDREN, and RIOEN pins. Although internal pullup/pulldown resistors exist on these pins,
providing external connectivity adds convenience to the user in debugging and flexibility in switching
operating modes. It also improves noise immunity for critical mode control inputs.
For the internal pullup/pulldown resistors for all device pins, see Table 2-5, Terminal Functions.
3.2Device Configuration Register Descriptions
Table 3-2 is a summary of the primary chip-level registers that are discussed in Section 3.3 through
Section 3.11.
3.3.1Controlling Internal Pulls on the Peripherals
3.3.1.1Device Control Register (DEVCTL)
The device control register (DEVCTL) controls the internal pulls on the I/O interfaces. The bits are
initialized on the rising edge of the Power-On Reset from the GPIO pins [5:0], then software can override
these latched values. When the DSP is out of reset, the DEVCTL bits control the pullup and pulldown
resistors. When the DSP is held in reset, the GPIO pins enable the pullup and pulldown resistors, directly.
These bits also enable or disable the output buffers on these interfaces. When the pull-up or pull-down
resistors are enabled, the output buffers are disabled. When not in use, all the inputs should be in a
known state (i.e., needs to be internally pulled) and the corresponding I/O buffers should be powered
down to save I/O power. The DEVCTL register is shown in Figure 3-1 and described in Table 3-3.
Section 3.3.1.3 contains more detail about the operation of the internal resistor pulls and the output buffer
operation. It explicitly lists the relevant pins individually under all possible configurations and states
whether the output buffers are enabled or disabled and whether the internal pull resistors are enabled or
disabled.
3116
1513121198
ReservedEMAC1_ENTSIP2_EN[2:0]TSIP1_EN2
7653210
TSIP1_EN[1:0]TSIP0_EN[2:0]UTOPIA_EN[1:0]HPI_EN
R/W-xxxR/W-xxxR/W-xxR/W-x
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
R/W-0R/W-xR/W-xxxR/W-xxx
www.ti.com
Reserved
R-0000 0000
Figure 3-1. Device Control Register (DEVCTL)
Table 3-3. Device Control Register (DEVCTL) Field Descriptions
BitFieldValueDescription
31:13ReservedReserved
12EMAC1_ENEMAC1 Internal Pulls Enable. Initialized at reset from GP05/EMAC1_EN pin.
0Enable the pulls on the 3.3-V EMAC1 I/O pins and power down the corresponding I/O buffers. Also
disable the EMAC1 RGMII I/O pins.
1Allow the pulls on the 3.3-V EMAC1 I/O to be disabled and the corresponding I/O buffers to be
powered up. Also allow the RGMII I/O buffers to be powered up. This input is combined with the
MACSEL1[1:0] configuration inputs to determine which I/O pins are enabled and which are
disabled. All disabled 3.3-V I/O pins will have internal pulls active.
11TSIP2_EN[2]TSIP2 Internal Pulls Enable[2]. Initialized at reset from GP04/TSIP2_EN pin.
0Enable the pulls on TX[7:4] and TR[7:4] of the TSIP2 I/O pins and power down the corresponding
I/O buffers.
1Disable the pulls on TX[7:4] and TR[7:4] of the TSIP2 I/O pins and power up the corresponding I/O
buffers.
10TSIP2_EN[1]TSIP2 Internal Pulls Enable[1]. Initialized at reset from GP04/TSIP2_EN pin.
0Enable the pulls on TX[3:2] and TR[3:2] of the TSIP2 I/O pins and power down the corresponding
I/O buffers.
1Disable the pulls on TX[3:2] and TR[3:2] of the TSIP2 I/O pins and power up the corresponding I/O
Table 3-3. Device Control Register (DEVCTL) Field Descriptions (continued)
BitFieldValueDescription
9TSIP2_EN[0]TSIP2 Internal Pulls Enable[0]. Initialized at reset from GP04/TSIP2_EN pin.
0Enable the pulls on all TSIP2 I/O pins and power down the I/O buffers. When this bit is low, the
1Disable the pulls on CLKA, CLKB, FSA, FSB, TX[1:0], and TR[1:0] of the TSIP2 I/O pins and power
8TSIP1_EN[2]TSIP1 Internal Pulls Enable[2]. Initialized at reset from GP03/TSIP1_EN pin.
0Enable the pulls on TX[7:4] and TR[7:4] of the TSIP1 I/O pins and power down the corresponding
1Disable the pulls on TX[7:4] and TR[7:4] of the TSIP1 I/O pins and power up the corresponding I/O
7TSIP1_EN[1]TSIP1 Internal Pulls Enable[1]. Initialized at reset from GP03/TSIP1_EN pin.
0Enable the pulls on TX[3:2] and TR[3:2] of the TSIP1 I/O pins and power down the corresponding
1Disable the pulls on TX[3:2] and TR[3:2] of the TSIP1 I/O pins and power up the corresponding I/O
6TSIP1_EN[0]TSIP1 Internal Pulls Enable[0]. Initialized at reset from GP03/TSIP1_EN pin.
0Enable the pulls on all TSIP1 I/O pins and power down the I/O buffers. When this bit is low, the
1Disable the pulls on CLKA, CLKB, FSA, FSB, TX[1:0], and TR[1:0] of the TSIP1 I/O pins and power
5TSIP0_EN[2]TSIP0 Internal Pulls Enable[2]. Initialized at reset from GP02/TSIP0_EN pin.
0Enable the pulls on TX[7:4] and TR[7:4] of the TSIP0 I/O pins and power down the corresponding
1Disable the pulls on TX[7:4] and TR[7:4] of the TSIP0 I/O pins and power up the corresponding I/O
4TSIP0_EN[1]TSIP0 Internal Pulls Enable[1]. Initialized at reset from GP02/TSIP0_EN pin.
0Enable the pulls on TX[3:2] and TR[3:2] of the TSIP0 I/O pins and power down the corresponding
1Disable the pulls on TX[3:2] and TR[3:2] of the TSIP0 I/O pins and power up the corresponding I/O
3TSIP0_EN[0]TSIP0 Internal Pulls Enable[0]. Initialized at reset from GP02/TSIP0_EN pin.
0Enable the pulls on all TSIP0 I/O pins and power down the I/O buffers. When this bit is low, the
1Disable the pulls on the clock inputs and control inputs and outputs of the UTOPIA I/O pins and
2UTOPIA_EN[1]UTOPIA Internal Pulls Enable[1]. Initialized at reset from GP01/UTOPIA_EN pin.
0Enable the pulls on UXDATA[15:8] and URDATA[15:8] of the UTOPIA I/O pins and power down the
1UTOPIA_EN[0]UTOPIA Internal Pulls Enable [0]. Initialized at reset from GP01/UTOPIA_EN pin.
0HPI_ENHPI Internal Pulls Enable. Initialized at reset from GP01/UTOPIA_EN pin.
1Disable the pulls on UXDATA[15:8] and URDATA[15:8] of the UTOPIA I/O pins and power up the
0Enable the pulls on all UTOPIA I/O pins and power down the I/O buffers. When this bit is low, the
1Disable the pulls on the UTOPIA clock inputs, control inputs and outputs, UXDATA[7:0], and
0Enable the pulls on the HPI I/O pins and power down the corresponding I/O buffers.
1Disable the pulls on all HPI I/O pins except HAS, HCS, and HINT and power up all HPI I/O buffers.
TMS320C6472
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
values of TSIP2_EN[2:1] = don't care.
up the corresponding I/O buffers.
I/O buffers.
buffers.
I/O buffers.
buffers.
values of TSIP1_EN[2:1] = don't care.
up the corresponding I/O buffers.
I/O buffers.
buffers.
I/O buffers.
buffers.
values of TSIP0_EN[2:1] = don't care.
power up the corresponding I/O buffers.
corresponding I/O buffers.
corresponding I/O buffers.
value of UTOPIA_EN[1] = don't care.
URDATA[7:0] and power up the corresponding I/O buffers.
The device control key register (DEVCTL_KEY) protects against inadvertently updating the DEVCTL
register with errant software. The DEVCTL_KEY register is shown in Figure 3-2.
310
KEY
R/W-0000 0000 0000 0000
LEGEND: R/W = Read/Write; -n = value after reset
Figure 3-2. Device Control Key Register (DEVCTL_KEY)
To update/write the DEVCTL register:
1. When the correct key value (KEY = 0A1E 183Ah) is written to the DEVCTL_KEY register, the DEVCTL
register becomes amenable for a single write anytime after this.
2. Once the DEVCTL register is written, no further writes to the DEVCTL register are allowed without
repeating Step 1.
The software should disable all the interrupts during the update of the DEVCTL register.
This section augments Table 3-3 in Section 3.3.1.1. It contains more detail about the operation of the
internal resistor pulls and the output buffer operation. It explicitly lists the relevant pins individually under
all possible configurations and states whether internal pull resistors are enabled or disabled. The 3.3-V
EMAC0 and EMAC1 pins are listed in Table 3-4, the HPI pins are listed in Table 3-5, the TSIP pins are
listed in Table 3-6, Table 3-7, Table 3-8 and the UTOPIA pins are listed in Table 3-9.
Use the following legend for Table 3-4 through Table 3-9:
•EN = Internal pull-up or pull-down resistors are enabled and output buffers are disabled.
•DIS = Internal pull-up or pull-down resistors are disabled and output buffers are enabled.
This is true for all cases except for three HPI control signals (HAS, HCS, and HINT) that always have their
internal pull resistors activated (see Table 3-5).
RGMII or RGMII or RGMII or RGMII or RGMII or RGMII or
Disabled Disabled Disabled Disabled Disabled Disabled
DISDISDISDISENENDISDISENENDISDISENEN
DISDISDISDISENENDISDISENENDISDISENEN
DISDISDISDISENENDISDISENENDISDISENEN
ENDISENENENENDISDISDISDISDISDISDISDIS
DISDISDISDISENENDISDISENENDISDISENEN
DISDISDISDISENENDISDISENENDISDISENEN
DISDISDISDISENENDISDISENENDISDISENEN
ENDISENENENENDISDISDISDISDISDISDISDIS
(1) DIS = Disabled internal pull resistor and enabled output buffer; EN = Enabled internal pull resistor and disabled output buffer.
(2) Although MDIO is shared between EMAC0 and EMAC1, only MACSEL0 (i.e., EMAC0) configuration pins are used to control the MDIO
interface. For example, when EMAC0 is in RGMII mode the 1.8-V MDIO pins are used (3.3-V MDIO pins are not used) and when
EMAC0 is in non-RGMII mode the 3.3-V MDIO pins are used (1.8-V RGMII MDIO pins are not used).
The device status register (DEVSTAT) depicts the status of the device configuration inputs that were
captured at device reset. The DEVSTAT register is shown in Figure 3-3.
3.5RMIIn Reset Registers (RMIIRESET0 and RMIIRESET1)
RMII supports switching of 10/100 Mbps modes and switching between half and full-duplex. The
RMIIRESET0 and RMIIRESET1 registers are used to reset the RMII interface to switch the speed and
duplex settings. The selection of 10/100 Mbps and half- and full-duplex modes is determined by registers
in the EMAC modules. For more information, see the TMS320C6472/TMS320TCI6486 DSP EthernetMedia Access Controller (EMAC)/Management Data Input/Output (MDIO) Module User's Guide (literature
number SPRUEF8).
3116
Reserved
R-0
1510
ReservedRESET
R-0R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Figure 3-4. RMIIn Reset Registers (RMIIRESET0 and RMIIRESET1)
Table 3-10. RMIIn Reset Registers (RMIIRESET0 and RMIIRESET1) Field Descriptions
Memory privilege is an extension of the memory protection defined in the C64x+ megamodule. It defines
the supervisor user mode privilege required to access peripherals that do not inherently have the
protection built in. For more information, see the TMS320C64x+ DSP Megamodule Reference Guide
(literature number SPRU871).
The host memory privilege permission register (HOSTPRIV) configures host memory privilege modes.
HOSTPRIV defines the privilege to be used when an external host uses direct IO with SRIO or HPI to
access any on-chip memory or peripherals or external memory via the EMIF. Writing a 1 makes
supervisor-mode accesses from the peripheral; writing a 0 makes user-mode accesses from the
peripheral. The default for these bits is supervisor-mode access.
The memory privilege permission register (PRIVPERM) defines the permission level necessary to access
peripheral registers on the CFG SCR. The defaults allow both user- and supervisor-level accesses to
these peripheral groups. If desired, the software can override accesses to these peripheral groups by
writing the values shown in Table 3-11 to the register bits. For the purposes of protection, certain
peripherals are grouped together (see Table 3-12), thus, the selected protection applies to the entire
group; i.e., setting 0 to the RIO bit field would make user-mode accesses to SRIO and SRIO wrappers
configuration space.
Table 3-11. Permission Values
ACCESSESPERMISSION VALUE
Supervisor and user modes00
Supervisor mode10
User mode01
None11
3.6.3Key-Based Protection for HOSTPRIV and PRIVPERM Registers (PRIVKEY)
Key-based protection of HOSTPRIV and PRIVPERM is provided for a higher level of protection or control
over changing the permission levels. The PRIVKEY register, shown in Figure 3-7 and described in
Table 3-13, is needed to service the key requirement. Updates to the HOSTPRIV and PRIVPERM
registers are only allowed when PRIVKEY contains the lower 16-bit key value (BEA7h). Protection is
provided by a following write to PRIVKEY to clear the register. The PRIVKEY is a 32-bit register with the
lower 16 bits as key field and upper 16 bits reserved to 0.
3116
Reserved
R/W-0000 0000 0000 0000
150
KEY
R/W-0000 0000 0000 0000
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
The NMI generator registers (NMIGR0-NMIGR5) create an NMI event to each C64x+ megamodule. The
NMIGR0 register generates an NMI event to C64x+ Megamodule0, the NMIGR1 register generates an
NMI event to C64x+ Megamodule1, etc. Writing a 1 to the NMIG field generates an NMI pulse. Writing a 0
has no effect; reads return 0 and have no other effect. The source ID fields found in IPCGR0-IPCGR5 can
be used along with the NMI generation registers to identify the source of the NMI.
3116
Reserved
R-0000 0000 0000 0000 0000 0000 0000 000
1510
ReservedNMIG
R-0000 0000 0000 0000 0000 0000 0000 000R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
3.7.2Inter-DSP Interrupt Registers (IPCGR0-IPCGR5 and IPCAR0-IPCAR5)
The IPCGRn (IPCGR0 thru IPCGR5) and IPCARn (IPCAR0 thru IPCAR5) registers facilitate inter-DSP
interrupts. This can be utilized by external hosts or C64x+ megamodules to generate interrupts to other
DSPs. A write of 1 to the IPCG field of IPCGRn register generates an interrupt pulse to C64x+
Megamodulen (n = 0-5). These registers also provide a source ID, by which up to 28 different sources of
interrupts can be identified.
3.7.3Host Interrupt and Event Pulse Generation Registers (IPCGR15 and IPCAR15)
The host interrupt and event pulse generation registers (IPCGR15 (or IPCGRH) and IPCAR15 (or
IPCARH)) facilitate host CPU interrupt. Operation and use of the IPCGR15 register is the same as
registers IPCGR0-5 and the IPCAR15 register is the same as registers IPCAR0-5. The interrupt output
pulse created by the IPCGR15 register is driven on a device pin host interrupt/event output (HOUT). The
interrupt output pulse is asserted for 4 CPU/6 cycles followed by a deassertion of 4 CPU/6 cycles.
The timer pin manager register (TPMGR) configures the timer output pin. The TPMGR register details are
shown in Figure 3-13 and described in Table 3-18.
31430
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 3-18. Timer Pin Manager Register (TPMGR) Field Descriptions
BitFieldValueDescription
31:4ReservedReserved
3:0TOUTSEL
www.ti.com
ReservedTOUTSEL
R-0000 0000 0000 0000 0000 0000 0000R/W-0000
Figure 3-13. Timer Pin Manager Register (TPMGR)
0000Nothing selected for TIMO2
0001Timer64 6 - TOUTL selected for TIMO2
0010Timer64 6 - TOUTH selected for TIMO2
0011Timer64 7 - TOUTL selected for TIMO2
0100Timer64 7 - TOUTH selected for TIMO2
0101Timer64 8 - TOUTL selected for TIMO2
0110Timer64 8 - TOUTH selected for TIMO2
0111Timer64 9 - TOUTL selected for TIMO2
1000Timer64 9 - TOUTH selected for TIMO2
1001Timer64 10 - TOUTL selected for TIMO2
1010Timer64 10 - TOUTH selected for TIMO2
1011Timer64 11 - TOUTL selected for TIMO2
1100Timer64 11 - TOUTH selected for TIMO2
The reset controller has inputs for each of the watchdog timer outputs. The reset mux registers determine
the method of reset that will be used when a watchdog timeout occurs.
3116
1598
7654310
DELAYReservedEVTSTATOMODELOCK
R/W-100R-0RC-0R/W-000R/W-0
LEGEND: R/W = Read/Write; R = Read only; C = Clear; -n = value after reset
Table 3-19. Reset Mux Registers (RSTMUX0-RSTMUX5) Field Descriptions
BitFieldValueDescription
31:9ReservedReserved
8:6DELAY
5ReservedReserved
4EVTSTATThe EVTSTAT bit indicates if any local timer event is received. The event could be a timeout event
3:1OMODEThe OMODE bits determine how to handle the local timer events.
0LOCKThe LOCK field prevents further writes to the register when set to 1. After the software configures
000256 CPU/6 cycles delay between NMI and local reset, when OMODE = 100.
001512 CPU/6 cycles delay between NMI and local reset, when OMODE = 100.
0101024 CPU/6 cycles delay between NMI and local reset, when OMODE = 100.
0112048 CPU/6 cycles delay between NMI and local reset, when OMODE = 100.
1004096 CPU/6 cycles delay between NMI and local reset, when OMODE = 100 (default).
1018192 CPU/6 cycles delay between NMI and local reset, when OMODE = 100.
11016384 CPU/6 cycles delay between NMI and local reset, when OMODE = 100.
11132768 CPU/6 cycles delay between NMI and local reset, when OMODE = 100.
0No event received (default).
1Timer event received by the reset mux block.
000Timer event input to the reset mux block does not cause any output event (default).
001Reserved
010Timer event input to the reset mux block causes local reset input to C64x+ megamodule.
011Timer event input to the reset mux block causes NMI input to C64x+ megamodule.
100Timer event input to the reset mux block causes NMI input followed by local reset input to C64x+
101Timer event input to the reset mux block causes system reset to the PLL controller.
110Reserved
111Reserved
0Register fields are not locked (default).
1Register fields are locked until the next timer reset.
(when the timer is configured in watchdog mode). Since there is only one output pin of a watchdog
event (WDOUT), the software can read this bit to know which one of the 6 timers has timed out.
Writing a 0 clears this bit.
megamodule. Delay between NMI and local reset is set in the DELAY bit field.
the timer in watchdog mode and the appropriate routing of events to C64x+ megamodule, it is
expected to set the LOCK bit to 1. This will prevent accidental modification of the bit fields of this
register. The LOCK bit is reset to 0 only on the next reset that resets the Timer64.
The reset status register (RESET_STAT) indicates the status of global (device) reset and of the local reset
for all six C64x+ megamodules.
313016
GRReserved
RC-0R-000 0000 0000 0000
151211109876543210
ReservedLR5LR4LR3LR2LR1LR0
R-00 0000 0000 0000RC-10RC-10RC-10RC-10RC-10RC-10
LEGEND: R/W = Read/Write; R = Read only; C = Clear; -n = value after reset
Table 3-20. Reset Status Register (RESET_STAT) Field Descriptions
BitFieldValueDescription
31GR1Global Reset. Writing a 1 to GR clears the bit, writing a 0 has no effect.
30:12ReservedReserved
11:10LR5Local Reset 5. Writing a 1 to LR5 clears the bit; writing a 0 has no effect.
9:8LR4Local Reset 4. Writing a 1 to LR4 clears the bit; writing a 0 has no effect.
7:6LR3Local Reset 3. Writing a 1 to LR3 clears the bit; writing a 0 has no effect.
5:4LR2Local Reset 2. Writing a 1 to LR2 clears the bit; writing a 0 has no effect.
3:2LR1Local Reset 1. Writing a 1 to LR1 clears the bit; writing a 0 has no effect.
1:0LR0Local Reset 0. Writing a 1 to LR0 clears the bit; writing a 0 has no effect.
www.ti.com
Figure 3-15. Reset Status Register (RESET_STAT)
00Core 5 has not received a local reset.
01A local reset (lreset_in) has been asserted to Core 5.
10Reserved
11Core 5 has responded with lreset_out.
00Core 4 has not received a local reset.
01A local reset (lreset_in) has been asserted to Core 4.
10Reserved
11Core 4 has responded with lreset_out.
00Core 3 has not received a local reset.
01A local reset (lreset_in) has been asserted to Core 3.
10Reserved
11Core 3 has responded with lreset_out.
00Core 2 has not received a local reset.
01A local reset (lreset_in) has been asserted to Core 2.
10Reserved
11Core 2 has responded with lreset_out.
00Core 1 has not received a local reset.
01A local reset (lreset_in) has been asserted to Core 1.
10Reserved
11Core 1 has responded with lreset_out.
00Core 0 has not received a local reset.
01A local reset (lreset_in) has been asserted to Core 0.
10Core 0 has responded with lreset_out in global boot situation.
11Core 0 has responded with lreset_out.
The boot progress register (BOOTPROGRESS) tracks the progress of the boot sequence. The ROM boot
code periodically writes values to this register to indicate progress. This can also be used by other
software as a debugging tool.
310
BOOTPROGRESS
R/W-0000 0000 0000 0000 0000 0000 0000 0000
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
The chip-level boot modes are set using the BOOTMODE[3:0] device pins. In addition to this, for local
boot purposes, each core can set its BOOTMODE choice using the registers BOOTMODE0 through
BOOTMODE5. The default values of these registers are set to immediate boot mode.
31430
ReservedBOOTMODE
R-0000 0000 0000 0000 0000 0000 0000R/W-0000
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Each C64x+ megamodule has its own boot address register (DSP_BOOT_ADDRn) associated with it. The
contents of these registers are the 22 MSBs of the initial fetch address of the C64x+ megamodulen from
where it starts executing after the boot complete bit is set.
In Immediate Boot (Boot mode 0) and HPI Boot (Boot mode 1) modes, all six registers have the L2 RAM
base address tie-off value 00 2000h as default, which corresponds to 0080 0000h. In the case of HPI boot
mode, the host can overwrite these registers before boot complete is set to change the boot address for
each C64x+ megamodule.
For other boot modes (boot modes 2 - 15), DSP_BOOT_ADDR0 has SL2 ROM base address tie-off value
00 0400h as the default. Other GEM_BOOT_ADDRn registers have L2 RAM base address tie-off values
00 2000h as default. In this mode, the application can set individual boot addresses for individual C64x+
megamodules by programming different values in the GEM_BOOT_ADDRn registers.
TMS320C6472
31222116
ReservedDSP_BOOT_ADDR
R-0R/W-00 0000 0010 0000 0000 0000
150
DSP_BOOT_ADDR
R/W-00 0000 0010 0000 0000 0000
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
A. For boot modes 2 - 15, DSP_BOOT_ADDR0 has default address 00 0400h and DSP_BOOT_ADDR1 - DSP_BOOT_ADDR5 have
default address 00 2000h. For boot mode 0 and 1, all registers have default address 00 2000h.
The JTAG ID register is a read-only register that identifies to the customer the JTAG ID (DEVICE_ID). For
the C6472 device, the JTAG ID register resides at address location 02A8 0008h. It reads 0009 102Fh. For
the actual register bit names and their associated bit field descriptions, see Figure 3-20 and Table 3-24.
3128 2712 1110
VARIANTPART NUMBERMANUFACTURER
(4-bit)(16-bit)(11-bit)
R-0000R-0000 0000 1001 0001R-0000 0010 111R-1
LEGEND: R = Read only; -n = value after reset
Figure 3-20. JTAG ID (DEVICE_ID) Register - C6472 Register Value
BitFieldValueDescription
31:28VARIANT0000Variant (4-Bit) value.
27:12PART NUMBER0000 0000 1001 0001 Part Number (16-Bit) value.
(1) Fixed value for each silicon revision. This table shows silicon revision 1.0, as an example.
(2) Fixed value irrespective of the silicon revision.
www.ti.com
LSB
Table 3-24. JTAG ID (DEVICE_ID) Register Field Descriptions
(1)
Note: The VARIANT field may be invalid if no CLKIN1 signal is applied. The
value of this field depends on the silicon revision being used. For more
information, see the TMS320C6472 Digital Signal Processor Silicon Errata
(literature number SPRZ300).
(2)
(2)
(2)
3.11 Silicon Revision ID Register Description
The silicon revision ID is a read-only register that provides silicon revision details. For the C6472 device,
the silicon revision ID register is at address location 02A8 070Ch. It reads 0010 0091h. The silicon
revision ID Register is shown in Figure 3-21 and described inTable 3-25.
312423201916
ReservedMAJOR REVISIONMINOR REVISION
8-bit4-bit4-bit
R-0000 0000R-0001R-0000
150
PART NUMBER
16-bit
R-0000 0000 1001 0001
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Figure 3-21. Silicon Revision ID Register
Table 3-25. Silicon Revision ID Register Field Descriptions
BitFieldValueDescription
31:24Reserved0000 0000Reserved
23:20MAJOR REVISION0001Major revision of the silicon
19:16MINOR REVISION0000Minor revision of the silicon
15:0PART NUMBER0000 0000 1001 0001 Part number of the silicon
(1) Fixed value for each silicon revision. This table shows silicon revision 1.0, as an example.
(2) Fixed value irrespective of the silicon revision.
On the C6472 device, the C64x+ megamodule, the EDMA3 transfer controllers, and the system
peripherals are interconnected through two switch fabrics. The switch fabrics allow for low-latency,
concurrent data transfers between peripherals and memories. The switch fabrics also allow for seamless
arbitration between the system masters when accessing system slaves.
4.1Internal Buses, Bridges, and Switch Fabrics
Two types of buses exist in the C6472 device: data buses and configuration buses. Some C6472
peripherals have both a data bus and a configuration bus interface, while others only have one type of
interface. Furthermore, the bus interface width and speed varies from peripheral to peripheral.
Configuration buses are mainly used to access the register space of a peripheral and the data buses are
used mainly for data transfers.
The C64x+ megamodule, the EDMA3 transfer controllers, and the various system peripherals can be
classified into two categories: masters and slaves. Masters are capable of initiating read and write
transfers in the system and do not rely on the EDMA3 for their data transfers. Slaves, on the other hand,
rely on the EDMA3 to perform transfers to and from them. Masters include the EDMA3 transfer controllers,
EMAC, TSIP, HPI, UTOPIA, and SRIO. Slaves include the EMIF and I2C.
The C6472 device contains two switch fabrics through which masters and slaves communicate: the data
switch fabric, known as the data switched central resource (SCR) and configuration switch fabric, known
as the configuration switched central resource (SCR). The data SCR is a high-throughput interconnect
mainly used to move data across the system (for more information, see Section 4.2). The data SCR
connects masters to slaves via 128-bit data buses running at a SYSCLK7 frequency, generated from the
PLL1 controller. Peripherals that have a 128-bit data bus interface running at this speed can connect
directly to the data SCR; other peripherals require a bridge. The configuration SCR is mainly used by the
C64x+ megamodules to access peripheral registers (for more information, see Section 4.4). The
configuration SCR connects C64x+ megamodules to slaves via 32-bit configuration buses also running at
a SYSCLK7 frequency. As with the data SCR, some peripherals require the use of a bridge to interface to
the configuration SCR. Note that the data SCR also connects to the configuration SCR.
TMS320C6472
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
Bridges perform a variety of functions:
•Conversion between configuration bus and data bus.
•Width conversion between peripheral bus width and SCR bus width.
•Frequency conversion between peripheral bus frequency and SCR bus frequency.
For example, TSIP modules require a bridge to convert their 32-bit data bus interface into a 128-bit
interface so that they can connect to the data SCR. Note that some peripherals can be accessed through
the data SCR and also through the configuration SCR.
Figure 4-1 shows the connection between slaves and masters through the data switched central resource
(SCR). Masters are shown on the right and slaves on the left. The data SCR connects masters to slaves
via 128-bit data buses running at frequency equal to the CPU frequency divided by 3.
Some peripherals and the C64x+ megamodule have both slave and master ports. Note that each EDMA3
transfer controller has an independent connection to the data SCR.
The Serial RapidIO (SRIO) peripheral has two connections to the data SCR. The first connection is used
when descriptors are being fetched from system memory. The other connection is used for all other data
transfers.
Note that masters can access the configuration SCR through the data SCR. The configuration SCR is
described in Section 4.4. Not all masters on the C6472 DSP may connect to all slaves. Allowed
connections are summarized in Table 4-1.
On the C6472 device, DMA data transfers use a priority-based arbitration. The C64x+ megamodule,
EDMA, TSIP, and SRIO peripherals define their own priorities. The Ethernet and HPI peripherals do not
define their own priorities, while the UTOPIA-PDMA only partially defines its own priority. Priorities for
Ethernet, HPI, and UTOPIA-PDMA transfers should be assigned via the Priority Allocation (PRI_ALLOC)
register (see Figure 4-2). A value of 000b has the highest priority, while 111b has the lowest priority. (For
more information on the default priority values in the C64x+ megamodule, EDMA, TSIP, and SRIO
peripheral registers, see the device-compatible reference guides). TI recommends that these priority
registers be reprogrammed upon initial use.
3116
Reserved
R-1111 1111 1111 1111
151412118
UTOPIA-
(A)
PDMA
R/W-1R/W-111R-1111
765320
ReservedHPIEMAC0
R-11R/W-111R/W-111
LEGEND: R/W = Read/Write; R = Read only; -n = value at reset
A. UTOPIA-PDMA has 2 bits of priority in the module. The PRI_ALLOC register supplies only the middle significant bit of the priority for
this module.
EMAC1Reserved
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
4.4Configuration Switch Fabric
Figure 4-3 shows the connection between the C64x+ megamodule and the configuration switched central
resource (SCR). The configuration SCR is mainly used by the C64x+ megamodules to access peripheral
registers. The data SCR also has a connection to the configuration SCR which allows masters to access
most peripheral registers. The only registers not accessible by the data SCR through the configuration
SCR are the C64x+ megamodule configuration registers; these can only be accessed by the C64x+
megamodules.
The configuration SCR uses 32-bit configuration buses running at a frequency equal to the CPU frequency
divided by 3.
The C64x+ Megamodule consists of several components — the C64x+ CPU, the L1 program and data
memory controllers, the L2 memory controller, the internal DMA (IDMA), the interrupt controller,
power-down controller, and external memory controller. The C64x+ Megamodule also provides support for
memory protection (for L1P, L1D, and L2 memories) and bandwidth management (for resources local to
the C64x+ Megamodule). Figure 5-1 shows a block diagram of the C64x+ Megamodule.
For more detailed information on the TMS320C64x+ megamodule on the C6472 device, see the
TMS320C64x+ DSP Megamodule Reference Guide (literature number SPRU871).
The TMS320C6472 device contains a 608KB level-2 memory (L2), a 32KB level-1 program memory
(L1P), and a 32KB level-1 data memory (L1D).
The L1P memory configuration for the C6472 device is as follows:
•Region 0 size is 0K bytes (disabled).
•Region 1 size is 32K bytes with no wait states.
The L1D memory configuration for the C6472 device is as follows:
•Region 0 size is 0K bytes (disabled).
•Region 1 size is 32K bytes with no wait states.
Figure 5-1. 64x+ Megamodule Block Diagram
Submit Documentation Feedback
Product Folder Link(s) :TMS320C6472
PRODUCTPREVIEW
4K bytes
8K bytes
16K bytes
L1P memory
00E0 0000h
00E0 4000h
00E0 6000h
00E0 7000h
00E0 8000h
direct
mapped
SRAM
1/2
dm
3/4
SRAM
SRAM
7/8
All
SRAM
000001010011100
Block base
address
L1P mode bits
cache
4K bytes
cache
direct
mapped
cache
direct
mapped
cache
4K bytes
8K bytes
16K bytes
L1D memory
00F0 0000h
00F0 4000h
00F0 6000h
00F0 7000h
00F0 8000h
2-way
SRAM
1/2
2-way
3/4
SRAM
SRAM
7/8
All
SRAM
000001010011100
Block base
address
L1D mode bits
cache
4K bytes
cache
2-way
cache
2-way
cache
TMS320C6472
SPRS612E–JUNE 2009–REVISED OCTOBER 2010
L1D is a two-way set-associative cache while L1P is a direct-mapped cache.
The L1P and L1D cache can be reconfigured via software through the L1PMODE field of the L1P
Configuration Register (L1PCFG) and the L1DMODE field of the L1D Configuration Register (L1DCFG) of
the C64x+ Megamodule. After device reset, L1P and L1D cache are configured as all cache or all SRAM.
The on-chip Bootloader changes the reset configuration for L1P and L1D. For more information, see the
TMS320C645x/C647x Bootloader User's Guide (literature number SPRUEC6).
Figure 5-2 and Figure 5-3 show the available SRAM/cache configurations for L1P and L1D, respectively.
L2 memory can be configured as all SRAM or as part 4-way set-associative cache. The amount of L2
memory that is configured as cache is controlled through the L2MODE field of the L2 Configuration
Register (L2CFG) of the C64x+ Megamodule. Figure 5-4 shows the available SRAM/cache configurations
for L2. By default, L2 is configured as all SRAM after device reset.
www.ti.com
For more information on the operation L1 and L2 caches, see the TMS320C64x+ DSP Cache User's
Guide (literature number SPRU862).
All memory on the C6472 has a unique location in the memory map (see Table 2-2, C6472 Memory Map
Summary).
Memory protection allows an operating system to define who or what is authorized to access L1D, L1P,
and L2 memory. To accomplish this, the L1D, L1P, and L2 memories are divided into pages. There are 16
pages of L1P (2KB each), 16 pages of L1D (2KB each), and up to 64 pages of L2. The L1D, L1P, and L2
memory controllers in the C64x+ Megamodule are equipped with a set of registers that specify the
permissions for each memory page. For L2, the number of protection pages and their sizes depend on the
L2 configuration of the device, as defined in the previous section. The actual sizes are listed in Table 5-2.
Table 5-2 shows the memory addresses used to access the L2 memory.
Each page may be assigned with fully orthogonal user and supervisor read, write, and execute
permissions. Additionally, a page may be marked as either (or both) locally or globally accessible. A local
access is a direct CPU access to L1D, L1P, and L2, while a global access is initiated by a DMA (either
IDMA or the EDMA3) or by other system masters.
The assignment of privilege IDs for CPU 0 and all non-EDMA system masters is based on silicon revision.
For silicon revisions ≤1.2, CPU 0 and all non-EDMA system masters on the device are assigned the same
privilege ID of 0. For silicon revsions >1.2, CPU 0 is assigned the privilege ID of 6 and all non-EDMA
system masters are assigned the same privilege ID of 0. CPUs 1-5 are each assigned a unique privilege
ID (see Table 5-3). It is only possible to specify whether the memory pages are locally or globally
accessible. The AIDx (x=0,1,2,3,4,5, or X) and LOCAL bits of the memory protection page attribute
registers specify the memory page protection scheme as listed in Table 5-4.
Whenever the CPU is the initiator of a memory transaction, the privilege mode (user or supervisor) in
which the CPU is running at that time is carried with those transactions. This includes EDMA3 transfers
that are programmed by the CPU. For most peripheral masters (EMAC0, EMAC1, UTOPIA, TSIP0, TSIP1,
and TSIP2), the privilege mode is always user mode. Two peripherals (HPI and SRIO) have
programmable privilege modes through a chip-level register, HOSTPRIV, and can be either user or
supervisor.
Table 5-3. Available Memory Page Protection Scheme with Privilege ID
1AID1Inherited from CPU
2AID2Inherited from CPU
3AID3Inherited from CPU
4AID4Inherited from CPU
5AID5Inherited from CPU
6 (Core 0,AIDXReservedReserved
silicon revisions ≤1.2)
6 (Core 0,AIDXInherited from CPU
silicon revisions >1.2)
>6AIDXReservedReserved
Table 5-4. Available Memory Page Protection Scheme with AIDx and Local Bits
PRIVID MODULELOCAL BITDESCRIPTION
00No access to memory page is permitted.
01Only direct access by CPU is permitted.
10Only accesses by system masters and IDMA are permitted (includes EDMA and IDMA
Megamodule interrupt controller) service routine. A CPU or DMA access to a page without the proper
permissions will:
•Block the access - reads return zero, writes are voided.
•Capture the initiator in a status register - ID, address, and access type are stored.
•Signal event to CPU interrupt controller.
The software is responsible for taking corrective action to respond to the event and resetting the error
status in the memory controller.
For more information on memory protection for L1D, L1P, and L2, see the TMS320C64x+ DSP
Megamodule Reference Guide (literature number SPRU871).
5.3Bandwidth Management
When multiple requestors contend for a single C64x+ Megamodule resource, the conflict is solved by
granting access to the highest priority requestor. The following four resources are managed by the
Bandwidth Management control hardware:
•Level 1 Program (L1P) SRAM/Cache
•Level 1 Data (L1D) SRAM/Cache
•Level 2 (L2) SRAM/Cache
•Memory-mapped registers configuration bus
The priority level for operations initiated within the C64x+ Megamodule; e.g., CPU-initiated transfers,
user-programmed cache coherency operations, and IDMA-initiated transfers, are declared through
registers in the C64x+ Megamodule. The priority level for operations initiated outside the C64x+
Megamodule by system peripherals is declared through the Priority Allocation Register (PRI_ALLOC), see
Figure 4-2. System peripherals with no fields in PRI_ALLOC have their own registers to program their
priorities.
Faults are handled by software in an interrupt (or exception, programmable within each C64x+
More information on the bandwidth management features of the C64x+ Megamodule can be found in the
TMS320C64x+ DSP Megamodule Reference Guide (literature number SPRU871).