•Six ALUs (32-/40-Bit), Each Supports
Single 32-Bit, Dual 16-Bit, or Quad 8-Bit
Arithmetic per Clock Cycle
•Two Multipliers Support Four 16 x 16-Bit
Multiplies (32-Bit Results) per Clock
Cycle or Eight 8 x 8-Bit Multiplies (16-Bit• ARM9 Memory Architecture
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)
– 80K-Byte L1D Data RAM/Cache (2-Way
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
– EmbeddedICE-RT™ Logic for Real-Time
Debug
– 16K-Byte Instruction Cache
– 8K-Byte Data Cache
– 16K-Byte RAM
– 8K-Byte ROM
• Emulation Trace Buffer™ (ETB11™) With 4-KB
Memory for ARM9 Debug
• Endianness: Little Endian for ARM and DSP
• Video Processing Subsystem
– Resize Engine Provides:
•Resize Images From 1/4x to 4x
•Separate Horizontal and Vertical Control
– Back End Provides:
•Hardware On-Screen Display (OSD)
•4 - 54 MHz DACs for a Combination of
– Composite NTSC/PAL Video
– Luma/Chroma Separate Video
(S-video)
– Component (YPbPr or RGB) Video
(Progressive)
•Digital Output
– 8-/16-Bit YUV or up to 24-Bit RGB
– HD Resolution
– Up to 2 Video Windows
1
Please be aware that an important notice concerning availability, standard warranty, and use in critical applications of Texas
Instruments semiconductor products and disclaimers thereto appears at the end of this data sheet.
2All trademarks are the property of their respective owners.
PRODUCTION DATA information is current as of publication date.
Products conform to specifications per the terms of the Texas
Instruments standard warranty. Production processing does not
necessarily include testingof all parameters.
The TMS320DM6443 (also referenced as DM6443) leverages TI’s DaVinci™ technology to meet the
networked media encode and decode application processing needs of next-generation embedded devices.
The DM6443 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 DM6443 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.
SPRS282G–DECEMBER 2005–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 4752 million instructions per second (MIPS) at a clock rate of 594 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 2376 million
MACs per second (MMACS), or eight 8-bit MACs per cycle for a total of 4752 MMACS. For more details
on the C64x+ DSP, see the TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide
(literature number SPRU732).
The DM6443 also has application-specific hardware logic, on-chip memory, and additional on-chip
peripherals similar to the other C6000 DSP platform devices. The DM6443 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: 1 configurable video port; 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); 2 64-bit general-purpose timers each configurable as 2 independent 32-bit timers;
1 64-bit watchdog timer; up to 71-pins of general-purpose input/output (GPIO) with programmable
interrupt/event generation modes, multiplexed with other peripherals; 3 UARTs with hardware
handshaking support on 1 UART; 3 pulse width modulator (PWM) peripherals; and 2 external memory
interfaces: an asynchronous external memory interface (EMIFA) for slower memories/peripherals, and a
higher speed synchronous memory interface for DDR2.
The DM6443 includes a Video Processing Sub-System (VPSS) that has a configurable Resizer and Video
Processing Back-End (VPBE) output used for display.
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) is comprised of an On-Screen Display Engine (OSD) and a
Video Encoder (VENC). The OSD engine is capable of handling 2 separate video windows and 2 separate
OSD windows. Other configurations include 2 video windows, 1 OSD window, and 1 attribute window
allowing up to 8 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.
The Ethernet Media Access Controller (EMAC) provides an efficient interface between the DM644x and
the network. The DM6443 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.
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.
www.ti.com
The HPI, I2C, SPI, USB2.0, and VLYNQ ports allow DM6443 to easily control peripheral devices and/or
communicate with host processors. The DM6443 also provides multimedia card support, MMC/SD, with
SDIO support.
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 DM6443 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 SPRS282F device-specific
data manual to make it an SPRS282G revision.
Scope: Added information/data on silicon revision 2.3.
Applicable updates to the DM64x device family, specifically relating to the TMS320DM6443 device, have
been incorporated.
SPRS282G–DECEMBER 2005–REVISED AUGUST 2010
Revision History
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
Section 6.13.2.3Table 6-52, Timing Requirements for VPBE CLK Inputs:
VPBE Electrical
Data/Timing
•Removed "VPFE Electrical Data/Timing" section
•Removed Parameter 1 [t
•Removed Parameter 2 [t
•Removed Parameter 3 [t
•Removed Parameter 4 [t
], Cycle time, PCLK
c(PCLK)
], Pulse duration, PCLK high
w(PCLKH)
], Pulse duration, PCLK low
w(PCLKL)
], Transition time, PCLK
t(PCLK)
Figure 6-46, VPBECLK Timing:
•Updated/changed figure title from "VPBE PCLK and VPBECLK Timing" to "VPBECLK Timing"
•Removed PCLK waveform
Table 6-53, Timing Requirements for VPBE Control Input With Respect to VPBECLK:
•Updated/changed table title from "Timing Requirements for VPBE Control Input With Respect to
PCLK and VPBECLK" to "Timing Requirements for VPBE Control Input With Respect to VPBECLK"
•Removed Parameter 9 [t
•Removed Parameter 10 [t
su(VCTLV-PCLK)
h(PCLK-VCTLV)
•Renumbered Parameter 27 as Parameter 9 [t
VPBECLK rising edge
•Renumbered Parameter 28 as Parameter 10 [t
VPBECLK rising edge
•Removed Parameter 33 [t
•Removed Parameter 34 [t
su(FIELD-PCLK)
h(PCLK-FIELD)
•Renumbered Parameter 35 as Parameter 33 [t
VPBECLK edge
•Renumbered Parameter 36 as Parameter 34 [t
VPBECLK edge
], Setup time, VCTL valid before PCLK edge
], Hold time, VCTL valid after PCLK edge
su(VCTLV-VPBECLK)
h(VPBECLK-VCTLV)
], Setup time, LCD_FIELD valid before PCLK edge
], Hold time, LCD_FIELD valid after PCLK edge
su(FIELD-VPBECLK)
h(VPBECLK-FIELD)
•Removed "PCLK may be configured ..." footnote
•Updated/changed "P = 1/(VCLKIN clock frequency) in ns ..." footnote
SPRS282G–DECEMBER 2005–REVISED AUGUST 2010
], Setup time, VCTL valid before
], Hold time, VCTL valid after
], Setup time, LCD_FIELD valid before
], Hold time, LCD_FIELD valid after
Figure 6-47, VPBE Input Timing With Respect to VPBECLK:
•Updated/changed figure title from "VPBE Input Timing With Respect to PCLK and VPBECLK" to
"VPBE Input Timing With Respect to VPBECLK"
•Removed VPBECLK waveform
•Renamed PCLK (Positive Edge Clocking) waveform as VPBECLK waveform
•Removed PCLK (Negative Edge Clocking) waveform
•Removed Parameters 27, 28, 35, and 36
Table 6-54, Switching Characteristics Over Recommended Operating Conditions for VPBE Control and
Data Output With Respect to VPBECLK:
•Updated/changed table title from "Switching Characteristics Over Recommended Operating
Conditions for VPBE Control and Data Output With Respect to PCLK and VPBECLK" to "Switching
Characteristics Over Recommended Operating Conditions for VPBE Control and Data Output With
Respect to VPBECLK"
Table 2-1 provides an overview of the TMS320DM6443 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 FEATURESDM6443
DDR2 Memory ControllerDDR2 (16/32-bit bus width)
Asynchronous EMIF (EMIFA)
Flash CardsMMC/SD with secure data input/output (SDIO)
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 IDControl Status Register (CSR.[31:16])0x1000
C64x+ MegamoduleRevision ID Register (MM_REVID[15:0])0x0000 (Silicon Revision 1.3 and earlier)
UART3 (one with RTS and CTS flow control)
SPI1 (supports 2 slave devices)
I2C1 (Master/Slave)
Audio Serial Port [ASP]1
10/100 Ethernet MAC with Management Data
Table 2-1. Characteristics of the Processor (continued)
HARDWARE FEATURESDM6443
Voltage
PLL Optionsx1 (Bypass), x22 (-594)
BGA Package357-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 Texas
Instruments standard warranty. Production processing does not necessarily include testing of all parameters.
(1)
Core (V)1.2 V (-594)
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
or Production Data (PD)
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.
www.ti.com
The ARM Subsystem includes the following features:
•ARM926EJ-S RISC processor
•ARMv5TEJ (32/16-bit) instruction set
•Little endian
•Co-Processor 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)
SPRS282G–DECEMBER 2005–REVISED AUGUST 2010
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®,
Windows® CE, 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.
www.ti.com
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 16KB 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 16-KB 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.
The ARM926EJ-S has built in DMA support for direct accesses to the ARM internal memory from a nonARM device. Furthermore, 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.
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 DM6443 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 DM6443 trace port is not pinned out and is instead only connected to the Embedded Trace Buffer.
The ETB has a 4KB 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 8KB 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
2.3.8.2External Memories
The ARM has access to the following external memories:
The ARM9 has access to all of the peripherals on the DM6443 device.
2.3.10 PLL Controller (PLLC)
The ARM Subsystem includes the PLL Controller. The PLL Controller contains a set of registers for
configuring DM6443’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
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 DMSoCARM Subsystem Reference Guide (literature number SPRUE14).
www.ti.com
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).
2.3.14 Power Management
DM6443 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).
DM6443 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.
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
The C64x+ Central Processing Unit (CPU) consists of eight functional units, two register files, and two
data paths as shown in Figure 2-1. The two general-purpose register files (A and B) each contain
32 32-bit registers for a total of 64 registers. The general-purpose registers can be used for data or can be
data address pointers. The data types supported include packed 8-bit data, packed 16-bit data, 32-bit
data, 40-bit data, and 64-bit data. Values larger than 32 bits, such as 40-bit-long or 64-bit-long values are
stored in register pairs, with the 32 LSBs of data placed in an even register and the remaining 8 or
32 MSBs in the next upper register (which is always an odd-numbered register).
The eight functional units (.M1, .L1, .D1, .S1, .M2, .L2, .D2, and .S2) are each capable of executing one
instruction every clock cycle. The .M functional units perform all multiply operations. The .S and .L units
perform a general set of arithmetic, logical, and branch functions. The .D units primarily load data from
memory to the register file and store results from the register file into memory.
SPRS282G–DECEMBER 2005–REVISED AUGUST 2010
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 for 16-bit inputs
and produces a 32-bit real and a 32-bit imaginary output. There are also complex multiplies with rounding
capability that produces one 32-bit packed output that contain 16-bit real and 16-bit imaginary values. The
32 x 32 bit multiply instructions provide the extended precision necessary for audio and other
high-precision algorithms on a variety of signed and unsigned 32-bit data types.
The .L or (Arithmetic Logic Unit) now incorporates the ability to do parallel add/subtract operations on a
pair of common inputs. Versions of this instruction exist to work on 32-bit data or on pairs of 16-bit data
performing dual 16-bit add and subtracts in parallel. There are also saturated forms of these instructions.
The C64x+ core enhances the .S unit in several ways. In the C64x core, dual 16-bit MIN2 and MAX2
comparisons were only available on the .L units. On the C64x+ core they are also available on the .S unit
which increases the performance of algorithms that do searching and sorting. Finally, to increase data
packing and unpacking throughput, the .S unit allows sustained high performance for the quad 8-bit/16-bit
and dual 16-bit instructions. Unpack instructions prepare 8-bit data for parallel 16-bit operations. Pack
instructions return parallel results to output precision including saturation support.
•SPLOOP - A small instruction buffer in the CPU that aids in creation of software pipelining loops where
multiple iterations of a loop are executed in parallel. The SPLOOP buffer reduces the code size
associated with software pipelining. Furthermore, loops in the SPLOOP buffer are fully interruptible.
•Compact Instructions - The native instruction size for the C6000 devices is 32 bits. Many common
instructions such as MPY, AND, OR, ADD, and SUB can be expressed as 16 bits if the C64x+
compiler can restrict the code to use certain registers in the register file. This compression is
performed by the code generation tools.
•Instruction Set Enhancement - As noted above, there are new instructions such as 32-bit
multiplications, complex multiplications, packing, sorting, bit manipulation, and 32-bit Galois field
multiplication.
•Exceptions Handling - Intended to aid the programmer in isolating bugs. The C64x+ CPU is able to
detect and respond to exceptions, both from internally detected sources (such as illegal op-codes) and
from system events (such as a watchdog time expiration).
•Privilege - Defines user and supervisor modes of operation, allowing the operating system to give a
basic level of protection to sensitive resources. Local memory is divided into multiple pages, each with
read, write, and execute permissions.
•Time-Stamp Counter - Primarily targeted for Real-Time Operating System (RTOS) robustness, a
free-running time-stamp counter is implemented in the CPU which is not sensitive to system stalls.
For more details on the C64x+ CPU and its enhancements over the C64x architecture, see the following
documents:
•TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide (literature number SPRU732)
•TMS320C64x 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.
TMS320DM6443
www.ti.com
SPRS282G–DECEMBER 2005–REVISED AUGUST 2010
Figure 2-1. TMS320C64x+™ CPU (DSP Core) Data Paths
The DSP memory map is shown in Section 2.5, Memory Map Summary. 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
www.ti.com
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
2.4.3Peripherals
The DSP has controllability for the following peripherals:
•EDMA3
•ASP
•2 Timers (Timer0 and Timer1) that can each be configured as 1 64-bit or 2 32-bit timers
2.4.4DSP Interrupt Controller
The DSP Interrupt Controller accepts device interrupts and appropriately maps them to the DSP’s
available interrupts. The DSP Interrupt Controller is briefly described in this document in Section 6.7,
Interrupts. For more detailed on the DSP Interrupt Controller, see the TMS320C64x/C64x+ DSP CPU and
Instruction Set Reference 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.
0x2000 00000x2000 7FFF32KDDR2 Control RegistersDDR2 Control RegistersDDR2 Control RegistersDDR2 Control Registers
0x2000 80000x41FF FFFF 544M-32k ReservedReservedReserved
(1) HPI's access to the configuration bus peripherals is limited to the power and sleep controller registers, PLL1 and PLL2 registers, and
HPI configuration registers.
(2) 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-29) 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, and multiplexed/shared pins, see Section 3,
Device Configurations, of this data manual.
Table 2-5. BOOT Terminal Functions
SIGNAL
NAMENO.
COUT0/
B3/A16I/O/Z
BTSEL0
COUT1/
B4/B16I/O/Z
BTSEL1
COUT2/bus width (EM_WIDTH). For an 8-bit-wide EMIFA data
B5/A17I/O/Zbus, EM_WIDTH = 0. For a 16-bit-wide EMIFA data bus,
EM_WIDTHEM_WIDTH = 1.
COUT3/source DSP_BT. The DSP is booted by the ARM when
B6/B17I/O/ZDSP_BT=0. The DSP boots from EMIFA when
DSP_BTDSP_BT=1.
YOUT0/
G5/D15I/O/Z
AEAW0
YOUT1/VPBE. At reset, the input states of AEAW[4:0] are
G6/D16I/O/Zsampled to set the EMIFA address bus width. See
AEAW1Section 3.4.2, Peripheral Selection at Device Reset, for
YOUT2/After reset, these are video encoder outputs YOUT[0:4]
G7/D17I/O/Zor RGB666/888 Red and Green data bit outputs G5, G6,
AEAW2G7, R3, and R4.
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
TYPE
(1)
OTHER
(2) (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 determine the ARM boot
IPDconfiguration. See below for the boot modes set by these
DV
DD18
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
ARM ROM Boot (NAND, SPI)
[default]
DV
IPD
DD18
00
01ARM EMIFA Boot (NOR)
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
IPD
DV
DD18
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
IPD
DV
DD18
After reset, it is video encoder output COUT3 or
RGB666/888 Blue data bit 6 output B6.
(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
(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.
(3)
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.
(3)
1.8-V power supply for PLLs (system).
www.ti.com
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.25, 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).
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): TMS320DM6443
DESCRIPTION
TMS320DM6443
SPRS282G–DECEMBER 2005–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 bi-directional 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
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 Peripheral 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 input 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
Table 2-16. Standalone GPIOV18 Terminal Functions
SIGNAL
NAMENO.
GPIO7C3I/O/ZDV
GPIO1E13I/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
This pin is standalone and functions as GPIO7.
This pin is standalone and functions as GPIO1.
Submit Documentation Feedback
Product Folder Link(s): TMS320DM6443
TMS320DM6443
SPRS282G–DECEMBER 2005–REVISED AUGUST 2010
www.ti.com
Table 2-17. USB Terminal Functions
SIGNAL
NAMENO.
M24XIF18IDV
M24XOF19ODV
M24V
M24V
DD
SS
F16S
F17GND
USB_VBUSJ17A I/O
USB_IDJ16A I/O
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.
(3)
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.
(3)
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.
(3)
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
(3)
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
(3)
USB_R1.
When the USB peripheral is not used, the USB_V
to VSS.
Analog 3.3 V power supply for USB phy.
(3)
(3)
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.
(3)
When the USB peripheral is not used, the USB_V
to DV
DD18
.
I/O Ground for USB phy.
(3)
When the USB peripheral is not used, the USB_V
to VSS.
Submit Documentation Feedback
Product Folder Link(s): TMS320DM6443
SSREF
DESCRIPTION
.
signal should be connected
SSREF
signal should be
DDA3P3
signal should be connected
DD1P8
signal should be connected
SS1P8
TMS320DM6443
www.ti.com
SPRS282G–DECEMBER 2005–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.
HSYNCC17I/O/ZVPBE Horizontal Sync signal that can be either an input or an output.
VSYNCC18I/O/ZVPBE Vertical Sync signal that can be either an input or an output.
VCLKD19I/O/ZDV
VPBECLKC19I/O/ZVPBE Clock Input
COUT0/This pins 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 pins 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
EM_WIDTHoutput data 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
DSP_BTbit 6 output B6.
COUT4/
B7
COUT5/Video encoder output COUT5 or RGB666/888 Green data bit 2 output
G2G2.
COUT6/Video encoder output COUT6 or RGB666/888 Green data bit 3 output
G3G3.
COUT7/Video encoder output COUT7 or RGB666/888 Green data bit 4 output
G4G4.
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
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
VIDEO OUT (VPBE)
IPD
DV
DD18
IPD
DV
DD18
DD18
VPBE Clock Output
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
DD18
DD18
DD18
DD18
Video encoder output COUT4 or RGB666/888 Blue data bit 7 output B7.
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
IPD
DV
DD18
DD18
DD18
DD18
DD18
DD18
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.
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
GPIO3/This pin is multiplexed between GPIO, and the VPBE.
B0/C14I/O/ZDV
LCD_FIELDinterlaced bidirectional LCD_FIELD.
GPIO4/This pin is multiplexed between GPIO and the VPBE.
R0In VPBE mode, it is RGB888 Red data bit 0 output R0.
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.
B14I/O/ZDV
E14I/O/ZDV
A14I/O/ZDV
D14I/O/ZDV
PWM1/
R2/B15I/O/ZDV
GPIO46
PWM2/
B2/A15I/O/ZDV
GPIO47
TYPE
(1)
OTHER
DD18
DD18
DD18
DD18
DD18
DD18
DD18
(2) (3)
DESCRIPTION
In VPBE mode, it is RGB888 Blue data bit 0 output B0 or LCD
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-20. 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.20-V analog core supply voltage (-594 device). When the DAC is not used, the
V
DDA_1P1V
signal should be 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/IPDThis pin is multiplexed between ATA/CF and UART1.
UART_RXD1DV
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/Z
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)
OTHER
IPD
DV
IPD
DV
IPD
DV
IPD
DV
DD18
DD18
DD18
DD18
DD18
DD18
DD18
DD18
(2) (3)
UART2
UART1
For UART1, it is receive data input UART_RXD1.
UART0
DESCRIPTION
www.ti.com
Table 2-22. PWM0, PWM1, PWM2 Terminal Functions
SIGNAL
NAMENO.
PWM2/
B2/A15I/O/ZDV
GPIO47
PWM1/
R2/B15I/O/ZDV
GPIO46
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.
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.
(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.
(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
MMC/SD/SDIO
Data clock output SD_CLK
Bi-directional command IO SD_CMD
These pins are the nibble-wide bi-directional data bus SD_DATA[3:0].
DV
DD33
DD33
DD33
Table 2-25. HPI Terminal Functions
SIGNAL
NAMENO.
EM_CS3B1I/O/ZDV
EM_BA[0]/
DA0/J3I/O/ZDV
HINT
EM_A[0]/This pin is multiplexed between EMIFA, ATA/CF, HPI, and GPIO.
DA2/For HPI, it is control input HCNTL1. The state of HCNTL1 and HCNTL0 determine
HCNTL1/if address, data, or control information is being transmitted between an external
J4I/O/ZDV
GPIO53host and DM644X.
EM_A[2]/
(CLE)/J1I/O/ZDV
HCNTL0
EM_A[1]/
(ALE)/J2I/O/ZDV
HHWIL
EM_R/W/This pin is multiplexed between EMIFA, ATA/CF, and HPI.
INTRQ/G3I/O/ZDV
HR/Wand low for writes.
EM_CS2/This pin is multiplexed between EMIFA and HPI.
HCSIn HPI mode, this pin is HPI Active Low Chip Select input HCS.
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)/IPUThis pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
IORDY/DV
F1I/O/Z
HRDY
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
Host-Port Interface (HPI)
DD18
DD18
DD18
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.
In HPI mode, it is the host interrupt output HINT.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), and HPI.
DD18
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 DM644X.
DD18
DD18
DD18
DD18
DD18
DD18
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), and HPI.
In HPI mode, it is Half-word identification input HHWIL.
For HPI, it is the Host Read Write input HR/W. This signal is active high for reads
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
For HPI, it is data strobe 2 input HDS2.
This pin is multiplexed between EMIFA (NAND/SmartMedia/xD), ATA/CF, and HPI.
For HPI, it is data strobe 1 input HDS1.
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) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal
(3) Specifies the operating I/O supply voltage for each signal
These pins are multiplexed between EMIFA (NAND), ATA/CF, and HPI.
In HPI mode, these are HD[15:0] and are multiplexed internally with the HPI
address lines.
No external pins. The Timer 2 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
Timer 2 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-27. 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)
RSV9M19IV
RSV10L19I/O/ZReserved. (Leave unconnected, do not connect to power or ground)
RSV11M18I/O/ZReserved. (Leave unconnected, do not connect to power or ground)
RSV12N15IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV13M17IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV14M16IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV15M15IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV16L18IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV17L17IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV18L16IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV19L15IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV20K19IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV21K18IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV22K17IIPDReserved. (Leave unconnected, do not connect to power or ground)
RSV23K16IIPDReserved. (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
TYPE
(1)
OTHER
IPD
V
SS
SS
(2) (3)
DESCRIPTION
RESERVED
Reserved. This pin must be tied directly to VSSfor normal device operation.
TI offers an extensive line of development tools for the TMS320DM644x 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 TMS320DM644x 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 TMS320DM644x 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.
www.ti.com
2.8.2Device and Development-Support Tool Nomenclature
To designate the stages in the product development cycle, TI assigns prefixes to the part numbers of all
DSP devices and support tools. Each DSP commercial family member has one of three prefixes: TMX,
TMP, or TMS (e.g., TMX320DM6443ZWT). 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.
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, commercial temperature
Blank = 594-MHz DSP, 297-MHz ARM9 [Default]
A. BGA = Ball Grid Array
B. For actual device part numbers (P/Ns) and ordering information, see the TI website (http://www.ti.com).
( )
SILICON REVISION
Blank = Silicon 1.3
A = Silicon 2.1
B = Silicon 2.3
TMS320DM6443
www.ti.com
Predictions show that prototype devices (TMX or TMP) have a greater failure rate than the standard
production devices. Texas Instruments recommends that these devices not be used in any production
system because their expected end-use failure rate still is undefined. Only qualified production devices are
to be used.
TI device nomenclature also includes a suffix with the device family name. This suffix indicates the
package type (for example, ZWT), the temperature range (for example, "Blank" is the commercial
temperature range), and the device speed range in megahertz (for example, "Blank" is the default
[594-MHz DSP, 297-MHz ARM9]).
Figure 2-6 provides a legend for reading the complete device name for any TMS320DM644x SoC platform
2.8.3.1Related Documentation From Texas Instruments
The following documents describe the TMS320DM644x Digital Media System-on-Chip (DMSoC). Copies
of these documents are available on the Internet at http://www.ti.com. Tip: Enter the literature number in
the search box provided at http://www.ti.com.
The current documentation that describes the DM644x DMSoC, related peripherals, and other technical
collateral, is available in the C6000 DSP product folder at: http://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
SPRS282G–DECEMBER 2005–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. For details, see Section 3.5.4, PINMUX0 Register
0x01C4 0004PINMUX1Pin multiplexing control 1. For details, see Section 3.5.5, PINMUX1 Register
0x01C4 0008DSPBOOTADDRBoot address of DSP. For details, see Section 3.3.1.2, DSPBOOTADDR
0x01C4 000CSUSPSRCEmulator Suspend Source. For details, see Section 3.6, Emulation Control.
0x01C4 0010INTGENARM/DSP Interrupt Status and Control. For details, see Section 6.7.3,
0x01C4 0014BOOTCFGDevice boot configuration. For details, see Section 3.3.1.1, BOOTCFG
0x01C4 0018 - 0x01C4 0027–Reserved.
0x01C4 0028JTAGIDJTAGID/Device ID number. For details, see Section 6.25.1, JTAG Peripheral
0x01C4 002C–Reserved.
0x01C4 0030HPI_CTLHPI control. For details, see Section 3.5.6.10, HPI and EMIFA/ATA Pin
0x01C4 0034USBPHY_CTLUSB PHY control. For details, see Section 6.15.1, USBPHY_CTL Register
0x01C4 0038CHP_SHRTSWChip shorting switch control. For details, see Section 3.2.1, Power
0x01C4 003CMSTPRI0Bus master priority control 0. For details, see Section 3.5.1, Switched Central
0x01C4 0040MSTPRI1Bus master priority control 1. For details, see Section 3.5.1, Switched Central
0x01C4 0044VPSS_CLKCTLVPSS clock control.
0x01C4 0048VDD3P3V_PWDNVDD 3.3V I/O powerdown control. For details, see Section 3.2.2, Power
0x01C4 004CDRRVTPEREnables access to the DDR2 VTP Register.
Global device power domains are controlled by the Power and Sleep Controller, except as shown in the
following sections.
3.2.1Power Configurations at Reset
As described in Section 6.3.1.3, DM6443 Power and Clock Domains, the DM6443 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 '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.
Note: Once the DSP power domain is enabled (powered up), it cannot be disabled (powered down).
Dynamic power down of the DSP is not supported on this device.
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
www.ti.com
Table 3-2. CHP_SHRTSW Register Description
NAMEDESCRIPTION
DSPPWRONDSP power domain enable.
0 = Shorting switch open
1 = Shorting switch closed
3.2.2Power Configurations after Reset
The VDD3P3V_PWDN register controls power to the 3.3V I/O buffers for MMC/SD/SDIO 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.
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 Description
NAMEDESCRIPTION
BTSELARM Boot mode selection pin states (BTSEL1, BTSEL0) captured at the rising edge of RESET.
‘00’ indicates ARM boots from ROM (NAND Flash/SPI Flash).
‘01’ indicates that ARM boots from EMIFA (NOR Flash).
‘10’ indicates that ARM boots from ROM (HPI).
‘11’ indicates that ARM boots from ROM (UART0).
DSP_BTDSP Boot mode selection pin state captured at the rising edge of RESET.
‘0’ sets ARM boot of C64x+.
‘1’ sets C64x+ self boot.
EM_WIDTHEMIFA data bus width selection pin state captured at the rising edge of RESET.
‘0’ sets EMIFA to 8 bit data bus width
‘1’ sets EMIFA to 16 bit data bus width.
DAEAWEMIFA 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 Description
NAMEDESCRIPTION
BOOTADDR[21:0]Upper 22 bits of the C64x+ DSP boot address.
3.3.2ARM Boot
The DM6443 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
www.ti.com
BTSEL1 BTSEL0BOOT 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 to load a secondary UBL via HPI to
AIM and transfers control to the user software.
•Support for up to 14KB UBL.
For further details on the ROM Bootloader, see the TMS320DM644x DMSoC ARM Subsystem ReferenceGuide (literature number SPRUE14).
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
3.3.3.1Host-Boot Mode
BOOT MODEBOOT MODEREGISTER VALUE
0Host BootInternal BootProgrammableARM sets an internal DSP memory location in DSPBOOTADDR
register where valid DSP code resides and loads code to this
internal DSP memory through DMA prior to releasing DSP reset.
0Host BootExternal BootProgrammableARM sets an external DSP memory location in DSPBOOTADDR
register (EMIFA or DDR2) where valid DSP code resides prior to
releasing DSP reset.
1Self BootAny, except HPI0x4220 0000Default EMIFA Base Address
1Host BootHPIProgrammableARM sets a DSP memory location in the DSPBOOTADDR
register. HPI loads code into the DM6443 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.
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.
www.ti.com
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 DM6443 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. DM6443 Default Bus Master Priorities
BUS
PRIORITY BIT FIELDMASTERDEFAULT PRIORITY LEVEL
VPSSPVPSS0 (VPSS PCR Register, DMA_PRI bit field)
[For more detailed information on the DMA_PRI bit field, see the
TMS320DM644x DMSoC 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
TMS320DM644x DMSoC 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
TMS320DM644x DMSoC Enhanced Direct Memory Access
(EDMA3) Controller User's Guide (literature number SPRUE23).]
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, PeripheralSelection After Device 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. DM6443 Multiplexed Peripheral Pins and Multiplexing Controls
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 (PinMultiplexing 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, 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 DM6443 device operation, always write a value of '0' to RSV bits 30, 27, and 26.
(1)
Table 3-14. PINMUX0 Register Description
NameDescription
EMACENEnable EMAC and MDIO function on default GPIO3V[0:16] pins.
HPIENEnable HPI module pins. Default value is derived from BTSEL[1:0] configuration inputs. HPIEN is 1 when the
LFLDENEnable LCD_FIELD function on default GPIO[3] pin
LOEENEnable LCD_OE function on default GPIO[0] pin
RGB888Enable VPBE RGB888 function on default GPIO[2:6, 46:47] pins
RGB666Enable VPBE RGB666 function on default GPIO[46:47] pins
ATAENEnable ATA function on default EMIFA and GPIO[52:53] pins and shared UART1 pins
HDIRENEnable HDDIR function on default GPIO[42] pin
VLYNQENEnable VLYNQ function on default GPIO[9,10:17] pins
VLSCRENEnable VLYNQ SCRUN function on default GPIO[9] pin
VLYNQWDVLYNQ data width selection. This expands the VLYNQ TXD[0:3] and RXD[0:3] functions on default GPIO[10:17]
AECS5Enable EMIFA EM_CS5 function on GPIO[8]
AECS4Enable EMIFA EM_CS4 function on GPIO[9]
AEAWEMIFA address width selection. Default value is latched at reset from AEAW[4:0] configuration input pins. This
BTSEL[1:0] = 10 and HPIEN is 0 (the default state) when BTSEL[1:0] is 00, 01, or 11.
pins.
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
(1) For proper DM6443 device operation, always write a value of '0' to RSV bit 9.
(2) Following device power up or reset to enable the UART2 and UART2 flow control, a value of '1' must be written to the UART2 and
U2FLO bits (bits 2 and 3, respectively).
Table 3-15. PINMUX1 Register Description
NameDescription
TIMINEnable TIM_IN function on default GPIO[49] pin
CLK1Enable CLK_OUT1 function on default GPIO[49] pin
CLK0Enable CLK_OUT0 function on default GPIO[48] pin
ASPEnable ASP function on default GPIO[29:34] pins
SPIEnable SPI function on default GPIO[37,39:42] pins
I2CEnable I2C function on default GPIO[43:44] pins
PWM2Enable PWM2 function on default GPIO[47] pin
PWM1Enable PWM1 function on default GPIO[46] pin
PWM0Enable PWM0 function on default GPIO[45] pin
U2FLOEnable UART2 flow control function on default disabled
UART2Enable UART2 function on default disabled
UART1Enable UART1 function on shared ATA (CF) DMACK, DMARQ pins
UART0Enable 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
The LCD controller in the VPSS requires multiplex control bit settings for certain modes of operation. Bits
within the PinMux0 register, which select between the LCD control signal function and GPIO, are
summarized in Table 3-18.
Table 3-18. VPBE (LCD) and GPIO Pin Multiplexing
PINMUX0
REGISTER FIELDS
LFLDENLOEENLCD_FIELD/B0/GPIO[3]LCD_OE/GPIO[0]
-0-GPIO[0]
-1-LCD_OE
0-B0/GPIO[3]
1-LCD_FIELD-
(1) Depends on RGB888 bit setting, see Table 3-19.
(1)
MULTIPLEXED PINS
-
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, and LCD functionality overrides the 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, and LFLDEN must be set to ‘0’.
SPRS282G–DECEMBER 2005–REVISED AUGUST 2010
Table 3-19. VPBE (RGB666, RGB888, and LCD), and GPIO Pin Multiplexing
PINMUX0 AND PINMUX1 REGISTER BIT FIELDSMULTIPLEXED PINS
RGB888 RGB666PWM2PWM1LFLDEN B2/R2/B0/
00000GPIO[47]GPIO[46]GPIO[3]
----1--LCD_FIELD
---1--PWM1-
--1--PWM2-01000B2R2GPIO[3]
1-000B2R2B0
PWM2/PWM1/LCD_FIELD/
GPIO[47]GPIO[46]GPIO[3]
Table 3-20. VPBE (RGB666, RGB888, and LCD) 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 DM644X 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.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.
Table 3-29 shows the PWM0/1/2 pin multiplexing. Each PWM output is independently controlled by its
own enable bit. The PWM function has priority over RGB888 muxing [see Section 3.5.6.3, VPBE (RGB666and RGB888) and GPIO Pin Multiplexing ].
Table 3-29. PWM0/1/2, RGB888, and GPIO Pin Multiplexing
PINMUX1 REGISTER BIT FIELDSMULTIPLEXED PINS
PWM2PWM1PWM0RGB888B2/R2/GPIO[45]
0000GPIO[47]GPIO[46]GPIO[45]
0001B2R2GPIO[45]
--1---PWM0
-1---PWM1-
1---PWM2--
3.5.6.9UART, ATA, and GPIO Pin Multiplexing
Each UART has independent pin multiplexing control bits in the PINMUX1 register.
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-30. If the ATA module is
not enabled, the pins are always configured for use by UART1.
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-32 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'.
(1) This pin shares GPIO functionality and is set by AEAW[4:0] as shown in Table 3-12, Table 3-13, and Table 3-14.
HR/W/HRDY/HDS1/HDS2/HCNTLB/HINT/HD[15:0]/
INTRQ/EM_WAIT/DIOR/DIOW/ATA2/ATA0/DD[15:0]/
EM_R/WIORDYEM_OEEM_WEEM_A[0]EM_BA[0]EM_D[15:0]
(1)
EM_R/WEM_WAITEM_OEEM_WEEM_A[2]
(1)
INTRQIORDYDIORDIOWEM_A[2]
(1)
(1)
EM_A[0]
EM_A[0]
(1)
EM_BA[0]EM_D[15:0]
(1)
ATA0DD[15:0]
3.6Emulation Control
The flexibility of the DM644x 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-33. 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 DM6443 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 DM6443 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
, USB_V
DDA1P1V
, USB_V
DD33
, DV
DD18
, MXVDD, M24VDD)
DDR2
DDA3P3
, DDR_V
DDA1P2LDO
(3)
)
DDDLL
(3)
(2)
, CV
, PLLV
DDDSP
DD18
)
, V
DDA1P8V
(3)
,-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
(1) This pin is an internal LDO output and connected via 1 mF 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 mF 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 TMS320DM6446/3 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)
TMS320DM6443
www.ti.com
6Peripheral and Electrical Specifications
6.1Parameter Information
6.1.1Parameter Information Device-Specific Information
SPRS282G–DECEMBER 2005–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 DM6443 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.
supplies. Once the CVDDsupply is powered up and the t
DD33
, DV
Product Folder Link(s): TMS320DM6443
, and DV
DDR2
Submit Documentation Feedback
supplies may be powered up in any order of
DD33
d(CVDD-DVDDXX)
d(CVDD-DVDDXX)
TMS320DM6443
SPRS282G–DECEMBER 2005–REVISED AUGUST 2010
6.3.1.1Power-Supply Design Considerations
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 DM6443 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 DM6443. 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 DM6443 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 8 small and
8 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.3DM6443 Power and Clock Domains
DM6443 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 DM6443.
The majority of the DM6443's modules lie within the "Always On" power domain. A separate domain called
the "DSP" domain houses the C64x+. The "DSP" domain is not always on. The "DSP" power domain is
powered by the CV
pins of the DM6443. Table 6-3 provides a listing of the DM6443 power and clock
DDDSP
domains.
Two primary reference clocks are required for the DM6443 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 DM6443 clock domains, see Table 6-4 (DM6443 Clock Domains) and Figure 6-6
(PLL1 and PLL2 Clock Domain Block Diagram).
The Power and Sleep Controller (PSC) controls DM6443 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 DM6443’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 DM6443 are shown in Table 6-5. The PSC register memory map is
given in Table 6-6. For more details on the PSC, see the TMS320DM644x DMSoC ARM SubsystemReference Guide (literature number SPRUE14).
DM6443 supports various types of resets. Power-on-reset (POR), warm reset, max reset, system reset,
C64x+ local reset, and module reset are summarized in Table 6-7.
Table 6-7. DM6443 Resets
TypeInitiatorDescription
Power-on-reset (POR)RESET pin active low while TRST is low.Global chip reset (Cold reset). Activates the POR signal
Warm resetRESET pin active low while TRST is high.Resets everything except for test and emulation logic.
Maximum resetEmulator, WD TimerSame as Warm reset, except for initiators.
C64x+ Local resetSoftware (register bit)MMR controls the C64x+ reset input. This is used for
Power-on-reset (POR) is the global chip reset and it affects test, emulation, and other circuitry. It is
invoked by driving the RESET pin active low while TRST is held low. A POR is required to place DM6443
into a known good initial state. POR can be asserted prior to ramping the core and I/O voltages or after
the core and I/O voltages have reached their proper operating conditions. As a best practice, RESET
should be asserted (held low) during power-up. Prior to deasserting RESET (low-to-high transition), the
core and I/O voltages should be at their proper operating conditions and if an external 27 MHz oscillator is
used on the MXI/CLKIN pin, the external clock should also be running at the correct frequency.
on chip, which is used to reset test and emulation logic.
ARM emulator stays alive during warm reset, but the
C64x+ emulator does not.
control of C64x+ reset by the ARM. The C64x+ Slave
DMA port is still alive when in local reset.
Warm reset is activated by driving the RESET pin active low, while TRST is inactive high. This does not
reset test or ARM emulation logic. An ARM emulator session will stay alive during warm reset, but a
C64x+ emulator session will not.
Maximum reset is initiated by the emulator or the watchdog timer and the reset effects are the same as a
warm reset. The emulator initiates a maximum reset via the ICEPICK module. When the watchdog timer
counter reaches zero, this will initiate a maximum reset to recover from a runaway condition. Both of the
maximum reset initiators can be masked by the ARM emulator.
System reset is initiated by the emulator and is a soft reset. Memory contents are maintained. Test,
emulation, clock, and power control logic are unaffected. The emulator initiates a system reset via the
C64x+ emulation logic, or through ICECRUSHER. Both of these reset initiators are non-maskable resets.
The C64x+ DSP has an internal reset input that allows a host to control it. This reset is configured through
a MMR bit (MDCTL[39].LRSTz) in the PSC module. When in C64x+ local reset, the slave DMA port on
C64x+ will remain active and the internal memory will be accessible.
For details on reset control/status registers, see the TMS320DM644x DMSoC ARM Subsystem ReferenceGuide (literature number SPRUE14)
For information on peripheral selection at the rising edge of RESET, see Section 3, Device Configurations,
of this data manual.
Table 6-8. Timing Requirements for Reset (see Figure 6-9)
NO.UNIT
1t
2t
3t
w(RST)
su(BOOT)
h(BOOT)
Width of the RESET pulse444ns
Setup time, boot configuration bits valid before RESET high444ns
Hold time, boot configuration bits valid after RESET high444ns
Table 6-9. Switching Characteristics Over Recommended Operating Conditions During Reset
(see Figure 6-9)
NO.UNIT
26t
d(PLL_LOCK)
4t
d(RSTL-DDRZZ)
5t
d(RSTL-DDRLL)
6t
d(RSTL-DDRHH)
16t
d(RSTL-DDRZHZ)
17t
d(RSTL-DDRLHL)
7t
d(RSTL-ZZ)
8t
d(RSTL-LOWL)
9t
d(RSTL-HIGHH)
18t
d(RSTL-HIGHLOWH)
19t
d(RSTL-LOWHIGHL)
24t
d(RSTL-ZIZ)
10t
d(RSTH-DDRZV)
11t
d(RSTH-DDRLV)
12t
d(RSTH-DDRHV)
20t
d(RSTH-DDRZHV)
21t
d(RSTH-DDRLHV)
13t
d(RSTH-ZV)
14t
d(RSTH-LOWV)
15t
d(RSTH-HIGHV)
22t
d(RSTH-HIGHLOWV)
23t
d(RSTH-LOWHIGHV)
25t
d(RSTH-ZIIV)
(1) P = MXI/CLKIN cycle time, in ns.
(2) Following RESET high, this signal group maintains the state the pins(s) achieved while RESET was driven low until the peripheral is
enabled via the PSC. For example, the DDR2 Z Group goes high impedance following RESET low and remains in the high-impedance
state following RESET high until the DDR2 controller is enabled via the PSC.
Delay time, PLL1 lock time2000Pns
Delay time, RESET low to DDR2 Z Group high impedance02P + 20ns
Delay time, RESET low to DDR2 Low Group low020ns
Delay time, RESET low to DDR2 High Group high020ns
Delay time, RESET low to DDR2 Z/High Group high impedance05P + 20ns
Delay time, RESET low to DDR2 Low/High Group low020ns
Delay time, RESET low to Z Group high impedance020ns
Delay time, RESET low to Low Group low020ns
Delay time, RESET low to High Group high020ns
Delay time, RESET low to High/Low Group high020ns
Delay time, RESET low to Low/High Group low020ns
Delay time, RESET low to Z/Invalid Group high impedance020ns
Delay time, RESET high to DDR2 Z Group valid
Delay time, RESET high to DDR2 Low Group valid
Delay time, RESET high to DDR2 High Group valid
Delay time, RESET high to DDR2 Z/High Group valid high4000Pns
Delay time, RESET high to DDR2 Low/High Group valid high4000Pns
Delay time, RESET high to Z Group valid
Delay time, RESET high to Low Group valid
Delay time, RESET high to High Group valid
Delay time, RESET high to High/Low Group valid low5100Pns
Delay time, RESET high to Low/High Group valid high5100Pns
Delay time, RESET high to Z/Invalid Group invalid4000Pns