•Six ALUs (32-/40-Bit), Each Supports
Single 32-Bit, Dual 16-Bit, or Quad 8-Bit
Arithmetic per Clock Cycle– 16K-Byte Instruction Cache
•Two Multipliers Support Four 16 x 16-Bit– 8K-Byte Data Cache
Multiplies (32-Bit Results) per Clock
Cycle or Eight 8 x 8-Bit Multiplies (16-Bit
Results) per Clock Cycle
– Load-Store Architecture With Non-Aligned
Support
– 64 32-Bit General-Purpose Registers
– Instruction Packing Reduces Code Size
– All Instructions Conditional
– Additional C64x+™ Enhancements
•Protected Mode Operation
•Exceptions Support for Error Detection
and Program Redirection
•Hardware Support for Modulo Loop
Operation
• C64x+ Instruction Set Features
– Byte-Addressable (8-/16-/32-/64-Bit Data)
– 8-Bit Overflow Protection
– Bit-Field Extract, Set, Clear
– Normalization, Saturation, Bit-Counting
– Compact 16-Bit Instructions
– Additional Instructions to Support Complex
Multiplies
Mapped)
Set-Associative)
– 64K-Byte L2 Unified Mapped RAM/Cache
(Flexible RAM/Cache Allocation)
• ARM926EJ-S Core
– Support for 32-Bit and 16-Bit (Thumb®
Mode) Instruction Sets
– DSP Instruction Extensions and Single Cycle
MAC
– ARM® Jazelle® Technology
– Embedded ICE-RT™ Logic for Real-Time
Debug
• ARM9 Memory Architecture
– 16K-Byte RAM
– 8K-Byte ROM
• Embedded Trace Buffer™ (ETB11™) With 4KB
Memory for ARM9 Debug
• Endianness: Little Endian for ARM and DSP
• Video Imaging Co-Processor (VICP)
• Video Processing Subsystem
– Front End Provides:
•CCD and CMOS Imager Interface
•BT.601/BT.656 Digital YCbCr 4:2:2
(8-/16-Bit) Interface
•Preview Engine for Real-Time Image
Processing
•Glueless Interface to Common Video
Decoders
•Histogram Module
•Auto-Exposure, Auto-White Balance, and
Auto-Focus Module
•Resize Engine
– Resize Images From 1/4x to 4x
– Separate Horizontal/Vertical Control
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.
• Audio Serial Port (ASP)
– I2S
– AC97 Audio Codec Interface
– Standard Voice Codec Interface (AIC12)
(Progressive)• 10/100 Mb/s Ethernet MAC (EMAC)
•Digital Output– IEEE 802.3 Compliant
– 8-/16-bit YUV or up to 24-Bit RGB– Media Independent Interface (MII)
– HD Resolution• VLYNQ™ Interface (FPGA Interface)
– Up to Two Video Windows• Host Port Interface (HPI) with 16-Bit
The TMS320DM6441 (also referenced as DM6441) leverages TI’s DaVinci™ technology to meet the
networked media encode and decode application processing needs of next-generation embedded devices.
The DM6441 enables OEMs and ODMs to quickly bring to market devices featuring robust operating
systems support, rich user interfaces, high processing performance, and long battery life through the
maximum flexibility of a fully integrated mixed processor solution.
The dual-core architecture of the DM6441 provides benefits of both DSP and Reduced Instruction Set
Computer (RISC) technologies, incorporating a high-performance TMS320C64x+ DSP core and an
ARM926EJ-S core.
The ARM926EJ-S is a 32-bit RISC processor core that performs 32-bit or 16-bit instructions and
processes 32-bit, 16-bit, or 8-bit data. The core uses pipelining so that all parts of the processor and
memory system can operate continuously.
The ARM core incorporates:
•A coprocessor 15 (CP15) and protection module
•Data and program memory management units (MMUs) with table look-aside buffers.
•Separate 16K-byte instruction and 8K-byte data caches. Both are four-way associative with virtual
index virtual tag (VIVT).
The TMS320C64x+™DSPs arethe highest-performancefixed-point DSPgeneration inthe
TMS320C6000™ DSP platform. It is based on an enhanced version of the second-generation
high-performance, advanced very-long-instruction-word(VLIW) architecture developed byTexas
Instruments (TI), making these DSP cores an excellent choice for digital media applications. The C64x is a
code-compatible member of the C6000™ DSP platform. The TMS320C64x+ DSP is an enhancement of
the C64x+ DSP with added functionality and an expanded instruction set.
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
Any reference to the C64x DSP or C64x CPU also applies, unless otherwise noted, to the C64x+ DSP and
C64x+ CPU, respectively.
With performance of up to 4104 million instructions per second (MIPS) at a clock rate of 513 MHz, the
C64x+ core offers solutions to high-performance DSP programming challenges. The DSP core possesses
the operational flexibility of high-speed controllers and the numerical capability of array processors. The
C64x+ DSP core processor has 64 general-purpose registers of 32-bit word length and eight highly
independent functional units—two multipliers for a 32-bit result and six arithmetic logic units (ALUs). The
eight functional units include instructions to accelerate the performance in video and imaging applications.
The DSP core can produce four 16-bit multiply-accumulates (MACs) per cycle for a total of 2052 million
MACs per second (MMACS), or eight 8-bit MACs per cycle for a total of 4104 MMACS. For more details
on the C64x+ DSP, see the TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide
(literature number SPRU732).
The DM6441 also has application-specific hardware logic, on-chip memory, and additional on-chip
peripherals similar to the other C6000 DSP platform devices. The DM6441 core uses a two-level
cache-based architecture. The Level 1 program cache (L1P) is a 256K-bit direct mapped cache and the
Level 1 data cache (L1D) is a 640K-bit 2-way set-associative cache. The Level 2 memory/cache (L2)
consists of an 512K-bit memory space that is shared between program and data space. L2 memory can
be configured as mapped memory, cache, or combinations of the two.
The peripheral set includes: two configurable video ports; a 10/100 Mb/s Ethernet MAC (EMAC) with a
management data input/output (MDIO) module; an inter-integrated circuit (I2C) bus interface; one audio
serial port (ASP); two 64-bit general-purpose timers each configurable as two independent 32-bit timers;
one 64-bit watchdog timer; up to 71 pins of general-purpose input/output (GPIO) with programmable
interrupt/event generation modes, multiplexed with other peripherals; three UARTs with hardware
handshaking support on one UART; three pulse width modulator (PWM) peripherals; and two external
memory interfaces: an asynchronous external memory interface (EMIFA) for slower memories/peripherals,
and a higher speed synchronous memory interface for DDR2.
The DM6441 device includes a video processing subsystem (VPSS) with two configurable video/imaging
peripherals: one video processing front-end (VPFE) input used for video capture, one video processing
back-end (VPBE) output with imaging coprocessor (VICP) used for display.
The video processing front-end (VPFE) consists of a CCD controller (CCDC), a preview engine
(previewer), histogram module, auto-exposure/white balance/focus module (H3A), and resizer. The CCDC
is capable of interfacing to common video decoders, CMOS sensors, and charge coupled devices (CCDs).
The previewer is a real-time image processing engine that takes raw imager data from a CMOS sensor or
CCD and converts from an RGB Bayer pattern to YUV4:2:2. The histogram and H3A modules provide
statistical information on the raw color data for use by the DM6441. The resizer accepts image data for
separate horizontal and vertical resizing from 1/4x to 4x in increments of 256/N, where N is between 64
and 1024.
The video processing back-end (VPBE) consists of an on-screen display engine (OSD) and a video
encoder (VENC). The OSD engine is capable of handling two separate video windows and two separate
OSD windows. Other configurations include two video windows, one OSD window, and one attribute
window allowing up to eight levels of alpha blending. The VENC provides four analog DACs that run at
54 MHz, providing a means for composite NTSC/PAL video, S-Video, and/or component video output. The
VENC also provides up to 24 bits of digital output to interface to RGB888 devices. The digital output is
capable of 8/16-bit BT.656 output and/or CCIR.601 with separate horizontal and vertical syncs. VFocus
(part of the VPBE functionality and operationally (e.g., 16-bit multiplexed address/data) is also provided.
The Ethernet media access controller (EMAC) provides an efficient interface between the DM6441 and the
network. The DM6441 EMAC support both 10Base-T and 100Base-TX, or 10 Mbits/second (Mbps) and
100 Mbps in either half- or full-duplex mode, with hardware flow control and quality of service (QOS)
support.
www.ti.com
The management data input/output (MDIO) module continuously polls all 32 MDIO addresses in order to
enumerate all PHY devices in the system. Once a PHY candidate has been selected by the ARM, the
MDIO module transparently monitors its link state by reading the PHY status register. Link change events
are stored in the MDIO module and can optionally interrupt the ARM, allowing the ARM to poll the link
status of the device without continuously performing costly MDIO accesses.
The HPI, I2C, SPI, USB2.0, and VLYNQ ports allow DM6441 to easily control peripheral devices and/or
communicate with host processors. The DM6441 also provides Memory Stick/Memory Stick PRO card
support, MMC/SD with SDIO support, and a universal serial bus (USB).
The DM6441 also includes a video/imaging coprocessor (VICP) to offload many video and imaging
processing tasks from the DSP core, making more DSP MIPS available for common video and imaging
algorithms. For more information on the VICP enhanced codecs, such as H.264 and MPEG4, please
contact your nearest TI sales representative.
The rich peripheral set provides the ability to control external peripheral devices and communicate with
external processors. For details on each of the peripherals, see the related sections later in this document
and the associated peripheral reference guides listed in Section 2.8.3.1, Related Documentation FromTexas Instruments.
The DM6441 has a complete set of development tools for both the ARM and DSP. These include C
compilers, a DSP assembly optimizer to simplify programming and scheduling, and a Windows™
debugger interface for visibility into source code execution.
This data manual revision history highlights the technical changes made to the SPRS359D device-specific
data manual to make it an SPRS359E revision.
Scope: Added information/data on silicon revision 2.3.
Applicable updates to the DM644x device family, specifically relating to the TMS320DM6441 device, have
been incorporated.
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
Revision History
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
•Added "In host boot mode, the ARM is the master and controls the reset and boot of the C64x+ ..."
paragraph
Submit Documentation Feedback
Product Folder Link(s): TMS320DM6441
TMS320DM6441
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
TMS320DM6441 Revision History (continued)
SEEADDITIONS/MODIFICATIONS/DELETIONS
Section 3.5.1Table 3-12, DM6441 Default Bus Master Priorities:
Switched Central
Resource (SCR) Bus
Priorities
Section 3.5.4
PINMUX0 Register
Description
•Added, for clarity, ", DMA_PRI bit fields" to the VPSSP Default Priority Level description [Cleared
Documentation Feedback Issue]
•Added "[For more detailed information ..." statement to the VPSSP, EDMATC0P, EDMATC1P, and
C64X+_DMAP rows
•Added "(MSTPRI1 Register)" to the HPIP row
•Removed VICPP row with Default Priority Level of 4
Figure 3-6, MSTPRI1 Register:
•Updated/changed the bit field of bits 22:20 from "RESERVED" to "HPIP"
•Updated/changed the default value of bits 22:20 from "R-100" to "R/W-100"
•"The PINMUX0 pin multiplexing register controls which peripheral is given ownership ..." paragraph:
–Updated/changed "... ownership over shared pins among EMAC, CCD, LCD, RGB888, RGB666,
ATA, VLYNQ, EMIFA, and GPIO peripherals" to "... ownership over shared pins among EMAC,
CCD, LCD, RGB888, RGB666, ATA, VLYNQ, EMIFA, HPI, and GPIO peripherals"
Figure 3-7, PINMUX0 Register:
•Bits 4–0: Updated/changed "R/W-LLLL" to "R/W-LLLLL"
•Updated/changed footnote from "For proper DM6441 device operation, always write a value of '0' to
RSV bits 30 and 29" to "For proper DM6441 device operation, always write a value of '0' to
RSV bit 30"
Table 3-14, PINMUX0 Register Field Descriptions:
•Updated/changed the description of Bit 29 (HPIEN) [Cleared Documentation Feedback Issue]
Section 6.6.3Table 6-19, Switching Characteristics Over Recommended Operating Conditions for CLK_OUT1:
Clock PLL Electrical
Data/Timing (Input and
Output Clocks)
•Removed "For proper DM6441 device operation, always write a value of '0' to RSV bit 9" footnote
•Bits 15–13: Updated/changed "R-0000 00" to "R-000"
•"Measured under the following conditions:" footnote:
–Added "For more details on core and I/O activity, as well as information relevant to board power
supply design, see the TMS320DM6441 Power Consumption Summary application report
(literature number SPRAAU3)."
•PLL Controller 2: Updated/changed "PLLDIV1 (/1)" to "PLLDIV1 (/10)"
•Updated/changed "EDMA" to "EDMA3"
•Updated/changed address range "0x01C4 1004 through 0x01C4 1014 to "Reserved"
•Updated/changed address range "0x01C4 1100 through 0x01C4 111F to "Reserved"
•Updated/changed address range "0x01C4 1308 through 0x01C4 17FF to "Reserved"
•Updated/changed the pins specified in the Z Group [Cleared Documentation Feedback Issue]
•Parameter 1 (tC): Added "ns" in UNIT column
Section 6.10.1.2Table 6-35, Switching Characteristics Over Recommended Operating Conditions for Asynchronous
EMIFA ElectricalMemory Cycles for EMIFA Module:
Data/Timing
Table 2-1 provides an overview of the TMS320DM6441 SoC. The table shows significant features of the
device, including the capacity of on-chip RAM, peripherals, internal peripheral bus frequency relative to the
C64x+ DSP, and the package type with pin count.
Table 2-1. Characteristics of the Processor
HARDWARE FEATURESDM6441
DDR2 Memory ControllerDDR2 (16/32-bit bus width)
Asynchronous EMIF (EMIFA)
Flash Cards
EDMA3
Timersseparate 32-bit timers)
Peripherals
Not all peripherals pins
are available at the
same time. (For more
details, see Section 3,
Device Configurations.)
On-Chip Memory
CPU ID + CPU Rev ID Control Status Register (CSR.[31:16])0x1000
C64x+ MegamoduleRevision ID Register (MM_REVID[15:0])0x0000 (Silicon Revision 1.3 and earlier)
Table 2-1. Characteristics of the Processor (continued)
HARDWARE FEATURESDM6441
Cycle Timens
Voltage
PLL Optionsx1 (bypass), x15 (1.05 V), x19 (1.2 V)
BGA Package361-pin BGA (ZWT)
Process Technologyµm0.09 µm
Product Status
(1) 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 testing of all parameters.
(1)
Core (V)1.05 V, 1.2 V
I/O (V)1.8 V, 3.3 V
CLKIN frequency multiplier
(27 MHz reference)
16 x 16 mm
ball finish SnAgCu
Product Preview (PP),
Advance Information (AI),PD
Production Data (PD)
DSP 2.47 ns, ARM 4.94 ns at 1.05 V
DSP 1.9 ns, ARM 3.9 ns at 1.2V
2.2Device Compatibility
The ARM926EJ-S RISC CPU is compatible with other ARM9 CPUs from ARM Holdings plc.
The C64x+ DSP core is code-compatible with the C6000™ DSP platform and supports features of the
C64x DSP family.
2.3ARM Subsystem
The ARM subsystem is designed to give the ARM926EJ-S (ARM9) master control of the device. In
general, the ARM is responsible for configuration and control of the device; including the DSP subsystem,
the VPSS subsystem, and a majority of the peripherals and external memories.
The ARM subsystem includes the following features:
•ARM926EJ-S RISC processor
•ARMv5TEJ (32/16-bit) instruction set
•Little endian
•Coprocessor 15 (CP15)
•MMU
•16KB instruction cache
•8KB data cache
•Write buffer
•16KB internal RAM (32-bit-wide access)
•8KB internal ROM (ARM bootloader for non-EMIFA boot options)
•Embedded trace module and embedded trace buffer (ETM/ETB)
The ARM subsystem integrates the ARM926EJ-S processor. The ARM926EJ-S processor is a member of
ARM9 family of general-purpose microprocessors. This processor is targeted at multi-tasking applications
where full memory management, high performance, low die size, and low power are all important. The
ARM926EJ-S processor supports the 32-bit ARM and 16-bit THUMB instruction sets, enabling the user to
trade off between high performance and high code density. Specifically, the ARM926EJ-S processor
supports the ARMv5TEJ instruction set, which includes features for efficient execution of Java byte codes,
providing Java performance similar to Just in Time (JIT) Java interpreter, but without associated code
overhead.
The ARM926EJ-S processor supports the ARM debug architecture and includes logic to assist in both
hardware and software debug. The ARM926EJ-S processor has a Harvard architecture and provides a
complete high performance subsystem, including:
•ARM926EJ -S integer core
•CP15 system control coprocessor
•Memory management unit (MMU)
•Separate instruction and data caches
•Write buffer
•Separate instruction and data tightly-coupled memories (TCMs) [internal RAM] interfaces
•Separate instruction and data AHB bus interfaces
•Embedded trace module and embedded trace buffer (ETM/ETB)
www.ti.com
For more complete details on the ARM9, refer to the ARM926EJ-S Technical Reference Manual, available
at http://www.arm.com.
2.3.2CP15
The ARM926EJ-S system control coprocessor (CP15) is used to configure and control instruction and
data caches, tightly-coupled memories (TCMs), memory management unit (MMU), and other ARM
subsystem functions. The CP15 registers are programmed using the MRC and MCR ARM instructions,
when the ARM in a privileged mode such as supervisor or system mode.
2.3.3MMU
The ARM926EJ-S MMU provides virtual memory features required by operating systems such as Linux™,
WindowCE®, Ultron®, ThreadX®, etc. A single set of two level page tables stored in main memory is used
to control the address translation, permission checks and memory region attributes for both data and
instruction accesses. The MMU uses a single unified translation lookaside buffer (TLB) to cache the
information held in the page tables. The MMU features are:
•Standard ARM architecture v4 and v5 MMU mapping sizes, domains and access protection scheme.
The size of the instruction cache is 16KB, data cache is 8KB. Additionally, the caches have the following
features:
•Virtual index, virtual tag, and addressed using the modified virtual address (MVA)
•Four-way set associative, with a cache line length of eight words per line (32-bytes per line) and with
two dirty bits in the Dcache
•Dcache supports write-through and write-back (or copy back) cache operation, selected by memory
region using the C and B bits in the MMU translation tables.
•Critical-word first cache refilling
•Cache lockdown registers enable control over which cache ways are used for allocation on a line fill,
providing a mechanism for both lockdown, and controlling cache corruption
•Dcache stores the physical address TAG (PA TAG) corresponding to each Dcache entry in the TAG
RAM for use during the cache line write-backs, in addition to the virtual address TAG stored in the
TAG RAM. This means that the MMU is not involved in Dcache write-back operations, removing the
possibility of TLB misses related to the write-back address.
•Cache maintenance operations provide efficient invalidation of, the entire Dcache or Icache, regions of
the Dcache or Icache, and regions of virtual memory.
The write buffer is used for all writes to a noncachable bufferable region, write-through region and write
misses to a write-back region. A separate buffer is incorporated in the Dcache for holding write-back for
cache line evictions or cleaning of dirty cache lines. The main write buffer has 16-word data buffer and a
four-address buffer. The Dcache write-back has eight data word entries and a single address entry.
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
2.3.5Tightly Coupled Memory (TCM)
ARM internal RAM is provided for storing real-time and performance-critical code/data and the interrupt
vector table. ARM internal ROM enables non-EMIFA boot options, such as NAND and UART. The RAM
and ROM memories interfaced to the ARM926EJ-S via the tightly coupled memory interface that provides
for separate instruction and data bus connections. Since the ARM TCM does not allow instructions on the
D-TCM bus or data on the I-TCM bus, an arbiter is included so that both data and instructions can be
stored in the internal RAM/ROM. The arbiter also allows accesses to the RAM/ROM from extra-ARM
sources (e.g., EDMA3 or other masters). The ARM926EJ-S has built-in DMA support for direct accesses
to the ARM internal memory from a non-ARM master. Because of the time-critical nature of the TCM link
to the ARM internal memory, all accesses from non-ARM devices are treated as DMA transfers.
Instruction and data accesses are differentiated via accessing different memory map regions, with the
instruction region from 0x0000 through 0x7FFF and data from 0x8000 through 0xFFFF. The instruction
region at 0x0000 and data region at 0x8000 map to the same physical 16K-byte TCM RAM. Placing the
instruction region at 0x0000 is necessary to allow the ARM interrupt vector table to be placed at 0x0000,
as required by the ARM architecture. The internal 16K-byte RAM is split into two physical banks of 8KB
each, which allows simultaneous instruction and data accesses to be accomplished if the code and data
are in separate banks.
2.3.6Advanced High-performance Bus (AHB)
The ARM subsystem uses the AHB port of the ARM926EJ-S to connect the ARM to the config bus and
the external memories. Arbiters are employed to arbitrate access to the separate D-AHB and I-AHB by the
config bus and the external memories bus.
2.3.7Embedded Trace Macrocell (ETM) and Embedded Trace Buffer (ETB)
To support real-time trace, the ARM926EJ-S processor provides an interface to enable connection of an
embedded trace macrocell (ETM). The ARM926ES-J subsystem in the DM6441 also includes the
embedded trace buffer (ETB). The ETM consists of two parts:
•Trace port provides real-time trace capability for the ARM9.
•Triggering facilities provide trigger resources, which include address and data comparators, counter,
and sequencers.
The DM6441 trace port is not pinned out and is instead only connected to the embedded trace buffer. The
ETB has a 4K-byte buffer memory. ETB enabled debug tools are required to read/interpret the captured
trace data.
2.3.8ARM Memory Mapping
The ARM memory map is shown in Section 2.5, Memory Map Summary, of this document. The ARM has
access to memories shown in the following sections.
2.3.8.1ARM Internal Memories
The ARM has access to the following ARM internal memories:
•16KB ARM internal RAM on TCM interface, logically separated into two 8-KB pages to allow
simultaneous access on any given cycle if there are separate accesses for code (I-TCM bus) and data
(D-TCM) to the different memory regions.
•8KB ARM internal ROM
www.ti.com
2.3.8.2External Memories
The ARM has access to the following external memories:
•DDR2 synchronous DRAM
•Asynchronous EMIF / NOR flash / NAND flash
•ATA/CF
•Flash card devices:
– MMC/SD with SDIO
– Memory Stick/Memory Stick PRO
– xD
– SmartMedia
2.3.8.3DSP Memories
The ARM has access to the following DSP memories:
•L2 RAM
•L1P RAM
•L1D RAM
2.3.8.4VICP Registers and Memories
The ARM has access to the registers and memories of the video/imaging coprocessor (VICP) subsystem.
DM6441 ARM and DSP integration features are as follows:
•DSP visibility from ARM’s memory map, see Section 2.5, Memory Map Summary, for details
•Boot modes for DSP - see Device Configurations section, Section 3.3.3, DSP Boot, for details
•ARM control of DSP boot / reset - see Device Configurations section, Section 3.3.2, ARM Boot, for
details
•ARM control of DSP isolation and powerdown / powerup - see Section 3, Device Configurations, for
details
•ARM & DSP Interrupts - see Section 6.7.1, ARM CPU Interrupts, and Section 6.7.2, DSP Interrupts, for
details
2.3.9Peripherals
The ARM9 has access to all of the peripherals on the DM6441 device with the exception of the VICP.
2.3.10 PLL Controller (PLLC)
The ARM subsystem includes the PLL controller. The PLL controller contains a set of registers for
configuring DM6441’s two internal PLLs (PLL1 and PLL2). The PLL controller provides the following
configuration and control:
•PLL bypass mode
•Set PLL multiplier parameters
•Set PLL divider parameters
•PLL power down
•Oscillator power down
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
The PLLs are briefly described in this document in Section 6.6, Clock PLLs. For more detailed information
on the PLLs and PLL Controller register descriptions, see the TMS320DM644x DMSoC ARM SubsystemReference Guide (literature number SPRUE14).
2.3.11 Power and Sleep Controller (PSC)
The ARM subsystem includes the power and sleep controller (PSC). Through register settings accessible
by the ARM9, the PSC provides two levels of power savings: peripheral/module clock gating and power
domain shut-off. Brief details on the PSC are given in Section 6.3, Power Supplies. For more detailed
information and complete register descriptions for the PSC, see the TMS320DM644x DMSoC ARMSubsystem Reference Guide (literature number SPRUE14).
2.3.12 ARM Interrupt Controller (AINTC)
The ARM interrupt controller (AINTC) accepts device interrupts and maps them to either the ARM’s IRQ
(interrupt request) or FIQ (fast interrupt request). The ARM interrupt controller is briefly described in this
document in the Interrupts section. For detailed information on the ARM interrupt controller, see the
TMS320DM644x DMSoC ARM Subsystem Reference Guide (literature number SPRUE14).
2.3.13 System Module
The ARM subsystem includes the system module. The system module consists of a set of registers for
configuring and controlling a variety of system functions. For details and register descriptions for the
system module, see Section 3, Device Configurations, and see the TMS320DM644x DMSoC ARMSubsystem Reference Guide (literature number SPRUE14).
DM6441 has several means of managing power consumption. There is extensive use of clock gating,
which reduces the power used by global device clocks and individual peripheral clocks. Clock
management can be utilized to reduce clock frequencies in order to reduce switching power. For more
details on power management techniques, see Section 3, Device Configurations, Section 6, Peripheraland Electrical Specifications, and see the TMS320DM644x DMSoC ARM Subsystem Reference Guide
(literature number SPRUE14).
DM6441 gives the programmer full flexibility to use any and all of the previously mentioned capabilities to
customize an optimal power management strategy. Several typical power management scenarios are
described in the following sections.
2.4DSP Subsystem
The DSP subsystem includes the following features:
•C64x+ DSP CPU
•32KB L1 program (L1P)/cache (up to 32KB)
•80KB L1 data (L1D)/cache (up to 32KB)
•64KB unified mapped RAM/cache (L2)
•Little endian
2.4.1C64x+ DSP CPU Description
www.ti.com
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 eight 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, one 16 x
32 bit multiply, two 16 x 16 bit multiplies, two 16 x 32 bit multiplies, two 16 x 16 bit multiplies with
add/subtract capabilities, four 8 x 8 bit multiplies, four 8 x 8 bit multiplies with add operations, and four
16 x 16 multiplies with add/subtract capabilities (including a complex multiply). There is also support for
Galois field multiplication for 8-bit and 32-bit data. Many communications algorithms such as FFTs and
modems require complex multiplication. The complex multiply (CMPY) instruction takes four 16-bit inputs
and produces a 32-bit real and a 32-bit imaginary output. There are also complex multiplies with rounding
capability that 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.
Other new features include:
•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 enhancement - As noted above, there are new instructions such as 32-bit
•Exceptions 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
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 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.
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 Technical Overview (literature number SPRU395)
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.
TMS320DM6441
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
www.ti.com
Figure 2-1. TMS320C64x+™ CPU (DSP Core) Data Paths
The DSP memory map is shown in Table 2-3. Configuration of the control registers for DDR2, EMIFA, and
ARM internal RAM is supported by the ARM. The DSP has access to memories shown in the following
sections.
2.4.2.1ARM Internal Memories
The DSP has access to the 16KB ARM internal RAM on the ARM D-TCM interface (i.e., data only).
2.4.2.2External Memories
The DSP has access to the following external memories:
•DDR2 synchronous DRAM
•Asynchronous EMIF / NOR Flash
2.4.2.3DSP Internal Memories
The DSP has access to the following DSP memories:
•L2 RAM
•L1P RAM
•L1D RAM
2.4.2.4C64x+ CPU
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
The C64x+ core uses a two-level cache-based architecture. The Level 1 program cache (L1P) is 32 KB
direct mapped cache and the Level 1 data cache (L1D) is 80 KB 2-way set associated cache. The Level 2
memory/cache (L2) consists of a 64 KB memory space that is shared between program and data space.
L2 memory can be configured as mapped memory, cache, or a combination of both.
Table 2-2 shows a memory map of the C64x+ CPU cache registers for the device.
Memory attribute registers for EMIFA/VLYNQ shadow 0x4200 0000 0x4FFF FFFF
www.ti.com
2.4.3Peripherals
The DSP has controllability for the following peripherals:
•VICP
•EDMA3
•ASP
•Two Timers (Timer 0 and Timer1) that can each be configured as one 64-bit or two 32-bit timers
2.4.4DSP Interrupt Controller
The DSP interrupt controller accepts device interrupts and appropriately maps them to available DSP
interrupts. The DSP interrupt controller is briefly described in this document in the Interrupts section. For
more detailed on the DSP interrupt controller, see the TMS320C64x/C64x+ DSP CPU and Instruction SetReference Guide (literature number SPRU732).
2.5Memory Map Summary
Table 2-3 shows the memory map address ranges of the device. Table 2-4 depicts the expanded map of
the configuration space (0x0180 0000 through 0x0FFF FFFF). The device has multiple on-chip memories
associated with its two processors and various subsystems. To help simplify software development a
unified memory map is used where possible to maintain a consistent view of device resources across all
bus masters.
(1) EMIFA shadow memory started a 0x4200 0000 is physically the same memory as location 0x0200 0000. Memory range 0x200 0000
through 0x09FF FFFF should only be used by C64x+ for data accesses. Memory range 0x4200 0000 through 0x4FFF FFFF can be
used by C64x+ for both code execution and data accesses.
Extensive use of pin multiplexing is used to accommodate the largest number of peripheral functions in
the smallest possible package. Pin multiplexing is controlled using a combination of hardware
configuration at device reset and software programmable register settings. For more information on pin
muxing, see Section 3.5.2, Multiplexed Pin Configurations, of this document.
2.6.1Pin Map (Bottom View)
Figure 2-2 through Figure 2-5 show the bottom view of the package pin assignments in four quadrants (A,
The terminal functions tables (Table 2-5 through Table 2-30) identify the external signal names, the
associated pin (ball) numbers along with the mechanical package designator, the pin type, whether the pin
has any internal pullup or pulldown resistors, and a functional pin description. For more detailed
information on device configuration, peripheral selection, multiplexed/shared pin, and debugging
considerations, see Section 3, Device Configurations, of this data manual.
Table 2-5. BOOT Terminal Functions
SIGNAL
NAMENO.
TYPE
(1)
COUT0/
B3/A16I/O/Z
BTSEL0
COUT1/
B4/B16I/O/Z01ARM EMIFA boot (NOR)
BTSEL1
COUT2/
B5/A17I/O/Z
EM_WIDTH
COUT3/
B6/B17I/O/Z
DSP_BT
YOUT0/
G5/D15I/O/Z
AEAW0
YOUT1/
G6/D16I/O/Z
AEAW1
YOUT2/input states of AEAW[4:0] are sampled to set the EMIFA address bus
G7/D17I/O/Zwidth. See Section 3.4.2, Peripheral Selection at Device Reset, for details.
AEAW2After reset, these are video encoder outputs YOUT[0:4] or RGB666/888
YOUT3/
R3/D18I/O/Z
AEAW3
YOUT4/
R4/E15I/O/Z
AEAW4
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = internal pulldown, IPU = internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal
(2)
OTHER
(3)
DESCRIPTION
BOOT
These pins are multiplexed between ARM boot mode and the VPBE. At
reset, the boot mode inputs BTSEL0 and BTSEL1 are sampled to
IPDdetermine the ARM boot configuration. See below for the boot modes set
DV
DD18
by these inputs. See Section 3.3, Bootmode, for more details.
After reset, these are video encoder outputs COUT0 and COUT1, or
RGB666/888 Blue output data bits 3 and 4 B3/B4.
BTSEL1BTSEL0ARM Boot Mode
00ARM ROM boot (NAND, SPI) [default]
IPD
DV
DD18
10ARM ROM boot (HPI)
11ARM ROM boot (UART0)
This pin is multiplexed between EMIFA and the VPBE. At reset, the input
state is sampled to set the EMIFA data bus width (EM_WIDTH). For an
IPD8-bit-wide EMIFA data bus, EM_WIDTH = 0. For a 16-bit-wide EMIFA data
DV
DD18
bus, EM_WIDTH = 1.
After reset, it is video encoder output COUT2 or RGB666/888 Blue output
data bit 5 B5.
This pin is multiplexed between DSP boot and the VPBE. At reset, the
input state is sampled to set the DSP boot source DSP_BT. The DSP is
IPDbooted by the ARM when DSP_BT=0. The DSP boots from EMIFA when
DV
DD18
DSP_BT=1.
After reset, it is video encoder output COUT3 or RGB666/888 Blue data
bit 6 output B6.
IPD
DV
DD18
IPD
DV
DD18
These pins are multiplexed between EMIFA and the VPBE. At reset, the
IPD
DV
DD18
Red and Green data bit outputs G5, G6, G7, R3, and R4.
F17GNDclock-in source is supplied, M24VSSshould still be connected to ground. When the
M2S
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
(3) For more information, see Section 5.2, Recommended Operating Conditions.
(4) For more information, see Section 5.2, Recommended Operating Conditions.
TYPE
(1)
OTHER
(2)
DESCRIPTION
OSCILLATOR, PLL
Crystal input MXI for MX oscillator (system oscillator, typically 27 MHz). If a crystal
DD18
DD18
(3)
input is not used, but instead a physical clock-in source is supplied, this is the
external oscillator clock input.
Crystal output for MX oscillator. If a crystal input is not used, but instead a physical
clock-in source is supplied, MXO should be left as a No Connect.
1.8-V power supply for MX oscillator. If a crystal input is not used, but instead a
physical clock-in source is supplied, MXVDDshould still be connected to the 1.8-V
power supply.
(3)
Ground for MX oscillator. If a crystal input is not used, but instead a physical
clock-in source is supplied, MXVSSshould still be connected to ground.
Crystal input for M24 oscillator (24 MHz for USB). If a crystal input is not used, but
DD18
instead a physical clock-in source is supplied, this is the external oscillator clock
input. When the USB peripheral is not used, M24XI should be left as a No Connect.
Crystal output for M24 oscillator. If a crystal input is not used, but instead a physical
DD18
clock-in source is supplied, M24XO should be left as a No Connect. When the USB
peripheral is not used, M24XO should be left as a No Connect.
1.8-V power supply for M24 oscillator. If a crystal input is not used, but instead a
(3)
physical clock-in source is supplied, M24VDDshould still be connected to the 1.8-V
power supply. When the USB peripheral is not used, M24VDDshould be connected
to the 1.8-V power supply.
(4)
Ground for M24 oscillator. If a crystal input is not used, but instead a physical
USB peripheral is not used, M24VSSshould be connected to ground.
(4)
1.8-V power supply for PLLs (system).
Table 2-7. Clock Generator Terminal Functions
SIGNAL
NAMENO.
CLK_OUT0/
GPIO48
K1I/O/ZDV
CLK_OUT1/This pin is multiplexed between the USB clock generator, timer, and GPIO.
TIM_IN/E19I/O/ZDV
GPIO4912 MHz or 24 MHz clock outputs.
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
DESCRIPTION
CLOCK GENERATOR
This pin is multiplexed between the PLL1 clock generator and GPIO.
DD18
DD18
For the PLL1 clock generator, it is clock output CLK_OUT0. This is configurable for
13.5 MHz or 27 MHz clock outputs.
For the USB clock generator, it is clock output CLK_OUT1. This is configurable for
RESETL4IThis is the active low global reset input.
TMSE6IJTAG test-port mode select input
TDOB5O/ZJTAG test-port data output
TDIA5IJTAG test-port data input
TCKA6IJTAG test-port clock input
RTCKB6O/ZJTAG test-port return clock output
TRSTD7IJTAG compatibility statement portion of this data manual (Section 6.26, IEEE
EMU1C6I/O/ZEmulation pin 1
EMU0D6I/O/ZEmulation pin 0
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = internal pulldown, IPU = internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
IPU
DV
IPU
DV
DV
IPU
DV
IPU
DV
DV
IPD
DV
IPU
DV
IPU
DV
(2) (3)
DD18
DD18
–
DD18
DD18
DD18
–
DD18
DD18
DD18
DD18
DESCRIPTION
RESET
JTAG
JTAG test-port reset. For IEEE 1149.1 JTAG compatibility, see the IEEE 1149.1
1149.1 JTAG).
www.ti.com
Table 2-9. EMIFA Terminal Functions
SIGNAL
NAMENO.
COUT2/sampled to set the EMIFA data bus width (EM_WIDTH). For an 8-bit-wide EMIFA
B5/A17I/O/Zdata bus, EM_WIDTH = 0. For a 16-bit-wide EMIFA data bus, EM_WIDTH = 1.
EM_WIDTHAfter reset, it is video encoder output COUT2 or RGB666/888 Blue output data bit 5
COUT3/sampled to set the DSP boot source DSP_BT. The DSP is booted by the ARM when
B6/B17I/O/ZDSP_BT=0. The DSP boots from EMIFA when DSP_BT=1.
DSP_BTAfter reset, it is video encoder output COUT3 or RGB666/888 Blue data bit 6 output
YOUT0/
G5/D15I/O/Z
AEAW0
YOUT1/
G6/D16I/O/Z
AEAW1
YOUT2/of AEAW[4:0] are sampled to set the EMIFA address bus width. See Section 3.4.2,
G7/D17I/O/ZPeripheral Selection at Device Reset, for details.
AEAW2After reset, these are video encoder outputs YOUT[0:4] or RGB666/888 Red and
YOUT3/
R3/D18I/O/Z
AEAW3
YOUT4/
R4/E15I/O/Z
AEAW4
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = Internal pulldown, IPU = Internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal
This pin is multiplexed between EMIFA and the VPBE. At reset, the input state is
DD18
B5.
This pin is multiplexed between DSP boot and the VPBE. At reset, the input state is
DD18
B6.
DD18
DD18
DD18
These pins are multiplexed between EMIFA and the VPBE. At reset, the input states
Green data bit outputs G5, G6, G7, R3, and R4.
DD18
DD18
Submit Documentation Feedback
Product Folder Link(s): TMS320DM6441
DESCRIPTION
TMS320DM6441
www.ti.com
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
Table 2-9. EMIFA Terminal Functions (continued)
SIGNAL
NAMENO.
EM_CS2/For EMIFA, this pin is Chip Select 2 output EM_CS2 for use with asynchronous
HCSmemories (i.e., NOR flash) or NAND flash. This is the chip select for the default boot
C2I/O/ZDV
EM_CS3B1I/O/ZDV
EM_CS4/This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
GPIO9/T2I/O/ZDV
VLYNQ_SCRUN(i.e., NOR flash) or NAND flash.
EM_CS5/This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
GPIO8/T1I/O/ZDV
VLYNQ_CLOCK(i.e., NOR flash) or NAND flash.
EM_R/W/
INTRQ/G3I/O/ZDV
HR/W
EM_WAIT/
(RDY/BSY)/IPUThis pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
IORDY/DV
F1I/O/Z
HRDY
EM_OE/
(RE)/
(IORD)/H4I/O/ZDV
DIOR/
HDS1
EM_WE
(WE)
(IOWR)/G2I/O/ZDV
DIOW/
HDS2
EM_BA[0]/
DA0/J3I/O/Z
HINT
EM_BA[1]/
DA1/H2I/O/ZDV
GPIO52
EM_A[21]/
GPIO10/T3I/O/ZDV
VLYNQ_TXD0
EM_A[20]/
GPIO11/R3I/O/ZDV
VLYNQ_RXD0
EM_A[19]/
GPIO12/R4I/O/ZDV
VLYNQ_TXD1
EM_A[18]/
GPIO13/P5I/O/ZDV
VLYNQ_RXD1
EM_A[17]/
GPIO14/R2I/O/ZDV
VLYNQ_TXD2
EM_A[16]/
GPIO15/R5I/O/ZDV
VLYNQ_RXD2
TYPE
(1)
(2) (3)
OTHER
DESCRIPTION
EMIFA FUNCTIONAL PINS: ASYNC / NOR
This pin is multiplexed between EMIFA and HPI.
DD18
and ROM boot modes.
DD18
DD18
DD18
DD18
DD18
DD18
DD18
For EMIFA, this pin is Chip Select 3 output EM_CS3 for use with asynchronous
memories (i.e., NOR flash) or NAND flash.
For EMIFA, it is Chip Select 4 output EM_CS4 for use with asynchronous memories
For EMIFA, it is Chip Select 5 output EM_CS5 for use with asynchronous memories
This pin is multiplexed between EMIFA, ATA/CF, and HPI.
For EMIFA, it is read/write output EM_R/W.
For EMIFA, it is wait state extension input EM_WAIT.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
For EMIFA, it is output enable output EM_OE.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
For NAND/SmartMedia/xD or EMIFA, it is write enable output EM_WE.
This pin is multiplexed between EMIFA, ATA/CF, and HPI.
For EMIFA, this is the Bank Address 0 output (EM_BA[0]).
IPDWhen connected to an 8-bit asynchronous memory, this pin is the lowest order bit of
DV
DD18
the byte address.
When connected to a 16-bit asynchronous memory, this pin has the same function
as EMIF address pin 22 (EM_A[22]).
This pin is multiplexed between EMIFA, ATA/CF, and GPIO.
For EMIFA, this is the Bank Address 1 output EM_BA[1].
DD18
When connected to a 16 bit asynchronous memory this pin is the lowest order bit of
the 16-bit word address.
When connected to an 8-bit asynchronous memory, this pin is the 2nd bit of the
address.
DD18
DD18
DD18
DD18
DD18
DD18
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For EMIFA, it is address bit 21 output EM_A[21].
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For EMIFA, it is address bit 20 output EM_A[20].
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For EMIFA, it is address bit 19 output EM_A[19].
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For EMIFA, it is address bit 18 output EM_A[18].
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For EMIFA, it is address bit 17 output EM_A[17].
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For EMIFA, it is address bit 16 output EM_A[16].
These pins are multiplexed between EMIFA (NAND), ATA/CF, and HPI. In all cases
they are used as a 16 bit bi-directional data bus.
For EMIFA (NAND), these are EM_D[15:0].
These pins are multiplexed between EMIFA (NAND), ATA/CF, and HPI. In all cases
they are used as a 16 bit bi-directional data bus.
For EMIFA (NAND), these are EM_D[15:0].
DDR2 clock
DDR2 differential clock
DDR2 clock enable
DDR2 active low chip select
DDR2 active low write enable
DDR2 data mask outputs
DQM3: For upper byte data bus DDR_D[31:24]
DQM2: For DDR_D[23:16]
DQM1: For DDR_D[15:8]
DQM0: For lower byte DDR_D[7:0]
DDR2 row access signal output
DDR2 column access signal output
Data strobe input/outputs for each byte of the 32-bit data bus. They are outputs to
the DDR2 memory when writing and inputs when reading. They are used to
synchronize the data transfers.
DQS3 : For upper byte DDR_D[31:24]
DQS2: For DDR_D[23:16]
DQS1: For DDR_D[15:8]
DQS0: For bottom byte DDR_D[7:0]
Bank select outputs (BS[2:0]). Two are required to support 1Gb DDR2 memories.
DDR2 address bus
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
(3) For more information, see Section 5.2, Recommended Operating Conditions.
(4) For more information, see Section 5.2, Recommended Operating Conditions.
(1)
TYPE
OTHER
I/O/ZDV
(2) (3)
DDR2
(4)
(4)
(4)
(4)
(4)
DDR2 data bus can be configured as 32-bits wide or 16-bits wide.
Reference voltage input for the SSTL_18 IO buffers.
Ground for the DDR2 digital locked loop.
Power (1.8 Volts) for the DDR2 digital locked loop.
Impedance control for DDR2 outputs. This must be connected via a 200 Ω resistor
to DV
DDR2
.
Impedance control for DDR2 outputs. This must be connected via a 200 Ω resistor
to VSS.
GPIO44For I2C, it is bidirectional data signal SDA.
C4I/O/ZDV
B4I/O/ZDV
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
DESCRIPTION
I2C
DD18
DD18
Table 2-12. Audio Serial Port (ASP) Terminal Functions
SIGNAL
NAMENO.
CLKX/This pin is multiplexed between ASP and GPIO.
GPIO29For ASP, it is transmit clock IO CLKX.
CLKR/This pin is multiplexed between ASP and GPIO.
GPIO30For ASP, it is receive clock IO CLKR.
FSX/This pin is multiplexed between ASP and GPIO.
GPIO31For ASP, it is transmit frame synchronization IO FSX.
FSR/This pin is multiplexed between ASP and GPIO.
GPIO32For ASP, it is receive frame synchronization IO FSR.
DX/This pin is multiplexed between ASP and GPIO.
GPIO33For ASP, it is data transmit output DX.
DR/This pin is multiplexed between ASP and GPIO.
GPIO34For ASP, it is data receive input DR.
B8I/O/ZDV
A8I/O/ZDV
C8I/O/ZDV
C7I/O/ZDV
B7I/O/ZDV
A7I/O/ZDV
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
DESCRIPTION
Audio Serial Port (ASP)
DD18
DD18
DD18
DD18
DD18
DD18
www.ti.com
Table 2-13. SPI Terminal Functions
SIGNAL
NAMENO.
SPI_EN0/This pin is multiplexed between SPI and GPIO.
GPIO37When used by SPI, it is SPI slave device 0 enable output SPI_EN0.
A4I/O/ZDV
SPI_EN1/
HDDIR/B2I/O/ZDV
GPIO42
SPI_CLK/This pin is multiplexed between SPI and GPIO.
GPIO39For SPI, it is clock output SPI_CLK.
SPI_DI/This pin is multiplexed between SPI and GPIO.
GPIO40For SPI, it is data input SPI_DI.
SPI_DO/This pin is multiplexed between SPI and GPIO.
GPIO41For SPI it is data output SPI_DO.
A3I/O/ZDV
B3I/O/ZDV
A2I/O/ZDV
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
DESCRIPTION
Serial Port Interface (SPI)
DD18
DD18
DD18
DD18
DD18
This pin is multiplexed between SPI, ATA, and GPIO.
When used by SPI, it is SPI slave device 1 enable output SPI_EN1.
GPIOV33_0/This pin is multiplexed between GPIO and Ethernet MAC.
TXENIn Ethernet MAC mode, it is transmit enable output TXEN.
GPIOV33_1/This pin is multiplexed between GPIO and Ethernet MAC.
TXCLKIn Ethernet MAC mode, it is transmit clock output TXCLK.
GPIOV33_2/This pin is multiplexed between GPIO and Ethernet MAC.
COLIn Ethernet MAC mode, it is collision detect input COL.
GPIOV33_6/This pin is multiplexed between GPIO and Ethernet MAC.
TXD3In Ethernet MAC mode, it is transmit data 3 output TXD3.
GPIOV33_5/This pin is multiplexed between GPIO and Ethernet MAC.
TXD2In Ethernet MAC mode, it is transmit data 2 output TXD2.
GPIOV33_4/This pin is multiplexed between GPIO and Ethernet MAC.
TXD1In Ethernet MAC mode, it is transmit data 1 output TXD1.
GPIOV33_3/This pin is multiplexed between GPIO and Ethernet MAC.
TXD0In Ethernet MAC mode, it is transmit data 0 output TXD0.
GPIOV33_11/This pin is multiplexed between GPIO and Ethernet MAC.
RXCLKIn Ethernet MAC mode, it is receive clock input RXCLK.
GPIOV33_12/This pin is multiplexed between GPIO and Ethernet MAC.
RXDVIn Ethernet MAC mode, it is receive data valid input RXDV.
GPIOV33_13/This pin is multiplexed between GPIO and Ethernet MAC.
RXERIn Ethernet MAC mode, it is receive error input RXER.
GPIOV33_14/This pin is multiplexed between GPIO and Ethernet MAC.
CRSIn Ethernet MAC mode, it is carrier sense input CRS.
GPIOV33_10/This pin is multiplexed between GPIO and Ethernet MAC.
RXD3In Ethernet MAC mode, it is receive data 3 input RXD3.
GPIOV33_9/This pin is multiplexed between GPIO and Ethernet MAC.
RXD2In Ethernet MAC mode, it is receive data 2 input RXD2.
GPIOV33_8/This pin is multiplexed between GPIO and Ethernet MAC.
RXD1In Ethernet MAC mode, it is receive data 1 input RXD1.
GPIOV33_7/This pin is multiplexed between GPIO and Ethernet MAC.
RXD0In Ethernet MAC mode, it is receive data 0 input RXD0.
GPIOV33_16/This pin is multiplexed between GPIO and Ethernet MAC.
MDCLKIn Ethernet MAC mode, it is management data clock output MDCLK.
GPIOV33_15/This pin is multiplexed between GPIO and Ethernet MAC.
MDIOIn Ethernet MAC mode, it is management data IO MDIO.
B13I/O/ZDV
A13I/O/ZDV
A12I/O/ZDV
C12I/O/ZDV
A11I/O/ZDV
D12I/O/ZDV
B12I/O/ZDV
A10I/O/ZDV
D11I/O/ZDV
D10I/O/ZDV
C10I/O/ZDV
E11I/O/ZDV
B11I/O/ZDV
C11I/O/ZDV
E12I/O/ZDV
B10I/O/ZDV
E10I/O/ZDV
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
GPIOV33_16/This pin is multiplexed between GPIO and Ethernet MAC.
MDCLKIn GPIO mode, it is 3.3V GPIO GPIOV33_16.
GPIOV33_15/This pin is multiplexed between GPIO and Ethernet MAC.
MDIOIn GPIO mode, it is 3.3V GPIO GPIOV33_15.
GPIOV33_14/This pin is multiplexed between GPIO and Ethernet MAC.
CRSIn GPIO mode, it is 3.3V GPIO GPIOV33_14.
GPIOV33_13/This pin is multiplexed between GPIO and Ethernet MAC.
RXERIn GPIO mode, it is 3.3V GPIO GPIOV33_13.
GPIOV33_12/This pin is multiplexed between GPIO and Ethernet MAC.
RXDVIn GPIO mode, it is 3.3V GPIO GPIOV33_12.
GPIOV33_11/This pin is multiplexed between GPIO and Ethernet MAC.
RXCLKIn GPIO mode, it is 3.3V GPIO GPIOV33_11.
GPIOV33_10/This pin is multiplexed between GPIO and Ethernet MAC.
RXD3In GPIO mode, it is 3.3V GPIO GPIOV33_10.
GPIOV33_9/This pin is multiplexed between GPIO and Ethernet MAC.
RXD2In GPIO mode, it is 3.3V GPIO GPIOV33_9.
GPIOV33_8/This pin is multiplexed between GPIO and Ethernet MAC.
RXD1In GPIO mode, it is 3.3V GPIO GPIOV33_8.
GPIOV33_7/This pin is multiplexed between GPIO and Ethernet MAC.
RXD0In GPIO mode, it is 3.3V GPIO GPIOV33_7.
GPIOV33_6/This pin is multiplexed between GPIO and Ethernet MAC.
TXD3In GPIO mode, it is 3.3V GPIO GPIOV33_6.
GPIOV33_5/This pin is multiplexed between GPIO and Ethernet MAC.
TXD2In GPIO mode, it is 3.3V GPIO GPIOV33_5.
GPIOV33_4/This pin is multiplexed between GPIO and Ethernet MAC.
TXD1In GPIO mode, it is 3.3V GPIO GPIOV33_4.
GPIOV33_3/This pin is multiplexed between GPIO and Ethernet MAC.
TXD0In GPIO mode, it is 3.3V GPIO GPIOV33_3.
GPIOV33_2/This pin is multiplexed between GPIO and Ethernet MAC.
COLIn GPIO mode, it is 3.3V GPIO GPIOV33_2.
GPIOV33_1/This pin is multiplexed between GPIO and Ethernet MAC.
TXCLKIn GPIO mode, it is 3.3V GPIO GPIOV33_1.
GPIOV33_0/This pin is multiplexed between GPIO and Ethernet MAC.
TXENIn GPIO mode, this pin is 3.3V GPIO pin GPIOV33_0.
B10I/O/ZDV
E10I/O/ZDV
C10I/O/ZDV
D10I/O/ZDV
D11I/O/ZDV
A10I/O/ZDV
E11I/O/ZDV
B11I/O/ZDV
C11I/O/ZDV
E12I/O/ZDV
C12I/O/ZDV
A11I/O/ZDV
D12I/O/ZDV
B12I/O/ZDV
A12I/O/ZDV
A13I/O/ZDV
B13I/O/ZDV
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
DESCRIPTION
GPIOV33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
DD33
www.ti.com
Table 2-16. Standalone GPIOV18 Terminal Functions
SIGNAL
NAMENO.
GPIO7C3I/O/ZDV
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
USB_DPG19A I/OUSB bi-directional Data Differential signal pair [positive/negative].
USB_DMH19A I/O
USB_R1H18A I/O
USB_V
USB_V
USB_V
USB_V
USB_V
SSREF
DDA3P3
SSA3P3
DD1P8
SS1P8
G16GND
J19S
J18GND
H17S
H16GND
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
(3) For more information, see Section 5.2, Recommended Operating Conditions.
Crystal input for M24 oscillator (24 MHz for USB).
DD18
If a crystal input is not used, but instead a physical clock-in source is supplied, this
is the external oscillator clock input.
When the USB peripheral is not used, M24XI should be left as a No Connect.
Crystal output for M24 oscillator.
DD18
If a crystal input is not used, but instead a physical clock-in source is supplied,
M24XO should be left as a No Connect.
When the USB peripheral is not used, M24XO should be left as a No Connect.
1.8-V power supply for M24 oscillator.
If a crystal input is not used, but instead a physical clock-in source is supplied,
M24VDDshould still be connected to the 1.8-V power supply.
When the USB peripheral is not used, M24VDDshould be connected to the 1.8-V
power supply.
Ground for M24 oscillator.
If a crystal input is not used, but instead a physical clock-in source is supplied,
M24VSSshould still be connected to ground.
When the USB peripheral is not used, M24VSSshould be connected to ground.
5-V input that signifies that VBUS is connected.
When the USB peripheral is not used, the USB_VBUS signal should be either
pulled down or pulled up via a 10-kΩ resistor.
USB operating mode identification pin. For Host mode operation, pull down this pin
to ground (VSS) via an external 1.5-kΩ resistor. For Device mode operation, pull up
this pin to DV
rail via an external 1.5-kΩ resistor.
DD33
When the USB peripheral is not used, the USB_ID signal should be either pulled
down or pulled up via a 10-kΩ resistor.
When the USB peripheral is not used, the USB_DP signal should be pulled high
and the USB_DM signal should be pulled down via a 10-kΩ resistor.
Reference current output. This must be connected via a 10-kΩ ±1% resistor to
USB_V
SSREF
.
When the USB peripheral is not used, the USB_R1 signal should be connected via
a 10-kΩ resistor to USB_V
Ground for reference current. This must be connected via a 10-kΩ ±1% resistor to
USB_R1.
When the USB peripheral is not used, the USB_V
to VSS.
Analog 3.3 V power supply for USB phy.
When the USB peripheral is not used, the USB_V
connected to DV
DD33
.
Analog ground for USB phy. When the USB peripheral is not used, the
USB_V
signal should be connected to VSS.
SSA3P3
1.8-V I/O power supply for USB phy.
When the USB peripheral is not used, the USB_V
to DV
DD18
.
I/O Ground for USB phy.
When the USB peripheral is not used, the USB_V
to VSS.
Submit Documentation Feedback
Product Folder Link(s): TMS320DM6441
SSREF
DESCRIPTION
.
signal should be connected
SSREF
signal should be
DDA3P3
signal should be connected
DD1P8
signal should be connected
SS1P8
TMS320DM6441
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
Table 2-17. USB Terminal Functions (continued)
SIGNAL
NAMENO.
USB_V
DDA1P2LDO
USB_V
SSA1P2LDO
G18S
G17GND
TYPE
(1)
OTHER
(3)
(3)
(2) (3)
DESCRIPTION
Core Power supply LDO output for USB phy. This must be connected via a 1-mF
capacitor to VSS.
When the USB peripheral is not used, the USB_V
connected via a 1-mF capacitor to VSS.
Core Ground for USB phy. This is the ground for the LDO and must be connected to
VSS.
When the USB peripheral is not used, the USB_V
connected to VSS.
Table 2-18. VLYNQ Terminal Functions
SIGNAL
NAMENO.
EM_CS5/
GPIO8/T1I/O/ZDV
VLYNQ_CLOCK
EM_CS4/
GPIO9/T2I/O/ZDV
VLYNQ_SCRUN
EM_A[15]/
GPIO16/P3I/O/ZDV
VLYNQ_TXD3
EM_A[17]/
GPIO14/R2I/O/ZDV
VLYNQ_TXD2
EM_A[19]/
GPIO12/R4I/O/ZDV
VLYNQ_TXD1
EM_A[21]/
GPIO10/T3I/O/ZDV
VLYNQ_TXD0
EM_A[14]/
GPIO17/P4I/O/ZDV
VLYNQ_RXD3
EM_A[16]/
GPIO15/R5I/O/ZDV
VLYNQ_RXD2
EM_A[18]/
GPIO13/P5I/O/ZDV
VLYNQ_RXD1
EM_A[20]/
GPIO11/R3I/O/ZDV
VLYNQ_RXD0
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
DESCRIPTION
VLYNQ
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is the clock (VLYNQ_CLOCK).
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is the serial clock run request (VLYNQ_SCRUN).
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is transmit bus bit 3 output VLYNQ_TXD3.
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is transmit bus bit 2 output VLYNQ_TXD2.
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is transmit bus bit 1 output VLYNQ_TXD1.
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is bit 0 of the transmit bus (VLYNQ_TXD0).
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is receive bus bit 3 input VLYNQ_RXD3.
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is receive bus bit 2 input VLYNQ_RXD2.
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is receive bus bit 1 input VLYNQ_RXD1.
This pin is multiplexed between EMIFA, GPIO, and VLYNQ.
For VLYNQ, it is receive bus bit 0 input VLYNQ_RXD0.
N15IIn 16-bit YCbCr mode, it is time multiplexed between CB3 and CR3 inputs.
M17IIn 16-bit YCbCr mode, it is time multiplexed between CB2 and CR2 inputs.
M16IIn 16-bit YCbCr mode, it is time multiplexed between CB1 and CR1 inputs.
M15IIn 16-bit YCbCr mode, it is time multiplexed between CB0 and CR0 inputs.
L18IIn 16-bit YCbCr mode, it is input Y7.
(1)
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
Table 2-19. VPFE Terminal Functions
(2) (3)
OTHER
VIDEO/IMAGE IN (VPFE)
–Pixel clock input used to load image data into the CCD controller (CCDC) on pins
DV
DD18
CI[7:0] and YI[7:0].
–Vertical synchronization signal that can be either an input (slave mode) or an output
DV
DD18
(master mode), which signals the start of a new frame to the CCDC.
–Horizontal synchronization signal that can be either an input (slave mode) or an
DV
DD18
output (master mode), which signals the start of a new line to the CCDC.
This pin is multiplexed between the CCDC and UART2.
When used by the CCDC as input CI7, it supports several modes.
IPDIn 16-bit CCD analog-front-end (AFE) mode, it is input CCD15.
DV
DD18
In 16-bit YCbCr mode, it is time multiplexed between CB7 and CR7 inputs.
In 8-bit YCbCr mode, it is time multiplexed between Y7, CB7, and CR7 of the upper
8-bit channel.
This pin is multiplexed between the CCDC and UART2.
When used by the CCDC as input CI6, it supports several modes. In 16-bit CCD
IPDAFE mode, it is input CCD14.
DV
DD18
In 16-bit YCbCr mode, it is time multiplexed between CB6 and CR6 inputs.
In 8-bit YCbCr mode, it is time multiplexed between Y6, CB6, and CR6 of the upper
8-bit channel.
This pin is multiplexed between the CCDC and UART2. When used by the CCDC as
input CI5, it supports several modes.
IPDIn 16-bit CCD AFE mode, it is input CCD13.
DV
DD18
In 16-bit YCbCr mode, it is time multiplexed between CB5 and CR5 inputs.
In 8-bit YCbCr mode, it is time multiplexed between Y5, CB5, and CR5 of the upper
8-bit channel.
This pin is multiplexed between the CCDC and UART2. When used by the CCDC as
input CI4, it supports several modes.
IPDIn 16-bit CCD AFE mode, it is input CCD12.
DV
DD18
In 16-bit YCbCr mode, it is time multiplexed between CB4 and CR4 inputs.
In 8-bit YCbCr mode, it is time multiplexed between Y4, CB4, and CR4 of the upper
8-bit channel.
This pin is CCDC input CI3 and it supports several modes. In 16-bit CCD AFE
mode, it is input CCD11.
DD18
In 8-bit YCbCr mode, it is time multiplexed between Y3, CB3, and CR3 of the upper
8-bit channel.
This pin is CCDC input CI2 and it supports several modes. In 16-bit CCD AFE
mode, it is input CCD10.
DD18
In 8-bit YCbCr mode, it is time multiplexed between Y2, CB2, and CR2 of the upper
8-bit channel.
This pin is CCDC input CI1 and it supports several modes.
In 16-bit CCD AFE mode, it is input CCD9.
DD18
In 8-bit YCbCr mode, it is time multiplexed between Y1, CB1, and CR1 of the upper
8-bit channel.
This pin is CCDC input CI0 and it supports several modes.
In 16-bit CCD AFE mode, it is input CCD8.
DD18
In 8-bit YCbCr mode, it is time multiplexed between Y0, CB0, and CR0 of the upper
8-bit channel.
This pin is CCDC input YI7 and it supports several modes.
In 16-bit CCD AFE mode, it is input CCD7.
DD18
In 8-bit YCbCr mode, it is time multiplexed between Y7, CB7, and CR7 of the lower
8-bit channel.
DESCRIPTION
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = internal pulldown, IPU = internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal
COUT0/This pin is multiplexed between ARM boot mode and the VPBE.
B3/A16I/O/ZAfter reset, this pin is either video encoder outputs COUT0, or
BTSEL0RGB666/888 Blue output data bits 3, B3.
COUT1/This pin is multiplexed between ARM boot mode and the VPBE.
B4/B16I/O/ZAfter reset, this pin is either video encoder outputs COUT1, or
BTSEL1RGB666/888 Blue output data bits 4, B4.
COUT2/This pin is multiplexed between EMIFA and the VPBE.
B5/A17I/O/ZAfter reset, it is video encoder output COUT2 or RGB666/888 Blue output
EM_WIDTHdata bit 5 B5.
COUT3/This pin is multiplexed between DSP boot and the VPBE.
B6/B17I/O/ZAfter reset, it is video encoder output COUT3 or RGB666/888 Blue data bit
DSP_BT6 output B6.
COUT4/
B7
COUT5/
G2
COUT6/
G3
COUT7/
G4
A18ODV
B18ODV
B19ODV
C16ODV
YOUT0/
G5/D15I/O/Z
AEAW0
YOUT1/
G6/D16I/O/Z
AEAW1
YOUT2/These pins are multiplexed between EMIFA and the VPBE.
G7/D17I/O/ZAfter reset, these are video encoder outputs YOUT[0:4] or RGB666/888
AEAW2Red and Green data bit outputs G5, G6, G7, R3, and R4.
YOUT3/
R3/D18I/O/Z
AEAW3
YOUT4/
R4/E15I/O/Z
AEAW4
YOUT5/
R5
YOUT6/
R6
YOUT7/
R7
GPIO0/This pin is multiplexed between GPIO and the VPBE.
LCD_OEIn VPBE mode, it is the LCD output enable LCD_OE.
GPIO2/This pin is multiplexed between GPIO and the VPBE.
G0In VPBE mode, it is RGB888 Green data bit 0 output G0.
E16ODV
E17ODV
E18ODV
C13I/O/ZDV
D13I/O/ZDV
(2)
OTHER
(3)
VIDEO OUT (VPBE)
IPD
DV
DD18
IPD
DV
DD18
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
DD18
DD18
DD18
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
DD18
DD18
DD18
DD18
DD18
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
DESCRIPTION
VPBE clock output
Video encoder output COUT4 or RGB666/888 Blue data bit 7 output B7.
Video encoder output COUT5 or RGB666/888 Green data bit 2 output G2.
Video encoder output COUT6 or RGB666/888 Green data bit 3 output G3.
Video encoder output COUT7 or RGB666/888 Green data bit 4 output G4.
Video encoder output YOUT5 or RGB666/888 Red data bit 5 output R5.
Video encoder output YOUT6 or RGB666/888 Red data bit 6 output R6.
Video encoder output YOUT7 or RGB666/888 Red data bit 7 output R7.
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = internal pulldown, IPU = internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal
GPIO3/This pin is multiplexed between GPIO, and the VPBE.
B0/C14I/O/ZDV
LCD_FIELDor LCD interlaced output LCD_FIELD.
GPIO4/
R0/B14I/O/ZDV
C_FIELD
GPIO5/This pin is multiplexed between GPIO and the VPBE.
G1In VPBE mode, it is RGB888 Green data bit 1 output G1.
GPIO6/This pin is multiplexed between GPIO and the VPBE.
B1In VPBE mode, it is RGB888 Blue data bit 1 output B1.
GPIO38/This pin is multiplexed between VPBE and GPIO.
R1In VPBE mode, it is RGB888 Red output data bit 1.
E14I/O/ZDV
A14I/O/ZDV
D14I/O/ZDV
PWM1/
R2/B15I/O/ZDV
GPIO46
PWM2/
B2/A15I/O/ZDV
GPIO47
OTHER
(3)
DD18
DD18
DD18
DD18
DD18
DD18
DD18
(2)
DESCRIPTION
In VPBE mode, it is RGB888 Blue data bit 0 output B0.
This pin is multiplexed between GPIO, the VPFE, and the VPBE.
In VPBE mode, it is RGB888 Red data bit 0 output R0.
This pin is multiplexed between PWM1, VPBE, and GPIO.
In VPBE mode, it is RGB888 Red output bit 2 (R2).
This pin is multiplexed between PWM2, VPBE, and GPIO.
In VPBE mode, it is RGB888 Blue output bit 2 (B2).
Table 2-21. DAC [Part of VPBE] Terminal Functions
SIGNAL
NAMENO.
DAC_VREFR17A I
DAC_IOUT_AP19A O
DAC_IOUT_BP18A O
DAC_IOUT_CR19A O
DAC_IOUT_DT19A O
V
DDA_1P8V
V
SSA_1P8V
V
DDA_1P1V
V
SSA_1P1V
R18S
P17GND
P16S
T18GND
DAC_RBIASR16A I
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
(3) For more information, see Section 5.2, Recommended Operating Conditions.
TYPE
(1)
OTHER
(3)
(3)
(3)
(3)
(3)
(3)
(2) (3)
DESCRIPTION
DAC[A:D]
Reference voltage input (0.5 V). When the DAC is not used, the DAC_VREF signal
should be connected to VSS.
Output of DAC A. When the DAC is not used, the DAC_IOUT_A signal should be
left as a No Connect.
Output of DAC B. When the DAC is not used, the DAC_IOUT_B signal should be
left as a No Connect.
Output of DAC C. When the DAC is not used, the DAC_IOUT_C signal should be
left as a No Connect.
Output of DAC D. When the DAC is not used, the DAC_IOUT_D signal should be
left as a No Connect.
1.8-V analog I/O power. When the DAC is not used, the V
connected to VSS.
Analog I/O ground. When the DAC is not used, the V
connected to VSS.
1.05-V analog core supply voltage (-405 device) or 1.20-V analog core supply
voltage (-513 device). When the DAC is not used, the V
connected to VSS.
Analog core ground. When the DAC is not used, the V
connected to VSS.
External resistor connection for current bias configuration. This pin must be
connected via a 4-kΩ resistor to V
DAC_RBIAS signal should be connected to VSS.
DMACK/This pin is multiplexed between ATA/CF and UART1.
UART_TXD1For UART1, it is transmit data output UART_TXD1.
DMARQ/This pin is multiplexed between ATA/CF and UART1.
UART_RXD1For UART1, it is receive data input UART_RXD1.
UART_RXD0/This pin is multiplexed between UART0 and GPIO.
GPIO35For UART0, it is receive data input UART_RXD0.
UART_TXD0/This pin is multiplexed between UART0 and GPIO. .
GPIO36For UART0, it is transmit data output UART_TXD0.
H3I/O/ZDV
G1I/O/ZDV
D5I/O/ZDV
C5I/O/ZDV
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = internal pulldown, IPU = internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
(2) (3)
OTHER
DESCRIPTION
UART2
IPDThis pin is multiplexed between the CCDC and UART2.
DV
DD18
When used by UART2 it is the receive data input UART_RXD2.
IPDThis pin is multiplexed between the CCDC and UART2.
DV
DD18
In UART2 mode, it is the transmit data output UART_TXD2.
IPDThis pin is multiplexed between the CCDC and UART2.
DV
DD18
In UART2 mode, it is the clear to send input UART_CTS2.
IPDThis pin is multiplexed between the CCDC and UART2.
DV
DD18
In UART2 mode, it is the ready to send output UART_RTS2.
PWM0/This pin is multiplexed between PWM0 and GPIO.
GPIO45For PWM0, it is output PWM0.
C15I/O/ZDV
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
DESCRIPTION
PWM2
DD18
This pin is multiplexed between PWM2, VPBE, and GPIO.
For PWM2, it is output PWM2.
PWM1
DD18
This pin is multiplexed between PWM1, VPBE, and GPIO.
For PWM1, it is output PWM1.
PWM0
DD18
Table 2-24. ATA/CF Terminal Functions
SIGNAL
NAMENO.
SPI_EN1/
HDDIR/B2I/O/ZDV
GPIO42
GPIO50/This pin is multiplexed between GPIO and ATA/CF.
ATA_CS0In ATA mode, it is ATA/CF chip select output ATA_CS0.
GPIO51/This pin is multiplexed between GPIO and ATA/CF.
ATA_CS1In ATA mode, it is ATA/CF chip select output ATA_CS1.
J5ODV
H1ODV
EM_R/W/
INTRQ/G3IDV
H/W
EM_WAIT/
(RDY/BSY)/IPUThis pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
IORDY/DV
F1I
HRDY
EM_OE/
( RE )/This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
( IORD )/H4ODV
DIOR/For ATA, it is read strobe output DIOR.
HDS1
EM_WE
(WE)This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
(IOWR)/G2ODV
DIOW/For ATA, it is write strobe output DIOW.
HDS2
DMACK/This pin is multiplexed between ATA/CF and UART1.
UART_TXD1For ATA/CF, it is DMA acknowledge output DMACK.
DMARQ/IPDThis pin is multiplexed between ATA/CF and UART1.
UART_RXD1DV
H3ODV
G1O
TYPE
(1)
OTHER
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
(2) (3)
DESCRIPTION
ATA/CF
This pin is multiplexed between SPI, ATA, and GPIO.
For ATA, it is buffer direction control output HDDIR.
This pin is multiplexed between EMIFA, ATA/CF, and HPI.
For ATA/CF, it is interrupt request input INTRQ.
For ATA/CF, it is IO Ready input IORDY.
For CF, it is read strobe output (IORD).
For CF, it is write strobe output (IOWR).
For ATA/CF, it is DMA request DMARQ input.
www.ti.com
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = Internal pulldown, IPU = Internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal
DA2/This pin is multiplexed between EMIFA, ATA/CF, HPI, and GPIO.
HCNTL1/For ATA/CF, it is Device address bit 2 output DA2.
J4I/O/ZDV
GPIO53
EM_BA[1]/
DA1/H2I/O/ZDV
GPIO52
EM_BA[0]/
DA0/J3I/O/ZDV
HINT
(1)
TYPE
OTHER
I/O/ZDV
DD18
DD18
DD18
DD18
(2) (3)
DESCRIPTION
These pins are multiplexed between EMIFA (NAND), ATA/CF, and HPI. In all cases
they are used as a 16 bit bi-directional data bus.
For ATA/CF, these are DD[15:0].
This pin is multiplexed between EMIFA, ATA/CF, and GPIO.
For ATA/CF, it is Device address bit 1 output DA1.
This pin is multiplexed between EMIFA, ATA/CF, HPI.
For ATA/CF, it is Device address bit 0 output DA0.
Table 2-25. MMC/SD/SDIO and Memory Stick/Memory Stick PRO Terminal Functions
SIGNAL
NAMENO.
SD_CLK/
MS_CLK
SD_CMD/
MS_BS
SD_DATA3/
MS_DATA3
SD_DATA2/
MS_DATA2
SD_DATA1/
MS_DATA1
SD_DATA0/
MS_DATA0
A9ODV
B9ODV
C9I/O/Z
D9I/O/Z
E9I/O/Z
D8I/O/Z
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
MMC/SD/SDIO and Memory Stick/Memory Stick PRO
This pin is multiplexed between MMC/SD/SDIO and Memory Stick/Memory Stick
DD33
PRO. For MMC/SD/SDIO, this is the data clock output SD_CLK.
In Memory Stick mode, this is the clock output MS_CLK.
This pin is multiplexed between MMC/SD/SDIO and Memory Stick/Memory Stick
DD33
PRO. For MMC/SD/SDIO, this is the Command IO output SD_CMD.
In Memory Stick mode, this is the Bus State output MS_BS.
These pins are multiplexed between MMC/SD/SDIO and Memory Stick/Memory
Stick PRO. In MMC/SD/SDIO mode, these pins are the nibble-wide bi-directional
DV
DD33
data bus SD_DATA[3:0].
In Memory Stick mode, these pins are the nibble-wide bi-directional data bus
MS_DATA[3:0].
EM_BA[0]/memory, this pin is the lowest order bit of the byte address. When connected to a
DA0/J3I/O/ZDV
HINT22 EM_A[22].
EM_A[0]/
DA2/
HCNTL1/
J4I/O/ZDV
GPIO53
EM_A[2]/
(CLE)/J1I/O/ZDV
HCNTL0
EM_A[1]/
(ALE)/J2I/O/ZDV
HHWIL
EM_R/W/read/write output EM_R/W.
INTRQ/G3I/O/ZDV
HR/WFor HPI, it is the Host Read Write input HR/W. This signal is active high for reads
EM_CS2/2 output EM_CS2 for use with asynchronous memories (i.e. NOR flash) or NAND
HCSflash. This is the chip select for the default boot and ROM boot modes.
C2I/O/ZDV
EM_WE
(WE)
(IOWR)/G2I/O/ZDV
DIOW/
HDS2
EM_OE/
(RE)/
(IORD)/H4I/O/ZDV
DIOR/
HDS1
EM_WAIT/
(RDY/BSY)/IPU
IORDY/DV
F1I/O/ZFor NAND/SmartMedia/xD, it is ready/busy input (RDY/BSY).
HRDY
TYPE
(1)
OTHER
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
(1) (2)
DESCRIPTION
Host-Port Interface (HPI)
For EMIFA, this pin is Chip Select 3 output.
In HPI mode, this pin must be pulled high via an external 10-kΩ resistor.
This pin is multiplexed between EMIFA, ATA/CF, and HPI. For EMIFA, this is the
Bank Address 0 output EM_BA[0]. When connected to an 8-bit asynchronous
16-bit asynchronous memory, this pin has the same function as EMIF address pin
For ATA/CF, it is Device address bit 0 output DA0.
In HPI mode, it is the host interrupt output HINT.
This pin is multiplexed between EMIFA, ATA/CF, HPI, and GPIO. For EMIFA, this is
Address output EM_A[0], which is the least significant bit on a 32-bit word address.
When connected to a 16-bit asynchronous memory, this pin is the 2nd bit of the
address. For an 8-bit asynchronous memory, this pin is the 3rd bit of the address.
For ATA/CF, it is Device address bit 2 output DA2.
For HPI, it is control input HCNTL1. The state of HCNTL1 and HCNTL0 determine if
address, data, or control information is being transmitted between an external host
and DM6441.
In GPIO mode, it is GPIO53.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), and HPI. For
EMIFA, this pin is the EM_A[2] address line.
For NAND/SmartMedia/xD, this pin is the Command Latch Enable output (CLE).
In HPI mode, it is control input HCNTL0. The state of HCNTL1 and HCNTL0
determine if address, data, or control information is being transmitted between an
external host and DM6441.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), and HPI. When
used for EMIFA, it is address output EM_A[1].
For NAND/SmartMedia/xD, it is Address Latch Enable output (ALE).
In HPI mode, it is Half-word identification input HHWIL.
This pin is multiplexed between EMIFA, ATA/CF, and HPI. For EMIFA, it is EMIF
For ATA/CF, it is interrupt request input INTRQ.
and low for writes.
This pin is multiplexed between EMIFA and HPI. For EMIFA, this pin is Chip Select
In HPI mode, this pin is HPI Active Low Chip Select input HCS.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
For EMIFA, it is write enable output EM_WE.
For NAND/SmartMedia/xD, it is write enable output (WE).
For CF, it is write strobe output (IOWR).
For ATA, it is write strobe output DIOW.
For HPI, it is data strobe 2 input HDS2.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
For EMIFA, it is output enable output EM_OE.
For NAND/SmartMedia/xD, it is read enable output (RE).
For CF, it is read strobe output (IORD).
For ATA, it is read strobe output DIOR.
For HPI, it is data strobe 1 input HDS1.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
For EMIFA, it is wait state extension input EM_WAIT.
For ATA/CF, it is IO Ready input IORDY.
For HPI, it is ready output HRDY.
(1) IPD = internal pulldown, IPU = internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(2) Specifies the operating I/O supply voltage for each signal
These pins are multiplexed between EMIFA (NAND), ATA/CF, and HPI. In all cases
they are used as a 16 bit bi-directional data bus. For EMIFA (NAND), these are
EM_D[15:0].
For ATA/CF, these are DD[15:0].
In HPI mode, these are HD[15:0] and are multiplexed internally with the HPI address
lines.
No external pins. The Watchdog timer and Timer 1 peripheral pins are not pinned out as external pins.
CLK_OUT1/
TIM_IN/E19I/O/ZDV
GPIO49
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) Specifies the operating I/O supply voltage for each signal
TYPE
(1)
OTHER
(2)
DESCRIPTION
Watchdog timer and Timer 1
Timer 0
DD18
This pin is multiplexed between the USB clock generator, timer, and GPIO.
For Timer0, it is the timer event capture input TIM_IN.
Table 2-28. Reserved Terminal Functions
SIGNAL
NAMENO.
RSV1A1Reserved. (Leave unconnected, do not connect to power or ground)
RSV2A19Reserved. (Leave unconnected, do not connect to power or ground)
RSV3W1Reserved. (Leave unconnected, do not connect to power or ground)
RSV4W19Reserved. (Leave unconnected, do not connect to power or ground)
RSV5D4IReserved. This pin must be tied directly to VSSfor normal device operation.
RSV6L3A OReserved. (Leave unconnected, do not connect to power or ground)
RSV7R8AReserved. (Leave unconnected, do not connect to power or ground)
RSV24M3SReserved. (Leave unconnected, do not connect to power or ground)
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(2) IPD = internal pulldown, IPU = internal pullup. (To pull up a signal to the opposite supply rail, a 1-kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal
TI offers an extensive line of development tools for the SoC 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 SoC-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 SoC application.
Hardware Development Tools:
Extended Development System (XDS™) Emulator
For a complete listing of development-support tools for the SoC platform, visit the Texas Instruments
web site on the Worldwide Web at http://www.ti.com uniform resource locator (URL). For information
on pricing and availability, contact the nearest TI field sales office or authorized distributor.
2.8.2Device and Development-Support Tool Nomenclature
www.ti.com
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., TMX320DM6441ZWT). Texas Instruments recommends two of three possible prefix
designators for its support tools: TMDX and TMDS. These prefixes represent evolutionary stages of
product development from engineering prototypes (TMX/TMDX) through fully qualified production
devices/tools (TMS/TMDS).
Device development evolutionary flow:
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 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.
TMX= Experimental device
TMP= Prototype device
TMS= Qualified device
SMX= Experimental device, MIL
SMJ = MIL-PRF-38535, QML
SM = High Rel (non-38535)
DEVICE FAMILY
320 = TMS320t DSP family
PACKAGE TYPE
(A)
ZWT = 361-pin plastic BGA, with Pb-free soldered balls
DEVICE
(B)
TEMPERATURE RANGE (DEFAULT: 0°C TO 85°C)
( )
Blank = 0°C to 85°C
405 (405-MHz DSP, 202.5−MHz ARM9 at 1.05V)
513 (513-MHz DSP, 256-MHz ARM9 at 1.2V)
A. BGA = Ball Grid Array
B. For actual device part numbers (P/Ns) and ordering information, see the TI website (http://www.ti.com).
S ( )
SILICON REVISION
0 = Initial Silicon
A= Silicon 2.1
B= Silicon 2.3
ROM SECURITY
S= Secure
N= Non-secure
TMS320DM6441
www.ti.com
TI device nomenclature also includes a suffix with the device family name. This suffix indicates the
package type (for example, ZWT), the temperature range (for example, "Blank" is the commercial
temperature range).
Figure 2-6 provides a legend for reading the complete device name for any SoC platform member.
2.8.3.1Related Documentation From Texas Instruments
The following documents describe the Digital Media System-on-Chip (DMSoC). Copies of these
documents are available on the Internet at www.ti.com. Tip: Enter the literature number in the search box
provided at www.ti.com.
The current documentation that describes the DM6441 DMSoC, related peripherals, and other technical
collateral, is available in the C6000 DSP product folder at: www.ti.com/c6000.
SPRU395TMS320C64x Technical Overview. Provides an introduction to the TMS320C64x digital
signal processors (DSPs) of the TMS320C6000 DSP family.
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.
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.
SPRUE14TMS320DM644x DMSoC ARM Subsystem Reference Guide. Describes the ARM
subsystem in the TMS320DM644x Digital Media System-on-Chip (DMSoC). The ARM
subsystem is designed to give the ARM926EJ-S (ARM9) master control of the device. In
general, the ARM is responsible for configuration and control of the device; including the
DSP subsystem, the video processing subsystem, and a majority of the peripherals and
external memories.
www.ti.com
SPRUE15TMS320DM644x DMSoC DSP Subsystem Reference Guide. Describes the digital signal
processor (DSP) subsystem in the TMS320DM644x Digital Media System-on-Chip (DMSoC).
SPRUE19TMS320DM644x DMSoC Peripherals Overview Reference Guide. Provides an overview
and briefly describes the peripherals available on the TMS320DM644x Digital Media
System-on-Chip (DMSoC).
Guide.Describestheasynchronousexternalmemoryinterface(EMIF)inthe
TMS320DM644x Digital Media System-on-Chip (DMSoC). The EMIF supports a glueless
interface to a variety of external devices.
SPRUE21TMS320DM644x DMSoC ATA Controller User's Guide. Describes the ATA controller in
the TMS320DM644x Digital Media System-on-Chip (DMSoC). The ATA controller provides a
glueless interface to storage media to be used by video and audio applications for video and
audio data storage.
SPRUE22TMS320DM644x DMSoC DDR2 Memory Controller User's Guide. Describes the DDR2
memory controller in the TMS320DM644x Digital Media System-on-Chip (DMSoC). The
DDR2 memory controller is used to interface with JESD79D-2A standard compliant DDR2
SDRAM devices.
SPRUE23TMS320DM644x DMSoC Enhanced Direct Memory Access (EDMA3) Controller User's
Guide. Describes the operation of the enhanced direct memory access (EDMA3) controller
in the TMS320DM644x Digital Media System-on-Chip (DMSoC). The EDMA3 controller’s
primary purpose is to service user-programmed data transfers between two memory-mapped
slave endpoints on the DMSoC.
SPRUE26TMS320DM644x DMSoC 64-Bit Timer User's Guide. Describes the operation of the
SPRUE29TMS320DM644x DMSoC Audio Serial Port (ASP) User's Guide. Describes the operation
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
Input/Output (MDIO) Module User's Guide. Discusses the ethernet media access
controller (EMAC) and physical layer (PHY) device management data input/output (MDIO)
module in the TMS320DM644x Digital Media System-on-Chip (DMSoC). The EMAC controls
the flow of packet data from the DMSoC to the PHY. The MDIO module controls PHY
configuration and status monitoring.
the general-purpose input/output (GPIO) peripheral in the TMS320DM644x Digital Media
System-on-Chip (DMSoC). 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.
software-programmable 64-bit timer in the TMS320DM644x Digital Media System-on-Chip
(DMSoC). Timer 0 and Timer 1 are used as general-purpose (GP) timers and can be
programmed in 64-bit mode, dual 32-bit unchained mode, or dual 32-bit chained mode;
Timer 2 is used only as a watchdog timer. The GP timer modes can be used to generate
periodic interrupts or enhanced direct memory access (EDMA) synchronization events. The
watchdog timer mode is used to provide a recovery mechanism for the device in the event of
a fault condition, such as a non-exiting code loop.
of the audio serial port (ASP) audio interface in the TMS320DM644x Digital Media
System-on-Chip (DMSoC). The primary audio modes that are supported by the ASP are the
AC97 and IIS modes. In addition to the primary audio modes, the ASP supports general
serial port receive and transmit operation, but is not intended to be used as a high-speed
interface.
SPRUE35TMS320DM644x DMSoC Universal Serial Bus (USB) Controller User's Guide. Describes
the universalserialbus(USB) controllerintheTMS320DM644x DigitalMedia
System-on-Chip (DMSoC). The USB controller supports data throughput rates up to 480
Mbps. It provides a mechanism for data transfer between USB devices and also supports
host negotiation.
SPRUE37TMS320DM644x DMSoC Video Processing Back End (VPBE) User's Guide. Describes
the video processing back end (VPBE) in the TMS320DM644x Digital Media System-on-Chip
(DMSoC) video processing subsystem. Included in the VPBE is the video encoder,
on-screen display, and digital LCD controller.
SPRUE97TMS320DM644x DMSoC Host Port Interface (HPI) User's Guide. Describes the features
and operation of the host port interface (HPI) in the TMS320DM644x Digital Media
System-on-Chip (DMSoC).
SPRA839Using IBIS Models for Timing Analysis. Describes how to properly use IBIS models to
attain accurate timing analysis for a given system.
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.
SPRAAA6EDMA v3.0 (EDMA3) Migration Guide for TMS320DM644x DMSoC. Describes migrating
from the Texas Instruments TMS320C64x digital signal processor (DSP) enhanced direct
memory access (EDMA2) to the TMS320DM644x Digital Media System-on-Chip (DMSoC)
EDMA3. This document summarizes the key differences between the EDMA3 and the
EDMA2 and provides guidance for migrating from EDMA2 to EDMA3.
The system module includes status and control registers required for configuration of the device. Brief
descriptions of the various registers are shown in Table 3-1. System module registers required for device
configurations are discussed in the following sections.
Table 3-1. System Module Register Memory Map
HEX ADDRESS RANGEREGISTER ACRONYMDESCRIPTION
0x01C4 0000PINMUX0Pin multiplexing control 0. See Section 3.5.4, PINMUX0 Register Description,
0x01C4 0004PINMUX1Pin multiplexing control 1. See Section 3.5.5, PINMUX1 Register Description,
0x01C4 0008DSPBOOTADDRBoot address of DSP. See Section 3.3.1.2, DSPBOOTADDR Register
0x01C4 000CSUSPSRCEmulator Suspend Source. See Section 3.6, Emulation Control, for details.
0x01C4 0010INTGENARM/DSP Interrupt Status and Control. See Section 6.7.3, ARM/DSP
0x01C4 0014BOOTCFGDevice boot configuration. See Section 3.3.1.1, BOOTCFG Register
0x01C4 0018 - 0x01C4 0027 –Reserved
0x01C4 0028JTAGIDJTAGID/Device ID number. See Section 6.26.1, JTAG Peripheral Register
0x01C4 002C–Reserved
0x01C4 0030HPI_CTLHPI control. See Section 3.5.6.10, HPI and EMIFA/ATA Pin Multiplexing, for
0x01C4 0034USBPHY_CTLUSB PHY control. See Section 6.14.1, USBPHY_CTL Register Description,
0x01C4 0038CHP_SHRTSWChip shorting switch control. See Section 3.2.1, Power Configurations at
0x01C4 003CMSTPRI0Bus master priority control 0. See Section 3.5.1, Switched Central Resource
0x01C4 0040MSTPRI1Bus master priority control 1. See Section 3.5.1, Switched Central Resource
0x01C4 0044VPSS_CLKCTLVPSS clock control.
0x01C4 0048VDD3P3V_PWDNVDD 3.3V I/O powerdown control. See Section 3.2.2, Power Configurations
0x01C4 004CDRRVTPEREnables access to the DDR2 VTP register.
0x01C4 0050 - 0x01C4 006F –Reserved
for details.
for details.
Description, for details.
Communications Interrupts, for details.
Description, for details.
Description(s) – JTAG ID Register, for details.
details.
for details.
Reset, for details.
(SCR) Bus Priorities, for details.
(SCR) Bus Priorities, for details.
after Reset, for details.
3.2Power Considerations
Global device power domains are controlled by the power and sleep controller, except as shown in the
following sections.
As described in Section 6.3.1.3, DM6441 Power and Clock Domains, the DM6441 has two power
domains: Always On and DSP. There is a shorting switch between the two power domains that must be
opened when the DSP domain is powered off and closed when the DSP domain is powered on.
The CHP_SHRTSW register, shown in Figure 3-1, controls the shorting switch between the device
always-on and DSP power domains. This switch should be enabled after powering-up the DSP domain.
Setting the DSPPWRON bit to a value of 1 closes (enables) the switch and enables the DSP power
domain. The default switch value is determined by the DSP_BT configuration input. If DSP self boot is
selected (DSP_BT=1), the DSP will be powered-up and DSPPWRON will be set to a value of 1. For ARM
boot operation (DSP_BT=0), DSPPWRON will be set to the disable value of 0 and must be set by the
ARM before the DSP domain power is turned on.
Figure 3-1. CHP_SHRTSW Register
3110
RESERVEDDSPPWRON
R-0000 0000 0000 0000 0000 0000 0000 000R/W-L
LEGEND: R = Read, W = Write, n = value at reset, L = pin state latched at reset rising
Table 3-2. CHP_SHRTSW Register Field Descriptions
BitFieldValueDescription
31 - 1RESERVEDReserved
0DSPPWRONDSP power domain enable
0Shorting switch open
1Shorting switch closed
www.ti.com
3.2.2Power Configurations after Reset
The VDD3P3V_PWDN register controls power to the 3.3V I/O buffers for MMC/SD/SDIO, Memory
Stick/Memory Stick PRO, and GPIOV33. The 3.3V I/Os are separated into two groups for independent
control as shown in Figure 3-2 and described in Table 3-3. By default, these pins are all disabled at reset.
Figure 3-2. VDD3P3V_PWDN Register
31210
RESERVEDIOPWDN1IOPWDN0
R-0000 0000 0000 0000 0000 0000 0000 00R/W-1R/W-1
LEGEND: R = Read, W = Write, n = value at reset
Table 3-3. VDD3P3V_PWDN Register Field Descriptions
The device is booted through multiple means: pin states captured at reset, primary bootloaders within
internal ROM or EMIFA, and secondary user bootloaders from peripherals or external memories. Boot
modes, pin configurations, and register configurations required for booting the device, are described in the
following sections.
3.3.1Bootmode Registers
The BOOTCFG and DSPBOOTADDR registers are described in the following sections. At reset, the status
of various pins required for proper boot are stored within these registers.
3.3.1.1BOOTCFG Register Description
The BOOTCFG register (located at address 0x01C4 0014) contains the status values of the BTSEL1,
BTSEL0, DSP_BT, EM_WIDTH, and AEAW[4:0] pins captured at the rising edge of RESET. The register
format is shown in Figure 3-3 and bit field descriptions are shown in Table 3-4. The captured bits are
software readable after reset.
Figure 3-3. BOOTCFG Register
319876543210
RESERVEDDSP_BTBTSELEM_WIDTHDAEAW
R-0000 0000 0000 0000 0000 000R-LR-LLR-LR-LLLLL
LEGEND: R = Read; W = Write; L = pin state latched at reset rising; -n = value after reset
Table 3-4. BOOTCFG Register Field Descriptions
BitFieldValueDescription
31 - 9RESERVEDReserved
8DSP_BTDSP boot mode selection pin state captured at the rising edge of RESET.
0Sets ARM boot of C64x+.
1Sets C64x+ self boot.
7 - 6BTSELARM boot mode selection pin states (BTSEL1, BTSEL0) captured at the rising edge of RESET.
00Indicates ARM boots from ROM (NAND Flash/SPI Flash).
01Indicates that ARM boots from EMIFA (NOR Flash).
10Indicates that ARM boots from ROM (HPI).
11Indicates that ARM boots from ROM (UART0).
5EM_WIDTHEMIFA data bus width selection pin state captured at the rising edge of RESET.
0Sets EMIFA to 8 bit data bus width
1Sets EMIFA to 16 bit data bus width.
4 - 0DAEAWEMIFA address bus width selection pin states (AEAW[4:0]) captured at the rising edge of RESET.
This configures EMIFA address pins multiplexed with GPIO. See the GPIO and EMIFA Multiplexing
tables (Table 3-9, Table 3-10, and Table 3-11).
The DSPBOOTADDR register contains the upper 22 bits of the C64x+ DSP reset vector. The register
format is shown in Figure 3-4 and bit field descriptions are shown in Table 3-5. DSPBOOTADDR is
readable and writable by software after reset.
Figure 3-4. DSPBOOTADDR Register
311090
BOOTADDR[21:0]RESERVED
R- 0100 0010 0010 0000 0000 00R-00 0000 0000
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 3-5. DSPBOOTADDR Register Field Descriptions
BitFieldValueDescription
31 - 10BOOTADDR[21:0]Upper 22 bits of the C64x+ DSP boot address.
9 - 0RESERVEDReserved
3.3.2ARM Boot
The DM6441 ARM can boot from EMIFA, internal ROM (NAND, SPI), UART0, or HPI, as determined by
the setting of the BTSEL[1:0] pins. The BTSEL[1:0] pins are read by the ARM ROM boot loader (RBL) to
further define the ROM boot mode. The ARM boot modes are summarized in Table 3-6.
Table 3-6. ARM Boot Modes
BTSEL1 BTSEL0 Boot ModeARM ResetBrief Description
00ARM NAND, SPI RBL0x0000 4000Up to 14 K-bytes secondary boot loader through NAND with up
01ARM EMIFA external Boot0x0200 0000EMIFA EM_CS2 external memory space.
10ARM HPI RBL0x0000 4000Up to 14 K-btyes secondary boot loader through an external
11ARM UART RBL0x0000 4000Up to 14 K-bytes secondary boot loader through UART0.
Vector
to 2 K-bytes page sizes.
host.
When the BTSEL[1:0] pins are set to the ARM EMIFA external boot ("01"), the ARM immediately begins
executing code from the EMIFA EM_CS2 memory space (0x0200 0000). When the BTSEL[1:0] pins
indicate a condition other than the ARM EMIFA external boot (!01), the RBL begins execution.
ARM NAND/SPI boot mode has the following features:
•Loads a secondary user boot loader (UBL) from NAND/SPI flash to ARM internal RAM (AIM) and
transfers control to the user software.
•Support for NAND with page sizes up to 2048 bytes.
•Support for error correction when loading UBL
•Support for up to 14KB UBL
•Optional, user selectable, support for use of DMA, I-cache, and PLL enable while loading UBL
ARM UART boot mode has the following features:
•Loads a secondary UBL via UART0 to AIM and transfers control to the user software.
•Support for up to 14KB UBL
ARM HPI boot mode has the following features:
•No support for a full firmware boot. Instead, waits for external host ot load a secondary UBL via HPI to
AIM and transfers control to the user software.
For further details on the ROM bootloader, see the TMS320DM644x DMSoC ARM Subsystem ReferenceGuide (literature number SPRUE14).
3.3.3DSP Boot
For C64x+ booting, the state of the DSP_BT pin is sampled at reset. If DSP_BT is low, the ARM will be
the master of C64x+ and control booting (host-boot mode). If DSP_BT is high, the C64x+ will boot itself
coming out of device reset (self-boot mode). Table 3-7 shows a summary of the DSP boot modes.
Table 3-7. DSP Boot Modes
DSP_BTDSPARMDSPBOOTADDRBrief Description
0Host bootInternal bootProgrammableARM sets an internal DSP memory location in DSPBOOTADDR
0Host bootExternal bootProgrammableARM sets an external DSP memory location in DSPBOOTADDR
1Self bootAny, except HPI0x4220 0000Default EMIFA base address
1Host bootHPIProgrammableARM sets a DSP memory location in the DSPBOOTADDR
Boot ModeBoot ModeRegister Value
register where valid DSP code resides and loads code to this
internal DSP memory through DMA prior to releasing DSP reset.
register (EMIFA or DDR2) where valid DSP code resides prior to
releasing DSP reset.
register.
HPI loads code into the DM6441 memory map with the entry point
set to the memory location specified in the DSPBOOTADDR
register. Once the HPI completes loading the code, the ARM
should release the DSP from reset.
3.3.3.1Host-Boot Mode
In host boot mode, the ARM is the master and controls the reset and boot of the C64x+. The C64x+ DSP
remains powered-off after device reset. The ARM is responsible for enabling power to the C64x+ and
releasing it from reset (PSC MMR bits: MDCTL[39].LRST and MRSTOUT1.MRSTz[39]). Prior to releasing
the C64x+ reset, the ARM must program the address from which the C64x+ will begin execution in the
DSPBOOTADDR register.
3.3.3.2Self-Boot Mode
In self-boot mode, the C64x+ power domain is turned on and the C64x+ DSP is released from reset
without ARM intervention. The C64x+ begins execution from the default EMIFA address (0x4220 0000)
contained within the DSPBOOTADDR register. The C64x+ begins execution with instruction (L1P) cache
enabled.
The following sections give information on configuration settings for the device at reset.
3.4.1Device Configuration at Device Reset
Table 3-8 shows a summary of device inputs required for booting the ARM and DSP, and configuring
EMIFA data and address bus widths for proper operation of the device at the rising edge of the RESET
input.
Table 3-8. Device Configurations (Input Pins Sampled at Reset)
DEVICE SIGNALS
SAMPLEDDESCRIPTION
AT RESET
BTSEL[1:0]COUT[1:0]ARM boot mode selection pins.
DSP_BTCOUT3DSP boot mode selection pin.
EM_WIDTHCOUT2EMIFA data bus width selection pin.
AEAW[4:0]YOUT[4:0]EMIFA address bus width selection pins for EMIFA address pins multiplexed with GPIO.
DEVICE SIGNAL NAME
AFTER RESET
‘00’ indicates ARM boots from ROM (NAND/SPI Flash).
‘01’ indicates that ARM boots from EMIFA (NOR Flash).
‘10’ indicates that the ARM boots from the HPI (ROM)
‘11’ indicates that ARM boots from ROM (UART0).
‘0’ sets ARM boot of C64x+.
‘1’ sets C64x+ self boot.
‘0’ sets EMIFA to 8-bit data bus width
‘1’ sets EMIFA to 16-bit data bus width.
See the GPIO and EMIFA Multiplexing tables (Table 3-9, Table 3-10, and Table 3-11) for
details.
3.4.2Peripheral Selection at Device Reset
As briefly mentioned in Table 3-8, the state of the AEAW[4:0] pins captured at reset configures the
number of EMIFA address pins required for device boot. These values are stored in the AEAW field of the
PINMUX0 register. At reset, this provides proper addressing for external boot. Unused address pins are
available for use as GPIO. The register settings are software programmable after reset. Table 3-9,
Table 3-10, and Table 3-11 show the AEAW[4:0] bit settings and the corresponding multiplexing for
EMIFA address and GPIO pins.
The number of EMIFA address bits enabled is configurable from 0 to 23. EM_BA[1] and EM_A[21:0] pins
that are not assigned to another peripheral and not enabled as address signals become GPIO pins. The
enabled address pins are always contiguous from EM_BA[1] upwards and address bits cannot be skipped.
The exception to this are the EM_A[2:1] pins. EM_A[2:1] are usable as the ALE and CLE signals for the
NAND Flash mode of EMIFA and are always enabled as EMIFA pins. If an address width of 0 is selected,
this still allows a NAND Flash to be accessed. Also, selecting an address width of 2, 3, or 4 (AEAW[4:0] =
00010, 00011, or 00100) always results in 4 address outputs. For these and other address bit enable
settings, see the GPIO and EMIFA Multiplexing tables (Table 3-9, Table 3-10, and Table 3-11).
The following sections give the details on configuring the device after reset.
3.5.1Switched Central Resource (SCR) Bus Priorities
Prioritization within the switched central resource (SCR) is programmable for each master. The register bit
fields and default priority levels for DM6441 bus masters are shown in Table 3-12. The priority levels
should be tuned to obtain the best system performance for a particular application. Lower values indicate
higher priority. For most masters, their priority values are programmed at the system level by configuring
the MSTPRI0 and MSTPRI1 registers. Details on the MSTPRI0/1 registers are shown in Figure 3-5 and
Figure 3-6. The C64x+, VPSS, and EDMA3 masters contain registers that control their own priority values.
Table 3-12. DM6441 Default Bus Master Priorities
Priority Bit FieldBus MasterDefault Priority Level
VPSSPVPSS0 (VPSS PCR registerRegister, DMA_PRI bit field)
[For more detailed information on the DMA_PRI bit field, see the TMS320DM644xDMSoC Video Processing Back End (VPBE) User's Guide (literature number
SPRUE37).]
EDMATC0PEDMATC00 (EDMA3CC QUEPRI register)
[For more detailed information on the QUEPRI register, see the TMS320DM644xDMSoC Enhanced Direct Memory Access (EDMA3) Controller User's Guide (literature
number SPRUE23).]
EDMATC1PEDMATC10 (EDMA3CC QUEPRI register)
[For more detailed information on the QUEPRI register, see the TMS320DM644xDMSoC Enhanced Direct Memory Access (EDMA3) Controller User's Guide (literature
number SPRUE23).]
ARM_DMAPARM (DMA)1 (MSTPRI0 register)
ARM_CFGPARM (CFG)1 (MSTPRI0 register)
C64X+_DMAPC64X+ (DMA)7 (C64x+ MDMAARBE.PRI register bit field)
[For more detailed information on the PRI bit field, see the TMS320DM644x DMSoC
There are numerous multiplexed pins that are shared by more than one peripheral. Some of these pins
are configured by external pullup/pulldown resistors only at reset, and others are configured by software.
As described in detail in Section 3.4.1, Device Configuration at Device Reset, and Section 3.4.2,
Peripheral Selection at Device Reset, hardware configurable multiplexed pins are programmed by external
pullup/pulldown resistors at reset to set the initial functionality of pins for use by a single peripheral. After
reset, software configurable multiplexed pins are programmable through memory mapped registers (MMR)
to allow the switching of pin functionalities during run-time. See Section 3.5.3, Peripheral Selection AfterDevice Reset, for more details on the register settings.
A summary of the pin multiplexing is shown in Table 3-13. The EMAC peripheral shares pins with the 3.3V
GPIO pins. The VLYNQ pins overlap upper EMIFA address pins resulting in a reduced EMIFA address
range as the VLYNQ width is increased. The ATA peripheral shares data lines and some control signals
with EMIFA. The ATA DMA pins are multiplexed with UART1. The ASP, UART0/1/2, SPI, I2C, and
PWM0/1/2 all default to GPIO pins when not enabled. The VPBE function of the VPSS requires additional
pins to implement the RGB888 mode. These are multiplexed with GPIOs.
Table 3-13. DM6441 Multiplexed Peripheral Pins and Multiplexing Controls
MULTIPLEXEDSECONDARY
PERIPHERALSFUNCTIONFUNCTION
EMIFA (NAND), HPI EMIFA:HPI:PinMux0:HPIEN
EMIFA, HPI, ATAEMIFA:ATA (CF):HPI:PinMux0:ATAENPinMux0:HPIEN
(CF)EM_D[0:15],DD[0:15], DA0HD[0:15], HINT
After device reset, the PINMUX0 and PINMUX1 registers are software programmable to allow multiplexing
of shared device pins between peripherals, as given in Section 2.7, Terminal Functions. Section 3.5.4,
PINMUX0 Register Description, Section 3.5.5, PINMUX1 Register Description, and Section 3.5.6, Pin
Multiplexing Register Field Details, identify the register settings necessary to configure specific multiplexed
functions and show the primary (default) function after reset.
3.5.4PINMUX0 Register Description
The PINMUX0 pin multiplexing register controls which peripheral is given ownership over shared pins
among EMAC, CCD, LCD, RGB888, RGB666, ATA, VLYNQ, EMIFA, HPI, and GPIO peripherals. The
register format is shown in Figure 3-7 and bit field descriptions are given in Table 3-14. More details on
the PINMUX0 pin muxing fields are given in Section 3.5.6, Pin Multiplexing Register Field Details. A value
of "1" enables the secondary or tertiary pin function.
LEGEND: R = Read; W = Write; L = pin state latched at reset rising edge; D = derived from pin states; -n = value after reset
(1) For proper DM6441 device operation, always write a value of '0' to RSV bit 30.
(1)
Table 3-14. PINMUX0 Register Field Descriptions
BitFieldValueDescription
31EMACENEnable EMAC and MDIO function on default GPIO3V[0:16] pins.
30RESERVEDReserved
29HPIENEnable HPI module pins. Default value is derived from BTSEL[1:0] configuration inputs. HPIEN is 1
28RESERVEDReserved
27CFLDENEnable CCD C_FIELD function on default GPIO[4] pin
26CWEEnable CCD C_WE function on default GPIO[1] pin
25LFLDENEnable LCD_FIELD function on default GPIO[3] pin
24LOEENEnable LCD_OE function on default GPIO[0] pin
23RGB888Enable VPBE RGB888 function on default GPIO[2:6, 46:47] pins
22RGB666Enable VPBE RGB666 function on default GPIO[46:47] pins
21 - 18RESERVEDReserved
17ATAENEnable ATA function on default EMIFA and GPIO[52:53] pins and shared UART1 pins
16HDIRENEnable HDDIR function on default GPIO[42] pin
15VLYNQENEnable VLYNQ function on default GPIO[9,10:17] pins
14VLSCRENEnable VLYNQ SCRUN function on default GPIO[9] pin
13 - 12VLYNQWDVLYNQ data width selection. This expands the VLYNQ TXD[0:3] and RXD[0:3] functions on default
11AECS5Enable EMIFA EM_CS5 function on GPIO[8]
10AECS4Enable EMIFA EM_CS4 function on GPIO[9]
9 - 5RESERVEDReserved
4 - 0AEAWEMIFA address width selection. Default value is latched at reset from AEAW[4:0] configuration input
when the BTSEL[1:0] = 10 and HPIEN is 0 (the default state) when BTSEL[1:0] is 00, 01, or 11.
GPIO[10:17] pins.
pins. This enables EMIF address function on default GPIO[10:28] pins.
The PINMUX1 pin multiplexing register controls which peripheral is given ownership over shared pins
among Timer, PLL, ASP, SPI, I2C, PWM, and UART peripherals. The register format is shown in
Figure 3-8 and bit field descriptions are given in Table 3-15. More details on the PINMUX1 pin muxing
fields are given in Section 3.5.6, Pin Multiplexing Register Field Details. A value of "1" enables the
secondary or tertiary pin function.
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 3-15. PINMUX1 Register Field Descriptions
BitFieldValueDescription
31 - 19RESERVEDReserved
18TIMINEnable TIM_IN function on default GPIO[49] pin
17CLK1Enable CLK_OUT1 function on default GPIO[49] pin
16CLK0Enable CLK_OUT0 function on default GPIO[48] pin
15 - 11RESERVEDReserved
10ASPEnable ASP function on default GPIO[29:34] pins
9MSKTEnable Memory Stick/Memory Stick PRO function on default MMC/SD/SDIO pins
8SPIEnable SPI function on default GPIO[37,39:42] pins
7I2CEnable I2C function on default GPIO[43:44] pins
6PWM2Enable PWM2 function on default GPIO[47] pin
5PWM1Enable PWM1 function on default GPIO[46] pin
4PWM0Enable PWM0 function on default GPIO[45] pin
3U2FLOEnable UART2 flow control function on default VPFE CI[5:4]/CCD_DATA[13:12] pins
2UART2Enable UART2 function on default VPFE CI[7:6]/CCD_DATA[15:14] pins
1UART1Enable UART1 function on shared ATA (CF) DMACK, DMARQ pins
0UART0Enable UART0 function on default GPIO[35:36] pins
The bit fields for various pin multiplexing options within the PINMUX0 and PINMUX1 registers are
described in the following sections.
3.5.6.1EMAC and GPIO3V Pin Multiplexing
The EMAC pin functions are selected as shown in Table 3-16. The functionality for each of the individual
pins affected by the PINMUX0 field settings is given in Table 3-17.
Table 3-16. EMAC and GPIO3V Pin Multiplexing Control
3.5.6.2VPFE (CCD), VPBE (LCD), and GPIO Pin Multiplexing
The CCD and LCD controllers in the VPSS require multiplex control bit settings for certain modes of
operation. Bits within the PinMux0 register, which select between the CCD or LCD control signal function
and GPIO, are summarized in Table 3-18.
Table 3-18. VPFE (CCD), VPBE (LCD), and GPIO Pin Multiplexing
PINMUX0 REGISTER FIELDSMULTIPLEXED PINS
CFLDENLFLDENCWELOEENR0/B0/GPIO[1]GPIO[0]
---0---GPIO[0]
---1---LCD_OE
--0---GPIO[1]-
--1---C_WE-
-0---B0/GPIO[3]
-1---LCD_FIELD-0---R0/GPIO[4]
1---C_FIELD---
(1) Depends on RGB888 bit setting, see Table 3-19.
C_FIELD/LCD_FIELD/C_WE/LCD_OE/
GPIO[4]GPIO[3]
(1)
(1)
---
--
3.5.6.3VPBE (RGB666 and RGB888) and GPIO Pin Multiplexing
Use of the RGB666 and RGB888 modes of the VPBE requires enabling RGB pins as shown in Table 3-19
and Table 3-20. Enabling PWM2, PWM1, CCD, and LCD functionality overrides the RGB modes. RGB666
interface pin functionality requires setting the RGB666 PINMUX0 register bit field to ‘1’ and PINMUX1
register bit fields PWM2 and PWM1 to ‘0’. Proper RGB888 interface operation requires setting PINMUX0
register bit field RGB888 to ‘1’ and bit fields PWM2, PWM1, CFLDEN, and LFLDEN must be set to ‘0’.
Table 3-19. VPBE (RGB666, RGB888, and LCD), VPFE (CCD), and GPIO Pin Multiplexing
PINMUX0 AND PINMUX1 REGISTER BIT FIELDSMULTIPLEXED PINS
3.5.6.4ATA, EMIFA, UART1, SPI, and GPIO Pin Multiplexing
The ATA peripheral shares pins with the EMIFA and UART1 as seen in Table 3-21. If ATA pin
functionality is enabled by setting the ATAEN bit field, the ATA module will drive the EMIFA data and
control pins. Enabling UART1 disables the use of the ATA DMARQ and DMACK signals and thus only
allows the ATA module to use PIO mode. The ATA HDDIR buffer direction control bit field works in
conjunction with the HDIREN enable bit field to allow the ATA pins to still be used as a GPIO or SPI_EN1
if the buffer is not being used (i.e. for compact flash). This multiplexing is shown in Table 3-22. When
ATAEN=0 and HDIREN=1 it indicates that the ATA interface has been disabled so that the EMIFA can be
used, but the ATA buffers are still present. HDDIR is driven low in this situation to ensure that the ATA
buffers drive away from DM6441 and don’t cause bus contention with the EMIFA. Note that switching
between EMIFA and ATA (clearing or setting ATAEN) must be carefully performed to prevent bus
contention. Since the ATA device can be a bus master, software must ensure that all outstanding DMA
requests have completed before clearing the ATAEN bit.
Table 3-21. ATA, EMIFA, and GPIO Pin Multiplexing Control
(1) This table assumes that the HPIEN bit in the PINMUX0 register is "0".
(2) This pin shares GPIO functionality set by AEAW[4:0] as shown in Table 3-9.
Table 3-23 and Table 3-24 show the VLYNQ pin control and multiplexing. If VLYNQ is disabled
(VLYNQEN=0), the AECS5 and AECS4 bits select between the GPIO[8] / EMIFA EM_CS5 and GPIO[9] /
EMIFA EM_CS4 functions, and the AEAW field determines the partitioning between GPIO and the upper
EMIFA address pins. If VLYNQ is enabled (VLYNQEN=1), VLYNQ_CLOCK, VLYNQ_TXD0, and
VLYNQ_RXD0 are always selected. The VLYNQ_SCRUN function is only enabled if VLYNQEN=1 and
VLSCREN=1 (VLSCREN overrides AECS4). The remaining VLYNQ TX/RX pins are selected based on
the VLYNQWD value. Unselected VLYNQ TX/RX pins will function as either GPIO or EMIFA address
based on the AEAW value.
Table 3-23. VLYNQ Control, EMIFA, and GPIO Pin Multiplexing
3.5.6.6Timer0 Input, CLK_OUT1, and GPIO Pin Multiplexing
The multiplexing of the CLK_OUT1 and Timer0 Input (Timer 0 only) functions is shown in Table 3-25.
Table 3-25. Timer0 Input, CLK_OUT1, and GPIO Pin
Multiplexing
PINMUX1 REGISTER BIT FIELDSMULTIPLEXED PINS
TIMINCLK1TIM_IN/
00GPIO[49]
01CLK_OUT1
1-TIM_IN
CLK_OUT1/
GPIO[49]
3.5.6.7ASP, SPI, I2C, ATA, and GPIO Pin Multiplexing
When the ASP, SPI, or I2C serial port functions are not selected, their pins may be used as GPIOs as
seen in Table 3-26, Table 3-27, and Table 3-28. The SPI_EN1 pin can also function as the HDDIR buffer
control when ATAEN is selected and the HDIREN bit is set.
Each UART has independent pin multiplexing control bits in the PINMUX1 register. The UART2 peripheral
may be used with or without the flow control signals. Table 3-30 shows how UART2 selection reduces the
width of the VPFE interface.
Setting the UART1 bit enables UART1 transmit and receive pin functionality. Since these are shared with
the ATA DMA handshake signals, enabling UART1 effectively disables the ATA DMA mode. However,
ATA PIO mode is still supported with UART1 enabled. This is shown in Table 3-31. If the ATA module is
not enabled, the pins are always configured for use by UART1.
Table 3-30. UART2, VPFE, and GPIO Pin Multiplexing
When the HPIEN bit is set, the HPI module is given control of most of the EMIFA/ATA control pins as well
as the EMIFA/ATA data bus. Table 3-33 shows which pins the HPI controls. HPIEN is set to 1 when the
state of the BTSEL[1:0] pins = 10 is latched at the rising edge of reset. Also, this bit can be manipulated
after reset by software. When the ATAEN bit is set and HPIEN is 0, the ATA mode of operation for pins
shared with the HPI is available. EMIFA mode functionality for the shared HPI pins is set when both
HPIEN and ATAEN are '0'.
The flexibility of the DM6441 architecture allows either the ARM or DSP to control the various peripherals
(setup registers, service interrupts, etc.). While this assignment is purely a matter of software convention,
during an emulation halt it is necessary for the device to know which peripherals are associated with the
halting processor so that only those modules receive the suspend signal. This allows peripherals
associated with the other (unhalted) processor to continue normal operation. The SUSPSRC register
indicates the emulation suspend source for those peripherals which support emulation suspend. The
SUSPSRC register format is shown in Figure 3-9. Brief details on the peripherals which correspond to the
register bits is given in Table 3-34. When the associated SUSPSRC bit is ‘0’, the peripheral’s emulation
suspend signal is controlled by the ARM emulator and when set to ‘1’ it is controlled by the DSP emulator.
On the DM6441 device, the C64x+ megamodule, the ARM subsystem, the EDMA3 transfer controllers,
and the system peripherals are interconnected through a switch fabric architecture (shown in Figure 4-1).
The switch fabric is composed of multiple switched central resources (SCRs) and multiple bridges. The
SCRs establish low-latency connectivity between master peripherals and slave peripherals. Additionally,
the SCRs provide priority-based arbitration and facilitate concurrent data movement between master and
slave peripherals. Through SCR, the ARM subsystem can send data to the DDR2 Memory Controller
without affecting a data transfer between the EMAC and L2 memory. Bridges are mainly used to perform
bus-width conversion as well as bus operating frequency conversion. For example, in Figure 4-1, Bridge 8
performs a frequency conversion between a bus operating at DSP/6 clock rate and a bus operating at
DSP/3 clock rate. Furthermore, Bridge 3 performs a bus-width conversion between a 64-bit bus and a
32-bit bus.
The C64x+ megamodule, the ARM subsystem, the EDMA3 transfer controllers, and the various system
peripherals can be classified into two categories: master peripherals and slave peripherals. Master
peripherals are typically capable of initiating read and write transfers in the system and do not rely on the
EDMA3 or on a CPU to perform transfers to and from them. The system master peripherals include the
C64x+ megamodule, the ARM subsystem, the EDMA3 transfer controllers, CF/ATA, VLYNQ, EMAC, USB,
and VPSS. Not all master peripherals may connect to all slave peripherals. The supported connections
are designated by an X in Table 4-1.
Table 4-1. System Connection Matrix
www.ti.com
MASTER
C64x+XXX
ARMXXX
VPSSX
CF/ATAXXXX
VLYNQXXXX
EMACXXXX
USBXXXX
EDMA3TC0XXXX
EDMA3TC1XXXX
HPIXXX
(1) The C64x+ megamodule has access to only the following peripherals connected to SCR3: EDMA3, ASP, and Timers. All other
peripherals/modules that support a connection to SCR3 have access to all peripherals/modules connected to SCR3.
(2) HPI's access to SCR3 is limited to the power and sleep controller registers, PLL1 and PLL2 registers, and HPI configuration registers.
Figure 4-1 displays the DM6441 system interconnect block diagram. The following is a list that helps
interpret this diagram:
•The direction of the arrows indicates either bus master or bus slave.
•The arrow originates at a bus master and terminates at a bus slave.
•The direction of the arrows does not indicate the direction of data flow. Data flow is typically
bi-directional for each of the documented bus paths.
•The pattern of each arrow's line indicates the clock rate at which it is operating, either DSP/2, DSP/3,
or DSP/6 clock rate.
•Some peripherals may have multiple instances shown in the diagram. A peripheral may have multiple
instances shown for a variety of reasons, some of which are described below:
– The peripheral/module has master port(s) for data transfers, as well as slave port(s) for register
access, data access, and/or memory access. Examples of these peripherals are C64x+
megamodule, EDMA3, CF/ATA, USB, EMAC, VPSS, VLYNQ, and HPI.
– The peripheral/module has a master port as well as slave memories. Examples of these are the
5.1Absolute Maximum Ratings Over Operating Case Temperature Range (Unless
Otherwise Noted)
Supply voltage ranges
Input voltage ranges
Output voltage ranges
Operating case temperature ranges, T
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) This pin is an internal LDO output and connected via 1 µF capacitor to USB_V
(3) All voltage values are with respect to V
stg
(1)
Core (CVDD, V
I/O, 3.3V (DV
I/O, 1.8V (DV
USB_V
DD1P8
DDA_1P1V
DD33
DD18
, MXVDD, M24VDD)
, USB_V
, USB_DV
, DV
DDR2
DDA_3P3
, DDR_V
DDA1P2LDO
(3)
)
DDDLL
(3)
(2)
, CV
, PLLV
DD18
DDDSP
, V
(3)
)
DDA_1P8V
,-0.5 V to 2.5 V
VII/O, 3.3V-0.5 V to 4.2 V
VII/O, 1.8V-0.5 V to 2.5 V
VOI/O, 3.3V-0.5 V to 4.2 V
VOI/O, 1.8V-0.5 V to 2.5 V
(default)0°C to 85°C
DDR_ZPDDR2 impedance control, connected via 200 Ω resistor to V
DDR_ZNDDR2 impedance control, connected via 200 Ω resistor to DV
(1)
,
)3.153.33.45V
DDDLL
,
SSDLL
SSA1P2LDO
, PLLV
,
DD18
,000V
SS
DDR2
DAC_VREFDAC reference voltage input0.4750.50.525V
DAC_RBIASDAC biasing, connected via 4 kΩ resistor to V
SSA_1P8V
USB_VBUSUSB external charge pump input4.7555.25V
V
IH
V
IL
T
C
F
SYSCLK1
(1) This pin is an internal LDO output and connected via 1 µF capacitor to USB_V
(2) Future variants of TI SOC devices may operate at voltages ranging from 0.9 V to 1.4 V to provide a range of system power/performance
options. TI highly recommends that users design-in a supply that can handle multiple voltages within this range (i.e., 1.0 V, 1.05 V,
1.1 V, 1.14 V, 1.2, 1.26 V with ±3% tolerances) by implementing simple board changes such as reference resistor values or input pin
configuration modifications. Not incorporating a flexible supply may limit the system's ability to easily adapt to future versions of TI SOC
devices.
(3) Oscillator ground must be kept separate from other grounds and connected directly to the crystal load capacitor ground.
(4) DDR_VREF is expected to equal 0.5DV
of the transmitting device and to track variations in the DV
(1) For test conditions shown as MIN, MAX, or NOM, use the appropriate value specified in Section 5.2, Recommended Operating
Conditions.
(2) IIapplies to input-only pins and bi-directional pins. For input-only pins, IIindicates the input leakage current. For bi-directional pins, I
indicates the input leakage current and off-state (Hi-Z) output leakage current.
(3) Applies only to pins with an internal pullup (IPU) or pulldown (IPD) resistor.
(4) IOZapplies to output-only pins, indicating off-state (Hi-Z) output leakage current.
(5) This pin is an internal LDO output and connected via 1 µF capacitor to USB_V
(6) Measured under the following conditions: 60% DSP CPU utilization; ARM doing typical activity (peripheral configurations, other
housekeeping activities); DDR2 Memory Controller at 50% utilization (135 MHz), 50% writes, 32 bits, 50% bit switching; 2 MHz ASP at
100% utilization; Timer0 at 100% utilization. At room temperature (25°C) for typical process devices. The actual current draw varies
across manufacturing processes and is highly application-dependent. For more details on core and I/O activity, as well as information
relevant to board power supply design, see the TMS320DM6441 Power Consumption Summary application report (literature number
NOTE: The data manual provides timing at the device pin. For output timing analysis, the tester pin electronics and its transmission line effects
must be taken into account. A transmission line with a delay of 2 ns or longer 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 or longer) from the
data manual timings.
42 Ω3.5 nH
Device Pin
(see note)
Input requirements in this data manual are tested with an input slew rate of < 4 Volts per nanosecond (4 V/ns) at the device pin.
V
ref
V
ref
= VIL MAX (or VOL MAX)
V
ref
= VIH MIN (or VOH MIN)
TMS320DM6441
www.ti.com
6Peripheral and Electrical Specifications
6.1Parameter Information
6.1.1Parameter Information Device-Specific Information
SPRS359E–SEPTEMBER 2006–REVISED AUGUST 2010
Figure 6-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.
6.1.1.1Signal Transition Levels
All input and output timing parameters are referenced to V
V
= 1.5 V. For 1.8 V I/O, V
ref
Figure 6-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 6-3. Rise and Fall Transition Time Voltage Reference Levels
6.1.1.2Timing Parameters and Board Routing Analysis
The timing parameter values specified in this data manual 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 the DDR2 memory controller interface, it is not necessary to use the IBIS models to analyze timing
characteristics. TI provides a PCB routing rules solution that describes the routing rules to ensure the
DDR2 memory controller interface timings are met. See the Implementing DDR2 PCB Layout on theTMS320DM644x DSP Application Report (literature number SPRAAC5).
6.2Recommended Clock and Control Signal Transition Behavior
All clocks and control signals should transition between VIHand VIL(or between VILand VIH) in a
monotonic manner.
6.3Power Supplies
For more information regarding TI's power management products and suggested devices to power TI
DSPs, visit www.ti.com/dsppower.
www.ti.com
6.3.1Power-Supply Sequencing
The DM6441 includes two core supplies — CVDDand CV
DV
The core supply power-up sequence is dependent on the DSP boot mode selected at reset. If the DSP
boot mode is configured as self-boot mode, then both core supplies must be powered up at the same
time.
If the DSP boot mode is configured as host-boot, where the ARM boots the DSP, the two core supplies
may be ramped simultaneously or powered up separately. When powered up separately, the CV
supply must not be ramped prior to the CVDDsupply. The CV
shorting switch is closed (enabled). Prior to powering up the CV
not driven to ground. Table 6-1 and Figure 6-4 describe the power-on sequence timing requirements for
DSP host-boot mode.
To minimize the voltage difference between these two core supplies, a single regulator source must be
used to power the CVDDand CV
For more information, see Section 3.2.1, Power Configurations at Reset.
DDR2
, and DV
. To ensure proper device operation, a specific power-up sequence must be followed.
Once the CVDDsupply has been powered up, the I/O supplies may be powered up. Table 6-2 and
Figure 6-5 show the power-on sequence timing requirements for the Core vs. I/O power-up. DV
DDXX
used to denote all I/O supplies.
NOTE
The DV
CV
DDDSP
supply power-up is specified relative to the CVDDsupply power-up, not the
DDXX
supply.
ns
is
Table 6-2. I/O Supply Power-On Timing Requirements (see Figure 6-5)
1.05 V and
NO.UNIT
1t
d(CVDD-DVDD)
Delay time, CVDDsupply ready to DV
supply ramp start0100ms
DDXX
1.2 V
MINMAX
Figure 6-5. I/O Supply Timings
There is not a specific power-up sequence that must be followed with respect to the order of the power-up
of the DV
specification is met, the DV
preference. All other supplies may also be powered up in any order of preference once the t
DD18
, DV
DDR2
, and DV
DD18
supplies. Once the CVDDsupply is powered up and the t
Core and I/O supply voltage regulators should be located close to the DSP (or DSP array) to minimize
inductance and resistance in the power delivery path. Additionally, when designing for high-performance
applications utilizing the DM6441 device, the PC board should include separate power planes for core,
I/O, and ground, all bypassed with high-quality low-ESL/ESR capacitors.
6.3.1.2Power-Supply Decoupling
In order to properly decouple the supply planes from system noise, place as many capacitors (caps) as
possible close to DM6441. Assuming 0603 caps, the user should be able to fit a total of 60 caps, 30 for
the core supplies and 30 for the I/O supplies. These caps need to be close to the DM6441 power pins, no
more than 1.25 cm maximum distance to be effective. Physically smaller caps, such as 0402, are better
because of their lower parasitic inductance. Proper capacitance values are also important. Small bypass
caps (near 560 pF) should be closest to the power pins. Medium bypass caps (220 nF or as large as can
be obtained in a small package) should be next closest. TI recommends no less than eight small and
eight medium caps per supply be placed immediately next to the BGA vias, using the "interior" BGA space
and at least the corners of the "exterior".
Larger caps for each supply can be placed further away for bulk decoupling. Large bulk caps (on the order
of 100 mF) should be furthest away, but still as close as possible. Large caps for each supply should be
placed outside of the BGA footprint.
Any cap selection needs to be evaluated from a yield/manufacturing point-of-view. As with the selection of
any component, verification of capacitor availability over the product’s production lifetime should be
considered.
www.ti.com
6.3.1.3DM6441 Power and Clock Domains
DM6441 includes two separate power domains: "Always On" and "DSP". The "Always On" power domain
is always on when the chip is on. The "Always On" domain is powered by the VDDpins of the DM6441.
The majority of the DM6441's modules lie within the "Always On" power domain. A separate domain called
the "DSP" domain houses the C64x+ and VICP. The "DSP" domain is not always on. The "DSP" power
domain is powered by the CV
pins of the DM6441. Table 6-3 provides a listing of the DM6441 power
DDDSP
and clock domains.
Two primary reference clocks are required for the DM6441 device. These can either be crystal input or
driven by external oscillators. A 27-MHz crystal is recommended for the system PLLs, which generate the
internal clocks for the ARM, DSP, coprocessors, peripherals (including imaging peripherals), and EDMA3.
The recommended 27-MHz input enables the use of the video DACs to drive NTSC/PAL television signals
at the proper frequencies. A 24-MHz crystal is also required if the USB peripheral is to be used. For
further description of the DM6441 clock domains, see Table 6-4 (DM6441 Clock Domains) and Figure 6-6
(PLL1 and PLL2 Clock Domain Block Diagram).
The power and sleep controller (PSC) controls DM6441 device power by turning off unused power
domains or gating off clocks to individual peripherals/modules. The PSC consists of a global PSC (GPSC)
and a set of Local PSCs (LPSCs). The GPSC contains memory mapped registers, power domain control,
PSC interrupt control, and a state machine for each peripheral/module. An LPSC is associated with each
peripheral/module and provides clock and reset control. The GPSC controls all of DM6441’s LPSCs. The
ARM subsystem does not have an LPSC module. ARM sleep mode is accomplished through the wait for
interrupt instruction. The LPSCs for DM6441 are shown in Table 6-5. The PSC Register memory map is
given in Table 6-6. For more details on the PSC, see Section 2.8.3, Documentation Support, for the
TMS320DM644x DMSoC ARM Subsystem Reference Guide (literature number SPRUE14).