• 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.