• Pin-Compatible with the TMS320C6455
Fixed-Point Digital Signal Processor
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.
2All trademarks are the property of their respective owners.
PRODUCTION DATA information is current as of publication date.
Products conform to specifications per the terms of the Texas
Instruments standard warranty. Production processing does not
necessarily include testingof all parameters.
The TMS320C64x+™ DSPs (including the TMS320C6454 device) are the highest-performance fixed-point
DSP generation in the TMS320C6000™ DSP platform. The C6454 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.
The C6454 device offers a lower cost pin-compatible migration path for C6455 customers who don't need
the 2MB of the C6455 or the high-speed interconnect provided by Serial RapidIO. The C6454 device also
provides an excellent migration path for existing C6414/6415/6416 customers who require C6454
advanced peripherals; DDR2 at 533 MHz provides 2x performance boost over older SDRAM interface,
gigabit Ethernet provides low-cost high-performance ubiquitous packet interface, and 66-MHz PCI
(revision 2.3 complaint) provides legacy high-bandwidth interconnect.
Based on 90-nm process technology and with performance of up to 8000 million instructions per second
(MIPS) [or 8000 16-bit MMACs per cycle] at a 1-GHz clock rate, the C6454 device offers cost-effective
solutions to high-performance DSP programming challenges. The C6454 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 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 1-GHz clock rate, this means 8000 16-bit MMACs can occur every second. Moreover, each
multiplier on the C64x+ core can compute one 32-bit x 32-bit MAC or four 8-bit x 8-bit MACs every clock
cycle.
The C6454 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 C6454 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 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 1048KB 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: an inter-integrated circuit bus module (I2C); two multichannel buffered serial
ports (McBSPs); a user-configurable 16-bit or 32-bit host-port interface (HPI16/HPI32); a peripheral
component interconnect (PCI); 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 C6454 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 I2C ports on the C6454 device allows the DSP to easily control peripheral devices and communicate
with a host processor. In addition, the standard multichannel buffered serial port (McBSP) may be used to
communicate with serial peripheral interface (SPI) mode peripheral devices.
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
The C6454 DSP 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.
A.McBSPs: Framing Chips - H.100, MVIP, SCSA, T1, E1; AC97 Devices; SPI Devices; Codecs.
B.The PCI peripheral pins are muxed with some of the HPI peripheral pins . For more detailed information, see
Section 3, Device Configuration.
C.Each of the TIMER peripherals (TIMER1 and TIMER0) is configurable as a 64-bit general-purpose timer, dual 32-bit
general-purpose timers, or a watchdog timer.
D.The PLL2 controller also generates clocks for the EMAC.
E.When accessing the internal ROM of the DSP, the CPU frequency must always be less than 750 MHz.
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
This data manual revision history highlights the technical changes made to the document in this revision.
Scope: Applicable updates to the C64x device family, specifically relating to the TMS320C6454 device,
have been incorporated.
SEEADDITIONS/MODIFICATIONS/DELETIONS
Table 3-1C6454 Device Configuration Pins (AEA[19:0], ABA[1:0], and PCI_EN):
Table 2-1. Characteristics of the C6454 Processor (continued)
HARDWARE FEATURESC6454
Device Part NumbersTMS320C6454ZTZ8 , TMS320C6454GTZ8
(For more details on the C64x+™ DSP part
numbering, see Figure 2-12)
TMS320C6454ZTZ7, TMS320C6454GTZ7
TMS320C6454ZTZ , TMS320C6454GTZ
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.
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
for 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 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.
•SPLOOP - A small instruction buffer in the CPU that aids in creation of software pipelining loops where
•Compact Instructions - The native instruction size for the C6000 devices is 32 bits. Many common
•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+ Megamodule Reference Guide (literature number SPRU871)
•TMS320C6455 Technical Reference (literature number SPRU965)
•TMS320C64x to TMS320C64x+ CPU Migration Guide (literature number SPRAA84)
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
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.
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.
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.
TMS320C6454
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
www.ti.com
Figure 2-1. TMS320C64x+™ CPU (DSP Core) Data Paths
Table 2-2 shows the memory map address ranges of the C6454 device. The external memory
configuration register address ranges in the C6454 device begin at the hex address location 0x7000 0000
for EMIFA and hex address location 0x7800 0000 for DDR2 Memory Controller.
Table 2-2. C6454 Memory Map Summary
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 reset, warm reset, and system reset. For more details on the
initiators of these resets, see Section 7.6, Reset Controller.
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.
Each boot mode can be classified as a hardware boot mode or as a software boot mode. Software boot
modes require the use of the on-chip bootloader. The bootloader is DSP code that transfers application
code from an external source into internal or external program memory after the DSP is taken out of reset.
The bootloader is permanently stored in the internal ROM of the DSP starting at byte address 0010
0000h. Hardware boot modes are carried out by the boot configuration logic. The boot configuration logic
is actual hardware that does not require the execution of DSP code. Section 2.4.1, Boot ModesSupported, describes each boot mode in more detail.
When accessing the internal ROM of the DSP, the CPU frequency must always be less than 750 MHz.
Therefore, when using a software boot mode, care must be taken such that the CPU frequency does not
exceed 750 MHz at any point during the boot sequence. After the boot sequence has completed, the CPU
frequency can be programmed to the frequency required by the application.
2.4.1Boot Modes Supported
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
The C6454 device has five boot modes:
•No boot (BOOTMODE[3:0] = 0000b)
With no boot, the CPU executes directly from the internal L2 SRAM located at address 0x80 0000.
Note: device operations is undefined if invalid code is located at address 0x80 0000. This boot mode is
a hardware boot mode.
•Host boot (BOOTMODE[3:0] = 0001b and BOOTMODE[3:0] = 0111b)
If host boot is selected, after reset, the CPU is internally "stalled" while the remainder of the device is
released. During this period, an external host can initialize the CPU's memory space as necessary
through Host Port Interface (HPI) or the Peripheral Component Interconnect (PCI) interface. Internal
configuration registers, such as those that control the EMIF can also be initialized by the host with two
exceptions: Device State Control registers (Section 3.4), PLL1 and PLL2 Controller registers
(Section 7.7 and Section 7.8) cannot be accessed through any host interface, including HPI and PCI.
Once the host is finished with all necessary initialization, it must generate a DSP interrupt (DSPINT) to
complete the boot process. This transition causes boot configuration logic to bring the CPU out of the
"stalled" state. The CPU then begins execution from the internal L2 SRAM located at 0x80 0000. Note
that the DSP interrupt is registered in bit 0 (channel 0) of the EDMA Event Register (ER). This event
must be cleared by software before triggering transfers on DMA channel 0.
All memory, with the exceptions previously described, may be written to and read by the host. This
allows for the host to verify what it sends to the DSP if required. After the CPU is out of the "stalled"
state, the CPU needs to clear the DSPINT, otherwise, no more DSPINTs can be received.
As previously mentioned, for the C6454 device, the Host Port Interface (HPI) and the Peripheral
Component Interconnect (PCI) interface can be used for host boot. To use the HPI for host boot, the
PCI_EN pin (Y29) must be low [default] (enabling the HPI peripheral) and BOOTMODE[3:0] must be
set to 0001b at device reset. Conversely, to use the PCI interface for host boot, the PCI_EN pin (Y29)
must be high (enabling the PCI peripheral) and BOOTMODE[3:0] must be set to 0111b at device reset.
For the HPI host boot, the DSP interrupt can be generated through the use of the DSPINT bit in the
HPI Control (HPIC) register.
For the HPI host boot, the CPU is actually held in reset until a DSP interrupt is generated by the host.
The DSP interrupt can be generated through the use of the DSPINT bit in the HPI Control (HPIC)
register. Since the CPU is held in reset during HPI host boot, it will not respond to emulation software
such as Code Composer Studio.
For the PCI host boot, the CPU is out of reset, but it executes an IDLE instruction until a DSP interrupt
is generated by the host. The host can generate a DSP interrupt through the PCI peripheral by setting
the DSPINT bit in the Back-End Application Interrupt Enable Set Register (PCIBINTSET) and the
Status Set Register (PCISTATSET).
Note that the HPI host boot is a hardware boot mode while the PCI host boot is a software boot mode.
If PCI boot is selected, the on-chip bootloader configures the PLL1 Controller such that CLKIN1 is
multiplied by 15. More specifically, PLLM is set to 0Eh (x15) and RATIO is set to 0 (÷1) in the PLL1
Multiplier Control Register (PLLM) and PLL1 Pre-Divider Register (PREDIV), respectively. The CLKIN1
frequency must not be greater than 50 MHz so that the maximum speed of the internal ROM, 750
MHz, is not violated. The CFGGP[2:0] pins must be set to 000b during reset for proper operation of the
PCI boot mode.
As mentioned previously, a DSP interrupt must be generated at the end of the host boot process to
begin execution of the loaded application. Since the DSP interrupt generated by the HPI and PCI 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 transfers on DMA
channel 0.
•EMIFA 8-bit ROM boot (BOOTMODE[3:0] = 0100b)
After reset, the device will begin executing software out of an Asynchronous 8-bit ROM located in
EMIFA CE3 space using the default settings in the EMIFA registers. This boot mode is a hardware
boot mode.
•Master I2C boot (BOOTMODE[3:0] = 0101b)
After reset, the DSP can act as a master to the I2C bus and copy data from an I2C EEPROM 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. This boot mode is a software boot mode.
•Slave I2C boot (BOOTMODE[3:0] = 0110b)
A Slave I2C boot is also implemented, which programs the DSP as an I2C Slave and simply waits for a
Master to send data using a standard boot table format.
Using the Slave I2C boot, a single DSP or a 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.
The Slave I2C boot is a software boot mode.
www.ti.com
2.4.22nd-Level Bootloaders
Any of the boot modes can be used to download a 2nd-level bootloader. A 2nd-level bootloader allows for
any level of customization to current boot methods as well as definition of a completely customized boot.
TI offers a few 2nd-level bootloaders, such as an EMAC bootloader, which can be loaded using the
Master I2C boot.
A. This pin functions as GP[1] by default. For more details, see the Device Configuration section of this document.
B. These McBSP1 peripheral pins are muxed with the GPIO peripheral pins and by default these signals function as GPIO peripheral pins. For
more details, see the Device Configuration section of this document.
C. These PCI peripheral pins are muxed with the GPIO peripheral pins and by default these signals function as GPIO peripheral pins. For more
details, see the Device Configuration section of this document.
Figure 2-10. EMAC/MDIO [MII, GMII, RMII, and RGMII] Peripheral Signals
Submit Documentation Feedback
Product Folder Link(s): TMS320C6454
HD[15:0]/AD[15:0]
HR/W
/PCBE2
HDS2/PCBE1
PCBE0/GP[2]
HHWIL/PCLK
HINT/PFRAME
PINTA/GP[14]
Data/Address
Arbitration
32
Clock
Control
PCI Interface
(A)
HAS/PPAR
PRST
/GP[13]
HRDY
/PIRDY
HCNTL0/PSTOP
PTRDY
PCBE3
PIDSEL
HCNTL1/PDEVSEL
HDS1/PSERR
Error
Command
Byte Enable
HCS/PPERR
PGNT/GP[12]
PREQ
/GP[15]
HD[31:16]/AD[31:16]
A. These PCI pins are muxed with the HPI or GPIO peripherals. By default, these signals function as HPI or GPIO or EMAC. For more
details on these muxed pins, see the Device Configuration section of this document.
TMS320C6454
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
Figure 2-11. PCI Peripheral Signals
www.ti.com
2.7Terminal Functions
The terminal functions table (Table 2-3) 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.
Table 2-3. Terminal Functions
SIGNAL
NAMENO.
CLKIN1N28IIPDClock Input for PLL1.
CLKIN2G3IIPDClock Input for PLL2.
PLLV1T29A1.8-V I/O supply voltage for PLL1
PLLV2A5A1.8-V I/O supply voltage for PLL2
SYSCLK4/GP[1]
TMSAJ10IIPUJTAG test-port mode select
TDOAH8O/ZIPUJTAG test-port data out
TDIAH9IIPUJTAG test-port data in
TCKAJ9IIPUJTAG test-port clock
TRSTAH7IIPD
(4)
EMU0
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = Internal pulldown, IPU = Internal pullup. For most systems, a 1-kΩ resistor can be used to oppose the IPU/IPD. For more detailed
information on pullup/pulldown resistors and situations where external pullup/pulldown resistors are required, see Section 3.7,
Pullup/Pulldown Resistors.
(3) These pins are multiplexed pins. For more details, see Section 3, Device Configuration.
(4) The C6454 DSP does not require external pulldown resistors on the EMU0 and EMU1 pins for normal or boundary-scan operation.
RESETSTATAE14OReset Status pin. The RESETSTAT pin indicates when the device is in reset
PORAF14IPower on reset.
GP[7]AG2I/O/ZIPD
GP[6]AG3I/O/ZIPD
GP[5]AJ2I/O/ZIPD
GP[4]AH2I/O/ZIPD
PREQ/ GP[15]P2I/O/Z
HOST-PORT INTERFACE (HPI) or PERIPHERAL COMPONENT INTERCONNECT (PCI)
PCI_ENY29IIPD
TYPE
(1)
IPD/IPU
(2)
DESCRIPTION
RESETS, INTERRUPTS, AND GENERAL-PURPOSE INPUT/OUTPUTS
Nonmaskable interrupt, edge-driven (rising edge)
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 versus relying on
the IPD.
PCI bus request (O/Z) or GP[15] (I/O/Z) [default]
PCI interrupt A (O/Z) or GP[14] (I/O/Z) [default]
PCI reset (I) or GP[13] (I/O/Z) [default]
PCI bus grant (I) or GP[12] (I/O/Z) [default]
PCI command/byte enable 0 (I/O/Z) or GP[2] (I/O/Z) [default]
McBSP1 transmit clock (I/O/Z) or GP[3] (I/O/Z) [default]
McBSP1 receive clock (I/O/Z) or GP[0] (I/O/Z) [default]
GP[1] pin (I/O/Z). SYSCLK4 is the clock output at 1/8 of the device speed (O/Z)
or this pin can be programmed as a GP[1] pin (I/O/Z) [default].
PCI enable pin. This pin controls the selection (enable/disable) of the HPI and
GP[15:8], or PCI peripherals. This pin works in conjunction with the
MCBSP1_EN (AEA5 pin) to enable/disable other peripherals (for more details,
see Section 3, Device Configuration).
(5) These pins function as open-drain outputs when configured as PCI pins.
HINT/PFRAMEU3I/O/ZHost interrupt from DSP to host (O/Z) or PCI frame (I/O/Z)
HCNTL1/PDEVSELU4I/O/Z
HCNTL0/PSTOPU5I/O/Z
HHWIL/PCLKV3I/O/Zorder)
HR/W/PCBE2T5I/O/ZHost read or write select (I) [default] or PCI command/byte enable 2 (I/O/Z)
HAS/PPART3I/O/ZHost address strobe (I) [default] or PCI parity (I/O/Z)
HCS/PPERRU6I/O/ZHost chip select (I) [default] or PCI parity error (I/O/Z)
HDS1/PSERR
(5)
U2I/O/ZHost data strobe 1 (I) [default] or PCI system error (I/O/Z)
HDS2/PCBE1U1I/O/ZHost data strobe 2 (I) [default] or PCI command/byte enable 1 (I/O/Z)
HRDY/PIRDYT4I/O/ZHost ready from DSP to host (O/Z) [default] or PCI initiator ready (I/O/Z)
PREQ/ GP[15]P2I/O/ZPCI bus request (O/Z) or GP[15] (I/O/Z) [default]
(6)
PINTA
/ GP[14]P3I/O/ZPCI interrupt A (O/Z) or GP[14] (I/O/Z) default]
PRST/ GP[13]R5I/O/ZPCI reset (I) or GP[13] (I/O/Z) [default]
PGNT/ GP[12]R4I/O/Zor PCI bus grant (I) or GP[12] (I/O/Z)[default]
PCBE0/ GP[2]P1I/O/ZPCI command/byte enable 0 (I/O/Z) or GP[2] (I/O/Z)[default]
PCBE3P5I/O/ZPCI command/byte enable 3 (I/O/Z). By default, this pin has no function.
PIDSELR3IPCI initialization device select (I). By default, this pin has no function.
PTRDYP4I/O/ZPCI target ready (PRTDY) (I/O/Z). By default, this pin has no function.
HD31/AD31AA3
HD30/AD30AA5
HD29/AD29AC4
HD28/AD28AA4
HD27/AD27AC5
HD26/AD26Y1
HD25/AD25AD2
HD24/AD24W1
HD23/AD23AC3
HD22/AD22AE1
HD21/AD21AD1
HD20/AD20W2
HD19/AD19AC1
HD18/AD18Y2
HD17/AD17AB1
HD16/AD16Y3
TYPE
I/O/Z
(1)
IPD/IPU
(2)
DESCRIPTION
Host control - selects between control, address, or data registers (I) [default] or
PCI device select (I/O/Z)
Host control - selects between control, address, or data registers (I) [default] or
PCI stop (I/O/Z)
Host half-word select - first or second half-word (not necessarily high or low
[For HPI16 bus width selection only] (I) [default] or PCI clock (I)
Host-port data [31:16] pin (I/O/Z) [default] or PCI data-address bus [31:16]
(I/O/Z)
AHOLDAN26OIPUEMIFA hold-request-acknowledge to the host
AHOLDR29IIPUEMIFA hold request from the host
ABUSREQL27OIPUEMIFA bus request output
EMIFA (64-BIT) - ASYNCHRONOUS/SYNCHRONOUS MEMORY CONTROL
AECLKINN29IIPDclock) is selected at reset via the pullup/pulldown resistor on the AEA[15] pin.
(1)
TYPE
I/O/ZHost-port data [15:0] pin (I/O/Z) [default] or PCI data-address bus [15:0] (I/O/Z)
IPD/IPU
(2)
•Active-low bank selects for the 64-bit EMIFA.
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
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.
EMIFA (64-BIT) - ADDRESS
Controls initialization of the DSP modes at reset (I) via pullup/pulldown resistors
[For more detailed information, see Section 3, Device Configuration.]
Note: If a configuration pin must be routed out from the device and 3-stated
(not driven), 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 where external
pullup/pulldown resistors are required, see Section 3.7, Pullup/PulldownResistors.
•Boot mode - device boot mode configurations (BOOTMODE[3:0]) [Note:
the peripheral must be enabled to use the particular boot mode.]
AEA[19:16]:
0000 - No boot (default mode)
0001 - Host boot (HPI)
0010 -Reserved
0011 - Reserved
0100 - EMIFA 8-bit ROM boot
0101 - Master I2C boot
0110 - Slave I2C boot
0111 - Host boot (PCI)
1000 thru 1111 - Reserved
For more detailed information on the boot modes, see Section 2.4, BootSequence.
CFGGP[2:0] pins must be set to 000b during reset for proper operation of
the PCI boot mode.
AEA15:
1 - SYSCLK4 (CPU/x) Clock Rate. The SYSCLK4 clock rate is software
selectable via the Software PLL1 Controller. By default, SYSCLK4 is
selected as CPU/8 clock rate.
•HPI peripheral bus width (HPI_WIDTH) select
[Applies only when HPI is enabled; PCI_EN pin = 0]
AEA14:
0 - HPI operates as an HPI16 (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.)
1 - HPI operates as an HPI32.
•Device Endian mode (LENDIAN)
AEA13:
0 - System operates in Big Endian mode
1 - System operates in Little Endian mode(default)
Note: For proper C6454 device operation, the AEA12 and AEA11 pins must
be externally pulled down with a 1-kΩ resistor at device reset.
AEA10/MACSEL1M25
AEA9/MACSEL0M27
AEA8/PCI_EEAIP25
AEA7N27
AEA6/PCI66U27
AEA5/MCBSP1_ENU28
AEA4/[RGMII interface requires a 1.8-V or 1.5-V I/O supply]
SYSCLKOUT_EN
T28
AEA3T27
AEA2/CFGGP2T26
AEA1/CFGGP1U26
AEA0/CFGGP0U25
(1)
TYPE
IPD/IPU
O/ZIPD
(2)
DESCRIPTION
•EMAC/MDIO interface select bits (MACSEL[1:0])
There are two configuration pins — MACSEL[1:0] — to select the
EMAC/MDIO interface.
AEA[10:9]: MACSEL[1:0]
If the PCI peripheral is disabled (PCI_EN pin = 0), this pin must not be
pulled up.
0 - PCI auto-initialization through I2C EEPROM is disabled (default).
1 - PCI auto-initialization through I2C EEPROM is enabled.
•PCI Frequency Selection (PCI66)
[The PCI peripheral needs be enabled (PCI_EN = 1) to use this function]
Selects the PCI operating frequency of 66-MHz or 33-MHz PCI operating
frequency is selected at reset via the pullup/pulldown resistor on the PCI66
pin:
AEA6:
0 - PCI operates at 33 MHz (default).
1 - PCI operates at 66 MHz.
Note: If the PCI peripheral is disabled (PCI_EN = 0), this pin must not be
pulled up.
•McBSP1 Enable bit (MCBSP1_EN)
Selects which function is enabled on the McBSP1/GPIO muxed pins
•SYSCLKOUT Enable pin (SYSCLKOUT_EN)
Selects which function is enabled on the SYSCLK4/GP[1] muxed pin
AEA4:
0 - GP[1] pin function of the SYSCLK4/GP[1] pin enabled (default).
1 - SYSCLK4 pin function of the SYSCLK4/GP[1] pin enabled.
•Configuration GPI (CFGGP[2:0]) (AEA[2:0])
These pins are latched during reset and their values are shown in the
DEVSTAT register. These values can be used by software routines for boot
operations.
AEA3:
For proper C6454 device operation, the AEA3 pin must be pulled down to V
using a 1-kΩ resistor.
DDR2 Memory Controller memory space enable. When the DDR2 Memory
Controller is enabled, it always keeps this pin low.
connected to the DDR2 SDRAM.
Note: There are no on-die termination resistors implemented on the C6454
DSP die.
DDR2 Memory Controller data strobe gate [3:0]
For hookup of these signals, see the Implementing DDR2 PCB Layout on theTMS320C6455/5 application report (literature number SPRAAA7).
•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).
TOUTL1AG7O/ZIPDTimer 1 output pin for lower 32-bit counter
TINPL1AJ6IIPDTimer 1 input pin for lower 32-bit counter
TOUTL0AF8O/ZIPDTimer 0 output pin for lower 32-bit counter
TINPL0AH6IIPDTimer 0 input pin for lower 32-bit counter
SCLAG26I/O/ZI2C clock. When the I2C module is used, use an external pullup resistor.
SDAAF26I/O/ZI2C data. When I2C is used, ensure there is an external pullup resistor.
MDCLKM5I/O/ZIPDMDIO serial clock (MDCLK) for MII/RMII/GMII mode (O)
MDION3I/O/ZIPUMDIO serial data (MDIO) for MII/RMII/GMII mode (I/O)
RGMDCLKB4O/ZMDIO serial clock (RGMII mode) (RGMDCLK) (O)
RGMDIOA4I/O/ZMDIO serial data (RGMII mode) (RGMDIO) (I/O)
There are two configuration pins - the MAC_SEL[1:0] (AEA[10:9] pins) - that select one of the four interface modes (MII, RMII, GMII, or
RGMII) for the EMAC/MDIO interface. For more detailed information on the EMAC configuration pins, see Section 3, Device Configuration.
MRCLKH1I
MCRS/ RMCRSDVJ4I/O/Zcarrier sense/receive data valid (RMCRSDV) (I) for RMII. MACSEL[1:0]
MRXER/This pin is EMAC receive error (MRXIR) (I) for MII [default], RMII, or GMII.
RMRXERMACSEL[1:0] dependent.
MANAGEMENT DATA INPUT/OUTPUT (MDIO) FOR MII/RMII/GMII
IPD/IPU
MULTICHANNEL BUFFERED SERIAL PORT 1 (McBSP1)
MULTICHANNEL BUFFERED SERIAL PORT 0 (McBSP0)
MANAGEMENT DATA INPUT/OUTPUT (MDIO) FOR RGMII
IEMAC receive data pins for MII [default], RMII, or GMII (MRXD[x:0]) (I).
(2)
McBSP external clock source (as opposed to internal) (I)
[shared by McBSP1 and McBSP0]
ETHERNET MAC (EMAC) [MII/RMII/GMII]
This pin is EMAC receive clock (MRCLK) for MII [default] or GMII.
MACSEL[1:0] dependent.
This pin is EMAC carrier sense (MCRS) (I) for MII [default] or GMII, or EMAC
dependent.
This pin is EMAC MII [default] or GMII receive data valid (MRXDV) (I).
MACSEL[1:0] dependent.
EMAC receive data bus for MII [default], RMII, or GMII These pins function as
MACSEL[1:0] dependent.
This pin is either EMAC MII [default] or GMII transmit clock (MTCLK) (I) or the
EMAC RMII reference clock (RMREFCLK) (I). The EMAC function is controlled
by the MACSEL[1:0] (AEA[10:9] pins). For more detailed information, see
There are two configuration pins - the MAC_SEL[1:0] (AEA[10:9] pins) - that select one of the four interface modes (MII, RMII, GMII, or
RGMII) for the EMAC/MDIO interface. For more detailed information on the EMAC configuration pins, see Section 3, Device Configuration.
RGREFCLKC4O/Zgenerate RXC clock to communicate with the EMAC. This clock is stopped
RGTXCD4O/Z
RGTXD3A2
RGTXD2C3
RGTXD1B3
RGTXD0A3
RGTXCTLD3O/Z
RGRXCE3I
RGRXD3C1I
RGRXD2E4I
RGRXD1E2I
RGRXD0E1I
RGRXCTLC2I
RSV02V5
RSV03W3
RSV04N11
RSV05P11
RSV07G4I
RSV09D26I
RSV11D24
RSV12C24
TYPE
O/Z
(1)
IPD/IPU
(2)
ETHERNET MAC (EMAC) [RGMII]
RGMII reference clock (O). This 125-MHz reference clock is provided as a
convenience. It can be used as a clock source to a PHY, so that the PHY may
while the device is in reset. This pin is available only when RGMII mode is
selected ( MACSEL[1:0] =11).
RGMII transmit clock (O). This pin is available only when RGMII mode is
selected (MACSEL[1:0] =11).
RGMII transmit data [3:0] (O). This pin is available only when RGMII mode is
selected (MACSEL[1:0] =11).
RGMII transmit enable (O). This pin is available only when RGMII mode is
selected (MACSEL[1:0] =11).
RGMII receive clock (I). This pin is available only when RGMII mode is selected
(MACSEL[1:0] =11).
RGMII receive data [3:0] (I). This pin is available only when RGMII mode is
selected (MACSEL[1:0] =11).
RGMII receive control (I). This pin is available only when RGMII mode is
selected (MACSEL[1:0] =11).
RESERVED FOR TEST
Reserved. These pins must be connected directly to core supply (CVDD) for
proper device operation.
Reserved. This pin must be connected directly to 1.5-/1.8-V I/O supply
(DV
) for proper device operation.
DD15
NOTE: If the EMAC RGMII is not used, these pins can be connected directly to
ground (VSS).
Reserved. This pin must be connected directly to the 1.8-V I/O supply (DV
for proper device operation.
Reserved. This pin must be connected to ground (VSS) via a 200-Ω resistor for
proper device operation.
NOTE: If the DDR2 Memory Controller is not used, the V
RSV12 pins can be connected directly to ground (VSS) to save power.
However, connecting these pins directly to ground will prevent 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.4.
Reserved. This pin must be connected to the 1.8-V I/O supply (DV
200-Ω resistor for proper device operation.
NOTE: If the DDR2 Memory Controller is not used, the V
RSV12 pins can be connected directly to ground (VSS) to save power.
However, connecting these pins directly to ground will prevent boundary-scan
from functioning on the DDR2 Memory Controller pins. To preserve
boundary-scan functionality on the DDR2 Memory Controller pins, see
Reserved. This pin must be connected to ground (VSS) via a 200-Ω resistor for
proper device operation.
NOTE: If the RGMII mode of the EMAC is not used, the DV
DD15
, V
REFHSTL
power. However, connecting these pins directly to ground 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.4.
Reserved. This pin must be connected to the 1.5/1.8-V I/O supply (DV
a 200-Ω resistor for proper device operation.
NOTE: If the RGMII mode of the EMAC is not used, the DV
DD15
, V
REFHSTL
power. However, connecting these pins directly to ground 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.4.
Reserved. This pin must be connected via a 39-Ω resistor directly to ground
rating of 1/10 W.
Reserved. This pin must be connected via a 20-Ω resistor directly to 3.3-V I/O
) for proper device operation. The resistor used should have a
minimal rating of 1/10 W.
DD33
Reserved. (Leave unconnected, do not connect to power or ground.)
F3INOTE: If the RGMII mode of the EMAC is not used, the DV
A26
C14ARSV12 pins can be connected directly to ground (VSS) to save power.
B2A
A13
E18
A1
B5
D2
D5S
F5
G6
H7
Table 2-3. Terminal Functions (continued)
(1)
TYPE
IPD/IPU
A1.8-V I/O supply voltage.
(2)
SUPPLY VOLTAGE MONITOR PINS
Die-side 1.2-V 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. If the CV
connected directly to the 1.2-V core supply (CVDD).
Die-side 3.3-V I/O supply (DV
indicate the voltage on the die and, therefore, provide the best probe point for
voltage monitoring purposes. If the DV
connected directly to the 3.3-V I/O supply (DV
Die-side 1.5-/1.8-V I/O supply (DV
indicate the voltage on the die and, therefore, provide the best probe point for
voltage monitoring purposes. If the DV
connected directly to the 1.5-/1.8-V I/O supply (DV
V
to save power. However, connecting these pins directly to ground will prevent
, RSV13, and RSV14 pins can be connected directly to ground (VSS)
REFHSTL
boundary-scan from functioning on the RGMII pins of the EMAC. To preserve
boundary-scan functionality on the RGMII pins, see Section 7.3.4.
Die-side 1.8-V I/O supply (DV
indicate the voltage on the die and, therefore, provide the best probe point for
voltage monitoring purposes. If the DV
connected directly to the 1.8-V I/O supply (DV
SUPPLY VOLTAGE PINS
(DV
/2)-V reference for SSTL buffer (DDR2 Memory Controller). This input
DD18
voltage can be generated directly from DV
a resistor divider circuit.
NOTE: The DDR2 Memory Controller is not used, the V
However, connecting these pins directly to ground will prevent 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.4.
(DV
/2)-V reference for HSTL buffer (EMAC RGMII). V
DD15
generated directly from DV
divider circuit.
NOTE: If the RGMII mode of the EMAC is not used, the DV
RSV13, and RSV14 pins can be connected to directly ground (VSS) to save
power. However, connecting these pins directly to ground 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.4.
1.8-V or 1.5-V I/O supply voltage for the RGMII function of the EMAC.
NOTE: If the RGMII mode of the EMAC is not used, the DV
RSV13, and RSV14 pins can be connected to directly ground (VSS) to save
power. However, connecting these pins directly to ground 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.4.
In case the customer would like to develop their own features and software on the C6454 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.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., TMS320C6454ZTZ). 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).
www.ti.com
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 against 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.
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=Initialsilicon
A letterindicatesanewsiliconrevision
Blank=0°Cto90°C(defaultcommercialtemperature)
A =-40°Cto105°C(extendedtemperature)
TMS320C6454
www.ti.com
SPRS311F–APRIL 2006–REVISED SEPTEMBER 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 1000 MHz [1 GHz]).
Figure 2-12 provides a legend for reading the complete device name for any TMS320C64x+™ DSP
generation member.
For device part numbers and further ordering information for TMS320C6454 in the ZTZ/GTZ package
type, see the TI website (www.ti.com) or contact your TI sales representative.
A.The extended temperature "A version" devices may have different operating conditions than the commercial
temperature devices. For more details, see Section 6.2, Recommended Operating Conditions.
B.BGA = Ball Grid Array
C.For silicon revision information, see the TMS320C6455/54 Digital Signal Processor Silicon Errata (literature number
SPRZ234).
Figure 2-12. TMS320C64x+™ DSP Device Nomenclature (including the TMS320C6454 DSP)
The following documents describe the TMS320C6454 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.
SPRU871TMS320C64x+ DSP Megamodule Reference Guide. Describes the TMS320C64x+ digital
signal processor (DSP) megamodule. 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.
SPRU732TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide. Describes the CPU
architecture, pipeline, instruction set, 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.
SPRAA84TMS320C64x to TMS320C64x+ CPU Migration Guide. Describes migrating from the Texas
Instruments TMS320C64x digital 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.
SPRU889High-Speed DSP Systems Design Reference Guide. Provides recommendations for
meeting the many challenges of high-speed DSP system design. These recommendations
include information about DSP audio, video, and communications systems for the C5000 and
C6000 DSP platforms.
SPRU971TMS320C645x DSP External Memory Interface (EMIF) User's Guide. This document
describes the operation of the external memory interface (EMIF) in the TMS320C645x digital
Submit Documentation Feedback
Product Folder Link(s): TMS320C6454
TMS320C6454
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
signal processors (DSPs).
SPRU970TMS320C645x DSP DDR2 Memory Controller User's Guide. This document describes the
DDR2 memory controller in the TMS320C645x digital-signal processors (DSPs).
SPRU969TMS320C645x DSP Host Port Interface (HPI) User's Guide. This guide describes the host
port interface (HPI) on the TMS320C645x 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.
SPRUEC6TMS320C645x/C647x Bootloader User's Guide. This document describes the features of
the on-chip Bootloader provided with the TMS320C645x/C647x digital signal processors
(DSPs). Included are descriptions of the available boot modes and any interfacing
requirements associated with them, instructions on generating the boot table, and
information on the different versions of the Bootloader.
SPRU966TMS320C645x DSP Enhanced DMA (EDMA3) Controller User's Guide. This document
describes the Enhanced DMA (EDMA3) Controller on the TMS320C645x digital signal
processors (DSPs).
SPRU580TMS320C6000 DSP Multichannel Buffered Serial Port (McBSP) Reference Guide.
Describes the operation of the multichannel buffered serial port (McBSP) in the digital signal
processors (DSPs) of the TMS320C6000 DSP family. The McBSP consists of a data path
and a control path that connect to external devices. Separate pins for transmission and
reception communicate data to these external devices. The C6000 CPU communicates to
the McBSP using 32-bit-wide control registers accessible via the internal peripheral bus.
www.ti.com
SPRU975TMS320C645x DSP EMAC/MDIO Module User's Guide. This 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 the
TMS320C645x digital signal processors (DSPs).
SPRUE60TMS320C645x DSP Peripheral Component Interconnect (PCI) User's Guide. This
document describes the peripheral component interconnect (PCI) port in the TMS320C645x
digital signal processors (DSPs). See the PCI Specification revision 2.3 for details on the PCI
interface.
User's Guide. This document describes the operation of the software-programmable
phase-locked loop (PLL) controller in the TMS320C645x 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 TMS320C645x DSP core, peripherals, and other modules inside the
TMS320C645x digital signal processors (DSPs).
SPRU974TMS320C645x DSP Inter-Integrated Circuit (I2C) Module User's Guide. This document
describes the inter-integrated circuit (I2C) module in the TMS320C645x Digital Signal
Processor (DSP). The I2C provides an interface between the TMS320C645x device and
other devices compliant with Philips Semiconductors Inter-IC bus (I2C-bus) specification
version 2.1 and connected by way of an I2C-bus. This document assumes the reader is
familiar with the I2C-bus specification.
SPRU968TMS320C645x DSP 64-Bit Timer User's Guide. This document provides an overview of the
64-bit timer in the TMS320C645x digital signal processors (DSPs). 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.
SPRU724TMS320C645x DSP General-Purpose Input/Output (GPIO) User's Guide. This document
describes the general-purpose input/output (GPIO) peripheral in the TMS320C645x digital
signal processors (DSPs). 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.
On the C6454 device, certain device configurations like boot mode, pin multiplexing, and endianess, are
selected at device reset. The status of the peripherals (enabled/disabled) is determined after device reset.
By default, the peripherals on the C6454 device are disabled and need to be enabled by software before
being used.
3.1Device Configuration at Device Reset
Table 3-1 describes the C6454 device configuration pins. The logic level of the AEA[19:0], ABA[1:0], and
PCI_EN 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 device configuration pins
are sampled during reset and are driven after the reset is removed. To avoid contention, the control device
should only drive the EMIFA pins when RESETSTAT is low.
If a configuration pin must be routed out from the device and 3-stated (not driven), 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 where external pullup/pulldown resistors are required, see
Section 3.7, Pullup/Pulldown Resistors.
www.ti.com
NOTE
Table 3-1. C6454 Device Configuration Pins (AEA[19:0], ABA[1:0], and PCI_EN)
CONFIGURATIONIPD/
PINIPU
AEA[19:16]IPD
AEA15P27IPD
NO.FUNCTIONAL DESCRIPTION
[N25,0100EMIFA 8-bit ROM boot
L26,
L25,
P26]
(1)
Boot Mode Selections (BOOTMODE [3:0]).
These pins select the boot mode for the device.
If selected for boot, the corresponding peripheral is automatically enabled after device reset.
For more detailed information on boot modes, see Section 2.4, Boot Sequence.
CFGGP[2:0] pins must be set to 000b during reset for proper operation of the PCI boot
mode.
EMIFA input clock source select (AECLKIN_SEL).
0AECLKIN (default mode)
1SYSCLK4 (CPU/x) Clock Rate. The SYSCLK4 clock rate is software selectable
via the Software PLL1 Controller. By default, SYSCLK4 is selected as CPU/8
clock rate.
(1) IPD = Internal pulldown, IPU = Internal pullup. For most systems, a 1-kΩ resistor can be used to oppose the IPU/IPD. For more detailed
information on pullup/pulldown resistors and situations where external pullup/pulldown resistors are required, see Section 3.7,
Pullup/Pulldown Resistors.
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.
1HPI operates in HPI32 mode.
HPI bus is 32 bits wide; HD[31:0] pins are used.
Applies only when HPI function of HPI/PCI multiplexed pins is selected (PCI_EN pin = 0).
Device Endian mode (LENDIAN).
1System operates in Little Endian mode (default).
For proper C6454 device operation, this pin must be externally pulled down with a 1-kΩ
resistor at device reset.
For proper C6454 device operation, this pin must be externally pulled down with a 1-kΩ
resistor at device reset.
EMAC Interface Selects (MACSEL[1:0]).
These pins select the interface used by the EMAC/MDIO peripheral.
0010/100 EMAC/MDIO with MII Interface [default]
0110/100 EMAC/MDIO with RMII Interface
1010/100/1000 EMAC/MDIO with GMII Interface
1110/100/1000 EMAC/MDIO with RGMII Interface
For more detailed information on the MAC_SEL[1:0] control pin selections, see .
PCI I2C EEPROM Auto-Initialization (PCI_EEAI).
PCI auto-initialization via external I2C EEPROM
0PCI auto-initialization through external I2C EEPROM is disabled. The PCI
AEA8P25IPD
Note: If the PCI pin function is disabled (PCI_EN pin = 0), this pin must not be pulled up.
AEA7N27IPDFor proper C6454 device operation, do not oppose the IPD on this pin.
PCI Frequency Selection (PCI66).
Selects the operating frequency of the PCI (either 33 MHz or 66 MHz).
AEA6U27IPD
Note: If the PCI pin function is disabled (PCI_EN pin = 0), this pin must not be pulled up.
McBSP1 pin function enable bit (MCBSP1_EN).
Selects which function is enabled on the McBSP1/GPIO multiplexed pins.
AEA5U28IPD
SYSCLKOUT Enable bit (SYSCLKOUT_EN).
AEA4T28IPD
AEA3T27IPD
[T26,
AEA[2:0]U26,IPD
U25]
Selects which function is enabled on the SYSCLK4/GP[1] muxed pin.
For proper C6454 device operation, the AEA3 pin must be pulled down to VSSusing a 1-kΩ
resistor.
Configuration General-Purpose Inputs (CFGGP[2:0])
The value of these pins is latched to the Device Status Register following device reset and is
used by the on-chip bootloader for some boot modes. For more information on the boot
modes, see Section 2.4, Boot Sequence.
peripheral uses the specified PCI default values (default).
1PCI auto-initialization through external I2C EEPROM is enabled. The PCI
peripheral is configured through external I2C EEPROM provided the PCI
peripheral pins are enabled (PCI_EN = 1).
0PCI operates at 33 MHz (default)
1PCI operates at 66 MHz
0GPIO pin function enabled (default).
This means all multiplexed McBSP1/GPIO pins function as GPIO pins.
1McBSP1 pin function enabled.
This means all multiplexed McBSP1/GPIO pins function as McBSP1 pins.
0GP[1] pin function is enabled (default)
1SYSCLK4 pin function is enabled
ABA0V26IPD0DDR2 Memory Controller peripheral pins are disabled (default)
ABA1V25IPD0EMIFA peripheral pins are disabled (default)
NO.FUNCTIONAL DESCRIPTION
(1)
PCI pin function enable bit (PCI_EN).
Selects which function is enabled on the HPI/PCI multiplexed pins.
0HPI pin function enabled (default)
This means all multiplexed HPI/PCI pins function as HPI pins.
1PCI pin function enabled
This means all multiplexed HPI/PCI pins function as PCI pins.
DDR2 Memory Controller enable (DDR2_EN).
1DDR2 Memory Controller peripheral pins are enabled
EMIFA enable (EMIFA_EN).
1EMIFA peripheral pins are enabled
3.2Peripheral Configuration at Device Reset
Some C6454 device peripherals share the same pins (internally multiplexed) and are mutually exclusive.
Therefore, not all peripherals may be used at the same time. The device configuration pins described in
Section 3.1, Device Configuration at Device Reset, determine which function is enabled for the multiplexed
pins.
www.ti.com
Note that when the pin function of a peripheral is disabled at device reset, the peripheral is permanently
disabled and cannot be enabled until its pin function is enabled and another device reset is executed.
Also, note that enabling the pin function of a peripheral does not enable the corresponding peripheral. All
peripherals on the C6454 device are disabled by default, except when used for boot, and must be enabled
through software before being used.
Other peripheral options like PCI clock speed and EMAC/MDIO interface mode can also be selected at
device reset through the device configuration pins. The configuration selected is also fixed at device reset
and cannot be changed until another device reset is executed with a different configuration selected.
The multiply factor of the PLL1 Controller is not selected through the configuration pins. The PLL1 multiply
factor is set in software through the PLL1 controller registers after device reset. The PLL2 multiply factor is
fixed. For more information, see Section 7.7, PLL1 and PLL1 Controller, and Section 7.8, PLL2 and PLL2Controller.
On the C6454 device, the PCI peripheral pins are multiplexed with the HPI pins. The PCI_EN pin selects
the function for the HPI/PCI multiplexed pins. The PCI66, PCI_EEAI, and HPI_WIDTH control other
functions of the PCI and HPI peripherals. Table 3-2 describes the effect of the PCI_EN, PCI66, PCI_EEAI,
and HPI_WIDTH configuration pins.
Table 3-2. PCI_EN, PCI66, PCI_EEAI, and HPI_WIDTH Peripheral Selection (HPI and PCI)
00b10/100 EMAC/MDIO with MII Interface [default]
01b10/100 EMAC/MDIO with RMII Interface
10b10/100/1000 EMAC/MDIO with GMII Interface
11b10/100/1000 EMAC/MDIO with RGMII Interface
(1) RGMII interface requires a 1.5-/1.8-V I/O supply.
PERIPHERAL FUNCTION SELECTED
EMAC/MDIO
(1)
3.3Peripheral Selection After Device Reset
On the C6454 device, peripherals can be in one of several states. These states are listed in Table 3-4.
Table 3-4. Peripheral States
STATEDESCRIPTION
Peripheral pin function has been completelyPCI
Static powerdown
Disabledoff. Default state for all peripherals not inEMAC/MDIO
Enabled
disabled through the device configurationMcBSP1
pins. Peripheral is held in reset and clock isEMAC/MDIO
turned off.EMIFA
Peripheral is held in reset and clock is turnedGPIO
static powerdown mode.McBSP0
Clock to the peripheral is turned on and theEMAC/MDIO
peripheral is taken out of reset.McBSP0
Enable in progressintermediate state when transitioning from an
disabled state to an enabled state.
Following device reset, all peripherals that are not in the static powerdown state are in the disabled state
by default. Peripherals used for boot such as HPI and PCI are enabled automatically following a device
reset.
Peripherals are only allowed certain transitions between states (see Figure 3-1).
www.ti.com
PERIPHERALS THAT CAN BE
IN THIS STATE
All peripherals that can be in an
enabled state.
Figure 3-2 shows the flow needed to change the state of a given peripheral on the C6454 device.
A 32-bit key (value = 0x0F0A 0B00) must be written to the Peripheral Lock register (PERLOCK) in order to
allow access to the PERCFG0 register. Writes to the PERCFG1 register can be done directly without
going through the PERLOCK register.
The instructions that write to the PERLOCK and PERCFG0 registers must be in the same
fetch packet if code is being executed from external memory. If the instructions are in
different fetch packets, fetching the second instruction from external memory may stall the
instruction long enough such that PERCFG0 register will be locked before the instruction is
executed.
3.4Device State Control Registers
The C6454 device has a set of registers that are used to control the status of its peripherals. These
registers are shown in Table 3-5 and described in the next sections.
The device state control registers can only be accessed using the CPU or the emulator.
When written with correct 32-bit key (0x0F0A0B00), the Peripheral Lock Register (PERLOCK) allows one
write to the PERCFG0 register within 16 SYSCLK3 cycles.
NOTE
The instructions that write to the PERLOCK and PERCFG0 registers must be in the same
fetch packet if code is being executed from external memory. If the instructions are in
different fetch packets, fetching the second instruction from external memory may stall the
instruction long enough such that PERCFG0 register will be locked before the instruction is
executed.
The Peripheral Configuration Register (PERCFG0) is used to change the state of the peripherals. One
write is allowed to this register within 16 SYSCLK3 cycles after the correct key is written to the PERLOCK
register.
NOTE
The instructions that write to the PERLOCK and PERCFG0 registers must be in the same
fetch packet if code is being executed from external memory. If the instructions are in
different fetch packets, fetching the second instruction from external memory may stall the
instruction long enough that the PERCFG0 register is locked before the instruction is
executed.
The Peripheral Configuration Register (PERCFG1) is used to enable the EMIFA and DDR2 Memory
Controller. EMIFA and the DDR2 Memory Controller do not have corresponding status bits in the
Peripheral Status Registers. The EMIFA and DDR2 Memory Controller peripherals can be used within 16
SYSCLK3 cycles after EMIFACTL and DDR2CTL are set to 1. Once EMIFACTL and DDR2CTL are set to
1, they cannot be set to 0. Note that if the DDR2 Memory Controller and EMIFA are disabled at reset
through the device configuration pins (DDR2.EN[ABA0] and EMIFA[ABA1]), they cannot be enabled
through the PERCFG1 register.
318
Reserved
R-0x00
7210
ReservedDDR2CTLEMIFACTL
R-0x00R/W-0R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
The Peripheral Status Registers (PERSTAT0 and PERSTAT1) show the status of the C6454 device
peripherals.
313029272624
ReservedHPISTATMcBSP1STAT
R-0R-0R-0
232120181716
McBSP0STATI2CSTATGPIOSTAT
R-0R-0R-0
1514121198
GPIOSTATTIMER1STATTIMER0STATEMACSTAT
R-0R-0R-0R-0
7650
EMACSTATReserved
R-0R-0
LEGEND: R = Read only; -n = value after reset
Figure 3-6. Peripheral Status Register 0 (PERSTAT0) - 0x02AC 0014
Table 3-9. Peripheral Status Register 0 (PERSTAT0) Field Descriptions
BitFieldValueDescription
31:30ReservedReserved.
29:27HPISTATHPI status
000HPI is in the disabled state
001HPI is in the enabled state
011HPI is in the static powerdown state
100HPI is in the disable in progress state
101HPI is in the enable in progress state
Others Reserved
26:24McBSP1STATMcBSP1 status
000McBSP1 is in the disabled state
001McBSP1 is in the enabled state
011McBSP1 is in the static powerdown state
100McBSP1 is in the disable in progress state
101McBSP1 is in the enable in progress state
Others Reserved
23:21McBSP0STATMcBSP0 status
000McBSP0 is in the disabled state
001McBSP0 is in the enabled state
011McBSP0 is in the static powerdown state
100McBSP0 is in the disable in progress state
101McBSP0 is in the enable in progress state
Table 3-9. Peripheral Status Register 0 (PERSTAT0) Field Descriptions (continued)
BitFieldValueDescription
20:18I2CSTATI2C status
000I2C is in the disabled state
001I2C is in the enabled state
011I2C is in the static powerdown state
100I2C is in the disable in progress state
101I2C is in the enable in progress state
Others Reserved
17:15GPIOSTATGPIO status
000GPIO is in the disabled state
001GPIO is in the enabled state
011GPIO is in the static powerdown state
100GPIO is in the disable in progress state
101GPIO is in the enable in progress state
Others Reserved
14:12TIMER1STATTimer1 status
000Timer1 is in the disabled state
001Timer1 is in the enabled state
011Timer1 is in the static powerdown state
100Timer1 is in the disable in progress state
101Timer1 is in the enable in progress state
Others Reserved
11:9TIMER0STATTimer0 status
000Timer0 is in the disabled state
001Timer0 is in the enabled state
011Timer0 is in the static powerdown state
100Timer0 is in the disable in progress state
101Timer0 is in the enable in progress state
Others Reserved
8:6EMACSTATEMAC/MDIO status
000EMAC/MDIO is in the disabled state
001EMAC/MDIO is in the enabled state
011EMAC/MDIO is in the static powerdown state
100EMAC/MDIO is in the disable in progress state
101EMAC/MDIO is in the enable in progress state
Others Reserved
5:0ReservedReserved
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
3116
Reserved
R-0
155320
ReservedPCISTAT
R-0R-0
LEGEND: R = Read only; -n = value after reset
Figure 3-7. Peripheral Status Register 1 (PERSTAT1) - 0x02AC 0018
The EMAC Configuration Register (EMACCFG) is used to assert and deassert the reset of the Reduced
Media Independent Interface (RMII) logic of the EMAC. For more details on how to use this register, see
Section 7.14, Ethernet MAC (EMAC).
3124
Reserved
R/W-0
2319181716
ReservedRMII_RSTReserved
R/W-0001bR/W-1R/W-0
150
Reserved
R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
The Emulator Buffer Powerdown Register (EMUBUFPD) is used to control the state of the pin buffers of
emulator pins EMU[18:2]. These buffers can be powered down if the device trace feature is not needed.
318
Reserved
R-0
710
ReservedEMUCTL
R-0R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
The device status register depicts the device configuration selected upon device reset. Once set, these
bits will remain set until a device reset. For the actual register bit names and their associated bit field
descriptions, see Figure 3-10 and Table 3-13.
Note that enabling or disabling peripherals through the Peripheral Configuration Registers (PERCFG0 and
PERCFG1) does not affect the DEVSTAT register. To determine the status of peripherals following writes
to the PERCFG0 and PERCFG1 registers, read the Peripherals Status Registers (PERSTAT0 and
PERSTAT1).
LEGEND: R/W = Read/Write; R = Read only; -x = value after reset
Note: The default values of the fields in the DEVSTAT register are latched from device configuration pins, as described in Section 3.1,
Device Configuration at Device Reset. The default values shown here correspond to the setting dictated by the internal pullup or pulldown
resistor.
Figure 3-10. Device Status Register (DEVSTAT) - 0x02A8 0000
Table 3-13. Device Status Register (DEVSTAT) Field Descriptions
BitFieldValueDescription
31:23ReservedReserved. Read-only, writes have no effect.
22EMIFA_ENEMIFA Enable (EMIFA_EN) status bit
21DDR2_ENDDR2 Memory Controller Enable (DDR2_EN) status bit
20PCI_ENPCI Enable (PCI_EN) status bit
19:17CFGGP[2:0]Used as General-Purpose inputs for configuration purposes.
16ReservedReserved. Read-only, writes have no effect.
15SYSCLKOUT_ENSYSCLKOUT Enable (SYSCLKOUT_EN) status bit
Shows the status of whether the EMIFA peripheral pins are enabled/disabled.
0EMIFA peripheral pins are disabled (default)
1EMIFA peripheral pins are enabled
Shows the status of whether the DDR2 Memory Controller peripheral pins are enabled/disabled.
0DDR2 Memory Controller peripheral pins are disabled (default)
1DDR2 Memory Controller peripheral pins are enabled
Shows the status of which function is enabled on the HPI/PCI multiplexed pins.
0HPI pin functions are enabled (default)
1PCI pin functions are enabled
These pins are latched at reset. These values can be used by S/W routines for boot operations.
Shows the status of which function is enabled on the SYSCLK4/GP[1] muxed pin.
0GP[1] pin function of the SYSCLK4/GP[1] pin enabled (default)
1SYSCLK4 pin function of the SYSCLK4/GP[1] pin enabled
Table 3-13. Device Status Register (DEVSTAT) Field Descriptions (continued)
BitFieldValueDescription
14MCBSP1_ENMcBSP1 Enable (MCBSP1_EN) status bit
Shows the status of which function is enabled on the McBSP1/GPIO muxed pins.
0GPIO pin functions enabled (default)
1McBSP1 pin functions enabled
13PCI66PCI Frequency Selection (PCI66) status bit
Shows the PCI operating frequency selected at reset.
0PCI operates at 33 MHz (default)
1PCI operates at 66 MHz
11PCI_EEAIPCI I2C EEPROM Auto-Initialization (PCI_EEAI) status bit
Shows whether the PCI auto-initialization via external I2C EEPROM is enabled/disabled.
0PCI auto-initialization through external I2C EEPROM is disabled; the PCI peripheral uses the
specified PCI default values (default).
1PCI auto-initialization through external I2C EEPROM is enabled; the PCI peripheral is configured
through external I2C EEPROM provided the PCI peripheral pin is enabled (PCI_EN = 1).
10:9MACSEL[1:0]EMAC Interface Select (MACSEL[1:0]) status bits
Shows which EMAC interface mode has been selected.
0010/100 EMAC/MDIO with MII Interface (default)
0110/100 EMAC/MDIO with RMII Interface
1010/100/1000 EMAC/MDIO with GMII Interface
1110/100/1000 EMAC/MDIO with RGMII Mode Interface
[RGMII interface requires a 1.8-V or 1.5-V I/O supply]
8:7ReservedReserved. Read-only, writes have no effect.
6LENDIANDevice Endian mode (LENDIAN)
Shows the status of whether the system is operating in Big Endian mode or Little Endian mode
(default).
0System is operating in Big Endian mode
1System is operating in Little Endian mode (default)
5HPI_WIDTHHPI bus width control bit.
Shows the status of whether the HPI bus operates in 32-bit mode or in 16-bit mode (default).
0HPI operates in 16-bit mode. (default)
1HPI operates in 32-bit mode
4AECLKINSELEMIFA input clock select
Shows the status of what clock mode is enabled or disabled for EMIFA.
0AECLKIN (default mode)
1SYSCLK4 (CPU/x) Clock Rate. The SYSCLK4 clock rate is software selectable via the PLL1
Controller. By default, SYSCLK4 is selected as CPU/8 clock rate.
3:0BOOTMODE[3:0]Boot mode configuration bits
Shows the status of what device boot mode configuration is operational.
BOOTMODE[3:0]
[Note: if selected for boot, the corresponding peripheral is automatically enabled after device reset.]
The JTAG ID register is a read-only register that identifies to the customer the JTAG/Device ID. For the
C6454 device, the JTAG ID register resides at address location 0x02A8 0008. For the actual register bit
names and their associated bit field descriptions, see Figure 3-11 and Table 3-14.
3128 2712 1110
VARIANTPART NUMBERMANUFACTURER
(4-bit)(16-bit)(11-bit)
R-nR-0000 0000 1000 1010b0000 0010 111bR-1
LEGEND: R = Read only; -n = value after reset
Figure 3-11. JTAG ID (JTAGID) Register - 0x02A8 0008
Table 3-14. JTAG ID (JTAGID) Register Field Descriptions
BitFieldValueDescription
31:28 VARIANTVariant (4-Bit) value. The value of this field depends on the silicon revision being
27:12 PART NUMBERPart Number (16-Bit) value. C6454 device value: 0000 0000 1000 1010b.
Proper board design should ensure that input pins to the C6454 device always be at a valid logic level and
not floating. This may be achieved via pullup/pulldown resistors. The C6454 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 3-stated (not driven), 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 3-stated (not driven),
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 VILlevel of
all inputs connected to the net. For a pullup resistor, this should be above the highest VIHlevel of all
inputs on the net. A reasonable choice would be to target the VOLor VOHlevels for the logic family of
the limiting device; which, by definition, have margin to the VILand VIHlevels.
•Select a pullup/pulldown resistor with the largest possible value; but, which 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 which 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 DVDDrail.
www.ti.com
For most systems, a 1-kΩ resistor can be used to oppose the IPU/IPD while meeting the above criteria.
Users should confirm this resistor value is correct for their specific application.
For most systems, 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 (II), and the low-/high-level input voltages (VILand VIH) for
the C6454 device, see Section 6.3, Electrical Characteristics Over Recommended Ranges of SupplyVoltage and Operating Case Temperature.
To determine which pins on the C6454 device include internal pullup/pulldown resistors, see Table 2-3,
Terminal Functions.
3.8Configuration Examples
Figure 3-12 and Figure 3-13 illustrate examples of peripheral selections/options that are configurable on
On the C6454 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. 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 C6454 device: data buses and configuration buses. Some C6454 device
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 McBSP via its 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. Masters include the EDMA3 traffic controllers
and PCI. Slaves include the McBSP and I2C.
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
The C6454 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). The data SCR
connects masters to slaves via 128-bit data buses running at a SYSCLK2 frequency (SYSCLK2 is
generated from 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 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).
The configuration SCR connects C64x+ Megamodule to slaves via 32-bit configuration buses running at a
SYSCLK2 frequency (SYSCLK2 is generated from PLL1 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 and DDR2 memory controller require a bridge to convert their 64-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
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 a SYSCLK2 frequency. SYSCLK2 is supplied by the PLL1 controller and
is fixed at a frequency equal to the CPU frequency divided by 3.
Some peripherals, like PCI and the C64x+ Megamodule, have both slave and master ports. Note that
each EDMA3 transfer controller has an independent connection to the data SCR.
Note that masters can access the configuration SCR through the data SCR. The configuration SCR is
described in Section 4.3.
Not all masters on the C6454 DSP may connect to all slaves. Allowed connections are summarized in
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 PLL1 and PLL2 controller registers; these can only be
accessed by the C64x+ Megamodule.
The configuration SCR uses 32-bit configuration buses running at SYSCLK2 frequency. SYSCLK2 is
supplied by the PLL1 controller and is fixed at a frequency equal to the CPU frequency divided by 3.
priority levels for C6454 bus masters are shown in Table 4-2. 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 Figure 4-3. The C64x+ megamodule and EDMA masters
contain registers that control their own priority values.
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.
In the PRI_ALLOC register, the HOST field applies to the priority of the HPI and PCI peripherals. The
EMAC field specifies the priority of the EMAC peripheral.
A. When accessing the internal ROM of the DSP, the CPU frequency must always be less than 750 MHz.
TMS320C6454
www.ti.com
5C64x+ Megamodule
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.
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
5.1Memory Architecture
For more detailed information on the TMS320C64x+ Megamodule on the C6454 device, see the
TMS320C64x+ Megamodule Reference Guide (literature number SPRU871).
The TMS320C6454 device contains a 1024KB 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 C6454 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 C6454 device is as follows:
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 (L1PMODE) 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 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.
www.ti.com
Figure 5-2. TMS320C6454 L1P Memory Configurations
Figure 5-3. TMS320C6454 L1D Memory Configurations
The L2 memory configuration for the C6454 device is as follows:
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.
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
– Memory size is 1024KB
– Starting address is 0080 0000h
– 2-cycle latency
– 4 × 128-bit bank configuration
– Memory size is 32K bytes (this corresponds to the internal ROM)
– Starting address is 0010 0000h
– 1-cycle latency
– 1 × 256-bit bank configuration
For more information on the operation L1 and L2 caches, see the TMS320C64x+ DSP Cache User'sGuide (literature number SPRU862).
All memory on the C6454 device has a unique location in the memory map (see Table 2-2).
When accessing the internal ROM of the DSP, the CPU frequency must always be less than 750 MHz.
Therefore, when using a software boot mode, care must be taken such that the CPU frequency does not
exceed 750 MHz at any point during the boot sequence. After the boot sequence has completed, the CPU
frequency can be programmed to the frequency required by the application. For more detailed information
ont he boot modes, see Section 2.4, Boot Sequence.
5.2Memory 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 16 pages of L2 (64KB 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. 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. Note that EDMA or IDMA transfers programmed by the
CPU count as global accesses.
The CPU and the system masters on the C6454 device are all assigned a privilege ID of 0. Therefore it is
only possible to specify whether memory pages are locally or globally accessible. The AID0 and LOCAL
bits of the memory protection page attribute registers specify the memory page protection scheme, see
Table 5-1.
Table 5-1. Available Memory Page Protection Schemes
AID0 BitLOCAL 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
11All accesses permitted
For more information on memory protection for L1D, L1P, and L2, see the TMS320C64x+ MegamoduleReference Guide (literature number SPRU871).
5.3Bandwidth Management
www.ti.com
accesses initiated by the CPU).
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
Section 4.4. 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).
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.
The C6454 device 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).
5.5Megamodule Resets
Table 5-2 shows the reset types supported on the C6454 device and they affect the resetting of the
Megamodule, either both globally or just locally.
Power-On ResetYY
Warm ResetYY
System ResetYY
CPU ResetNY
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
NOTE
Table 5-2. Megamodule Reset (Global or Local)
GLOBALLOCAL
RESET TYPEMEGAMODULEMEGAMODULE
RESETRESET
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
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 Figure 5-5
and described in Table 5-3. The C64x+ Megamodule revision is dependant on the silicon revision being
used. For more information, see the TMS320C6455/54 Digital Signal Processor Silicon Errata (literature
number SPRZ234).
3116 150
VERSIONREVISION
R-1hR-n
LEGEND: R = Read only; -n = value after reset
A.The C64x+ Megamodule revision is dependant on the silicon revision being used. For more information, see
the TMS320C6455/54 Digital Signal Processor Silicon Errata (literature number SPRZ234).
Table 5-3. Megamodule Revision ID Register (MM_REVID) Field Descriptions
BitFieldValueDescription
31:16VERSION1hVersion of the C64x+ Megamodule implemented on the device. This field is always read as 1h.
15:0REVISIONRevision of the C64x+ Megamodule version implemented on the device. The C64x+ Megamodule
revision is dependant on the silicon revision being used. For more information, see the
TMS320C6455/54 Digital Signal Processor Silicon Errata (literature number SPRZ234).
0180 00A0MEVTFLAG0Masked Event Flag Status Register 0 (Events [31:0])
0180 00A4MEVTFLAG1Masked Event Flag Status Register 1
0180 00A8MEVTFLAG2Masked Event Flag Status Register 2
0180 00ACMEVTFLAG3Masked Event Flag Status Register 3
6.1Absolute Maximum Ratings Over Operating Case Temperature Range (Unless
Otherwise Noted)
Supply voltage range:CV
Input voltage (VI) range:3.3-V pins (except PCI-capable pins)-0.5 V to DV
Output voltage (VO) range:3.3-V pins (except PCI-capable pins)-0.5 V to DV
Operating case temperature range, TC:(default)0°C to 90°C
Storage temperature range, T
(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 V
stg
(1)
(2)
DD
(2)
DV
DD33
DV
, DV
DD15
DD18
PLLV1, PLLV2
(2)
, AV
DLL1
, AV
DLL2
(2)
PCI-capable pins-0.5 V to DV
-0.5 V to 1.5 V
-0.5 V to 4.2 V
-0.5 V to 2.5 V
-0.5 V to 2.5 V
DD33
DD33
RGMII pins-0.5 V to 2.5 V
DDR2 memory controller pins-0.5 V to 2.5 V
DD33
PCI-capable pins-0.5 V to DV
DD33
RGMII pins-0.5 V to 2.5 V
DDR2 memory controller pins-0.5 V to 2.5 V
(1) For test conditions shown as MIN, MAX, or NOM, use the appropriate value specified in the recommended operating conditions table.
(2) These rated numbers are from the PCI Local Bus Specification (version 2.3). The DC specifications and AC specifications are defined in
Table 4-3 and Table 4-4, respectively, of the PCI Local Bus Specification.
(3) IIapplies to input-only pins and bi-directional pins. For input-only pins, IIindicates the input leakage current. For bi-directional pins, I
includes input leakage current and off-state (hi-Z) output leakage current.
I
(4) PCI input leakage currents include Hi-Z output leakage for all bidirectional buffers with 3-state outputs.
(5) IOZapplies to output-only pins, indicating off-state (hi-Z) output leakage current.
(6) Assumes the following conditions: 60% CPU utilization; DDR2 at 50% utilization (250 MHz), 50% writes, 32 bits, 50% bit switching; two
2-MHz McBSPs at 100% utilization, 50% switching; two 75-MHz Timers at 100% utilization; device configured for HPI32 mode with
pull-up resistors on HPI pins; room temperature (25°C). The actual current draw is highly application-dependent. For more details on
core and I/O activity, see the TMS320C6455/54 Power Consumption Summary application report (literature number SPRAAE8).
NOTE: The data sheet provides timing at the device pin. For output timing analysis, the tester pin electronics and its transmission line ef fects 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.
Input requirements in this data sheet are tested with an input slew rate of < 4 Volts per nanosecond (4 V/ns) at the device pin.
42 Ω3.5 nH
Device Pin
(see Note)
V
ref
= 1.5 V
V
ref
= VIL MAX (or VOL MAX)
V
ref
= VIH MIN (or VOH MIN)
TMS320C6454
www.ti.com
SPRS311F–APRIL 2006–REVISED SEPTEMBER 2010
7C64x+ Peripheral Information and Electrical Specifications
7.1Parameter Information
Figure 7-1. Test Load Circuit for AC Timing Measurements
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.13.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-2. Input and Output Voltage Reference Levels for AC Timing Measurements
All rise and fall transition timing parameters are referenced to VILMAX and VIHMIN for input clocks,
VOLMAX and VOHMIN for output clocks.
Figure 7-3. Rise and Fall Transition Time Voltage Reference Levels
7.1.23.3-V Signal Transition Rates
All timings are tested with an input edge rate of 4 volts per nanosecond (4 V/ns).
7.1.3Timing 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 utilizing 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 TimingAnalysis 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-1 and Figure 7-4).
Figure 7-4 represents a general transfer between the DSP and an external device. The figure also
represents board route delays and how they are perceived by the DSP and the external device.
Table 7-1. Board-Level Timing Example
NO.DESCRIPTION
1Clock route delay
2Minimum DSP hold time
3Minimum DSP setup time
4External device hold time requirement
5External device setup time requirement
6Control signal route delay
7External device hold time
8External device access time
9DSP hold time requirement
10DSP setup time requirement
11Data route delay
www.ti.com
(see Figure 7-4)
A.Control signals include data for Writes.
B.Data signals are generated during Reads from an external device.
7.2Recommended Clock and Control Signal Transition Behavior
All clocks and control signals must transition between VIHand VIL(or between VILand VIH) in a monotonic
manner.
TI recommends the power-supply sequence shown in Figure 7-5. After the DV
remaining power supplies can be powered up at the same time as CVDDas long as their supply voltage
never exceeds the CVDDvoltage during powerup. 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.
Figure 7-5. Power-Supply Sequence
Table 7-2. Timing Requirements for Power-Supply Sequence
NO.UNIT
1t
su(DVDD33-CVDD12)
2t
su(CVDD12-ALLSUP)
Setup time, DV
Setup time, CV
supply stable before CV
DD33
supply stable before all other supplies stable0200ms
DD12
supply stable0.5200ms
DD12
supply is stable, the
DD33
-720
-850
A-1000/-1000
MINMAX
7.3.2Power-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.
7.3.3Power-Down Operation
One of the power goals for the C6454 device is to reduce power dissipation due to unused peripherals.
There are different ways to power down peripherals on the C6454 device.
Some peripherals can be statically powered down at device reset through the device configuration pins
(see Section 3.1, Device Configuration at Device Reset). Once in a static power-down state, the peripheral
is held in reset and its clock is turned off. Peripherals cannot be enabled once they are in a static
power-down state. To take a peripheral out of the static power-down state, a device reset must be
executed with a different configuration pin setting.
After device reset, all peripherals on the C6454 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.3, Peripheral Selection AfterDevice Reset.
Peripherals used for booting, like I2C and HPI, are automatically enabled after device reset. It is not
possible to disable these peripherals after the boot process is complete.
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).
7.3.4Preserving Boundary-Scan Functionality on RGMII and DDR2 Memory Pins
When the RGMII mode of the EMAC is not used, the DV
pins can be connected directly to ground (VSS) to save power. However, this will prevent boundary-scan
from functioning on the RGMII pins of the EMAC. To preserve boundary-scan functionality on the RGMII
pins, DV
•DV
•V
REFHSTL
DV
, V
DD15
DD15
REFHSTL
and DV
- connect to a voltage of DV
supply using two 1-kΩ resistors to form a resistor divider circuit.
DD18
, RSV14, and RSV13 should be connected as follows:
DD15MON
- connect these pins to the 1.8-V I/O supply (DV
/2. The DV
DD18
•RSV13 - connect this pin to ground (VSS) via a 200-Ω resistor.
•RSV14 - connect this pin to the 1.8-V I/O supply (DV
Similarly, when the DDR2 Memory Controller is not used, the V
connected directly to ground (VSS) to save power. However, this will prevent boundary-scan from
functioning on the DDR2 Memory Controller pins. To preserve boundary-scan functionality on the DDR2
Memory Controller pins, V
•V
REFSSTL
DV
- connect to a voltage of DV
supply using two 1-kΩ resistors to form a resistor divider circuit.
DD18
REFSSTL
, RSV11, and RSV12 should be connected as follows:
/2. The DV
DD18
•RSV11 - connect this pin to ground (VSS) via a 200-Ω resistor.
•RSV12 - connect this pin to the 1.8-V I/O supply (DV