Communications Infrastructure Digital Signal Processor
Data Manual
PRODUCT ION DATA infor mation is current as of p ublication dat e.
Products conform to specifications per the terms of Texas
Instruments standard warranty. Production processing does not
necessarily include testing of all parameters.
Literature Number: SPRS582B
July 2010
TMS320C6457
Data Manual
SPRS582B—July 2010
Release History
Additions/Modifications/Deletions
SPRS582B• Added 850 mHz clock speed.
• Added content to the Warm Reset section describing how to preserve contents of DDR2 SDRAM through a Warm Reset
cycle with Self-Refresh mode enabled on the SDRAM.
• Corrected typo in the Reset Timing Requirements table, parameter number 2: changed RESET
• Corrected 1.2-V to 1.1-V in last item of Features bullet list.
SPRS582A• Corrected CORECLK(P|N) and ALTCORECLK max frequency, minimum period time, duty cycle, and transition times
• Corrected Period Jitter tolerance, duty cycle, and transition times for DDRREFCLK(P|N) and ALTDDRCLK
• Corrected PLL2 block diagram to include correct reference to PLLV
• Added DDR2CLKOUT0(N|P) and DDR2CLKOUT0(N|P) min and max frequency to PLL2 Clock Frequency Ranges table
• Removed PLLOUT term from the PLL2 Clock Frequency ranges table
• Clarified wording in the introduction of the PLL2 section and on the effective x5 multiplier that generates
DDR2CLKOUT0(N|P) and DDR2CLKOUT0(N|P) from DDRREFCLK(P|N) or ALTDDRCLK
• Added Table 7-4 Power Supply to Peripheral I/O Mapping to clarify the exact I/O and reference clock buffers each power
supply provides power for
• Added Overshoot/Undershoot definition to Table 6-1 Absolute Maximum Ratings
• Fixed typo in Table 2-1 under the 1.2 GHz space, “1.2 V, 1.8 V, and 3.3 V” now correctly reads “1.1 V, 1.8 V, and 3.3 V”
• Fixed typo for the McBSP timing parameters. “P = 1/CORECLK” now correctly reads “P = 1/SYSREFCLK”
• Fixed typo in 7.3.1 Power-Supply Sequencing - The SPRAAG5 reference now correctly references SPRAAV7
(A) The CMH mechanical package designator represents the version of the GMH package with lead-free balls. For more detailed information, see ‘‘Mechanical Data’’ on
page 209 of this document.
1.2 Description
The TMS320C64x+™ DSPs (including the TMS320C6457 device) are the highest-performance fixed-point DSP
generation in the TMS320C6000™ DSP platform. The C6457 device is based on the third-generation
high-performance, advanced VelociTI™ very-long-instruction-word (VLIW) architecture developed by Texas
Instruments (TI), making these DSPs 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.
Based on 65-nm process technology and with performance of up to 9600 million instructions per second (MIPS) [or
9600 16-bit MMACs per cycle] at a 1.2-GHz clock rate, the C6457 device offers cost-effective solutions to
high-performance DSP programming challenges. The C6457 DSP possesses the operational flexibility of high-speed
controllers and the numerical capability of array processors.
The C64x+ DSP 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+ .M unit doubles the multiply
throughput versus the C64x core by performing four 16-bit × 16-bit multiply-accumulates (MACs) every clock
cycle. Thus, eight 16-bit × 16-bit MACs can be executed every cycle on the C64x+ core. At a 1.2-GHz clock rate, this
means 9600 16-bit MMACs can occur every second. Moreover, each multiplier on the C64x+ core can compute one
32-bit × 32-bit MAC or four 8-bit × 8-bit MACs every clock cycle.
The C6457 device includes Serial RapidIO®. This high-bandwidth peripheral dramatically improves system
performance and reduces system cost for applications that include multiple DSPs on a board, such as video and
telecom infrastructures and medical/imaging.
122009 Texas Instruments Incorporated
TMS320C6457
Communications Infrastructure Digital Signal Processor
www.ti.com
The C6457 DSP integrates a large amount of on-chip memory organized as a two-level memory system. The level-1
(L1) program and data memories on the C6457 device 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 whereas L1 data (L1D) is a two-way set associative cache. The level 2 (L2) memory is shared between program
and data space and is 2048KB in size. L2 memory can also be configured as mapped RAM, cache, or some
combination of the two. L2 is configurable up to 1MB of cache. 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.
2
The peripheral set includes: an inter-integrated circuit bus module (I
(McBSPs); an 8-bit Universal Test and Operations PHY Interface for Asynchronous Transfer Mode (ATM) Slave
[UTOPIA Slave] port; two 64-bit general-purpose timers (also configurable as four 32-bit timers); a
user-configurable 16-bit or 32-bit host-port interface (HPI16/HPI32); a 16-pin general-purpose input/output port
(GPIO) with programmable interrupt/event generation modes; an 10/100/1000 Ethernet media access controller
(EMAC), which provides an efficient interface between the C6457 DSP core processor and the network; a
management data input/output (MDIO) module (also part of the EMAC) that continuously polls all 32 MDIO
addresses in order to enumerate all PHY devices in the system; a glueless external memory interface (64-bit EMIFA),
which is capable of interfacing to synchronous and asynchronous peripherals; and a 32-bit DDR2 SDRAM interface.
The C6457 device has three high-performance embedded coprocessors [one enhanced Viterbi Decoder Coprocessor
(VCP2) and two enhanced Turbo Decoder Coprocessors (TCP2_A and TCP2_B)] that significantly speed up
channel-decoding operations on-chip. The VCP2 operating at CPU clock ÷ 3 can decode more than 694 7.95-Kbps
adaptive multi-rate (AMR) [K = 9, R = 1/3] voice channels. The VCP2 supports constraint lengths K = 5, 6, 7, 8, and
9, rates R = 3/4, 1/2, 1/3, 1/4, and 1/5, and flexible polynomials, while generating hard decisions or soft decisions.
Each TCP2 operating at CPU clock ÷ 3 can decode up to fifty 384-Kbps or eight 2-Mbps turbo encoded channels
(assuming 6 iterations). The TCP2 implements the max*log-map algorithm and is designed to support all
polynomials and rates required by Third-Generation Partnership Projects (3GPP and 3GPP2), with fully
programmable frame length and turbo interleaver. Decoding parameters such as the number of iterations and
stopping criteria are also programmable. Communications between the VCP2/TCP2s and the CPU are carried out
through the EDMA3 controller.
C); two multichannel buffered serial ports
SPRS582B—July 2010
PRODUCT PREVIEW
The C6457 device has a complete set of development tools, which includes: a new C compiler, an assembly optimizer
to simplify programming and scheduling, and a Windows® debugger interface for visibility into source code
execution.
2009 Texas Instruments Incorporated13
TMS320C6457
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
1.3 Functional Block Diagram
Figure 1-2 Shows the functional block diagram of the TMS320C6457 device.
(A) Each of the TIMER peripherals (TIMER1 and TIMER0) is configurable as either one 64-bit general-purpose timer or two 32-bit general-purpose timers or a watchdog timer.
142009 Texas Instruments Incorporated
TMS320C6457
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
2 Device Overview
2.1 Device Characteristics
Table 2-1 provides an overview of the TMS320C6457 DSP. The table shows significant features of the C6457 device,
including the capacity of on-chip RAM, the peripherals, the CPU frequency, and the package and pin count.
2.2 CPU (DSP Core) Description
Table 2-1Characteristics of the C6457 Processor (Part 1 of 2)
HARDWARE FEATURES TMS320C6457
EMIFA (64-bit bus width) (clock source = AECLKIN or SYSCLK7) 1
DDR2 Memory Controller (32-bit bus width) [1.8 V I/O]
(clock source = DDRREFCLKN|P)
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
Table 2-1Characteristics of the C6457 Processor (Part 2 of 2)
HARDWARE FEATURES TMS320C6457
Product StatusProduction Data (PD)PD
Device Part
Numbers
End of Table 2-1
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
PRODUCT PREVIEW
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.
The C64x+ CPU extends the performance of the C64x core through enhancements and new features.
(For more details on the C64x+™ DSP part numbering, see Figure 2-12)
www.ti.com
TMS320C6457CMH/GMH
Each C64x+ .M unit can perform one of the following each clock cycle: one 32 × 32 bit multiply, two 16 × 16 bit
multiplies, two 16 × 32 bit multiplies, four 8 × 8 bit multiplies, four 8 × 8 bit multiplies with add operations, and four
16 × 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 produces one
32-bit packed output that contain 16-bit real and 16-bit imaginary values. The 32 × 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.
Communications Infrastructure Digital Signal Processor
www.ti.com
•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:
•TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide (literature number SPRU732)
•TMS320C64x+ DSP Cache User's Guide (literature number SPRU862)
•TMS320C64x+ Megamodule Reference Guide (literature number SPRU871)
•TMS320C64x to TMS320C64x+ CPU Migration Guide (literature number SPRAA84)
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
Figure 2-1 shows the DSP core functional units and data paths.
Figure 2-1TMS320C64x+ CPU (DSP Core) Data Paths
www.ti.com
PRODUCT PREVIEW
Data path A
ST1b
ST1a
LD1b
LD1a
LD2a
LD2b
32 MSB
32 LSB
32 MSB
32 LSB
DA1
DA2
32 LSB
32 MSB
.L1
.S1
.M1
.D1
.D2
.M2
src1
src2
odd dst
even dst
long src
long src
even dst
odd dst
src1
src2
dst2
dst1
src1
src2
src1
src2
src2
src1
src2
src1
dst2
dst1
dst
dst
Odd
register
file A
(A1, A3,
A5...A31)
(D)
8
8
(D)
32
32
32
32
(A)
(B)
(C)
2x
1x
(C)
(B)
(A)
Odd
register
file B
(B1, B3,
B5...B31)
Even
register
file A
(A0, A2,
A4...A30)
Even
register
file B
(B0, B2,
B4...B30)
src2
src1
.S2
.L2
odd dst
even dst
long src
long src
even dst
odd dst
src2
src1
8
8
Data path B
32 MSB
ST2a
32 LSB
ST2b
(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.
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
2.3 Memory Map Summary
Table 2-2 shows the memory map address ranges of the TMS320C6457 device. The external memory configuration
register address ranges in the C6457 device begin at the hex address location 0x7000 0000 for EMIFA and hex
address location 0x7800 0000 for DDR2 Memory Controller.
Table 2-2TMS320C6457 Memory Map Summary (Part 1 of 3)
MEMORY BLOCK DESCRIPTIONBLOCK SIZE (BYTES)HEX ADDRESS RANGE
EMIFA CE2 Data -SBSRAM/Async 8M A000 0000 - A07F FFFF
Reserved 256M - 8M A080 0000 - AFFF FFFF
EMIFA CE3 Data -SBSRAM/Async 8M B000 0000 - B07F FFFF
Reserved 256M - 8M B080 0000 - BFFF FFFF
EMIFA CE4 Data -SBSRAM/Async 8M C000 0000 - C07F FFFF
Reserved 256M - 8M C080 0000 - CFFF FFFF
EMIFA CE5 Data -SBSRAM/Async 8M D000 0000 - D07F FFFF
Reserved 256M - 8M D080 0000 - DFFF FFFF
DDR2 EMIF CE0 Data 512M E000 0000 - FFFF FFFF
End of Table 2-2
TMS320C6457
SPRS582B—July 2010
2.4 Boot Sequence
The boot sequence is a process by which the DSP's internal memory is loaded with program and data sections. The
DSP's internal registers are programmed with predetermined values. The boot sequence is started automatically
after each power-on reset, warm reset, and system reset. A local reset to an individual C64x+ Megamodule should
not affect the state of the hardware boot controller on the device. For more details on the initiators of the resets, see
Section 7.6 ‘‘Reset Controller’’ on page 123.
The C6457 supports several boot processes begins execution at the ROM base address, which contains the
bootloader code necessary to support various device boot modes. The boot processes are software driven; using the
BOOTMODE[3:0] device configuration inputs to determine the software configuration that must be completed.
2.5 Boot Modes Supported
The device supports several boot processes, which leverage the internal boot ROM. Most boot processes are software
driven, using the BOOTMODE[3:0] device configuration inputs to determine the software configuration that must
be completed. From a hardware perspective, there are two possible boot modes:
•Public ROM Boot - C64x+ Megamodule is released from reset and begins executing from the L3 ROM base
address. After performing the boot process (e.g., from I
Megamodule then begins execution from the L2 RAM base address.
•Secure ROM Boot - On secure devices, the C64x+ Megamodule is released from reset and begin executing
from secure ROM. Software in the secure ROM will free up internal RAM pages, after which the C64x+
Megamodule initiates the boot process. The C64x+ Megamodule performs any authentication and decryption
required on the bootloaded image prior to beginning execution.
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
The boot process performed by the C64x+ Megamodule in public ROM boot and secure ROM boot are determined
by the BOOTMODE[3:0] value in the DEVSTAT register. The C64x+ Megamodule reads this value, and then
executes the associated boot process in software. Table 2-3 shows the supported boot modes.
Table 2-3TMS320C6457 Supported Boot Modes
Mode NameBootmode[3:0]Description
No Boot 0000b No Boot
2
C Master Boot A 0001b Slave I2C address is 0x50. The C64x+ Megamodule configures I2C, acts as a master to the I2C bus and
I
2
I
C Master Boot B 0010b Similar to I2C boot A except the slave I2C address is 0x51.
2
C Slave Boot 0011b The C64x+ Megamodule configures I2C and acts as a slave and will accept data and code section
I
PRODUCT PREVIEW
HPI Boot 0100b Host boot.
EMIFA Boot 0101b External memory boot from ACE3 space (0xB0000000 address).
EMAC Master Boot 0110b
EMAC Slave Boot 0111b
EMAC Forced-Mode Boot 1000b
Reserved 1001b Reserved
RapidIO Boot (Config 0) 1010b
RapidIO Boot (Config 1) 1011b
RapidIO Boot (Config 2) 1100b
RapidIO Boot (Config 3) 1101b
End of Table 2-3
www.ti.com
copies data from an I
table format. The destination address and length are contained within the boot table.
packets through the I2C interface. It is required that an I
TI Ethernet Boot. The C64x+ Megamodule configures EMAC and EDMA, if required, and brings the
code image into the internal on-chip memory via the protocol defined by the boot method (EMAC
bootloader).
The C64x+ Megamodule configures the SRIO and an external host loads the application via SRIO
peripheral, using directIO protocol. A doorbell interrupt is used to indicate that the code has been
loaded. For more details on the RapidIO configurations, see Table 2-4.
2
C EEPROM or a device acting as an I2C slave to the DSP using a predefined boot
2
C master is present in the system.
The C64x+ Megamodule configures Serial RapidIO, EMAC, and EDMA, if required, and brings the code image into
the internal on-chip memory via the protocol defined by the boot method (SRIO EMAC bootloader).
Bootmode 11 - Config 1 125 MHz 3.125 Gbps One 4× SRIO link
Bootmode 12 - Config 2 156.25 MHz 1.25 Gbps One 4× SRIO link
Bootmode 13 - Config 3 156.25 MHz 3.125 Gbps One 4× SRIO link
End of Table 2-4
All the other BOOTMODE[3:0] modes are reserved.
2.5.1 Second-Level Bootloaders
Any of the boot modes can be used to download a second-level bootloader. A second-level bootloader allows for any
level of customization to current boot methods as well as the definition of a completely customized boot.
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
2.8 Terminal Functions
The terminal functions table Table 2-6 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 pullup/pulldown resistors, see Section 3 ‘‘Device
Configuration’’ on page 59.
Use the symbol definitions in Table 2-5 when reading Table 2-6.
Table 2-5I/O Functional Symbol Definitions
Functional
Symbol
Internal 100-μA pulldown or pullup is provided for this terminal. In most systems, a 1-kΩ resistor can
IPD or IPU
AAnalog signalType
GNDGroundType
IInput terminalType
OOutput terminalType
SSupply voltageType
ZThree-state terminal or high impedanceType
End of Table 2-5
be used to oppose the IPD/IPU. For more detailed information on pulldown/pullup resistors and
situations in which external pulldown/pullup resistors are required, see Section 3.6 ‘‘Pullup/Pulldown
Resistors’’ on page 63.
Definition
Table 2-6
Column Heading
IPD/IPU
Table 2-6Terminal Functions (Part 1 of 22)
Signal NameBall No.TypeIPD/IPU Description
CLOCK/PLL CONFIGURATIONS
CORECLKN AH7 I Clock Input for PLL1 (differential).
CORECLKP AH6 I Clock Input for PLL1 (differential).
ALTCORECLK AF6 Alternate Core Clock (single-ended) input to main PLL [vs. CORECLK(N|P)].
Core Clock Select. Selects between CORECLK(N|P) and ALTCORECLK to the Main PLL.
CORECLKSEL AE6
SYSCLKOUT AD7 O/Z IPD SYSCLKOUT is the clock output at 1/10 (default rate) of the device speed.
DDRREFCLKN E6 I DDR Reference Clock Input to DDR PLL (differential).
DDRREFCLKP D6 I DDR Reference Clock Input to DDR PLL (differential).
ALTDDRCLK C6 I Alternate DDR Clock (single-ended) input to DDR PLL [vs. DDRREFCLK(N|P)].
DDRCLKSEL G6 I
RIOSGMIICLKN AG6 RapidIO/SGMII Reference Clock to drive the RapidIO and SGMII SerDes (differential).
RIOSGMIICLKP AG7 RapidIO/SGMII Reference Clock to drive the RapidIO and SGMII SerDes (differential).
• When CORECLKSEL = 0, it selects the differential clock [CORECLK(N|P)].
• When CORECLKSEL = 1, it selects the single-ended clock [ALTCORECLK].
DDR Clock Select. Selects between DDRREFCLK(N|P) and ALTDDRCLK to the DDR PLL.
• When DDRCLKSEL = 0, it selects the differential clock [DDRREFCLK(N|P)].
• When DDRCLKSEL = 1, it selects the single-ended clock [ALTDDRCLK].
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
Table 2-6Terminal Functions (Part 2 of 22)
Signal NameBall No.TypeIPD/IPU Description
TMS Y2 I IPU JTAG test-port mode select
TDO AF1 O/Z JTAG test-port data out
TDI AB1 I IPU JTAG test-port data in
TCK AH3I IPU JTAG test-port clock
AE2 I IPD
TRST
EMU0(3) AD5
EMU1(3) AE5 Emulation pin 1
PRODUCT PREVIEW
EMU2 AH5 Emulation pin 2
EMU3 AE4 Emulation pin 3
EMU4 AH4 Emulation pin 4
EMU5 AG4 Emulation pin 5
EMU6 AF4 Emulation pin 6
EMU7 AG2 Emulation pin 7
EMU8 AG3 Emulation pin 8
EMU9 AD4 Emulation pin 9
EMU10 AE3 Emulation pin 10
EMU11 AF2 Emulation pin 11
EMU12 AE1 Emulation pin 12
EMU13 AF3 Emulation pin 13
EMU14 AC1 Emulation pin 14
EMU15 AD1 Emulation pin 15
EMU16 AD3 Emulation pin 16
EMU17 AA1 Emulation pin 17
EMU18 AC2 Emulation pin 18
AH23 I Device reset
RESET
NMI AE19 I IPD
RESETSTAT
POR
AF23 O Reset Status pin. The RESETSTAT pin indicates when the device is in reset
AG22 I Power on reset.
I/O/Z IPU
RESETS, INTERRUPTS, AND GENERAL-PURPOSE INPUT/OUTPUTS
www.ti.com
JTAG EMULATION
JTAG test-port reset. For IEEE 1149.1 JTAG compatibility, see 7.22.3.1 ‘‘IEEE 1149.1 JTAG
Compatibility Statement’’ on page 206.
Emulation pin 0
Nonmaskable interrupt, edge-driven (rising edge).
NOTE: Any noise on the NMI pin may trigger an NMI interrupt. Therefore, if the NMI pin is not
used, it is recommended that the NMI pin be grounded instead of relying on the IPD.
N25 O IPU EMIFA hold-request-acknowledge to the host
R28 I IPU EMIFA hold request from the host
O/Z IPU
O/Z IPU
EMIFA (64-BIT) — ASYNCHRONOUS/SYNCHRONOUS MEMORY CONTROL
• When interfacing to 16-bit Asynchronous devices, ABA1 carries bit 1 of the byte address.
• For an 8-bit Asynchronous interface, ABA[1:0] are used to carry bits 1 and 0 of the byte address.
EMIFA memory space enables.
• Enabled by bits 28 through 31 of the word address
• Only one pin is asserted during any external data access
NOTE: The C6457 device does not have ACE0 and ACE1 pins.
EMIFA byte-enable control.
• 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.
EMIFA (64-BIT) — BUS ARBITRATION
EMIFA external input clock. The EMIFA input clock (AECLKIN or SYSCLK7 clock) is selected at
reset via the pullup/pulldown resistor on the GPIO[15] pin.
NOTE: AECLKIN is the default for the EMIFA input clock.
Programmable synchronous address strobe or read-enable
• For programmable synchronous interface, the R_ENABLE field in the Chip Select x
Configuration Register selects between ASADS and ASRE:
– If R_ENABLE = 0, then the ASADS/ASRE signal functions as the ASADS signal.
– If R_ENABLE = 1, then the ASADS/ASRE signal functions as the ASRE signal.
UXCLK A4 ISource clock for UTOPIA transmit driven by Master ATM Controller.
UXCLAV C3 O/Z
UXENB
B3 I
UXSOC G4 O/Z
PRODUCT PREVIEW
UXADDR4 J4
UXADDR3 H5
UXADDR2 K3
UXADDR1 J5
UXADDR0 H4
UXDATA7 F3
UXDATA6 E4
UXDATA5 C4
UXDATA4 A3
UXDATA3 H3
UXDATA2 G3
UXDATA1 F4
UXDATA0 E3
URCLK C1 I Source clock for UTOPIA receive driven by Master ATM Controller.
URCLAV B2 O/Z
K4 I
URENB
URSOC G2 I
URADDR4 K1
URADDR3 K2
URADDR2 J1
URADDR1 J3
URADDR0 H2
I
O/Z
UTOPIA SLAVE (ATM CONTROLLER) — RECEIVE INTERFACE
I
www.ti.com
Transmit cell available status output signal from UTOPIA Slave.
•0 indicates a complete cell is NOT available for transmit
• 1 indicates a complete cell is available for transmit
UTOPIA transmit interface enable input signal. Asserted by the Master ATM Controller to indicate
that the UTOPIA Slave should put out on the Transmit Data Bus the first byte of valid data and
the UXSOC signal in the next clock 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 8-bit Transmit Data Bus
(UXDATA[7:0]).
UTOPIA transmit address pins (UXADDR[4:0]) (I) 5-bit Slave transmit address input pins driven by
the Master ATM Controller to identify and select one of the Slave devices (up to 31 possible) in
the ATM System.
UTOPIA 8-bit transmit data bus (I/O/Z) Using the Transmit Data Bus, the UTOPIA Slave (on the
rising edge of the UXCLK) transmits the 8-bit ATM cells to the Master ATM Controller.
Receive cell available status output signal from UTOPIA Slave.
• 0 indicates NO space is available to receive a cell from Master ATM Controller.
• 1 indicates space is available to receive a cell from Master ATM Controller.
UTOPIA receive interface enable input signal. Asserted by the Master ATM Controller to indicate
to the UTOPIA Slave to sample the Receive Data Bus (URDATA[7:0]) and URSOC signal in the next
clock cycle or thereafter.
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 8-bit Receive Data
Bus (URDATA[7:0]).
UTOPIA receive address pins [URADDR[4:0] (I)]: 5-bit Slave receive address input pins driven by
the Master ATM Controller to identify and select one of the Slave devices (up to 31 possible) in
the ATM System.
Communications Infrastructure Digital Signal Processor
www.ti.com
Table 2-6Terminal Functions (Part 13 of 22)
Signal NameBall No.TypeIPD/IPU Description
URDATA7 G1
URDATA6 F2
URDATA5 F1
URDATA4 E2
URDATA3 E1
URDATA2 D2
URDATA1 D1
URDATA0 C2
RIORXN0 AG8
RIORXP0 AG9
RIORXN1 AF11
RIORXP1 AF10
RIORXN2 AH13
RIORXP2 AH12
RIORXN3 AE13
RIORXP3 AE12
RIOTXN0 AE9
RIOTXP0 AE8
RIOTXN1 AH9
RIOTXP1 AH10
RIOTXN2 AF13
RIOTXP2 AF14
RIOTXN3 AG13
RIOTXP3 AG14
SGMIIRXN AF16
SGMIIRXP AF17
SGMIITXN AH15
SGMIITXP AH14
MDIO AH19 I/O/Z IPU MDIO Data
MDCLK AH18 O IPD MDIO Clock
PTV18A16APTV Compensation NMOS Reference Input. Install with 47-Ω, 5% resistor to GND
U19A 1.1-V CVDD Supply Monitor
CV
DDMON
DV
DV
U22A3.3-V DV
DD33MON
G23A1.8-V DVDD Supply Monitor
DD18MON
I
I
O
I Ethernet MAC SGMII Receive Data
O Ethernet MAC SGMII Transmit Data
UTOPIA 8-bit Receive Data Bus (I/O/Z). Using the Receive Data Bus, the UTOPIA Slave (on the
rising edge of the URCLK) can receive the 8-bit ATM cell data from the Master ATM Controller.
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
2.9 Development
2.9.1 Development Support
In case the customer would like to develop their own features and software on the C6457 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.
•Hardware Development Tools:
–Extended Development System (XDS™) Emulator (supports C6000™ DSP multiprocessor system debug)
–EVM (Evaluation Module)
2.9.2 Device Support
2.9.2.1 Device 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.,
TMX320C6457CMH). Texas Instruments recommends two of three possible 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).
Device development evolutionary flow:
•TMX: Experimental device that is not necessarily representative of the final device's electrical specifications
•TMP: Final silicon die that conforms to the device's electrical specifications but has not completed quality and
reliability verification
•TMS: Fully qualified production device
Support tool development evolutionary flow:
•TMDX: Development-support product that has not yet completed Texas Instruments internal qualification
testing.
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 have been demonstrated fully. TI's standard warranty applies.
PRODUCT PREVIEW
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.
TI device nomenclature also includes a suffix with the device family name. This suffix indicates the package type (for
example, CMH), the temperature range (for example, blank is the default case temperature range), and the device
speed range, in megahertz (for example, blank is 1000 MHz [1 GHz]).
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
provides a legend for reading the complete device name for any TMS320C64x+™ DSP generation member.
For device part numbers and further ordering information for TMS320C6457 in the CMH package type, see the TI
website www.ti.com or contact your TI sales representative.
Figure 2-12TMS320C64x+™ DSP Device Nomenclature (including the TMS320C6457 DSP)
TMX320C6457
PREFIX
TMX = Experimental device
TMS = Qualified device
DEVICE FAMILY
320 = TMS320 DSP family
PRODUCT PREVIEW
DEVICE
C64x+ DSP: C6457
SILICON REVISION
Blank = Initial Silicon 1.1
A = Silicon Rev 1.2
B = Silicon Rev 1.3
C = Silicon Rev 1.4
()
CMH
()
()
850 MHz
1 GHz
1.2 GHz
www.ti.com
DEVICE SPEED RANGE
Blank=1GHz
2 = 1.2 GHz
8 = 850 MHz
TEMPERATURE RANGE
Blank = 0°C to +100°C (default case temperature)
Blank = 0°C to +100°C (default case temperature)
A = -40°C to +100°C
Blank = 0°C to +95°C (default case temperature)
A = -40°C to +95°C
PACKAGE TYPE
CMH = 688-pin plastic BGA, with Pb-Free solder balls
GMH = 688-pin plastic BGA, with Pb-ed solder balls
(A)
(A) BGA = Ball Grid Array
2.9.2.2 Documentation Support
The documents shown in Table 2-7 describe the TMS320C6457 Communications Infrastructure 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 TMS320C6457, related peripherals, and other technical collateral, is
available in the C6000 DSP product folder at: www.ti.com/c6000.
Table 2-7Relevant Documents (Part 1 of 2)
TI Literature No.Description
SPRU732 TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide. Describes the CPU architecture, pipeline, instruction set,
SPRU871 TMS320C64x+ Megamodule Reference Guide. Describes the TMS320C64x+ digital signal processor (DSP) megamodule.
SPRAA84 TMS320C64x to TMS320C64x+ CPU Migration Guide. Describes migrating from the Texas Instruments TMS320C64x digital
SPRU889High-Speed DSP Systems Design Reference Guide. Provides recommendations for meeting the many challenges of
SPRUGK5 TMS320C6457 DSP DDR2 Memory Controller User's Guide. This document describes the DDR2 memory controller in
SPRUGK6 TMS320C6457 DSP Enhanced DMA (EDMA3) Controller User's Guide. This document describes the Enhanced DMA (EDMA3)
SPRUGK2 TMS320C6457 DSP External Memory Interface (EMIF) User's Guide. This document describes the operation of the external
and interrupts for the TMS320C64x and TMS320C64x+ digital signal processors (DSPs) of the TMS320C6000 DSP family.
The C64x/C64x+ DSP generation comprises fixed-point devices in the C6000 DSP platform. The C64x+ DSP is an
enhancement of the C64x DSP with added functionality and an expanded instruction set.
Included is a discussion on the internal direct memory access (IDMA) controller, the interrupt controller, the power-down
controller, memory protection, bandwidth management, and the memory and cache.
signal processor (DSP) to the TMS320C64x+ DSP. The objective of this document is to indicate differences between the
two cores. Functionality in the devices that is identical is not included.
high-speed DSP system design. These recommendations include information about DSP audio, video, and
communications systems for the C5000 and C6000 DSP platforms.
the TMS320C6457 digital-signal processors (DSPs).
Controller on the TMS320C6457 device.
memory interface (EMIF) in the digital signal processors (DSPs) of the TMS320C6457 DSP family.
Communications Infrastructure Digital Signal Processor
www.ti.com
Table 2-7Relevant Documents (Part 2 of 2)
TI Literature No.Description
SPRUGL2 TMS320C6457 DSP General-Purpose Input/Output (GPIO) User's Guide. This document describes the general-purpose
SPRUGK7 TMS320C6457 DSP Host Port Interface (HPI) User's Guide. This guide describes the host port interface (HPI) on the
SPRUGK3TMS320C6457 DSP Inter-Integrated Circuit (I
SPRUGK4TMS320C6457 Serial RapidIO (SRIO) User's Guide. This document describes the Serial RapidIO (SRIO) on the TMS320C6457
SPRUGL3 TMS320C6457 DSP Software-Programmable Phase-Locked Loop (PLL) Controller UG. This document describes the operation
SPRUGL0 TMS320C6457 DSP 64-Bit Timer User's Guide. This document provides an overview of the 64-bit timer in the TMS320C6457
SPRUGK1 TMS320C6457 DSP Turbo-Decoder Coprocessor 2 (TCP2) Reference Guide. Channel decoding of high bit-rate data channels
SPRUGL1TMS320C6457 DSP Universal Test & Operations PHY Interface for ATM 2 (UTOPIA2) User's Guide. This document describes the
SPRUGK0TMS320C6457 DSP Viterbi-Decoder Coprocessor 2 (VCP2) Reference Guide. Channel decoding of voice and low bit-rate data
SPRUGK9TMS320C6457 DSP Ethernet Media Access Controller (EMAC) / Management Data Input Output (MDIO) User’s Guide. This
SPRUGK8TMS320C6457 DSP Multichannel Buffered Serial Port (McBSP) Reference Guide. This document describes the operation of the
SPRUGL4TMS320C6457 DSP Power/Sle ep Controller (PSC) User’s Guide. This document covers the usage of the Power/Sleep Controller
SPRUGL5TMS320C6457 DSP Bootloader User’s Guide. This document describes the features of the on-chip bootloader provided with
End of Table 2-7
input/output (GPIO) peripheral in the digital signal processors (DSPs) of the TMS320C6457 DSP family. The GPIO peripheral
provides dedicated general-purpose pins that can be configured as either inputs or outputs. When configured as an input,
you can detect the state of the input by reading the state of an internal register. When configured as an output, you can
write to an internal register to control the state driven on the output pin.
TMS320C6457 digital signal processors (DSPs). The HPI enables an external host processor (host) to directly access DSP
resources (including internal and external memory) using a 16-bit (HPI16) or 32-bit (HPI32) interface.
2
(I
C) module in the TMS320C6457 Digital Signal Processor (DSP). The I2C provides an interface between the TMS320C6457
device and other devices compliant with Philips Semiconductors Inter-IC bus (I
connected by way of an I
devices.
of the software-programmable phase-locked loop (PLL) controller in the TMS320C6457 digital signal processors (DSPs).
The PLL controller offers flexibility and convenience by way of software-configurable multipliers and dividers to modify
the input signal internally. The resulting clock outputs are passed to the TMS320C6457 DSP core, peripherals, and other
modules inside the TMS320C6457 DSP.
DSP. The timer can be configured as a general-purpose 64-bit timer, dual general-purpose 32-bit timers, or a watchdog
timer. When configured as a dual 32-bit timers, each half can operate in conjunction (chain mode) or independently
(unchained mode) of each other.
found in third generation (3G) cellular standards requires decoding of turbo-encoded data. The turbo-decoder
coprocessor (TCP) in some of the digital signal processor (DSPs) of the TMS320C6000™ DSP family has been designed to
perform this operation for IS2000 and 3GPP wireless standards. This document describes the operation and programming
of the TCP.
universal test and operations PHY interface for asynchronous transfer mode (ATM) 2 (UTOPIA2) in the TMS320C6457
digital signal processors (DSPs) of the TMS320C6000™ DSP family.
channels found in third generation (3G) cellular standards requires decoding of convolutional encoded data. The
Viterbi-decoder coprocessor 2 (VCP2) provided in TMS320C6457 devices has been designed to perform Viterbi-Decoding
for IS2000 and 3GPP wireless standards. The VCP2 coprocessor has been designed to perform forward error correction for
2G and 3G wireless systems. The VCP2 coprocessor offers a very cost effective and synergistic solution when combined
with Texas Instruments (TI) DSPs. The VCP2 can support 1941 12.2 Kbps class A 3G voice channels running at 333 MHz. This
document describes the operation and programming of the VCP2.
document provides a functional description of the Ethernet Media Access Controller (EMAC) and Physical layer (PHY)
device Management Data Input/Output (MDIO) module integrated with TMS320C6457 devices. Included are the features
of the EMAC and MDIO modules, a discussion of their architecture and operation, how these modules connect to the
outside world, and the registers description for each module.
multichannel buffered serial port (McBSP) in the digital signal processors (DSPs) of the TMS320C6000™ DSP family.
(PSC) in the TMS320C6457 device.
the TMS320C6457 Digital Signal Processor (DSP).
2
C-bus. This document assumes the reader is familiar with the I2C-bus specification.
2
C) Module User's Guide. This document describes the inter-integrated circuit
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
3 Device Configuration
On the TMS320C6457 device, certain device configurations like boot mode and endianess, are selected at device
power-on reset. The status of the peripherals (enabled/disabled) is determined after device power-on reset. By
default, the peripherals on the C6457 device are disabled and need to be enabled by software before being used.
3.1 Device Configuration at Device Reset
Table 3-1 describes the C6457 device configuration pins. The logic level is latched at power-on 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 device configuration pins are sampled during power-on reset and are driven after the reset is
removed. To avoid contention, the control device must stop driving the device configuration pins of the DSP.
Note—If a configuration pin must be routed out from the device and it is not driven (Hi-Z state), the
internal pullup/pulldown (IPU/IPD) resistor should not be relied upon. TI recommends the use of an
external pullup/pulldown resistor. For more detailed information on pullup/pulldown resistors and
situations in which external pullup/pulldown resistors are required, see Section 3.6 ‘‘Pullup/Pulldown
Resistors’’ on page 63.
Table 3-1TMS320C6457 Device Configuration Pins
Configuration Pin No. IPD/IPU
GPIO[0]
A5IPU
GPIO[4:1]
GPIO[8:5] [B25,
GPIO[13:9] [C23,
GPIO[14]
GPIO[15]
CORECLKSEL
DDRCLKSEL
End of Table 3-1
1 Internal 100-μA pulldown or pullup is provided for this terminal. In most systems, a 1-kΩ resistor can be used to oppose the IPD/IPU. For more detailed information on
pulldown/pullup resistors and situations in which external pulldown/pullup resistors are required, see Section 3.6 ‘‘Pullup/Pulldown Resistors’’ on page 63.
[B5,
B4, D5,
E5]
F5, C5,
F6]
D24,
C25,
A25,
C24]
D23IPD
F23IPD
AE6
G6
(1)
Functional Description
Device Endian mode (LENDIAN)
0 = Device operates in Big Endian mode.
1 = Device operates in Little Endian mode (default).
IPD
IPD Device Number (DEVNUM[3:0])
IPD
Boot Mode Selection (BOOTMODE [3:0])
These pins select the boot mode for the device. For more information on the boot modes, see Section
2.4 ‘‘Boot Sequence’’ on page 21.
Configuration General-Purpose Inputs (CFGGP[4:0])
The value of these pins is latched to the Device Status Register following power-on reset and is used by
the software.
HPI peripheral bus width select (HPIWIDTH)
0 = HPI operates in HPI16 mode (default).
HPI bus is 16 bits wide; HD[15:0] pins are used and the remaining HD[31:16] pins are reserved pins in
the Hi-Z state.
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
www.ti.com
3.2 Peripheral Selection After Device Reset
Several of the peripherals on the TMS320C6457 are controlled by the Power Sleep Controller (PSC). By default, the
SRIO, TCP2_A, TCP2_B, and VCP are held in reset and clock-gated. The memories in these modules are also in a
low-leakage sleep mode. Software is required to turn these memories on. Then, the software enables the modules
(turns on clocks and de-asserts reset) before these modules can be used.
In addition, the EMIFA, HPI, and UTOPIA come up clock-gated and held in reset. Memories in these modules are
already enabled. Software is required to enable these modules before they are used as well.
If one of the above modules is used in the selected ROM boot mode, the ROM code will automatically enable the
module.
PRODUCT PREVIEW
All other modules come up enabled by default and there is no special software sequence to enable. For more detailed
information on the PSC usage, see the TMS320C6457 DSP Power/Sleep Controller PSC User's Guide (literature
number SPRUGL4).
3.3 Device State Control Registers
The C6457 device has a set of registers that are used to control the status of its peripherals. These registers are shown
in Table 3-2 and described in the next sections.
Table 3-2Device State Control Registers
Hex Address Range Acronym Description
0288 0818 JTAGID
0288 081C -Reserved
0288 0820 DEVSTATStores parameters latched from configuration pins
0288 0824 - 0288 0837 -Reserved
0288 0838 KICK0
0288 083C KICK1
0288 0840 DSP_BOOT_ADDR DSP boot address
0288 0844 - 0288 090F -Reserved
0288 0910 DEVCFGParameters set through software for device configuration
0288 0914MACID1EFUSE derived MAC address for C6457
0288 0918MACID2EFUSE derived MAC address for C6457
0288 0922 - 0288 091B -Reserved
0288 091C PRI_ALLOCSets priority for Master peripherals
0288 0920 WDRSTSELReset select for Watchdog (Timer1)
End of Table 3-2
1 Writes are conditional based on valid keys written to both the KICK0 and KICK1 registers.
(1)
Parameters for DSP device ID. Also referred to as JTAG or BSDL ID. These are readable by the
configuration bus and can be accessed via the JTAG and the CPU.
Two successive key writes are required to get write access to any of the device state control
register s. KICK0 is th e first key re gister. The written data must be 0x83E70B13 to unlock it and it must
be written before the KICK1 register. Writing any other value will lock the device state control
registers.
KICK1 is the second key register to be unlocked in order to get write access to any of the device state
control registers. The written data must be 0x95A4F1E0 to unlock it and it must be written after the
KICK0 register. Writing any other value will lock the device state control registers.
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
3.4 Device Status Register Description
The device status register depicts the device configuration selected upon power-on reset. Once set, these bits will
remain set until a power-on reset. For the actual register bit names and their associated bit field descriptions, see
Table 3-4 and Table 3-5.
Table 3-3 shows the parameters that are set through software to configure different components on the device. The
configuration is done through the device configuration DEVCFG register, which is one-time writeable through
software. The register is reset on all hard resets and is locked after the first write.
Table 3-3Device Configuration Register Fields
Field Reset Description Settings
Device Configuration 1 Register Fields
CLKS0 0b McBSP0 CLKS Select 0 = CLKS0 device pin
1 = chip_clks from Main.PLL
CLKS1 0b McBSP1 CLKS Select 0 = CLKS1 device pin
1 = chip_clks from Main.PLL
SYSCLKOUTEN 1b SYSCLKOUT Enable 0 = No clock output
1 = Clock output enabled
End of Table 3-3
Table 3-4Device Configuration Status Register (DEVSTAT)
1 = System is operating in Little Endian mode (default)
C Master Boot (Slave Address 0x50)
2
C Master Boot (Slave Address 0x51)
2
C Slave Boot
www.ti.com
3.5 JTAG ID (JTAGID) Register Description
The JTAG ID register is a read-only register that identifies to the customer the JTAG/Device ID. For the C6457
device, the JTAG ID register resides at address location 0x0288 0818. For the actual register bit names and their
associated bit field descriptions, see Table 3-6 and Table 3-7.
Table 3-6JTAG ID (JTAGID) Register
HEX ADDRESS - 0288 0818h
Bit31302928272625242322212019181716
AcronymVARIANTPART NUMBER (16-bit)
(1)
Reset
Bit1514131211109876543210
AcronymPART NUMBER (Continued)MANUFACTURERLSB
(1)
Reset
1 R/W = Read/Write; R = Read only; -n = value after reset
Table 3-7JTAG ID (JTAGID) Register Field Descriptions
BitAcronymValueDescription
31:28VARIANT0000Variant (4-Bit) value. The value of this field depends on the silicon revision being used.
27:12PART NUMBER0000 0000 1001 0110bPart Number for boundary scan
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
3.6 Pullup/Pulldown Resistors
Proper board design should ensure that input pins to the C6457 device always be at a valid logic level and not
floating. This may be achieved via pullup/pulldown resistors. The C6457 device features internal pullup (IPU) and
internal pulldown (IPD) resistors on most pins to eliminate the need, unless otherwise noted, for external
pullup/pulldown resistors.
An external pullup/pulldown resistor needs to be used in the following situations:
•Device Configuration Pins: If the pin is both routed out and are not driven (in Hi-Z state), an external
pullup/pulldown resistor must be used, even if the IPU/IPD matches the desired value/state.
•Other Input Pins: If the IPU/IPD does not match the desired value/state, use an external pullup/pulldown
resistor to pull the signal to the opposite rail.
For the device configuration pins (listed in Table 3-1), if they are both routed out and are not driven (in Hi-Z state),
it is strongly recommended that an external pullup/pulldown resistor be implemented. Although, internal
pullup/pulldown resistors exist on these pins and they may match the desired configuration value, providing
external connectivity can help ensure that valid logic levels are latched on these device configuration pins. In
addition, applying external pullup/pulldown resistors on the device configuration pins adds convenience to the user
in debugging and flexibility in switching operating modes.
Tips for choosing an external pullup/pulldown resistor:
•Consider the total amount of current that may pass through the pullup or pulldown resistor. Make sure to
include the leakage currents of all the devices connected to the net, as well as any internal pullup or pulldown
resistors.
•Decide a target value for the net. For a pulldown resistor, this should be below the lowest V
connected to the net. For a pullup resistor, this should be above the highest V
A reasonable choice would be to target the V
by definition, have margin to the V
and VIH levels.
IL
or VOH levels for the logic family of the limiting device; which,
OL
level of all inputs on the net.
IH
•Select a pullup/pulldown resistor with the largest possible value that can still ensure that the net will reach the
target pulled value when maximum current from all devices on the net is flowing through the resistor. The
current to be considered includes leakage current plus, any other internal and external pullup/pulldown
resistors on the net.
•For bidirectional nets, there is an additional consideration that sets a lower limit on the resistance value of the
external resistor. Verify that the resistance is small enough that the weakest output buffer can drive the net to
the opposite logic level (including margin).
•Remember to include tolerances when selecting the resistor value.
•For pullup resistors, also remember to include tolerances on the DV
DD
rail.
level of all inputs
IL
PRODUCT PREVIEW
For most systems:
•A 1-kΩ resi stor can b e used to op pos e the IPU/I PD wh ile meeting the above criteria. Users should confirm this
resistor value is correct for their specific application.
•A 20-kΩ resistor can be used to compliment the IPU/IPD on the device configuration pins while meeting the
above criteria. Users should confirm this resistor value is correct for their specific application.
For more detailed information on input current (I
), and the low-level/high-level input voltages (VIL and VIH) for
I
the TMS320C6457 device, see Section 6.3 ‘‘Electrical Characteristics’’ on page 89.
To determine which pins on the C6457 device include internal pullup/pulldown resistors, seeTable 2-6 ‘‘Terminal
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
4 System Interconnect
On the TMS320C6457 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 master peripherals and slave peripherals; for example, through a switch fabric the CPU can send data to the
Viterbi co-processor (VCP2) without affecting a data transfer between the HPI and the DDR2 memory controller.
The switch fabrics also allow for seamless arbitration between the system masters when accessing system slaves.
4.1 Internal Buses, Bridges, and Switch Fabrics
Two types of buses exist in the C6457 device: data buses and configuration buses. Some C6457 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. However, in some cases, the
configuration bus is also used to transfer data. For example, data is transferred to the VCP2 and TCP2 via their
configuration bus. Similarly, the data bus can also be used to access the register space of a peripheral. For example,
the EMIFA and DDR2 memory controller registers are accessed through their data bus interface.
The C64x+ Megamodule, the EDMA3 traffic 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. Examples of masters
include the EDMA3 traffic controllers, SRIO, EMAC, and HPI. Examples of slaves include the McBSP, UTOPIA,
2
C.
and I
The C6457 device contains two switch fabrics through which masters and slaves communicate. The data switch
fabric, known as the data switched central resource (SCR), is a high-throughput interconnect mainly used to move
data across the system (for more information, see Section 4.2 ‘‘Data Switch Fabric Connections’’). The data SCR
connects masters to slaves via 128-bit data buses running at a SYSCLK4 frequency (SYSCLK4 is generated from PLL
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 switch fabric, also known as the configuration switch central resource (SCR), is mainly used by
the C64x+ Megamodule to access peripheral registers (for more information, see Section 4.3 ‘‘Configuration Switch
Fabric’’). The configuration SCR connects C64x+ Megamodule to slaves via 32-bit configuration buses running at a
SYSCLK4 frequency (SYSCLK4 is generated from PLL controller). 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.
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, the EMIFA requires a bridge to convert its 64-bit data bus interface into a 128-bit interface so that it
can connect to the data SCR. In the case of the TCP2 and VCP2, a bridge is required to connect the data SCR to the
64-bit configuration bus interface.
Note that some peripherals can be accessed through the data SCR and also through the configuration SCR.
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
www.ti.com
4.2 Data Switch Fabric Connections
Figure 4-1 shows the connection between slaves and masters through the data switched central resource (SCR).
Masters are shown on the left and slaves on the right. The data SCR connects masters to slaves via 128-bit data buses
running at a SYSCLK4 frequency. SYSCLK4 is supplied by the PLL controller and is fixed at a frequency equal to the
CPU frequency divided by 3.
Figure 4-1Data Switched Central Resource Block Diagram
Communications Infrastructure Digital Signal Processor
www.ti.com
Masters are shown on the left and slaves on the right. The data SCR connects masters to slaves via 128-bit data buses
running at a SYSCLK4 frequency. SYSCLK4 is supplied by the PLL controller and is fixed at a 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.3 ‘‘Configuration Switch Fabric’’.
Not all masters on the C6457 DSP may connect to all slaves. Allowed connections are summarized in Table 4-1.
Table 4-1SCR Connection Matrix
Configuration
VCP2 TCP2_ATCP2_BMcBSPsL3 ROMUTOPIA
TC0 Y Y Y N N N N Y Y Y
TC1 N N Y Y Y N N Y Y Y
TC2 N N N Y Y Y Y Y Y Y
TC3 N N N N N Y Y Y Y Y
TC4 N N N N N N Y Y Y Y
TC5 N N N N N N Y Y Y Y
EMAC N N N N N N N Y Y Y
HPI N N N N N N Y Y Y Y
(1)
SRIO
Megamodule Y Y Y Y Y Y N Y Y N
End of Table 4-1
1 Applies to both descriptor and data accesses by the SRIO peripheral.
N N N N N N Y Y Y Y
SCR
DDR2 Memory
Controller
SPRS582B—July 2010
EMIFAMegamodule
PRODUCT PREVIEW
4.3 Configuration Switch Fabric
Figure 4-2 shows the connection between the C64x+ Megamodule and the configuration switched central resource
(SCR). The configuration SCR is mainly used by the C64x+ Megamodule 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 device configuration registers
and the PLL controller registers; these can only be accessed by the C64x+ Megamodule.
The configuration SCR uses 32-bit configuration buses running at SYSCLK4 frequency. SYSCLK4 is supplied by the
PLL controller and is fixed at a frequency equal to the CPU frequency divided by 3.
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
4.4 Bus Priorities
On the TMS320C6457 device, bus priority is programmable for each master. The register bit fields and default
priority levels for C6457 bus masters are shown in Table 4-2.
Table 4-2TMS320C6457 Default Bus Master Priorities
Bus Master Default Priority Level Priority Control
The priority levels should be tuned to obtain the best system performance for a particular application. Lower values
indicate higher priorities. For some masters, the priority values are programmed at the system level by configuring
the PRI_ALLOC register. Details on the PRI_ALLOC register are shown in Table 4-3 and Table 4-4. The C64x+
megamodule, SRIO, and EDMA masters contain registers that control their own priority values.
Table 4-3Priority Allocation Register (PRI_ALLOC)
0x0288 091C
Bit31302928272625242322212019181716
Acronym
(1)
Reset
Bit1514131211109876543210
Acronym
(1)
Reset
1 R/W = Read/Write; R = Read only; -n = value after reset
ReservedHPISRIO_CPPIEMAC
R-0000 000R/W-010R/W-001R/W-001
Table 4-4Priority Allocation Register (PRI_ALLOC) Field Descriptions
BitAcronymValueDescription
31:16Reserved0000 0000 0000 0000Reserved.
15:9Reserved0000 000Reserved.
8:6HOST010Priority of the HPI peripheral.
5:3SRIO_CPPI001Priority of the Serial RapidIO when accessing descriptors from system memory. This priority is set
2:0EMAC001Priority of the EMAC peripheral.
End of Table 4-4
in the peripheral, itself.
Reserved
R-0000 0000 0000 0000
PRODUCT PREVIEW
The priority is enforced when several masters in the system are vying for the same endpoint. Note that the
configuration SCR port on the data SCR is considered a single endpoint meaning priority will be enforced when
multiple masters try to access the configuration SCR. Priority is also enforced on the configuration SCR side when
a master (through the data SCR) tries to access the same endpoint as the C64x+ megamodule.
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
In the PRI_ALLOC register, the HOST field applies to the priority of the HPI peripheral. The EMAC fields specify
the priority of the EMAC peripheral. The SRIO_CPPI field is used to specify the priority of the Serial RapidIO when
accessing descriptors from system memory. The priority for Serial RapidIO data accesses is set in the peripheral
itself.
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
5 C64x+ Megamodule
The C64x+ Megamodule consists of several components:
•The C64x+ CPU and associated C64x+ Megamodule core
•Level-one and level-two memories (L1P, L1D, L2)
•Interrupt controller
•Power-down controller
•External memory controller
•A dedicated power/sleep controller (LPSC)
The C64x+ Megamodule also provides support for memory protection and bandwidth management (for resources
local to the C64x+ Megamodule). Figure 5-1 shows a block diagram of the C64x+ Megamodule.
Figure 5-164x+ Megamodule Block Diagram
32KB L1P
Memory Controller (PMC) With
Memory Protect/Bandwidth Mgmt
Boot
Controller
LPSCPLLC
GPSC
C64x+ DSP Core
Instruction Fetch
16-/32-bit Instruction Dispatch
Control Registers
In-Circuit Emulation
Instruction Decode
Data Path A
A Register File
A31-A16
A15-A0
.M1
.L1.S1
xxxx.D1.D2
Data Memory Controller (DMC) With
Memory Protect/Bandwidth Mgmt
B Register File
32KB L1D
Data Path B
B31-B16
B15-B0
.M2
xxxx.S2.L2
Interrupt and Exception Controller
Unified Memory
Controller (UMC)
Controller (EMC)
External Memory
L2 Cache/
SRAM
2048KB
PRODUCT PREVIEW
DMA Switch
Fabric
CFG Switch
Fabric
For more detailed information on the TMS320C64x+ megamodule on the C6457 device, see the TMS320C64x+
Megamodule Reference Guide (literature number SPRU871).
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
5.1 Memory Architecture
The TMS320C6457 device contains a 2048KB level-2 memory (L2), a 32KB level-1 program memory (L1P), and a
32KB level-1 data memory (L1D). All memory on the C6457 has a unique location in the memory map (see
Table 2-2 ‘‘TMS320C6457 Memory Map Summary’’ on page 19).
After device reset, L1P and L1D cache are configured as all cache, by default. The L1P and L1D cache can be
reconfigured via software through the L1PMODE field of the L1P Configuration Register (L1PMODE) and the
L1DMODE field of the L1D Configuration Register (L1DCFG) of the C64x+ Megamodule. L1D is a two-way
set-associative cache, while L1P is a direct-mapped cache.
The on-chip bootloader changes the reset configuration for L1P and L1D. For more information, see the
TMS320C6457 Bootloader User's Guide (literature number SPRUGL5).
PRODUCT PREVIEW
For more information on the operation L1 and L2 caches, see the TMS320C64x+ DSP Cache User's Guide (literature
number SPRU862).
5.1.1 L1P Memory
The L1P memory configuration for the C6457 device is as follows:
•Region 0 size is 0K bytes (disabled)
•Region 1 size is 32K bytes with no wait states
www.ti.com
Figure 5-2 shows the available SRAM/cache configurations for L1P.
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
5.1.3 L2 Memory
The L2 memory configuration for the C6457 device is as follows:
•Memory size is 2048KB
•Starting address is 0080 0000h
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.
Communications Infrastructure Digital Signal Processor
www.ti.com
5.1.4 L3 Memory
The L3 ROM on the device is 64KB. The contents of the ROM are divided into two partitions. The first is the ROM
bootloader with the primary purpose of containing software to boot the device. There is no requirement to block
accesses from this portion to the ROM. The second partition is the secure portion of ROM, which has a secure kernel
that is necessary for support of security features on the device. The secure portion of ROM cannot be accessed both
on secure, and non-secure parts. Only secure supervisors should have access.
Emulation accesses follows the same rules of the secure portion of the ROM. Emulation can access the non-secure
portion of the ROM, but cannot read the secure portion of the ROM.
SPRS582B—July 2010
5.2 Memory Protection
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 64 pages of L2 (32KB each). 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.
Each page may be assigned with fully orthogonal user and supervisor read, write, and execute permissions. In
addition, a page may be marked as either (or both) locally accessible 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. Note that EDMA or IDMA transfers programmed by the CPU count as global accesses. On a
secure device, pages can be restricted to secure access only (default) or opened up for public, non-secure access.
The CPU and each of the system masters on the device are all assigned a privilege ID (see Table 5-1). It is only
possible to specify whether memory pages are locally or globally accessible.
Table 5-1Available Memory Page Protection Scheme With Privilege ID
Privid Module Description
0 C64x+ Megamodule
1 Reserved
2 Reserved
3 EMAC
4 RapidIO and RapidIO CPPI
5 HPI
End of Table 5-1
The AID0 and LOCAL bits of the memory protection page attribute registers specify the memory page protection
scheme, see Table 5-2.
Table 5-2Available Memory Page Protection Schemes
AID0 Bit Local Bit Description
0 0 No access to memory page is permitted.
0 1 Only direct access by CPU is permitted.
1 0 Only accesses by system masters and IDMA are permitted (includes EDMA and IDMA accesses initiated by the CPU).
1 1 All accesses permitted
PRODUCT PREVIEW
Faults are handled by software in an interrupt (or an exception, programmable within the C64x+ 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 ignored
•Capture the initiator in a status register — ID, address, and access type are stored
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
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+ Megamodule Reference Guide (literature number SPRU871).
5.3 Bandwidth Management
When multiple requestors contend for a single C64x+ Megamodule resource, the conflict is resolved 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
PRODUCT PREVIEW
•Memory-mapped registers configuration bus
The priority level for operations initiated within the C64x+ Megamodule are declared through registers in the C64x+
Megamodule. These operations are:
•CPU-initiated transfers
•User-programmed cache coherency operations
•IDMA-initiated transfers
www.ti.com
The priority level for operations initiated outside the C64x+ Megamodule by system peripherals is declared through
the Priority Allocation Register (PRI_ALLOC), see Section 4.4 ‘‘Bus Priorities’’ on page 69. System peripherals with
no fields in PRI_ALLOC have their own registers to program their priorities.
More information on the bandwidth management features of the C64x+ Megamodule can be found in the
TMS320C64x+ Megamodule Reference Guide (literature number SPRU871.)
5.4 Power-Down Control
The C64x+ Megamodule supports the ability to power-down various parts of the C64x+ Megamodule. The
power-down controller (PDC) of the C64x+ Megamodule can be used to power down L1P, the cache control
hardware, the CPU, and the entire C64x+ Megamodule. These power-down features can be used to design systems
for lower overall system power requirements.
Note—The C6457 does not support power-down modes for the L2 memory at this time.
More information on the power-down features of the C64x+ Megamodule can be found in the TMS320C64x+
Megamodule Reference Guide (literature number SPRU871).
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
5.5 Megamodule Resets
Table 5-3 shows the reset types supported on the C6457 device and they affect the resetting of the Megamodule,
either both globally or just locally.
Table 5-3Megamodule Reset (Global or Local)
Reset Type Global Megamodule Reset Local Megamodule Reset
Power-On Reset Y Y
Warm Reset Y Y
System Reset Y Y
CPU Reset N Y
End of Table 5-3
For more detailed information on the global and local Megamodule resets, see the TMS320C64x+ Megamodule
Reference Guide (literature number SPRU871). And for more detailed information on device resets, see Section
7.6 ‘‘Reset Controller’’ on page 123.
5.6 Megamodule Revision
The version and revision of the C64x+ Megamodule can be read from the Megamodule Revision ID Register
(MM_REVID) located at address 0181 2000h. The MM_REVID register is shown in Table 5-4 and described in
Table 5-5. The C64x+ Megamodule revision is dependant on the silicon revision being used.
Table 5-4Megamodule Revision ID Register (MM_REVID)
Address - 0181 2000h
Bit31302928272625242322212019181716
Acronym
(1)
Reset
Bit1514131211109876543210
Acronym
(1)
Reset
1 R/W = Read/Write; R = Read only; -n = value after reset
Table 5-5Megamodule Revision ID Register (MM_REVID) Field Descriptions
BitAcronymValueDescription
31:16VERSION5hVersion of the C64x+ Megamodule implemented on the device. This field is always read as 5h.
15:0REVISION-Revision of the C64x+ Megamodule version implemented on the device.
End of Table 5-5
VERSION
R-5h
REVISION
R-n
5.7 C64x+ Megamodule Register Descriptions
Table 5-6Megamodule Interrupt Registers (Part 1 of 2)
Hex Address Range Acronym Register Name
0180 0000 EVTFLAG0 Event Flag Register 0 (Events [31:0])
0180 0004 EVTFLAG1 Event Flag Register 1
0180 0008 EVTFLAG2 Event Flag Register 2
0180 000C EVTFLAG3 Event Flag Register 3
0180 0010 - 0180 001C -Reserved
0180 0020 EVTSET0 Event Set Register 0 (Events [31:0])
1 These addresses correspond to the L2 memory protection page attribute registers 32-63 (L2MPPA32 - L2MPPA63) of the C64x+ Megamodule. These registers are not
supported for the C6457 device.
2 These addresses correspond to the L1P memory protection page attribute registers 0-15 (L1PMPPA0 - L1PMPPA15) of the C64x+ Megamodule. These registers are not
supported for the C6457 device.
3 These addresses correspond to the L1D memory protection page attribute registers 0-15 (L1DMPPA0 - L1DMPPA15) of the C64x+ Megamodule. These registers are not
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
6 Device Operating Conditions
Based on JESD22-C101C (Field-Induced Charged-Device Model Test Method for
Electrostatic-Discharge-Withstand Thresholds of Microelectronic Components), the TMS320C6457 device’s
charged-device model (CDM) sensitivity classification is Class II (200 V to < 500 V). Specifically, DDR memory
interface and SerDes pins conform to ±200-V level. All other pins conform to ±500 V.
6.1 Absolute Maximum Ratings
Table 6-1Absolute Maximum Ratings
(1)
Over Operating Case Temperature Range (Unless Otherwise Noted)
CVDD -0.3 V to 1.35 V
-0.3 V to 2.45 V
DV
DD18
-0.3 V to 3.60V
DV
DD33
Supply voltage range
0.49 × DV
V
(2)
:
REFSSTL
V
, V
, V
DD11
DDD11
-0.3 V to 2.45 V
V
DDR18
, AV
AV
DD118
DD218
Ground 0 V
V
SS
-0.3 V to 1.35 V
DDT11
LVCMOS (1.8V)-0.3 V to DV
LVCMOS (3.3V)-0.3 V to DV
to 0.51 × DV
DD18
DD18
-0.3 V to 2.45 V
+ 0.3 V
DD18
+ 0.3 V
DD33
DDR2 -0.3 V to 2.45 V
Input voltage (V
) range:
I
2
C-0.3 V to 2.45 V
I
LVDS -0.3 V to D
VDD18
+ 0.3 V
LJCB -0.3 V to 1.35 V
VDD11
DD18
DD33
DD11
+ 0.3 V
+ 0.3 V
+ 0.3 V
+ 0.3 V
Output voltage (V
) range:
O
SerDes -0.3 V to D
LVCMOS (1.8V)-0.3 V to DV
LVCMOS (3.3V)-0.3 V to DV
DDR2 -0.3 V to 2.45 V
2
C -0.3 V to 2.45 V
I
SerDes -0.3 V to DV
850 MHz CPU0°C to 100°C
Operating case temperature range, T
Commercial
:
C
Extended
1-GHz CPU0°C to 100°C
1.2-GHz CPU0°C to 95°C
1-GHz CPU-40°C to 100°C
1.2-GHz CPU-40°C to 95°C
LVCMOS (1.8V)
(3)
Overshoot/undershoot
Storage temperature range, T
LVCMOS (3.3V)
DDR2
2
I
C
: -65°C to 150°C
stg
20% Overshoot/Undershoot for 20% of
Signal Duty Cycle
End of Table 6-1
1 Stresses beyond those listed under "absolute maximum ratings" may cause permanent damage to the device. These are stress ratings only, and functional operation of the
device at these or any other conditions beyond those indicated under "recommended operating conditions" is not implied. Exposure to absolute-maximum-rated
conditions for extended periods may affect device reliability.
2 All voltage values are with respect to VSS.
3 Overshoot/Undershoot percentage relative to I/O operating values - for example the maximum overshoot value for 1.8-V LVCMOS signals is DV
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
6.2 Recommended Operating Conditions
www.ti.com
Table 6-2Recommended Operating Conditions
Supply core voltage
CV
DD
1.8-V supply I/O voltage 1.711.81.89V
DV
DD18
3.3-V supply I/O voltage 3.1353.33.465V
DV
DD33
DDR2 reference voltage 0.49 × DV
V
REFSSTL
V
DDR18
V
PRODUCT PREVIEW
DDA11
V
DDD11
V
DDT11
PLLV
PLLV
Ground 000V
V
SS
V
IH
V
IL
Operating case temperature
T
C
End of Table 6-2
1 All differential clock inputs comply with the LVDS Electrical Specification, IEEE 1596.3-1996 and all SerDes I/Os comply with the XAUI Electrical Specification, IEEE
802.3ae-2002.
2 All SerDes I/Os comply with the XAUI Electrical Specification, IEEE 802.3ae-2002.
1 For test conditions shown as MIN, MAX, or TYP, use the appropriate value specified in the recommended operating conditions table.
2II applies to input-only pins and bi-directional pins. For input-only pins, II indicates the input leakage current. For bi-directional pins, II includes input leakage current and
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
Table 6-4Power Supply to Peripheral I/O Mapping
Over Recommended Ranges of Supply Voltage and Operating Case Temperature (Unless Otherwise Noted)2
Power SupplyI/O Buffer TypeAssociated Peripheral
Supply core voltageLJCB
CV
DD
DV
1.8-V supply I/O voltage
PRODUCT PREVIEW
DD18
3.3-V supply I/O voltage LVCMOS (3.3 V)
DV
DD33
SRIO/SGMII SerDes analog supply CMLSRIO/SGMII SerDes CML I/O buffer
V
DDA11
End of Table 6-4
1 Please note that this table does not attempt to describe all functions of all power supply terminals but only those whose purpose it is to power peripheral I/O buffers and
clock input buffers.
2 Please see the TMS320TCI6484 and TMS320C6457 DSPs Hardware Design Guide(SPRAAV7) for more information about individual peripheral I/O.
Communications Infrastructure Digital Signal Processor
www.ti.com
SPRS582B—July 2010
7 C64x+ Peripheral Information and Electrical Specifications
This chapter describes the various peripherals on the TMS320C6457 DSP. Peripheral specific information, timing
diagrams, electrical specifications and register memory maps are described in this chapter.
7.1 Parameter Information
This section describes the conditions used to capture the electrical data seen in this chapter.
Figure 7-1Test Load Circuit for AC Timing Measurements
Tester Terminal Electronics
42 W
4.0 pF1.85 pF
(A) The data manual provides timing at the device terminal. For output timing analysis, the tester terminal electronics and its transmission line effects must be taken into
account. A transmission line with a delay of 2 ns can be used to produce the desired transmission line effect. The transmission line is intended as a load only. It is not
necessary to add or subtract the transmission line delay (2 ns) from the data sheet timings.
(B) Input requirements in this data sheet are tested with an input slew rate of < 4 Volts per nanosecond (4 V/ns) at the device terminal.
3.5 nH
Transmission Line
Zo=50W
(see Note A)
Data Manual Timing Reference Point
Output Under Test
Device Terminal
(see Note B)
The load capacitance value stated is only for characterization and measurement of AC timing signals. This load
capacitance value does not indicate the maximum load the device is capable of driving.
7.1.1 1.8-V Signal Transition Levels
All input and output timing parameters are referenced to 0.9 V for both 0 and 1 logic levels.
Figure 7-2Input and Output Voltage Reference Levels for 1.8-V AC Timing Measurements
V = 0.9 V
ref
PRODUCT PREVIEW
All rise and fall transition timing parameters are reference to VIL MAX and VIH MIN for input clocks.
Figure 7-3Rise and Fall Transition Time Voltage Reference Levels
V = V MIN (or VMIN)
refIHOH
2009 Texas Instruments IncorporatedC64x+ Peripheral Information and Electrical Specifications91
TMS320C6457
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
7.1.2 3.3-V Signal Transition Levels
All input and output timing parameters are referenced to 1.5 V for both 0 and 1 logic levels.
Figure 7-4Input and Output Voltage Reference Levels for 3.3-V AC Timing Measurements
V = 1.5 V
ref
www.ti.com
All rise and fall transition timing parameters are referenced to VIL MAX and VIH MIN for input clocks, V
and V
Figure 7-5Rise and Fall Transition Time Voltage Reference Levels
MIN for output clocks.
OH
PRODUCT PREVIEW
7.1.3 3.3-V Signal Transition Rates
All timings are tested with an input edge rate of 4 volts per nanosecond (4 V/ns).
7.1.4 Timing Parameters and Board Routing Analysis
The timing parameter values specified in this data sheet do not include delays by board routings. As a good board
design practice, such delays must always be taken into account. Timing values may be adjusted by
increasing/decreasing such delays. TI recommends using the available I/O buffer information specification (IBIS)
models to analyze the timing characteristics correctly. To properly use IBIS models to attain accurate timing analysis
for a given system, see the Using IBIS Models for Timing Analysis application report (literature number SPRA839).
If needed, external logic hardware such as buffers may be used to compensate any timing differences.
For inputs, timing is most impacted by the round-trip propagation delay from the DSP to the external device and
from the external device to the DSP. This round-trip delay tends to negatively impact the input setup time margin,
but also tends to improve the input hold time margins (see Table 7-1andFigure 7-6).
V = V MIN (or VMIN)
refIHOH
OL
MAX
Table 7-1Board-Level Timing Example
(see Figure 7-6)
No. Description
1 Clock route delay
2 Minimum DSP hold time
3 Minimum DSP setup time
4 External device hold time requirement
5 External device setup time requirement
6 Control signal route delay
7 External device hold time
8 External device access time
9 DSP hold time requirement
10 DSP setup time requirement
11 Data route delay
End of Table 7-1
92C64x+ Peripheral Information and Electrical Specifications2009 Texas Instruments Incorporated
TMS320C6457
Communications Infrastructure Digital Signal Processor
www.ti.com
Figure 7-6 shows a general transfer between the DSP and an external device. The figure also shows board route
delays and how they are perceived by the DSP and the external device
Figure 7-6Board-Level Input/Output Timings
AECLKOUT
(Output from DSP)
AECLKOUT
(Input to External Device)
Control Signals
(Output from DSP)
Control Signals
(Input to External Device)
Data Signals
(Output from External Device)
Data Signals
(Input to DSP)
(A)
(B)
(B)
3
6
1
2
4
5
7
8
9
11
10
SPRS582B—July 2010
(A) Control signals include data for writes.
(B) Data signals are generated during reads from an external device.
7.2 Recommended Clock and Control Signal Transition Behavior
All clocks and control signals must transition between VIH and VIL (or between VIL and VIH) in a monotonic
manner.
7.3 Power Supplies
The following sections describe the proper power-supply sequencing and timing needed to properly power on the
C6457 DSP. This section also describes proper power-supply decoupling methods.
PRODUCT PREVIEW
2009 Texas Instruments IncorporatedC64x+ Peripheral Information and Electrical Specifications93
TMS320C6457
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
7.3.1 Power-Supply Sequencing
TI recommends the power-supply sequence shown in Figure 7-7 and described in Table 7-2. The figure shows that
the 1.8-V I/O supply should be ramped first. This is followed by the scaled core supply and the fixed 1.1-V supplies
which must ramp within 5 ms of each other. The 3.3-V I/O supply should ramp up last. Some TI power-supply
devices include features that facilitate power sequencing; for example, Auto-Track or Slow-Start/Enable features.
For more information, visit www.ti.com/dsppower. See the TMS320TCI6468 and TMS329C6457 DSPs Hardware Design Guide (SPRAAV7) for further details on proper power-supply sequencing.
Figure 7-7Power-Supply Sequence
DV
DD18
www.ti.com
PRODUCT PREVIEW
V(DDR2)
REFSSTL
CV
DD11
DV
DD11
DV
DD33
POR
Table 7-2Timing Requirements for Power-Supply Sequence
No.MinMax Unit
1t
su(DVDD18-DVDD11)
2t
su(DVDD11-DVDD33)
3t
h(DVDD33-POR)
End of Table 7-2
Setup Time, DV
Setup Time, DV
Hold time, POR low after DV
DD18
DD11
7.3.2 Power-Supply Decoupling
In order to properly decouple the supply planes from system noise, place as many capacitors (caps) as possible close
to the DSP. These caps need to be close to the DSP, no more than 1.25 cm maximum distance to be effective.
Physically smaller caps are better, such as 0402, but need to be evaluated from a yield/manufacturing point-of-view.
Parasitic inductance limits the effectiveness of the decoupling capacitors, therefore physically smaller capacitors
should be used while maintaining the largest available capacitance value. As with the selection of any component,
verification of capacitor availability over the product's production lifetime should be considered.
and V
and CV
1
2
3
supplies stable before DV
REFSSTL
supplies stable before DV
DD11
supplies stable100μs
DD33
and CV
DD11
supply stable0.5200ms
DD33
supplies stable0.5200ms
DD11
7.3.3 Power-Down Operation
One of the power goals for the C6457 is to reduce power dissipation due to unused peripherals. There are different
ways to power down peripherals on the device.
After device reset, all peripherals on the C6457 device are in a disabled state and must be enabled by software before
being used. It is possible to enable only the peripherals needed by the application while keeping the rest disabled.
Note that peripherals in a disabled state are held in reset with their clocks gated. For more information on how to
enable peripherals, see Section 3.2 ‘‘Peripheral Selection After Device Reset’’ on page 60
94C64x+ Peripheral Information and Electrical Specifications2009 Texas Instruments Incorporated
TMS320C6457
Communications Infrastructure Digital Signal Processor
www.ti.com
Peripherals used for booting, like I2C and HPI, are automatically enabled after device reset. It is possible to
disable peripherals used for booting after the boot process is complete. This, too, results in gating of the clock(s) to
the powered-down peripheral. Once a peripheral is powered-down, it must remain powered down until the next
device reset.
The C64x+ Megamodule also allows for software-driven power-down management for all of the C64x+
megamodule components through its Power-Down Controller (PDC). The CPU can power-down part or the entire
C64x+ megamodule through the power-down controller based on its own execution thread or in response to an
external stimulus from a host or global controller. More information on the power-down features of the C64x+
Megamodule can be found in the TMS320C64x+ Megamodule Reference Guide (literature number SPRU871).
SPRS582B—July 2010
7.4 Enhanced Direct Memory Access (EDMA3) Controller
The primary purpose of the EDMA3 is to service user-programmed data transfers between two memory-mapped
slave endpoints on the device. The EDMA3 services software-driven paging transfers (e.g., data movement between
external memory and internal memory), performs sorting or subframe extraction of various data structures, services
event-driven peripherals such as a McBSP or the UTOPIA port, and offloads data transfers from the device CPU.
The EDMA3 includes the following features:
•Fully orthogonal transfer description
–3 transfer dimensions:
›Array (multiple bytes)
›Frame (multiple arrays)
›Block (multiple frames)
–Single event can trigger transfer of array, frame, or entire block
–Independent indexes on source and destination
•Flexible transfer definition:
–Increment or FIFO transfer addressing modes
–Linking mechanism allows for ping-pong buffering, circular buffering, and repetitive/continuous
transfers, all with no CPU intervention
–Chaining allows multiple transfers to execute with one event
•256 PaRAM entries
–Used to define transfer context for channels
–Each PaRAM entry can be used as a DMA entry, QDMA entry, or link entry
•64 DMA channels
–Manually triggered (CPU writes to channel controller register), external event triggered, and chain
triggered (completion of one transfer triggers another)
•8 Quick DMA (QDMA) channels
–Used for software-driven transfers
–Triggered upon writing to a single PaRAM set entry
•6 transfer controllers and 6 event queues with programmable system-level priority
•Interrupt generation for transfer completion and error conditions
•Debug visibility
–Queue watermarking/threshold allows detection of maximum usage of event queues
–Error and status recording to facilitate debug
PRODUCT PREVIEW
Each of the transfer controllers has a direct connection to the switched central resource (SCR). Table 4-1 ‘‘SCR
Connection Matrix’’ on page 67 lists the peripherals that can be accessed by the transfer controllers.
2009 Texas Instruments IncorporatedC64x+ Peripheral Information and Electrical Specifications95
TMS320C6457
Communications Infrastructure Digital Signal Processor
SPRS582B—July 2010
7.4.1 EDMA3 Device-Specific Information
The EDMA supports two addressing modes: constant addressing and increment addressing mode. Constant
addressing mode is applicable to a very limited set of use cases; for most applications increment mode can be used.
On the C6457 DSP, the EDMA can use constant addressing mode only with the Enhanced Viterbi-Decoder
Coprocessor (VCP2) and the Enhanced Turbo Decoder Coprocessor (TCP2). Constant addressing mode is not
supported by any other peripheral or internal memory in the C6457 DSP. Note that increment mode is supported
by all C6457 peripherals, including VCP2 and TCP2. For more information on these two addressing modes, see the
TMS320C6457 DSP Enhanced DMA (EDMA3) Controller User's Guide (literature number SPRUGK6).
A DSP interrupt must be generated at the end of an HPI boot operation to begin execution of the loaded application.
Because the DSP interrupt generated by the HPI is mapped to the EDMA event DSP_EVT (DMA channel 0), it will
get recorded in bit 0 of the EDMA Event Register (ER). This event must be cleared by software before triggering
PRODUCT PREVIEW
transfers on DMA channel 0. The EDMA3 on the C6457 DSP supports active memory protection, but it does not
support proxied memory protection.
7.4.2 EDMA3 Channel Synchronization Events
The EDMA3 supports up to 64 DMA channels that can be used to service system peripherals and to move data
between system memories. DMA channels can be triggered by synchronization events generated by system
peripherals. Table 7-3 lists the source of the synchronization event associated with each of the DMA channels. On
the C6457, the association of each synchronization event and DMA channel is fixed and cannot be reprogrammed.
www.ti.com
For more detailed information on the EDMA3 module and how EDMA3 events are enabled, captured, processed,
prioritized, linked, chained, and cleared, etc., see the TMS320C6457 DSP Enhanced DMA (EDMA3) Controller User's Guide (literature number SPRUGK6).
1 In addition to the ev ents shown in this table, each of the 64 channels can also be synchronized with the transfer completion or alternate transfer completion events. For more
detailed information on EDMA event-transfer chaining, see the TMS320C6457 DSP Enhanced DM A (EDMA3) Controller User's Guide (literature number SPRUGK6).
2 HPI boot is terminated using a DSP interrupt. The DSP interrupt is registered in bit 0 (channel 0) of the EDMA Event Register (E R). T his eve nt m ust b e cl ear ed b y sof twa re b efo re
triggering transfers on DMA channel 0.
C Receive Event
2
C Transmit Event
(1)
(Part 2 of 2)
SPRS582B—July 2010
PRODUCT PREVIEW
7.4.3 EDMA3 Peripheral Register Description(s)
Table 7-4EDMA3 Registers (Part 1 of 15)
Hex Address Acronym Register Name
02A0 0000 PID Peripheral ID Register
02A0 0004 CCCFG EDMA3CC Configuration Register
02A0 0008 - 02A0 00FC -Reserved
02A0 0100 DCHMAP0 DMA Channel 0 Mapping Register
02A0 0104 DCHMAP1 DMA Channel 1 Mapping Register
02A0 0108 DCHMAP2 DMA Channel 2 Mapping Register
2009 Texas Instruments IncorporatedC64x+ Peripheral Information and Electrical Specifications97
TMS320C6457
Communications Infrastructure Digital Signal Processor