available
– 3.3-V and 1.8-V I/O, 1.35-V Core
– 338-Pin Ball Grid Array at 65nm Process
Technology
• High-Performance Digital Media
System-on-Chip (DMSoC)
– 432-MHz ARM926EJ-S Clock Rate
– 4:2:2 (8-/16-Bit) Interface
– Capable of 1080p 30fps H.264 video
processing
– Pin compatible with DM365 processors
– Fully Software-Compatible With ARM9™
– Extended temperature available for 432-Mhz
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.
Developers can now deliver crystal clear multi-format video at up to 1080p H.264 at 30fps (encode and
closed-looped decode) in their digital video designs without concerns of video format support, constrained
network bandwidth, limited system storage capacity or cost with the new TMS320DM368 DaVinci™ video
processors from Texas Instruments Incorporated (TI).
The DM368 is capable of achieving HD video processing at 1080p 30fps H.264 and is completely
pin-to-pin compatible with the DM365 processors, using the same ARM926EJ-S core running at 432 MHz.
This ARM9-based DM368 device supports production-qualified H.264BP/MP/HP, MPEG-4, MPEG-2,
MJPEG and VC1/WMV9 codecs providing customers with the flexibility to select the right video codec for
their application. These codecs run on independent coprocessors (HDVICP and MJCP) offloading all
compression needs from the main ARM core. This allows developers to obtain optimal performance from
the ARM for their applications, including their multi-channel, multi-stream and multi-format needs.
Video surveillance designers achieve greater compression efficiency to provide more storage without
straining the network bandwidth. Developers of media playback and camera-driven applications, such as
video doorbells, digital signage, digital video recorders, portable media players and more can take
advantage of the low power consumption and can ensure interoperability, as well as product scalability by
taking advantage of the full suite of codecs supported on the DM368.
Along with multi-format HD video, the DM368 also features a suite of peripherals saving developers on
system cost and complexity to enable a seamless interface to most additional external devices required
for video applications. The image sensor interface is flexible enough to support CCD, CMOS, and various
other interfaces such as BT.656, BT1120. The DM368 also offers a high level of integration with HD
display support, including three built-in 10-bit HD analog video digital-to-analog converters (DACs),
DDR2/mDDR, Ethernet MAC, USB 2.0, integrated audio, host port interface (HPI), analog-to digital
converter and many more features saving developers on overall system costs, as well as real estate on
their circuit boards allowing for a slimmer, sleeker design.
available at the same time (For
more detail, see the Device
Configuration section).
On-Chip CPU MemoryOrganization16-KB I-cache, 8-KB D-cache, 32-KB RAM,
JTAG BSDL_IDJTAGID register (address location: 0x01C4 0028)
CPU Frequency (Maximum)MHzARM: 432-MHz
Voltage
PLL Options
BGA Package13 x 13 mm338-Pin BGA (ZCE)
Process Technology65 nm
SPIFive (each supports two slave devices)
I2COne (Master/Slave)
10/100 Ethernet MAC with Management Data I/OOne
Multi-Channel Buffered Serial Port [McBSP]One McBSP
Power Management and Real Time Clock Subsystem
(PRTCSS)
Key Scan4 x 4 Matrix, 5 x 3 Matrix
Voice CodecOne
Analog-to-Digital Converter (ADC)6-channel, 10-bit Interface
General-Purpose Input/Output PortUp to 104
Pulse width modulator (PWM)Four outputs
Configurable Video Ports
USB 2.0High Speed Host
Wireless InterfacesThrough SDIO
RTOFour Channels
Core (V)1.35 V
I/O (V)3.3 V, 1.8 V
Reference frequency options19.2 MHz, 24 MHz, 27 MHz, 36 MHz
Table 2-1. Characteristics of the Processor (continued)
HARDWARE FEATURESDEVICE
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)
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.
2.3ARM Subsystem Overview
The ARM Subsystem contains components required to provide the ARM926EJ-S (ARM) master control of
the overall device system, including the components of the ARM Subsystem, the peripherals, and the
external memories.
The ARM is responsible for handling system functions such as system-level initialization, configuration,
user interface, user command execution, connectivity functions, interface and control of the subsystem,
etc. The ARM is master and performs these functions because it has a large program memory space and
fast context switching capability, and is thus suitable for complex, multi-tasking, and general-purpose
control tasks.
2.3.1Components of the ARM Subsystem
www.ti.com
The ARM Subsystem consists of the following components:
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)
For more complete details on the ARM9, refer to the ARM926EJ-S Technical Reference Manual, available
at http://www.arm.com
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.4MMU
The ARM926EJ-S MMU provides virtual memory features required by operating systems such as Linux,
WindowCE, ultron, ThreadX, etc. A single set of two level page tables stored in main memory is used to
control the address translation, permission checks and memory region attributes for both data and
instruction accesses. The MMU uses a single unified Translation Lookaside Buffer (TLB) to cache the
information held in the page tables. The MMU features are:
•Standard ARM architecture v4 and v5 MMU mapping sizes, domains and access protection scheme.
•Access permissions for large pages and small pages can be specified separately for each quarter of
the page (subpage permissions)
•Hardware page table walks
•Invalidate entire TLB, using CP15 register 8
•Invalidate TLB entry, selected by MVA, using CP15 register 8
•Lockdown of TLB entries, using CP15 register 10
www.ti.com
2.3.5Caches and Write Buffer
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.
2.3.6Tightly 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 boot modes include NAND, MMC/SD, UART, USB, SPI, EMAC, and HPI.
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., EDMA 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 0x10000 through 0x17FFF. 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 32-KB RAM is split into two physical banks of 16KB
each, which allows simultaneous instruction and data accesses to be accomplished if the code and data
are in separate banks.
2.3.7Advanced High-performance Bus (AHB)
The ARM Subsystem uses the AHB port of the ARM926EJ-S to connect the ARM to the configuration bus
and the external memories. Arbiters are employed to arbitrate access to the separate D-AHB and I-AHB
by the configuration bus and the external memories bus.
2.3.8Embedded 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 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 device 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.9ARM Memory Mapping
The ARM memory map is shown in Table 2-3 and Table 2-4. This section describes the memories and
interfaces within the ARM's memory map.
2.3.9.1ARM Internal Memories
The ARM has access to the following ARM internal memories:
•32KB ARM Internal RAM on TCM interface, logically separated into two 16KB 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.
•16KB ARM Internal ROM
2.3.9.2External Memories
The ARM has access to the following External memories:
The ARM has access to all of the peripherals on the device.
2.3.11 ARM Interrupt Controller (AINTC)
The device ARM Interrupt Controller (AINTC) has the following features:
•Supports up to 64 interrupt channels (16 external channels)
•Interrupt mask for each channel
•Each interrupt channel can be mapped to a Fast Interrupt Request (FIQ) or to an Interrupt Request
(IRQ) type of interrupt.
•Hardware prioritization of simultaneous interrupts
•Configurable interrupt priority (2 levels of FIQ and 6 levels of IRQ)
•Configurable interrupt entry table (FIQ and IRQ priority table entry) to reduce interrupt processing time
The ARM core supports two interrupt types: FIQ and IRQ. See the ARM926EJ-S Technical Reference
Manual for detailed information about the ARM’s FIQ and IRQ interrupts. Each interrupt channel is
mappable to an FIQ or to an IRQ type of interrupt, and each channel can be enabled or disabled. The
INTC supports user-configurable interrupt-priority and interrupt entry addresses. Entry addresses minimize
the time spent jumping to interrupt service routines (ISRs). When an interrupt occurs, the corresponding
highest priority ISR’s address is stored in the INTC’s ENTRY register. The IRQ or FIQ interrupt routine can
read the ENTRY register and jump to the corresponding ISR directly. Thus, the ARM does not require a
software dispatcher to determine the asserted interrupt.
www.ti.com
2.4System Control Module
The system control module is a system-level module containing status and top-level control logic required
by the device. The system control module consists of a miscellaneous set of status and control registers,
accessible by the ARM and supporting all of the following system features and operations:
•Device identification
•Device configuration
– Pin multiplexing control
– Device boot configuration status
•ARM interrupt and EDMA event multiplexing control
•Special peripheral status and control
– Timer64
– USB PHY control
– VPSS clock and video DAC control and status
– DDR VTP control
– Clockout circuitry
– GIO de-bounce control
•Power management
– Deep sleep
•Bandwidth Management
– Bus master DMA priority control
For more information on the System Control Module refer to Section 3, Device Configurations and the
TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number SPRUFG5).
The device is designed for minimal power consumption. There are two components to power
consumption: active power and leakage power. Active power is the power consumed to perform work and
scales with clock frequency and the amount of computations being performed. Active power can be
reduced by controlling the clocks in such a way as to either operate at a clock setting just high enough to
complete the required operation in the required time-line or to run at a clock setting until the work is
complete and then drastically cut the clocks (e.g. to PLL Bypass mode) until additional work must be
performed. Leakage power is due to static current leakage and occurs regardless of the clock rate.
Leakage, or standby power, is unavoidable while power is applied and scales roughly with the operating
junction temperatures. Leakage power can only be avoided by removing power completely from a device
or subsystem. The device includes several power management modes which are briefly described in
Table 2-2. See the TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number
SPRUFG5) for more information on power management.
Table 2-2. Power Management Conditions
POWER MGMT.OTHERDDR
APPLICATIONPRTCSSPERIPH.CLOCK/DESCRIPTION
SCENARIOCLOCKSMODE
PRTCSSActiveOffOffOffOffOffOffOffOff
Deep Sleep Mode
StandbyActiveOnOnOffOnOffOff"Self-device. Clocks are
Low-powerBypasstimers. Since ARM will
(PLL Bypass Mode)Modenot have access to
Table 2-3 shows the memory map address ranges of the device. Table 2-4 depicts the expanded map of
the Configuration Space (0x01C0 0000 through 0x01FF FFFF). The device has multiple on-chip memories
associated with its processor 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. The bus masters are the ARM, EDMA, EMAC, USB, HPI, MJCP, HDVICP and VPSS. The
Master Peripherals are EMAC, USB, and HPI. Please refer to Section 4 for more details.
EMAC Control Registers0x01D0 70000x01D0 9FFF0x01D0 7FFF4K
EMAC Control Module RAM0x01D0 80008K
EMAC Control Module Registers0x01D0 A0000x01D0 AFFF4K
EMAC MDIO Control Registers0x01D0 B0000x01D0 B7FF2K
Voice Codec0x01D0 C0000x01D0 C3FF1K
Reserved0x01D0 C4000x01D0 FFFF17K
ASYNC EMIF Control0x01D1 00000x01D1 0FFF4K
Multimedia / SD 00x01D1 10000x01D1 FFFF60K
Reserved0x01D2 00000x01D3 FFFF128K
Reserved0x01D4 00000x01DF FFFF768K
Reserved0x01E0 00000x01FF FFFF2M
ASYNC EMIF Data (CE0)0x0200 00000x03FF FFFF32M
ASYNC EMIF Data (CE1)0x0400 00000x05FF FFFF32M
Reserved0x0600 00000x09FF FFFF64M
Reserved0x0A00 00000x0FFF FFFF96M
www.ti.com
2.7Pin Assignments
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.
2.7.1Pin Map (Bottom View)
Figure 2-2 through Figure 2-5 show the pin assignments in four quadrants (A, B, C, and D). Note that
Table 2-5 provides a complete pin description list which shows external signal names, the associated pin
(ball) numbers along with the mechanical package designator, the pin type, whether the pin has any
internal pullup or pulldown resistors, and a functional pin description. For more detailed information on
device configuration, peripheral selection, multiplexed/shared pins, and debugging considerations, see
Section 3.
Table 2-5. Pin Descriptions
NameBGATypeGroupPowerIPUResetDescription
ID
(5)
CIN7
CIN6
CIN5
CIN4
CIN3
CIN2
(5)
(5)
(5)
(5)
(5)
A15I/OISIFV
C15I/OISIFV
B16I/OISIFV
A16I/OISIFV
A17I/OISIFV
C16I/OISIFV
(1)
(2)
Supply
DD_ISIF18_33
(3)
IPD
State
IPDInputStandard ISIF Analog Front End (AFE): raw[7]
YCC 16-bit: time multiplexed between chroma:
CB/CR[07]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the upper channel. Y/CB/CR[07]
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[6]
YCC 16-bit: time multiplexed between chroma:
CB/CR[06]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the upper channel. Y/CB/CR[06]
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[5]
YCC 16-bit: time multiplexed between chroma:
CB/CR[05]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the upper channel. Y/CB/CR[05]
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[4]
YCC 16-bit: time multiplexed between chroma:
CB/CR[04]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the upper channel. Y/CB/CR[04]
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[3]
YCC 16-bit: time multiplexed between chroma:
CB/CR[03]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the upper channel. Y/CB/CR[03]
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[2]
YCC 16-bit: time multiplexed between chroma:
CB/CR[02]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the upper channel. Y/CB/CR[02]
(4)
(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. See Section 6.3 , Power Supplies for more detail.
(3) PD = pull-down, PU = pull-up. (To pull up a signal to the opposite supply rail, a 1 kΩ resistor should be used.)
(4) To reduce EMI and reflections, depending on the trace length, approximately 22 Ω to 50 Ω damping resistors are recommend on the
following outputs placed near the device: YOUT(0-7),COUT(0-7), HSYNC,VSYNC,LCD_OE,FIELD, and,VCLK. The trace lengths should
be minimized.
(5) The Y input (YIN[7:0]) and C input (CIN[7:0]) buses can be swapped by programming the field bit YCINSWP in the VPFE CCD
Configuration (CCDCFG) register (0x01C7 0136h).
IF YCINSWP bit is 0 (default) YIN[7:0] = Y signal / CIN[7:0] = C signal .
IF YCINSWP bit is 1 YIN[7:0] = C signal / CIN[7:0] = Y signal
For more information, see the TMS320DM36x Video Processing Front End (VPFE) Reference Guide (literature number SPRUFG8).
IPDInputStandard ISIF Analog Front End (AFE): raw[1]
YCC 16-bit: time multiplexed between chroma:
CB/CR[01]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the upper channel. Y/CB/CR[01]
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[0]
YCC 16-bit: time multiplexed between chroma:
CB/CR[00]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the upper channel. Y/CB/CR[00]
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[15]
SPI3
YCC 16-bit: time multiplexed between luma: Y[07]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the lower channel. Y/CB/CR[07]
GIO: GIO[103]
SPI3: Clock
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[14]
SPI3
YCC 16-bit: time multiplexed between luma: Y[06]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the lower channel. Y/CB/CR[06]
GIO: GIO[102]
SPI3: Slave Input Master Output Data Signal
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[13]
SPI3
YCC 16-bit: time multiplexed between luma: Y[05]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the lower channel. Y/CB/CR[05]
GIO: GIO[101]
SPI3: Chip Select 0
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[12]
YCC 16-bit: time multiplexed between luma: Y[04]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the lower channel. Y/CB/CR[04]
GIO: GIO[100]
SPI3: Slave Output Master Input Data Signal
SPI3: Chip Select 1
www.ti.com
(4)
(6) The Y input (YIN[7:0]) and C input (CIN[7:0]) buses can be swapped by programming the field bit YCINSWP in the VPFE CCD
Configuration (CCDCFG) register (0x01C7 0136h).
IF YCINSWP bit is 0 (default) YIN[7:0] = Y signal / CIN[7:0] = C signal .
IF YCINSWP bit is 1 YIN[7:0] = C signal / CIN[7:0] = Y signal
For more information, see the TMS320DM36x Video Processing Front End (VPFE) Reference Guide (literature number SPRUFG8).
IPDInputStandard ISIF Analog Front End (AFE): raw[11]
YCC 16-bit: time multiplexed between luma: Y[03]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the lower channel. Y/CB/CR[03]
GIO: GIO[99]
(6)
YIN2
/ GIO98B15I/OISIF /V
GIO
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[10]
YCC 16-bit: time multiplexed between luma: Y[02]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the lower channel. Y/CB/CR[02]
GIO: GIO[98]
(6)
YIN1
/ GIO97D14I/OISIF /V
GIO
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[09]
YCC 16-bit: time multiplexed between luma: Y[01]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the lower channel. Y/CB/CR[01]
GIO: GIO[97]
(7)
YIN0
/ GIO96D15I/OISIF /V
GIO
DD_ISIF18_33
IPDInputStandard ISIF Analog Front End (AFE): raw[08]
YCC 16-bit: time multiplexed between luma: Y[00]
YCC 08-bit (which allows for 2 simultaneous decoder
inputs), it is time multiplexed between luma and
chroma of the lower channel. Y/CB/CR[00]
GIO: GIO[96]
HD / GIO95C14I/OISIF /V
GIOan input (slave mode) or an output (master mode).
DD_ISIF18_33
IPDInputHorizontal synchronization signal that can be either
Tells the ISIF when a new line starts.
GIO: GIO[95]
VD / GIO94B14I/OISIF /V
GIOinput (slave mode) or an output (master mode). Tells
DD_ISIF18_33
IPDInputVertical synchronization signal that can be either an
the ISIF when a new frame starts.
GIO: GIO[94]
C_WE_FIELD /E13I/OISIF /V
GIO93 / CLKOUT0GIO /(AFE/TG) to gate the DDR output of the ISIF module.
DD_ISIF18_33
IPDInputWrite enable input signal is used by external device
/ USBDRVVBUSCLKOU
T / USB
Alternately, the field identification input signal is used
by external device (AFE/TG) to indicate the which of
two frames is input to the ISIF module for sensors
with interlaced output. ISIF handles 1- or 2-field
sensors in hardware.
GIO: GIO[93]
CLKOUT0: Clock Output
USB: Digital output to control external 5 V supply
PCLKD13I/O/Z ISIFV
DD_ISIF18_33
IPDInputPixel clock input (strobe for lines CI7 through YI0)
(4)
(7) The Y input (YIN[7:0]) and C input (CIN[7:0]) buses can be swapped by programming the field bit YCINSWP in the VPFE CCD
Configuration (CCDCFG) register (0x01C7 0136h).
IF YCINSWP bit is 0 (default) YIN[7:0] = Y signal / CIN[7:0] = C signal .
IF YCINSWP bit is 1 YIN[7:0] = C signal / CIN[7:0] = Y signal
For more information, see the TMS320DM36x Video Processing Front End (VPFE) Reference Guide (literature number SPRUFG8).
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
DDS33
InputDigital Video Out: VENC settings determine
function
(9)
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
DDS33
InputDigital Video Out: VENC settings determine
function
(9)
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
DDS33
InputDigital Video Out: VENC settings determine
function
(9)
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
DDS33
InputDigital Video Out: VENC settings determine
function
(9)
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
DDS33
InputDigital Video Out: VENC settings determine
function
(9)
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
DDS33
InputDigital Video Out: VENC settings determine
function
(11)
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
DDS33
InputDigital Video Out: VENC settings determine
function
(11)
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
GIO
DDS33
InputVideo Encoder: Horizontal Sync
GIO: GIO[84]
GIO
DDS33
InputVideo Encoder: Vertical Sync
GIO: GIO[83]
GIO
DDS33
Output Video Encoder: Data valid duration
GIO: GIO[82]
www.ti.com
(4)
(11)
(11)
(11)
(8) The Y output (YOUT[7:0]) and C output (COUT[7:0]) buses can be swapped by programming the field bit YCOUTSWP in the VPFE
CCD Configuration (CCDCFG) register (0x01C7 0136h). If the YCOUTSWP bit is 0 (default), YOUT[7:0] = Y signal / COUT[7:0] = C
signal . If the YCOUTSWP bit is 1, YOUT[7:0] = C signal / COUT[7:0] = Y signal. For more information, see the TMS320DM36x VideoProcessing Front End (VPFE) Reference Guide (literature number SPRUFG8).
(9) To reduce EMI and reflections, depending on the trace length, approximately 22 Ω to 50 Ω damping resistors are recommend on the
following outputs placed near the device: YOUT(0-7),COUT(0-7), HSYNC,VSYNC,LCD_OE,FIELD, and,VCLK. The trace lengths should
be minimized.
(10) The Y output (YOUT[7:0]) and C output (COUT[7:0]) buses can be swapped by programming the field bit YCOUTSWP in the VPFE
CCD Configuration (CCDCFG) register (0x01C7 0136h). If the YCOUTSWP bit is 0 (default), YOUT[7:0] = Y signal / COUT[7:0] = C
signal . If the YCOUTSWP bit is 1, YOUT[7:0] = C signal / COUT[7:0] = Y signal. For more information, see the TMS320DM36x VideoProcessing Front End (VPFE) Reference Guide (literature number SPRUFG8).
(11) To reduce EMI and reflections, depending on the trace length, approximately 22 Ω to 50 Ω damping resistors are recommend on the
following outputs placed near the device: YOUT(0-7),COUT(0-7), HSYNC,VSYNC,LCD_OE,FIELD, and,VCLK. The trace lengths should
be minimized.
Video Encoder: External clock Input, used if clock
rates > 27 MHz are needed, e.g. 74.25 MHz for
HDTV digital output.
Digital Video Out: B2
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM3: PWM3 Output
GIO
DDS33
InputVideo Encoder: Video Output Clock
GIO: GIO[79]
DDS33
InputGIO: GIO[92]
Digital Video Out: VENC settings determine
(11)
function
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM0: PWM0 Output
DDS33
InputGIO: GIO[91]
Digital Video Out: VENC settings determine
(11)
function
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM1: PWM1 Output
DDS33
InputGIO: GIO[90]
/ RTO0
Digital Video Out: VENC settings determine
(11)
function
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM2: PWM2 Output
RTO0: RTO0 Output
DDS33
InputGIO: GIO[89]
RTO1
Digital Video Out: VENC settings determine
(13)
function
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM2: PWM2 Output
RTO1: RTO1 Output
(11)
(4)
.
(11)
(12) The Y output (YOUT[7:0]) and C output (COUT[7:0]) buses can be swapped by programming the field bit YCOUTSWP in the VPFE
CCD Configuration (CCDCFG) register (0x01C7 0136h). If the YCOUTSWP bit is 0 (default), YOUT[7:0] = Y signal / COUT[7:0] = C
signal . If the YCOUTSWP bit is 1, YOUT[7:0] = C signal / COUT[7:0] = Y signal. For more information, see the TMS320DM36x VideoProcessing Front End (VPFE) Reference Guide (literature number SPRUFG8).
(13) To reduce EMI and reflections, depending on the trace length, approximately 22 Ω to 50 Ω damping resistors are recommend on the
following outputs placed near the device: YOUT(0-7),COUT(0-7), HSYNC,VSYNC,LCD_OE,FIELD, and,VCLK. The trace lengths should
be minimized.
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM2: PWM2 Output
RTO2: RTO2 Output
DDS33
InputGIO: GIO[87]
/ RTO3
Digital Video Out: VENC settings determine
(13)
function
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM2: PWM2 Output
RTO3: RTO3 Output
DDS33
InputGIO: GIO[86]
Digital Video Out: VENC settings determine
(13)
function
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM3: PWM3 Output
STTRIG: Camera FLASH control trigger signal
DDS33
InputGIO: GIO[85]
Digital Video Out: VENC settings determine
(15)
function
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
PWM3: PWM3 Output
DDS33
InputGIO: GIO[81]
Note: This pin will be used as oscillator configuration
(OSCCFG). The GIO81(OSCCFG) state is latched
during reset, and it specifies the oscillation frequency
range mode of the pin. See Section 3.7.6 for more
details.
Video Encoder: Field identifier for interlaced display
(15)
formats
.
For more details, see the DM36x DMSoC VideoProcessor Back End User's Guide (SPRUFG9).
Digital Video Out: R2
PWM3: PWM3 Output
www.ti.com
(4)
(15)
(14) The Y output (YOUT[7:0]) and C output (COUT[7:0]) buses can be swapped by programming the field bit YCOUTSWP in the VPFE
CCD Configuration (CCDCFG) register (0x01C7 0136h). If the YCOUTSWP bit is 0 (default), YOUT[7:0] = Y signal / COUT[7:0] = C
signal . If the YCOUTSWP bit is 1, YOUT[7:0] = C signal / COUT[7:0] = Y signal. For more information, see the TMS320DM36x VideoProcessing Front End (VPFE) Reference Guide (literature number SPRUFG8).
(15) To reduce EMI and reflections, depending on the trace length, approximately 22 Ω to 50 Ω damping resistors are recommend on the
following outputs placed near the device: YOUT(0-7),COUT(0-7), HSYNC,VSYNC,LCD_OE,FIELD, and,VCLK. The trace lengths should
be minimized.
DDR Data Clock
DDR Complementary Data Clock
DDR Row Address Strobe
DDR Column Address Strobe
DDR Write Enable
DDR Chip Select
DDR Clock Enable
Data mask input for DDR_DQ[15:8]
Data mask input for DDR_DQ[7:0]
Data strobe input/outputs for each byte of the 16-bit
data bus used to synchronize the data transfers.
Output to DDR2 when writing and inputs when
reading. They are used to synchronize the data
transfers.
DDR_DQS1: For DDR_DQ[15:8]
DD18_DDR
Data strobe input/outputs for each byte of the 16-bit
data bus used to synchronize the data transfers.
Output to DDR2 when writing and inputs when
reading. They are used to synchronize the data
transfers.
DDR_DQS0: For DDR_DQ[7:0]
DD18_DDR
DDR: Complimentary data strobe input/outputs for
each byte of the 16-bit data bus. They are outputs to
the DDR2 when writing and inputs when reading.
They are used to synchronize the data transfers.
Note: This signal is used in double ended differential
memory interfaces supported by the device.
DD18_DDR
DDR: Complimentary data strobe input/outputs for
each byte of the 16-bit data bus. They are outputs to
the DDR2 when writing and inputs when reading.
They are used to synchronize the data transfers.
Note: This signal is used in double ended differential
memory interfaces supported by the device.
Bank select outputs. Two are required for 1Gb DDR2
memories.
Bank select outputs. Two are required for 1Gb DDR2
memories.
Bank select outputs. Two are required for 1Gb DDR2
memories.
DDR Address Bus bit 13
DDR Address Bus bit 12
DDR Address Bus bit 11
DDR Address Bus bit 10
DDR Address Bus bit 09
DDR Address Bus bit 08
DDR Address Bus bit 07
DDR Address Bus bit 06
DDR Address Bus bit 05
DDR Address Bus bit 04
DDR Address Bus bit 03
DDR Address Bus bit 02
DDR Address Bus bit 01
DDR Address Bus bit 00
DDR Data Bus bit 15
DDR Data Bus bit 14
DDR Data Bus bit 13
DDR Data Bus bit 12
DDR Data Bus bit 11
DDR Data Bus bit 10
DDR Data Bus bit 09
DDR Data Bus bit 08
DDR Data Bus bit 07
DDR Data Bus bit 06
DDR Data Bus bit 05
DDR Data Bus bit 04
DDR Data Bus bit 03
DDR Data Bus bit 02
DDR Data Bus bit 01
DDR Data Bus bit 00
DDR: Loopback signal for external DQS gating.
same constraints as used for DDR clock and data.
DDR_T9IDDRV
DQGATE1Route to DDR and back to DDR_DQGATE0 with
DD18_DDR
DDR: Loopback signal for external DQS gating.
same constraints as used for DDR clock and data.
DDR_VREFP11PWR DDRV
DDR_PADREFPR11ODDRV
EM_A13 / GIO78 /V18I/O/Z AEMIF / V
BTSEL[2]GIO /
DD_AEMIF1_18_
BTSEL[d by
DD18_DDR
DD18_DDR
33
IPU/IPDInputAsync EMIF: Address Bus bit[13]
disable
DDR: DDR_VREF is .5* V
specific reference voltage.
DDR: External resistor ( 50 ohm to ground)
2]default
GIO: GIO[78]
BTSEL[2]: See Section 3.2, Device Boot Modes for
system usage of these pins.
EM_A12 / GIO77 /U18I/O/Z AEMIF / V
BTSEL[1]GIO /
BTSEL[d by
DD_AEMIF1_18_
33
IPU/IPDInputAsync EMIF: Address Bus bit[12]
disable
1]default
GIO: GIO[77]
BTSEL[1]: See Section 3.2, Device Boot Modes for
system usage of these pins.
EM_A11 / GIO76 /V19I/O/Z AEMIF / V
BTSEL[0]GIO /
BTSEL[d by
DD_AEMIF1_18_
33
IPU/IPDInputAsync EMIF: Address Bus bit[11]
disable
0]default
GIO: GIO[76]
BTSEL[0]: See Section 3.2, Device Boot Modes for
HPI: The state of HCNTLA and HCNTLB determines
if address, data, or control information is being
transmitted between an external host and the device.
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
Output Async EMIF: Address Bus bit[01]
HPI: This pin is half-word identification input HHWIL.
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
InputAsync EMIF: Address Bus bit[00] Note that the
EM_A0 is always a 32-bit address
KEYSC
DD_AEMIF2_18_
33
AN /
HPI
GIO: GIO[56]
Keyscan: B2
HPI: The state of HCNTLA and HCNTLB determines
if address, data, or control information is being
transmitted between an external host and the device.
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
DD_AEMIF1_18_
KEYSCIn 16-bit mode, lowest address bit.
33
InputAsync EMIF: Bank Address 1 signal = 16-bit
address.
AN /In 8-bit mode, second lowest address bit
HPI
GIO: GIO[66]
Keyscan: B1
HPI: This pin is host interrupt output HINT
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
InputAsync EMIF: Bank Address 0 signal = 8-bit address.
In 8-bit mode, lowest address bit.
KEYSC
DD_AEMIF1_18_
33
AN
Async EMIF: Address line (bit[14] when using 16-bit
memories.
GIO: GIO[65]
Keyscan: B0
InputAsync EMIF: Data Bus bit[15]
HPI
DD_AEMIF1_18_
33
GIO: GIO[64]
HPI: Data bus bit [15]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
InputAsync EMIF: Data Bus bit[13]
HPI
DD_AEMIF1_18_
33
GIO: GIO[62]
HPI: Data bus bit [13]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
InputAsync EMIF: Data Bus bit[12]
HPI
DD_AEMIF1_18_
33
GIO: GIO[61]
HPI: Data bus bit [12]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
InputAsync EMIF: Data Bus bit[11]
HPI
DD_AEMIF1_18_
33
GIO: GIO[60]
HPI: Data bus bit [11]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
InputAsync EMIF: Data Bus bit[10]
HPI
DD_AEMIF1_18_
33
GIO: GIO[59]
HPI: Data bus bit [10]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
InputAsync EMIF: Data Bus bit[09]
HPI
DD_AEMIF1_18_
33
GIO: GIO[58]
HPI: Data bus bit [9]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI: Data bus bit [8]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
InputAsync EMIF: Data Bus bit[07]
HPI: Data bus bit [7]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
InputAsync EMIF: Data Bus bit[06]
HPI: Data bus bit [6]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
InputAsync EMIF: Data Bus bit[05]
HPI: Data bus bit [5]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
InputAsync EMIF: Data Bus bit[04]
HPI: Data bus bit [4]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
InputAsync EMIF: Data Bus bit[03]
HPI: Data bus bit [3]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
InputAsync EMIF: Data Bus bit[02]
HPI: Data bus bit [2]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
InputAsync EMIF: Data Bus bit[01]
HPI: Data bus bit [1]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
HPI
DD_AEMIF2_18_
33
InputAsync EMIF: Data Bus bit[00]
HPI: Data bus bit [0]
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
Output Async EMIF: Lowest numbered Chip Select. Can be
programmed to be used for standard asynchronous
memory. Used for the default boot and ROM boot
modes.
GIO: GIO[56]
HPI: this pin is HPI chip select input.
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
DD_AEMIF2_18_
HPImemories (example: flash), OneNand or NAND
33
Output Async EMIF: Second Chip Select., Can be
programmed to be used for standard asynchronous
memory.
GIO: GIO[55]
HPI: This pin is host address strobe.
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
Output Async EMIF: Write Enable
HPI
DD_AEMIF2_18_
33
GIO: GIO[54]
HPI: This pin is host data strobe input 2.
Note: HPI is pin multiplexed with Asynchronous
EMIF at the output pin. HPI is available only when
boot mode selected is HPI boot mode. In this
configuration, the device will always act as a slave.
Output Async EMIF: Output Enable
HPI
DD_AEMIF2_18_
33
GIO: GIO[53]
HPI: This pin is host data strobe input 1.
IPUInputAsync EMIF: Async WAIT
HPI
DD_AEMIF2_18_
33
GIO: GIO[52]
HPI: This pin is host ready output from DSP to host.
Output Async EMIF: Address Valid Detect for OneNAND
interface
HPI
DD_AEMIF1_18_
33
GIO: GIO[51]
HPI: This pin is host read or write select input.
YNote: If the USB peripheral is not used at all in the
Supply
DDS33
DDA33_USB
(2)
IPD
(3)
State
IPDInputGIO: GIO[00]
USB D+ (differential signal pair)
application, this pin should be connected to 3.3V .
USB_DMP1A I/O USBPHV
YNote: If the USB peripheral is not used at all in the
DDA33_USB
USB D- (differential signal pair)
application, this pin should be connected to VSS.
V
DDA33_USB
P4PWR3.3-V USB analog power supply
Note: If the USB peripheral is not used at all in the
application, this pin should be connected to 3.3V.
V
SSA33_USB
P3GND3.3-V USB ground
Note: If the USB peripheral is not used at all in the
application, this pin should be connected to VSS.
V
DDA12LDO_USB
M5PWROutput For proper device operation, even if the USB
peripheral is not used, a 0.22µF capacitor must be
connected as close as possible to the package, and
the capacitor mst be connected to V
V
DDA18_USB
N5PWR1.8-V USB analog power supply
Note: If the USB peripheral is not used at all in the
application, this pin should be connected to 1.8V.
V
SSA18_USB
P2GND1.8-V USB ground
Note: If the USB peripheral is not used at all in the
application, this pin should be connected to VSS.
USB_IDM1A IUSBPHV
Y
DDA33_USB
USB operating mode identification pin.
For device mode operation only, pull up this pin to
VDDwith a 1.5K ohm resistor.
For host mode operation only, pull down this pin to
ground (VSS) with a 1.5K ohm resistor.
If using an OTG or mini-USB connector, this pin will
be set properly via the cable/connector configuration.
Note: If the USB peripheral is not used at all in the
application, this pin should be connected to 3.3V.
USB_VBUSN2A I/O USBPHUSB_VBUSThis pin is used by the USB Controller to detect a
Ypresence of 5V power (4.4V is the threshold) on the
USB_VBUS line for normal operation. This power is
sourced by the USB Component that is assuming the
role of a Host. In other words, the power on the
USB_VBUS line is not sourced by the Device. From
DM368 perspective, when operating as a Host, it
ensures that the external power supply that the
DM368 has sourced is within the required voltage
level (>= 4.4V) and when DM368 is operating as a
Device, the presence of a 5V power on the VBUS
Line is used to signify the presence of an external
Host.
Note 1: When the DM368 is operating as a Device, it
uses the power on the USB_VBUS line to power up
its internal pull-up resistor on the D+ line.
Note2: If the USB peripheral is not used at all in the
application, this pin should be connected to VSS.
SFor more pin termination details, see Section 6.7,
(2)
Supply
DD18_PRTCSS
IPD
(3)
State
InputPRTCSS: General Input / Output Signal 5
Power Management and Real Time Clock
Subsystem (PRTCSS).
SFor more pin termination details, see Section 6.7,
DD18_PRTCSS
InputPRTCSS: General Input / Output Signal 6
Power Management and Real Time Clock
Subsystem (PRTCSS).
SFor more pin termination details, see Section 6.7,
DD18_PRTCSS
Output PRTCSS: General Output Signal 0
Power Management and Real Time Clock
Subsystem (PRTCSS).
SFor more pin termination details, see Section 6.7,
DD18_PRTCSS
Output PRTCSS: General Output Signal 1
Power Management and Real Time Clock
Subsystem (PRTCSS).
SFor more pin termination details, see Section 6.7,
DD18_PRTCSS
Output PRTCSS: General Output Signal 2
Power Management and Real Time Clock
Subsystem (PRTCSS).
SFor more pin termination details, see Section 6.7,
DD18_PRTCSS
Output PRTCSS: General Output Signal 3
Power Management and Real Time Clock
Subsystem (PRTCSS).
SNote: If the RTC calendar is not used, this pin should
DD12_PRTCSS
InputPRTCSS: Crystal Input for PRTCSS oscillator
be pulled down.
For more pin termination details, see Section 6.7,
Power Management and Real Time Clock
Subsystem (PRTCSS).
SNote: If the RTC calendar is not used, this pin should
DD12_PRTCSS
Output PRTCSS: Crystal Output for PRTCSS oscillator
be left unconnected.
For more pin termination details, see Section 6.7,
Power Management and Real Time Clock
Subsystem (PRTCSS).
SFor more pin termination details, see Section 6.7,
DD12_PRTCSS
InputPRTCSS: Reset signal for PRTCSS
Power Management and Real Time Clock
Subsystem (PRTCSS).
SFor more pin details, see Section 6.7.
SNote: If an external oscillator is to be used, the
DD12_PRTCSS
DDS33
DDMXI
InputPRTCSS: Reset pin for system power sequencing
InputGlobal chip reset
InputCrystal input for system oscillator
external oscillator clock signal should be connected
to the MXI1 pin with a 1.8V amplitude. The MXO1
should be left unconnected and the VSS_MX1 signal
should be connected to board ground (Vss).
SNote: If an external oscillator is to be used, the
DDMXI
Output Output for system oscillator
external oscillator clock signal should be connected
to the MXI1 pin with a 1.8V amplitude. The MXO1
should be left unconnected and the VSS_MX1 signal
should be connected to board ground (Vss).
EMU[1:0] = 00 - Force Debug Scan chain (ARM and
ARM ETB TAPs connected)
EMU[1:0] = 11 - Normal Scan chain (ICEpick only)
RSV2R4IFor proper device operation, this pin must be tied to
ground.
RSV1R1OFor proper device operation, this pin must be left
unconnected.
RSV0A1OFor proper device operation, this pin must be left
unconnected.
CV
DD
G6PWRCore power (1.35-V).
G8
H7
H8
H12
J8
J12
J14
K8
K12
L13
M6
M10
M12
M13
V
DD12_PRTCSS
V
DDA18_PLL
V
DDRAM
J6PWRPower supply for RTC oscillator, PRTCSS, and
K7
PRTCSS I/O (1.35-V).
N4PWRAnalog power for PLL (1.8 V).
D4OOutput For proper device operation, this pin must be
connected to a 1.0uF (6.2V) capacitor, and the other
end of the capacitor must be connected to Vss.
Note: this pin is an internal power supply pin and
should not be connected to any external power
supply.”
TI offers an extensive line of development tools for device systems, including tools to evaluate the
performance of the processors, generate code, develop algorithm implementations, and fully integrate and
debug software and hardware modules. The tools support documentation is electronically available within
the Code Composer Studio™ Integrated Development Environment (IDE).
The following products support development of device 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
Hardware Development Tools:
Extended Development System (XDS™) Emulator (supports TMS320DM368 DMSoC multiprocessor
system debug) EVM (Evaluation Module)
For a complete listing of development-support tools for the TMS320DM368 DMSoC platform, visit the
Texas Instruments web site on the Worldwide Web at http://www.ti.com.For information on pricing and
availability, contact the nearest TI field sales office or authorized distributor.
2.9.2Device 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., ). Texas Instruments recommends two of three possible prefix designators for its
support tools: TMDX and TMDS. These prefixes represent evolutionary stages of product development
from engineering prototypes (TMX/TMDX) through fully qualified production devices/tools (TMS/TMDS).
www.ti.com
Device development evolutionary flow:
TMXExperimental device that is not necessarily representative of the final device's electrical
specifications.
TMPFinal silicon die that conforms to the device's electrical specifications but has not completed
quality and reliability verification.
TMSFully-qualified production device.
Support tool development evolutionary flow:
TMDXDevelopment-support product that has not yet completed Texas Instruments internal
qualification testing.
TMDSFully qualified development-support product.
TMX and TMP devices and TMDX development-support tools are shipped against the following
disclaimer:
"Developmental product is intended for internal evaluation purposes."
TMS devices and TMDS development-support tools have been characterized fully, and the quality and
reliability of the device have been demonstrated fully. TI's standard warranty applies.
Predictions show that prototype devices (TMX or TMP) have a greater failure rate than the standard
production devices. Texas Instruments recommends that these devices not be used in any production
system because their expected end-use failure rate is undefined. Only qualified production devices are to
be used in production.
PREFIX
TMX = Experimental device
TMS = Production device
TMS
320 DM368
ZCE ( )
DEVICE FAMILY
320 = TMS320 DSP family
PACKAGE TYPE
ZCE = 338-pin plastic BGA with Pb-free soldered balls
(A)
DEVICE
DM368
(B)
A
B
C
. BGA = Ball Grid Array
. For actual device part numbers (P/Ns) and ordering information, contact your nearest TI Sales Representative.
. For more information on silicon revision, see the(literature number SPRZ316).TMS320DM368 Silicon Errata
( )
SILICON REVISION
(C)
( )
TEMPERATURE GRADE
Blank = 0 to 85C
D = -40 to 85C
F = Face Detection
TMS320DM368
www.ti.com
TI device nomenclature also includes a suffix with the device family name. This suffix indicates the
package type (for example, ZCE), the temperature range (for example, "Blank" is the commercial
temperature range), and the device speed range in megahertz (for example, 202 is 202.5 MHz). The
following figure provides a legend for reading the complete device name for any TMS320DM368 DMSoC
platform member.
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
Figure 2-6. Device Nomenclature
2.9.3Related Documentation From Texas Instruments
The following documents describe the TMS320DM36x Digital Media System-on-Chip (DMSoC). Copies of
these documents are available on the internet at www.ti.com.
SPRZ315TMS320DM368 DMSoC Silicon Errata Describes the known exceptions to the functional
specifications for the TMS320DM368 DMSoC.
SPRUFG5TMS320DM36x Digital Media System-on-Chip (DMSoC) ARM Subsystem Users Guide.
This document describes the ARM Subsystem in the TMS320DM36x 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 components of the ARM Subsystem, the peripherals,
and the external memories.
SPRUFG8TMS320DM36x Digital Media System-on-Chip (DMSoC) Video Processing Front End
(VPFE) Users Guide. This document describes the Video Processing Front End (VPFE) in
the TMS320DM36x Digital Media System-on-Chip (DMSoC).
SPRUFG9TMS320DM36x Digital Media System-on-Chip (DMSoC) Video Processing Back End
(VPBE) Users Guide. This document describes the Video Processing Back End (VPBE) in
the TMS320DM36x Digital Media System-on-Chip (DMSoC).
SPRUFH0TMS320DM36x Digital Media System-on-Chip (DMSoC) 64-bit Timer Users Guide. This
SPRUFH1TMS320DM36x Digital Media System-on-Chip (DMSoC) Serial Peripheral Interface (SPI)
document describes the operation of the software-programmable 64-bit timers in the
TMS320DM36x Digital Media System-on-Chip (DMSoC).
Users Guide. This document describes the serial peripheral interface (SPI) in the
TMS320DM36x Digital Media System-on-Chip (DMSoC). The SPI is a high-speed
synchronous serial input/output port that allows a serial bit stream of programmed length (1
to 16 bits) to be shifted into and out of the device at a programmed bit-transfer rate. The SPI
is normally used for communication between the DMSoC and external peripherals. Typical
applications include an interface to external I/O or peripheral expansion via devices such as
Submit Documentation Feedback
Product Folder Link(s): TMS320DM368
TMS320DM368
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
shift registers, display drivers, SPI EPROMs and analog-to-digital converters.
SPRUFH2TMS320DM36x Digital Media System-on-Chip (DMSoC) Universal Asynchronous
Receiver/Transmitter (UART) Users Guide. This document describes the universal
asynchronous receiver/transmitter (UART) peripheral in the TMS320DM36x Digital Media
System-on-Chip (DMSoC). The UART peripheral performs serial-to-parallel conversion on
data received from a peripheral device, and parallel-to-serial conversion on data received
from the CPU.
SPRUFH3TMS320DM36x Digital Media System-on-Chip (DMSoC) Inter-Integrated Circuit (I2C)
Peripheral Users Guide. This document describes the inter-integrated circuit (I2C)
peripheral in the TMS320DM36x Digital Media System-on-Chip (DMSoC). The I2C peripheral
provides an interface between the DMSoC and other devices compliant with the I2C-bus
specification and connected by way of an I2C-bus.
SPRUFH5TMS320DM36x Digital Media System-on-Chip (DMSoC) Multimedia Card (MMC)/Secure
Digital (SD) Card Controller Users Guide. This document describes the multimedia card
(MMC)/securedigital(SD)cardcontrollerintheTMS320DM36xDigitalMedia
System-on-Chip (DMSoC).
SPRUFH6TMS320DM36x Digital Media System-on-Chip (DMSoC) Pulse-Width Modulator (PWM)
Users Guide. This document describes the pulse-width modulator (PWM) peripheral in the
TMS320DM36x Digital Media System-on-Chip (DMSoC).
SPRUFH7TMS320DM36x Digital Media System-on-Chip (DMSoC) Real-Time Out (RTO) Controller
Users Guide. This document describes the Real Time Out (RTO) controller in the
TMS320DM36x Digital Media System-on-Chip (DMSoC).
www.ti.com
SPRUFH8TMS320DM36x Digital Media System-on-Chip (DMSoC) General-Purpose Input/Output
(GPIO) Users Guide. This document describes the general-purpose input/output (GPIO)
peripheral in the TMS320DM36x Digital Media System-on-Chip (DMSoC). The GPIO
peripheral provides dedicated general-purpose pins that can be configured as either inputs
or outputs.
SPRUFH9TMS320DM36x Digital Media System-on-Chip (DMSoC) Universal Serial Bus (USB)
Controller Users Guide. This document describes the universal serial bus (USB) controller
in the TMS320DM36x Digital Media 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.
SPRUFI0TMS320DM36x Digital Media System-on-Chip (DMSoC) Enhanced Direct Memory
Access (EDMA) Controller Users Guide. This document describes the operation of the
enhanced direct memory access (EDMA3) controller in the TMS320DM36x Digital Media
System-on-Chip (DMSoC). TheEDMA controller's primary purposeis to service
user-programmed data transfers between two memory-mapped slave endpoints on the
DMSoC.
SPRUFI1TMS320DM36x Digital Media System-on-Chip(DMSoC) Asynchronous External
Memory Interface (EMIF) Users Guide. This document describes the asynchronous
external memory interface (EMIF) in the TMS320DM36x Digital Media System-on-Chip
(DMSoC). The EMIF supports a glueless interface to a variety of external devices.
(DDR2/mDDR)Memory ControllerUsersGuide.Thisdocument describesthe
DDR2/mDDR memory controller in the TMS320DM36x Digital Media System-on-Chip
(DMSoC). The DDR2/mDDR memory controller is used to interface with JESD79D-2A
standard compliant DDR2 SDRAM and mobile DDR devices.
SPRUFI3TMS320DM36x Digital Media System-on-Chip (DMSoC) Multibuffered Serial Port
Interface (McBSP) User's Guide. This document describes the operation of the
SPRUFI4TMS320DM36x Digital Media System-on-Chip (DMSoC) Universal Host Port Interface
SPRUFI5TMS320DM36x Digital Media System-on-Chip (DMSoC) Ethernet Media Access
SPRUFI7TMS320DM36x Digital Media System-on-Chip (DMSoC) Analog to Digital Converter
SPRUFI8TMS320DM36x Digital Media System-on-Chip (DMSoC) Key Scan User's Guide. This
SPRUFI9TMS320DM36x Digital Media System-on-Chip (DMSoC) Voice Codec User's Guide. This
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
multibuffered serial host port interface in the TMS320DM36x Digital Media System-on-Chip
(DMSoC). The primary audio modes that are supported by the McBSP are the AC97 and IIS
modes. In addition to the primary audio modes, the McBSP supports general serial port
receive and transmit operation.
(UHPI) User's Guide. This document describes the operation of the universal host port
interface in the TMS320DM36x Digital Media System-on-Chip (DMSoC).
Controller (EMAC) User's Guide. This document describes the operation of the ethernet
media access controllerface in the TMS320DM36x Digital Media System-on-Chip (DMSoC).
(ADC) User's Guide. This document describes the operation of the analog to digital
conversion in the TMS320DM36x Digital Media System-on-Chip (DMSoC).
document describes the key scan peripheral in the TMS320DM36x Digital Media
System-on-Chip (DMSoC).
document describes the voice codec peripheral in the TMS320DM36x Digital Media
System-on-Chip (DMSoC). This module can access ADC/DAC data with internal FIFO (Read
FIFO/Write FIFO). The CPU communicates to the voice codec module using 32-bit-wide
control registers accessible via the internal peripheral bus.
SPRUFJ0TMS320DM36x Digital Media System-on-Chip (DMSoC) Power Management and
Real-Time Clock Subsystem (PRTCSS) User's Guide. This document provides a
functional description of the Power Management and Real-Time Clock Subsystem
(PRTCSS) in the TMS320DM36x Digital Media System-on-Chip (DMSoC) and PRTC
interface (PRTCIF).
This section provides a detailed overview of the device.
3.1System Module Registers
The system module includes status and control registers for configuration of the device. Brief descriptions
of the various registers are shown in Table 3-1. For more information on the System Module registers, see
the TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number SPRUFG5).
Table 3-1. System Module Register Memory Map
HEX ADDRESSREGISTER ACRONYMDESCRIPTION
0x01C4 0000PINMUX0Pin Mux 0 (Video In) Pin Mux Register
0x01C4 0004PINMUX1Pin Mux 1 (Video Out) Pin Mux Register
0x01C4 0008PINMUX2Pin Mux 2 (AEMIF) Pin Mux Register
0x01C4 000CPINMUX3Pin Mux 3 (GIO/Misc) Pin Mux Register
0x01C4 0010PINMUX4Pin Mux 4 (Misc) Pin Mux Register
0x01C4 0014BOOTCFGBoot Configuration
0x01C4 0018ARM_INTMUXMultiplexing Control for Interrupts
0x01C4 001CEDMA_EVTMUXMultiplexing Control for EDMA Events
0x01C4 0020DDR_SLEWDDR Slew Rate
0x01C4 0024UHPICTLUHPI Control
0x01C4 0028DEVICE_IDDevice ID
0x01C4 002CVDAC_CONFIGVideo DAC Configuration
0x01C4 0030TIMER64_CTLTimer64 Input Control
0x01C4 0034USB_PHY_CTLUSB PHY Control
0x01C4 0038MISCMiscellaneous Control
0x01C4 003CMSTPRI0Master Priorities Register 0
0x01C4 0040MSTPRI1Master Priorities Register 1
0x01C4 0044VPSS_CLK_CTLVPSS Clock Mux Control
0x01C4 0048PERI_CLKCTLPeripheral Clock Control
0x01C4 004CDEEPSLEEPDEEPSLEEP Control
0x01C4 0050-Reserved
0x01C4 0054DEBOUNCE0Debounce for GIO0 Input
0x01C4 0058DEBOUNCE1Debounce for GIO1 Input
0x01C4 005CDEBOUNCE2Debounce for GIO2 Input
0x01C4 0060DEBOUNCE3Debounce for GIO3 Input
0x01C4 0064DEBOUNCE4Debounce for GIO4 Input
0x01C4 0068DEBOUNCE5Debounce for GIO5 Input
0x01C4 006CDEBOUNCE6Debounce for GIO6 Input
0x01C4 0070DEBOUNCE7Debounce for GIO7 Input
0x01C4 0074VTPIOCRVTP IO Control
0x01C4 0078PUPDCTL0IO cell pullup/down on/off control #0
0x01C4 007CPUPDCTL1IO cell pullup/down on/off control #1
0x01C4 0080HDVICPBTHDVICP Boot Register
0x01C4 0084PLL1_CONFIGPLL1 Configuration Register
0x01C4 0088PLL2_CONFIGPLL2 Configuration Register
(1) For more details on the system module registers, see the TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number
The ARM can boot from either Asynchronous EMIF (OneNand/NOR) or from ARM ROM, as determined
by the setting of the device configuration pins BTSEL[2:0]. The boot selection pins (BTSEL[2:0]) determine
the ARM boot process. After reset (POR, warm reset, or max reset), ARM program execution begins in
ARM ROM at 0x0000: 8000, except when BTSEL[2:0] = 001, indicating AEMIF (OneNand/NOR) flash
boot.
3.2.1Boot Modes Overview
The ARM ROM boot loader (RBL) executes when the BTSEL[2:0] pins indicate a condition other than the
normal ARM EMIF boot.
•If BTSEL[2:0] = 001 - Asynchronous EMIF boot mode (NOR or OneNAND). This mode is handled by
hardware control and does not involve the ROM. In the case of OneNAND, the user is responsible for
putting any necessary boot code in the OneNAND's boot page. This code shall configure the AEMIF
module for the OneNAND device. After the AEMIF module is configured, booting will continue
immediately after the OneNAND’s boot page with the AEMIF module managing pages thereafter.
•If MMC/SD boot fails, then MMC/SD boot is tried again.
•If UART boot fails, then UART boot is tried again.
•If USB boot fails, then USB boot is tried again.
•If SPI boot fails, then SPI boot is tried again.
•If EMAC boot fails, then EMAC boot is tried again.
•If HPI boot fails, then HPI boot is tried again.
•RBL shall update boot status (PASS/FAIL) in MISC register bits 8 and 9 in System control module.
•ARM ROM Boot - NAND Mode
– No support for a full firmware boot. Instead, copies a second stage user boot loader (UBL) from
NAND flash to ARM internal RAM (AIM) and transfers control to the user-defined UBL.
– Support for NAND with page sizes up to 4096 bytes.
– Support for magic number error detection and retry (up to 24 times) when loading UBL
– Support for up to 30KB UBL (32KB IRAM - ~2KB for RBL stack)
– Optional, user-selectable, support for use of DMA and I-cache during RBL execution (i.e.,while
loading UBL)
– Supports booting from 8-bit NAND devices (16-bit NAND devices are not supported)
– Uses/Requires 4-bit HW ECC (NAND devices with ECC requirements ≤ 4 bits per 512 bytes are
supported)
– Supports NAND flash that requires chip select to stay low during the tR read time
•ARM ROM Boot - MMC/SD Mode
– No support for a full firmware boot. Instead, copies a second stage User Boot Loader (UBL) from
MMC/SD to ARM Internal RAM (AIM) and transfers control to the user software.
– Support for MMC/SD Native protocol (MMC/SD SPI protocol is not supported)
– Support for descriptor error detection and retry (up to 24 times) when loading UBL
– Support for up to 30KB UBL (32KB - ~2KB for RBL stack)
– SDHC boot supported by RBL
•ARM ROM Boot - UART mode
– If the state of BTSEL[2:0] pins at reset is 011, then the UART boot mode executes. This mode
enables a small program, referred to here as a user boot loader (UBL), to be downloaded to the
on-chip ARM internal RAM via the on-chip serial UART and executed. A host program, (referred to
as serial host utility program), manages the interaction with RBL and provides a means for operator
feedback and input. The UART boot mode execution assumes the following UART settings:
Time-Out 500 ms, one-shot Serial RS-232 port 115.2 Kbps, 8-bit, no parity, one stop bit Command,
data, and checksum format Everything sent from the host to the device UART RBL must be in
ASCII format
– No support for a full firmware boot. Instead, loads a second stage user boot loader (UBL) via UART
to ARM internal RAM (AIM) and transfers control to the user software.
– Support for up to 30KB UBL (32KB - ~2KB for RBL stack)
•ARM ROM Boot – USB Mode
– No support for a full firmware boot. Instead, loads a second stage User Boot Loader (UBL) via USB
to ARM Internal RAM (AIM) and transfers control to the users software.
•ARM ROM Boot – SPI Mode
– The device will copy UBL to ARM Internal RAM (AIM) via SPI interface from a SPI peripheral like
SPI EEPROM. RBL will then transfer control to the UBL.
•ARM ROM Boot – EMAC Mode
– The device will send a boot request packet and the host/server will respond with the boot packets.
RBL will wait for all boot packets to arrive and then transfer control to the UBL which is received via
boot packets. In EMAC boot mode an I2C EEPROM or SPI EEPROM is necessary for
programming EMAC descriptor (including EMAC address for the device)
Note: If a magic number is not found in the EEPROM, then the EMAC boot mode will use a default
MAC address. In this case, there will be no magic number support.
•ARM ROM Boot – HPI Mode
– The Host will copy UBL to ARM Internal RAM (AIM) via HPI interface and notify the ROM
bootloader after copy is finished. RBL will then transfer control to the UBL.
www.ti.com
The general boot sequence is shown in Figure 3-1. For more information, refer to the TMS320DM36x
DMSoC ARM Subsystem Reference Guide (literature number SPRUFG5).
The device requires one primary reference clock. The reference clock frequency may be generated either
by crystal input or by external oscillator. The reference clock is the clock at the pins named MXI1/MXO1,
and which drives two separate PLL controllers (PLLC1 and PLLC2). PLLC1 generates the clocks required
by the ARM, EDMA, VPSS and the rest of the peripherals. PLL2 generates the clock required by the DDR
PHY interface and is also capable of providing clocks to the ARM, USB, Video, or Voice Codec modules
as well as a flexible clocking option. Figure 3-2 represents the clocking architecture for the ARM
subsystem. For more information on device clocking and the system PLL controller please see the
TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number SPRUFG5).
Two PLL controllers provide clocks to different components of the chip. The PLL controller 1 (PLLC1)
provides clocks to most of the components of the chip. The PLL controller 2 (PLLC2) provides clocks to
the DDR PHY and is also capable of providing clocks to the ARM, USB, VPSS or the Voice Codec
modules instead as well.
As a module, the PLL controller provides the following:
•Glitch-free transitions (on changing PLL settings)
There are two PLLs on the device, and they are independently controlled. PLLC1 generates the
frequencies needed for the ARM, Video Processing Sub System (VPSS), MJCP coprocessor block,
EDMA, and peripherals.
The reference clock for both PLLs is the single crystal input. Both PLLs will be of the same type . It should
be noted that the USB2.0 PHY contains a third PLL embedded within it. Table 3-2, and Figure 3-3
describe the customization of PLLC1.
•Provides primary system clock
•Software configurable
•Accepts clock input or internal oscillator input
•PLL pre-divider value is programmable
•PLL multiplier value is programmable
•PLL post-divider value is programmable . See the data manual for all supported configurations.
•Only SYSCLK [9:1] are used
Table 3-2. PLLC1 Output Clocks
PLLC1SYSCLKyUsed ByPLLDIV Divider
PLLC1SYSCLK1USB reference clock
PLLC1SYSCLK2ARM926EJ-S, HDVICP block clock
PLLC1SYSCLK3MJCP and HDVICP bus interface clockProgrammable
PLLC1SYSCLK4Configuration bus clock, peripheral system interfaces,Programmable
PLLC2 provides the USB reference clock , ARM926EJ-S, DDR 2x clock, Voice Codec clock and VENC
27MHz, 74.25MHz clock. The PLLC2 functionality can be programmed via the PLLC2 registers. The
following list, Table 3-3, and Figure 3-4 describe the customization of PLLC2.
The PLLC2 customization includes the following features:
•PLLC2 provides DDR PHY, USB reference clock , ARM926EJ-S clock, VENC 27MHz, 74.25Hz clock
and Voice codec clock
•Software configurable
•Accepts clock input or internal oscillator input (the same input as PLLC1)
Like the DM365, the DM368 uses two PLLs to generate the two fundamental clocks used on the device.
These two clocks feed two divider blocks which generate all of the functional clocks used by the
peripherals and cores in the DM368. The ARM926 and DDR peripheral in the DM368 are limited to a
maximum clock frequency of 432 MHz and 340 MHz respectively. There are some peripheral clocks on
the DM368 which are required to operate at a specific frequency by functional specification or convention.
These frequencies are detailed in Table 3-5.
Table 3-5. Specific Peripheral Operating Frequencies
VENC (standard definition)27required to generate a valid NTSC signal
ClockRequired Frequency (MHz)Reason
VENC (high definition)74.25required to generate a valid ATSC signal
USB36, 24, or 19.2required by the USB peripheral to generate a 48 MHz USB clock
Voice Codec4.096required to generate a precise 16 kHz audio sample rate
While it is possible to generate both a 432 MHz and 340 MHz clock with the two PLLs, these two
frequencies cannot be divided down to generate all required frequencies from Table 3-5. Several different
frequency solutions are required to cover all of these requirements. The different solutions for different
input crystal frequencies are listed in the tables below.
The following tables show examples of the PLL combinations that can be supported with DM368. Please
see the TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number SPRUFG5) for
additional details on special peripherals clocking considerations and for additional PLL controller
configuration details.
There are several important points to note from these tables.
•A 432 MHz functional clock will result in DM368 voice codec sampling frequency of 16.07KHz. The
difference of 0.4375% versus 16KHz specification should be acceptable for the majority of audio
applications. If the DM368 voice codec is required to operate at precisely 16 kHz then the functional
clock can be reduced to achieve precisely that sample frequency but the ARM926 and HDVICP will
have to run at a reduced rate resulting in lower video performance.
•If a 24 MHz input crystal is used it is not possible to generate a 74.25 MHz HD video output clock.
•If a 19.2 MHz input crystal is used it is not possible to generate a valid 74.25 MHz HD output clock.
(1) M = PLL controller multiplier. N = PLL controller divider.
(2) All shaded frequencies derive from the PLL2 controller.
(3) PLLC1SYSCLK4 (Configuration bus clock, peripheral system interfaces, EDMA) should be half of the PLLC1SYSCLK3 (MJCP and
HDVICP bus interface clock).
(4) The Voice Codec divider value is the combination of the PLL controller 2 SYSCLK4 and Peripheral Clock Control Register PLLDIV2 bit
setting divider.
(5) PLL Output is calculated by = Oscillator Input * (2M/(N+1)).
(1) M = PLL controller multiplier. N = PLL controller divider.
(2) All shaded frequencies derive from the PLL2 controller.
(3) PLLC1SYSCLK4 (Configuration bus clock, peripheral system interfaces, EDMA) should be half of the PLLC1SYSCLK3 (MJCP and
HDVICP bus interface clock).
(4) The Voice Codec divider value is the combination of the PLL controller 2 SYSCLK4 and Peripheral Clock Control Register PLLDIV2 bit
setting divider.
(5) PLL Output is calculated by = Oscillator Input * (2M/(N+1)).
(1) M = PLL controller multiplier. N = PLL controller divider.
(2) All shaded frequencies derive from the PLL2 controller.
(3) PLLC1SYSCLK4 (Configuration bus clock, peripheral system interfaces, EDMA) should be half of the PLLC1SYSCLK3 (MJCP and
(4) The Voice Codec divider value is the combination of the PLL controller 2 SYSCLK4 and Peripheral Clock Control Register PLLDIV2 bit
(5) PLL Output is calculated by = Oscillator Input * (2M/(N+1)).
(1) M = PLL controller multiplier. N = PLL controller divider.
(2) All shaded frequencies derive from the PLL2 controller.
(3) PLLC1SYSCLK4 (Configuration bus clock, peripheral system interfaces, EDMA) should be half of the PLLC1SYSCLK3 (MJCP and
(4) The Voice Codec divider value is the combination of the PLL controller 2 SYSCLK4 and Peripheral Clock Control Register PLLDIV2 bit
(5) PLL Output is calculated by = Oscillator Input * (2M/(N+1)).
(5)
(MHz)(MHz)
HDVICP bus interface clock).
setting divider.
(2M/(N+1))PLL Output(2M/(N+1))27 MHz74.25MHz
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
(1) (2)(3)
(4)
kHz)
(1) (2)(3)
(4)
kHz)
kHz)
Video Encoder
Encoder
For maximum H.264 encode performance the ARM must run at 432 MHz and the DDR at 340 MHz. Any
speed decrease to either of these will reduce encode performance. This means that if the ARM speed
must be reduced to enable another function it will impact the encode performance.
If USB is required then a 36 MHz, 24 MHz or 19.2 MHz input crystal is preferred as those can support
USB at full ARM rate.
If a video output is needed then a 36 MHz, 27 MHz or 24 MHz input crystal should be used. For HD video
output it may be preferred to use the EXTCLK input to inject an external 74.25 MHz clock and at the same
time operate the ARM at 432 MHz.
3.3.7Peripheral Clocking Considerations
The device supports several peripherals with special clocking considerations (VPBE, USB, Key Scan,
ADC, Voice Codec, MJCP, HDVICP, AUXCLK, DDR2 EMIF). For more detail on these special
considerations, see the Peripheral Clocking Considerations section of theTMS320DM36x DMSoC ARMSubsystem Reference Guide (literature number SPRUFG5).
3.4Power and Sleep Controller (PSC)
In the device system, the Power and Sleep Controller (PSC) is responsible for managing transitions of
system power on/off, clock on/off, and reset. A block diagram of the PSC is shown in Figure 3-5. Many of
the operations of the PSC are transparent to software, such as power-on-reset operations. However, the
PSC provides you with an interface to control several important clock and reset operations.
The PSC includes the following features:
•Manages chip power-on/off, clock on/off, and resets
•Provides a software interface to:
– Control module clock ON/OFF
The device makes extensive use of pin multiplexing to accommodate the large number of peripheral
functions in the smallest possible package. In order to accomplish this, pin multiplexing is controlled using
a combination of hardware configuration (at device reset) and software control. No attempt is made by the
hardware to ensure that the proper pin muxing has been selected for the peripherals or interface mode
being used, thus proper pin muxing configuration is the responsibility of the board and software designers.
An overview of the pin multiplexing is shown in Table 3-10.
All pin multiplexing options are configurable by software via pin mux registers that reside in the System
Control Module. The PinMux0 Register controls the Video In muxing, PinMux1 register controls Video Out
signals, PinMux2 register controls AEMIF signals, PinMux3 registers control the multiplexing of the GIO
signals, the PinMux4 register controls the SPI and MMC/SD0 signals. See the TMS320DM36x DMSoCARM Subsystem Reference Guide (literature number SPRUFG5) for complete descriptions of the pin mux
registers.
The device configuration pins are multiplexed with AEMIF pins. Note that the AECFG[2:0] inputs only
select the default AEMIF address pin muxing. The number of active address pins may be increased or
reduced at any time by modifying the appropriate bits in the PinMux2 control register. After the device
configuration pins are sampled at reset, they automatically change to function as AEMIF pins. For more
details on AEMIF default configuration, see Section 3.7.5.
Table 3-10. Peripheral Pin Mux Overview
PeripheralMuxed WithPrimary FunctionSecondary FunctionTertiary Function
VPFE (video in)GPIO and SPI3GPIOVPFE (video in)SPI3
VPBE (video out)GPIO, PWM, and RTOGPIOVPBE (video out)PWM & RTO
AEMIFGPIOAEMIFGPIO
McBSPGPIOGPIOMcBSP
MMC/SD0MMC/SD0
MMC/SD1GPIO and EMIFGPIOMMC/SD1EMIF
CLKOUTGPIOGPIOCLKOUT
I2CGPIOGPIOI2C
UART0/UART1GPIOGPIOUART
SPI0,SPI1,SPI2,SPI4 GPIOGPIOSPI
EMACGPIOGPIOEXTINTEMAC
HPIAEMIFAEMIFHPI
There are five types of reset. The types of reset differ by how they are initiated and/or by their effect on
the chip. Each type is briefly described in Table 3-11 and further described in the TMS320DM36x DMSoCARM Subsystem Reference Guide (literature number SPRUFG5).
Table 3-11. Reset Types
TypeInitiatorEffect
POR (Power-On-Reset)RESET pin low and TRST lowTotal reset of the chip (cold reset).
Activates the POR signal on chip, which is used to reset
test/emulation logic.
Warm ResetRESET pin lowResets everything except for test/emulation logic.
ARM emulator stays alive during Warm reset.
Max ResetARM emulator or Watchdog TimerSame effect as warm reset.
(WDT)
System ResetARM emulatorA soft reset.
Soft reset maintains memory contents, and does not affect or reset
clocks or power states.
Module ResetARM softwareCan independently apply reset to each module, via an MMR.
Intended as a debug tool, and not necessarily for general use.
3.7Default Device Configurations
After POR, warm reset, and max reset, the chip is in its default configuration. This section highlights the
default configurations associated with PLLs, clocks, ARM boot mode, and AEMIF.
www.ti.com
Note: Default configuration is the configuration immediately after POR, warm reset, and max reset and
just before the boot process begins. The boot ROM updates the configuration. See Section 3.2 for more
information on the boot process.
3.7.1Device Configuration Pins
The device configuration pins are described in Table 3-12. The device configuration pins are latched at
reset and allow you to configure all of the following options at reset:
•ARM Boot Mode
•Asynchronous EMIF pin configuration
These pins are described further in the following sections.
Note: The device configuration pins are multiplexed with AEMIF pins. After the device configuration pins
are sampled at reset, they automatically change to function as AEMIF pins. Pin multiplexing is described
in Section 3.5.
Table 3-12. Device Configuration
Device Configuration InputFunctionPinpull-down)
BTSEL[2:0]Selects ARM boot modeEM_A[13:11]000
AECFG[2:0]AEMIF Configuration
000 = Boot from ROM (NAND)(Boot from ROM - NAND)
001 = Boot from AEMIF
010 = Boot from ROM (MMC/SD)
011 = Boot from ROM (UART)
100 = Boot from ROM (USB)
101 = Boot from ROM (SPI)
110 = Boot from ROM (EMAC)
111 = Boot from ROM (HPI)
(1)
AECFG[2] = '0' for 8-bit AEMIF configuration(8-bit NAND)
AECFG[2] = '1' for 16-bit AEMIF configuration
OSCCFG = '0' for mode #1(Mode #1)
OSCCFG = '1' for mode #2
Sampledpull-up/
Default Setting (by internal
3.7.2PLL Configuration
After POR, warm reset, and max reset, the PLLs and clocks are set to their default configurations. The
PLLs are in bypass mode and disabled by default. This means that the input reference clock at MXI1
(typically 24 MHz) drives the chip after reset. For more information on device clocking, see Section 3.3 .
The default state of the PLLs is reflected in the default state of the register bits in the PLLC registers.
Refer to the TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number SPRUFG5).
3.7.3Power Domain and Module State Configuration
Only a subset of modules are enabled after reset by default. Table 3-13 shows which modules are
enabled after reset. Table 3-13 shows that the following modules are enabled depending on the sampled
state of the device configuration pins. For example, if UART boot mode is BTSEL[2:0] = 011, then the
default state of the UART module is enabled. For more information on module configuration, refer to the
TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number SPRUFG5).
Table 3-13. LPSC Assignments and Module Configuration
The ARM can boot from either Asynchronous EMIF (OneNand/NOR) or from ARM ROM, as determined
by the setting of the device configuration pins BTSEL[2:0]. The boot selection pins (BTSEL[2:0]) determine
the ARM boot process. After reset (POR, warm reset, or max reset), ARM program execution begins in
ARM ROM at 0x0000: 8000, except when BTSEL[2:0] = 001, indicating AEMIF (OneNand/NOR) flash
boot.
The input pins AECFG[2:0] determine the AEMIF configuration immediately after reset. Pins that are not
assigned to another peripheral and not enabled as address signals become GPIOs. These may be used
as ALE and CLE signals for NAND Flash control if booting from internal ROM. If booting from NOR Flash
then the appropriate number of address output must be enabled by the AECFG[2:0] inputs at reset. The
enabled address signals are always contiguous from EM_BA[1] upwards; bits cannot be skipped. EM_A[0]
does not represent the lowest AEMIF address bit. The device has 23 address lines and 2 chip selects with
an 8-bit or 16-bit option. The device supports only 8-bit and 16-bit data widths for the AEMIF.
•16-bit mode: EM_BA[1] represents the LS address bit (the half-word address) and EM_BA[0]
represents address bit (A[14]). The maximum number of address lines pins in 16-bit mode are 23,
which include EM_BA[1] + EM_A[0:13] +EM_BA[0] (as pin A[14] via PINMUX2 register) + EM_A[15:20]
+EM_A[21] (via PINMUX4 register)
Note: Pins EM_A[15:21] are available by programming the PinMux4 register in software after boot, but
must be pulled down externally so that valid voltage levels are provided on the full set of address pins
during boot time. EM_A[15:21] come out of reset as GPIO pins per the PinMux4 register.
•8-bit mode: EM_BA[1:0] represent the 2 LS address bits. Additional selections are available by
programming the PinMux2 register in software after boot. The maximum number of address lines in
8-bit mode are 23, which include EM_BA[0:1] + EM_A[0:13] + A[14] (via PINMUX4 register) +
EM_A[15:20].
Note: Pins EM_A[15:20] are available by programming the PinMux4 register in software after boot, but
must be pulled down externally so that valid voltage levels are provided on the full set of address pins
during boot time. EM_A[15:20] come out of reset as GPIO pins per the PinMux4 register.
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
For additional details about the PinMux2 and PinMux4 registers, see the TMS320DM36x DMSoC ARMSubsystem Reference Guide (literature number SPRUFG5).
The device's pin-mux control logic allows all of the Asynchronous EMIF address pins to be used as
GPIOs. If devices (such as NAND Flash) attached to the AEMIF require less than the 16 address pins
provided, then the unused upper-order addresses may be configured as GPIOs. These pins must be
configured at reset so that pins being driven by the AEMIF with addresses will not cause bus contention
with pins being driven by the system as general purpose inputs.
The AECFG[2:0] value does not affect the operation of the AEMIF module itself, only which of its address
bits are seen on the device pins (resulting in the natural ramifications if devices don’t receive all address
signals or if contention with general purpose inputs occurs). As shown in Table 3-14, the number of
address bits enabled on the AEMIF is selectable from 0 to 16 at boot time, see notes above for additional
support of up-to 23 address lines.
When AEMIF is enabled, the wait state registers are reset to the slowest possible configuration, which is
88 cycles per access (16 cycles of setup, 64 cycles of strobe, and 8 cycles of hold). Thus, with a 24 MHz
clock at MXI/MXO, the AEMIF is configured to run at (12 MHz/ 88) which equals approximately 136.36
kHz.
3.7.6Oscillator Frequency Configuration
The oscillator input pins, MXI1, MXO, are designed to operate in two frequency ranges depending on the
GIO81(OSCCFG) pin sampled at reset, which should be set according to the required input frequency of
operation. See Table 3-15 for details.
Table 3-15. Operation Frequency
MODEGIO81 (OSCCFG)OSCILLATION
1015 - 35MHz
2130 - 40MHz
The frequency selection pin cannot be changed dynamically while the oscillator is running. They should
only be set once before oscillator startup.
The GIO81(OSCCFG) state is latched during reset, and it specifies the oscillation frequency mode as
shown in Table 3-15.
Proper board design should ensure that input pins to the DMSoC device always be at a valid logic level
and not floating. This may be achieved via pullup/pulldown resistors. The DMSoC features internal pullup
(IPU) and internal pulldown (IPD) resistors on most pins to eliminate the need, unless otherwise noted, for
external pullup/pulldown resistors.
An external pullup/pulldown resistor needs to be used in the following situations:
•Boot and Configuration Pins: If the pin is both routed out and 3-stated (not driven), an external
pullup/pulldown resistor is strongly recommended, even if the IPU/IPD matches the desired
value/state.
•Other Input Pins: If the IPU/IPD does not match the desired value/state, use an external
pullup/pulldown resistor to pull the signal to the opposite rail.
For the boot and configuration pins, if they are both routed out and 3-stated (not driven), it is stronglyrecommendedthatanexternalpullup/pulldownresistorbeimplemented.Although,internal
pullup/pulldown resistors exist on these pins and they may match the desired configuration value,
providing external connectivity can help ensure that valid logic levels are latched on these device boot and
configuration pins. In addition, applying external pullup/pulldown resistors on the boot and configuration
pins adds convenience to the user in debugging and flexibility in switching operating modes.
Tips for choosing an external pullup/pulldown resistor:
•Consider the total amount of current that may pass through the pullup or pulldown resistor. Make sure
to include the leakage currents of all the devices connected to the net, as well as any internal pullup or
pulldown resistors.
•Decide a target value for the net. For a pulldown resistor, this should be below the lowest VILlevel of
all inputs connected to the net. For a pullup resistor, this should be above the highest VIHlevel of all
inputs on the net. A reasonable choice would be to target the VOLor VOHlevels for the logic family of
the limiting device; which, by definition, have margin to the VILand VIHlevels.
•Select a pullup/pulldown resistor with the largest possible value; but, which can still ensure that the net
will reach the target pulled value when maximum current from all devices on the net is flowing through
the resistor. The current to be considered includes leakage current plus, any other internal and
external pullup/pulldown resistors on the net.
•For bidirectional nets, there is an additional consideration which sets a lower limit on the resistance
value of the external resistor. Verify that the resistance is small enough that the weakest output buffer
can drive the net to the opposite logic level (including margin).
•Remember to include tolerances when selecting the resistor value.
•For pullup resistors, also remember to include tolerances on the DVDDrail.
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
For most systems, a 1-kΩ resistor can be used to oppose the IPU/IPD while meeting the above criteria.
Users should confirm this resistor value is correct for their specific application.
For most systems, a 20-kΩ resistor can be used to compliment the IPU/IPD on the boot and configuration
pins while meeting the above criteria. Users should confirm this resistor value is correct for their specific
application.
For more detailed information on input current (II), and the low-/high-level input voltages (VILand VIH) for
the device, see Section 5.2, Recommended Operating Conditions.
For the internal pullup/pulldown resistors for all device pins, see the peripheral/system-specific terminal
functions table.
The device uses a 64-bit crossbar architecture to control access between device processors, subsystems
and peripherals. There are eleven transfer masters (TCs have separate read and write connections)
connected to the crossbar; ARM, the Video Processing Subsystem (VPSS), the master peripherals (USB,
EMAC, HPI), and four EDMA transfer controllers. These can be connected to seven separate slave ports;
ARM, the DDR EMIF, CFG bus peripherals, MJCP, and HDVICP. Not all masters may connect to all
slaves. Connection paths are indicated by √ at intersection points shown in Table 4-1.
Table 4-1. System Connection Matrix
SLAVE MODULE
DMAARM InternalMPEG/JPEGHD Video ImageConfig Bus RegistersDDR EMIF
5.1Absolute Maximum Ratings Over Operating Case Temperature Range
(Unless Otherwise Noted)
Supply voltage rangesAll 1.8 V supplies-0.3 V to 2.45 V
Input voltage rangesAll 3.3 V I/Os-0.5 V to 3.8 V
Operating case temperature ranges
Storage temperature rangesT
(1) Stresses beyond those listed under "absolute maximum ratings" may cause permanent damage to the device. These are stress ratings
only, and functional operation of the device at these or any other conditions beyond those indicated under "recommended operating
conditions" is not implied. Exposure to absolute-maximum-rated conditions for extended periods may affect device reliability.
(2) All voltage values are with respect to V
(1) (2)
SS.
All 1.35-V supplies-0.3 V to 1.6 V
All 3.3 V supplies-0.3 V to 3.8 V
All 1.8 V I/Os-0.5 V to 2.6 V
USB_VBUS0 V to 5.5 V
Commercial Temperature T
Extended Temperature [D version devices] T
(1) For proper device operation, this pin must always be connected to C
(2) Oscillator ground must be kept separate from other grounds and connected directly to the crystal load capacitor ground (see
VDD
.
Section 6.6.1).
(3) For proper device operation, keep this pin separate from digital ground.
(4) These I/O specifications apply to regular 3.3 V I/Os and do not apply to DDR2/mDDR, USB I/Os. DDR2/mDDR I/Os are 1.8 V I/Os and
High-level input voltage I/O (1.35-V)
(PWRCNT/PWRST/RTCXI/RTCXO)
HIgh-level switchable input3.3V I/O mode2
(4)
voltage
(VDD_AEMIF1_18_33,
VDD_AEMIF2_18_33,
VDD_ISIF_18_33 powered
(5)(6) (7)(8)
I/Os)
Low-level input voltage
(4)
1.8V I/O mode0.7V
, excludes switchable I/O
(3.3V I/O)
Low-level input voltage
(4)
, non-DDR2 I/O, excludes switchable I/O0.3*VDDS
(1.8V I/O)18
Voltage Input
Low
V
IL12RTC
V
IL1833
RTC Low-level input voltage
(1.35V I/O)
Low-level switchable input3.3V I/O mode0.8
(4)
voltage
(VDD_AEMIF1_18_33,
VDD_AEMIF2_18_33,
VDD_ISIF_18_33 powered
(4)
1.8V I/O mode
I/Os)
V
REF
R
BIAS
HD 3CH DAC
Video Buffer
USB
Voice Codec
ADCF
TemperatureT
(5) V
(6) V
(7) Example 1: V
(8) V
(9)
R
LOAD_X
C
BG
R
OUT
R
FB
(9)
R
BIAS
C
BG
USB_VBUSUSB external charge pump input05.25V
V
DDA12LDO_USB
f
s
-System clock256fskHz
SCLK
c
DD_AEMIF1_18_33
]pins, Keyscan, or GPIO pins.
DD_AEMIF2_18_33:
Keyscan, or GPIO pins.
Example 2: V
DD_ISIF_18_33
(SPI3_SCLK,SPI3_SIMO,SPI3_SCS[0], SPI3_SCS[1]) or USBDRVVBUS or GPIO pins.
: can be used as a power supply for EM_A[3:13], EM_BA0, EM_BA1, EM_CE[0], EM_ADV, EM_CLK, EM_D[8:15
can be used as a power supply for EM_A[0:2], EM_CE[1], EM_WE, EM_OE, EM_WAIT, EM_D[0:7] pins, HPI,
DD_AEMIF2_18_33
DD_AEMIF1_18_33
: can be used as a power supply for VPFE pins (CIN[7:0], YIN[7:0], C_WE_FIELD, PCLK), or SPI3
DAC reference voltage475500525mV
DAC full-scale current adjust resistor237624002424Ω
Output resistor74.257575.75Ω
Bypass capacitor0.1uF
Output resistor (ROUT), between TVOUT and VFB pins2128.521502171.5
Feedback resistor, between VFB and IDACOUT pins.207921002121
Full-scale current adjust resistor2400Ω
Bypass capacitor0.1uF
Internal LDO output
(10)
Sampling frequency816kHz
SCLK frequency2MHz
Operating case temperature
range
at 1.8-V for 8-bit NAND V
and V
DD_AEMIF2_18_33
at 1.8-V for 16-bit NAND.
Default Temperature085°C
Extended Temperature [D version
devices]
DD_AEMIF1_18_33
at 3.3-V for GPIO.
(9) See Section 6.12.2.4. Also, resistors should be E-96 spec line (3 digits with 1% accuracy).
(10) For proper device operation, this pin must be connected to a 0.22mF capacitor to V
Zero Scale Offset Error0.5%
G_ERRGain Error-55%
Ch_matchChannel matching+/-2%
Output high voltage
(top of 75% NTSC or PAL colorbar)
Output low voltage
(bottom of sync tip)
Video Buffer
V
OH(VIDBUF)
V
OL(VIDBUF)
RESResolution10bits
V
OUT
Output VoltageR
= 75 Ω0.351.35V
LOAD
(1)
MINTYPMAXUNIT
-
DDS18
100
-100
= 75 Ω0V
1.35
0.35
±10
REF
mA
V
V
(1) For test conditions shown as MIN, MAX, or NOM, use the appropriate value specified in the recommended operating conditions table.
(2) These I/O specifications apply to regular 3.3 V and 1.8V I/Os and do not apply to DDR2/mDDR, USB I/Os. DDR2/mDDR I/Os are 1.8 V
I/Os and adhere to JESD79-2A standard, USB I/Os adhere to USB2.0 spec.
(3) This specification applies only to pins with an internal pullup (PU) or pulldown (PD). See or Section 2.8 for pin descriptions.
(4) To pull up a signal to the opposite supply rail, a 1 kΩ resistor is recommended.
(5) IOZapplies to output only pins, indicating off-state (Hi-Z) output leakage current.
6Peripheral Information and Electrical Specifications
6.1Parameter Information Device-Specific Information
A.The data sheet 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 model of the tester pin electronics is shown in Figure 6-1. 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 sheet timings.
Input requirements in this data sheet are tested with an input slew rate of < 4 Volts per nanosecond (4 V/ns) at the
device pin and the input signals are driven between 0V and the appropriate I/O supply for the signal.
Figure 6-1. Test Load Circuit for AC Timing Measurements
www.ti.com
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.1Signal Transition Levels
All input and output timing parameters are referenced to V
V
= 1.65 V. For 1.8 V I/O, V
ref
= 0.9 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.2Timing Parameters and Board Routing Analysis
for both "0" and "1" logic levels. For 3.3 V I/O,
ref
The timing parameter values specified in this data sheet do not include delays by board routings. As a
good board design practice, such delays must always be taken into account. Timing values may be
adjusted by increasing/decreasing such delays. TI recommends utilizing the available I/O buffer
information specification (IBIS) models to analyze the timing characteristics correctly. To properly use IBIS
models to attain accurate timing analysis for a given system, see the Using IBIS Models for TimingAnalysis Application Report (literature number SPRA839). If needed, external logic hardware such as
buffers may be used to compensate any timing differences.
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
The power supplies are summarized in Table 6-1.
Table 6-1. Power Supplies
CUSTOMERTOLERANCEPACKAGEDEVICE PLANEDESCRIPTION
BOARD SUPPLYPLANE
1.35V±5%1.35VCV
1.8 V±5%1.8 VV
3.3 V±5%3.3 VV
1.8/3.3 V±5%1.8/3.3 VV
0 V0 VV
0 V0 VV
0 V0 VV
DD
V
DD12_PRTCSS
V
DDA12_DAC
V
PP
DD18_PRTCSS
V
DDMXI
V
DD18_SLDO
V
DD18_DDR
V
DDA18_PLL
V
DDA18_USB
V
DDA18_VC
V
DDA18_DAC
V
DDS18
V
DDA18_ADC
DDS33
V
DDA33_USB
V
DDA33_VC
DD_AEMIF1_18_33
V
DD_AEMIF2_18_33
V
DD_ISIF18_33
SS_MX1
SS_32K
SS
Core power supply
RTC oscillator power supply
PWR CTRL power supply
PWR CTRL 1.35-V I/O power supply
DAC 1.35-V analog power supply
VPPpower supply
PWR CTRL 1.8-V power supply
MXI1 (oscillator) 1.8-V power supply
Power supply for internal RAM
For proper device operation, this pin must be connected to V
1.8-V DDR2 Supply Voltage
1.8-V PLL Analog Supply Voltage
1.8-V USB Analog Supply Voltage
1.8-V Voice Codec Module Analog Supply Voltage
1.8-V DAC Analog Supply Voltage
1.8-V Supply Voltage
1.8-V ADC Supply Voltage
3.3-V I/O Supply Voltage
3.3-V USB Analog Supply Voltage
3.3-V Voice Codec Module Analog Supply Voltage
Switchable 3.3/1.8-V EMIF1 Supply Voltage
Note: Power supply is switchable for AEMIF and its multiplexed
peripherals (3.3/1.8 V)
(2)
.
Switchable 3.3/1.8-V EMIF2 Supply Voltage
Note: Power supply is switchable for AEMIF and its multiplexed
peripherals (3.3/1.8 V)
(2)
.
Switchable 3.3/1.8-V ISIF Supply Voltage
Note: Power supply is switchable for ISIF and its multiplexed
peripherals (3.3V/1.8V)
(5)
Oscillator (MXI1) ground
Note: For proper device operation, connect to external crystal
capacitor ground and must be kept separate from other grounds.
Oscillator (32K) ground
Note: For proper device operation, connect to external crystal
capacitor ground and must be kept separate from other grounds.
Ground
.
DDS18
(1)
(3)
(4)
(1) V
DD_AEMIF1_18_33
]pins, Keyscan, or GPIO pins.
(2) Example 1: V
Example 2: V
(3) V
DD_AEMIF2_18_33:
Keyscan, or GPIO pins.
(4) V
DD_ISIF_18_33
(SPI3_SCLK,SPI3_SIMO,SPI3_SCS[0], SPI3_SCS[1]) or USBDRVVBUS or GPIO pins.
(5) Example 1 V
is to be used like SPI3 or GPIO or CLKOUT0, or USBDRVVBUS.
: can be used as a power supply for EM_A[3:13], EM_BA0, EM_BA1, EM_CE[0], EM_ADV, EM_CLK, EM_D[8:15
DD_AEMIF2_18_33
DD_AEMIF1_18_33
can be used as a power supply for EM_A[0:2], EM_CE[1], EM_WE, EM_OE, EM_WAIT, EM_D[0:7] pins, HPI,
at 1.8-V for 8-bit NAND V
and V
DD_AEMIF2_18_33
at 1.8-V for 16-bit NAND.
DD_AEMIF1_18_33
at 3.3-V for GPIO.
: can be used as a power supply for VPFE pins (CIN[7:0], YIN[7:0], C_WE_FIELD, PCLK), or SPI3
DD_ISIF_18_33
power supply can be at 1.8V for VPFE pin functionality or it can be at 3.3V if other peripherals pin functionality
In order to ensure device reliability, the device requires the following power supply power-on and
power-off sequences. See Section 5.2, Recommended Operating Conditions, for a description of the
power supplies.
•The following power sequences are recommended to prevent damage to the device.
•The PRTCSS core must always be powered-on and powered-off regardless of whether the PRTCSS
feature is used.
•If the PRTCSS sequencer is to be used in any PRTCSS modes, please refer to the TMS320DM36xPRTCSS User's Guide (literature number SPRUFJ0) for more details on the differences to the power
sequence.
www.ti.com
6.4.1Simple Power-On and Power-Off Method
The following steps must be followed in sequential order for the simple power-on method:
1. Power on the PRTCSS/ Main core (1.35-V).
2. Power on the PRTCSS/Main I/O (1.8-V).
3. Power on the Main/Analog I/O (3.3-V).
Note for simple power-on: RESET must be low until all supplies are ramped up.
The following steps should be followed for the simple power-off method:
1. Power off the Main/Analog I/O (3.3-V).
2. Power off the PRTCSS/Main I/O (1.8-V).
3. Power off the PRTCSS/Main core (1.35-V).
Notes for simple power-off:
– If RESET is low, steps 2 and 3 may be performed simultaneously.
– If RESET is not low, these steps must be followed sequentially.
6.4.2Restricted Power-On and Power-Off Method
The following steps should be followed for the restricted power-on method:
The following steps should be followed for the restricted power-off method:
1. Power off Main/Analog I/O (3.3-V).
2. Power off PRTCSS/Main I/O (1.8-V).
3. Power off PRTCSS/Main core (1.35-V).
When booting the DM368 from OneNAND, you must ensure that the OneNAND device is ready with valid
program instructions before the DM368 attempts to read program instructions from it. In particular, before
you release the device's reset, you must allow time for OneNAND device power to stabilize and for the
OneNAND device to complete its internal copy routine. During the internal copy routine, the OneNAND
device copies boot code from its internal non-volatile memory to its internal boot memory section. Board
designers typically achieve this requirement by design of the system power and reset supervisor circuit.
Refer to your OneNAND device datasheet for OneNAND power ramp and stabilization times and for
OneNAND boot copy times.
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
– RESET must be low until all supplies are ramped up.
– Steps 1, 2, and 3 may be performed simultaneously if the Main core finishes ramping up before the
I/Os and the maximum delta voltage difference between the 1.8-V and 3.3-V I/Os is 2.0-V until the
1.8-V I/O reaches the full voltage.
Notes for restricted power-off:
– The 3.3-/1.8-V I/Os may be powered off simultaneously if the maximum delta voltage difference
between them is 2.0V until the 1.8-V I/O is completely powered off, and the PRTCSS/Main core
must be powered down last.
6.4.3Power-Supply Design Considerations
Core and I/O supply voltage regulators should be located close to the device to minimize inductance and
resistance in the power delivery path. Additionally, when designing for high-performance applications
utilizing the 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.4.4Power-Supply Decoupling
In order to properly decouple the supply planes from system noise, place as many capacitors (caps) as
possible close to the device. These caps need to be close to the 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 uF) 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. See also Section 6.6.1 for additional recommendations on power supplies for the
oscillator/PLL supplies.
(1) BTSEL[2:0] and AECFG[2:0] are the boot configuration pins during device reset.
(2) C = MXI1/CLKIN cycle time in ns. For example, when MXI1/CLKIN frequency is 24 MHz use C = 41.6 ns.
(3) E = 1/PLLC1SYSCLK4 cycle time in ns.
Active low width of the RESET pulse12Cns
Setup time, boot configuration pins valid before RESET rising edge2Ens
Hold time, boot configuration pins valid after RESET rising edge0ns
The device has one oscillator input/output pair (MXI1/MXO1) usable with external crystals or ceramic
resonators to provide clock inputs. The optimal frequencies for the crystals are 19.2 MHz, 24 MHz, 27
MHz, and 36 MHz. Optionally, the oscillator inputs are configurable for use with external clock oscillators.
If external clock oscillators are used, to minimize the clock jitter, a single clean power supply should power
both the device and the external oscillator circuit and the minimum CLKIN rise and fall times must be
observed. The electrical requirements and characteristics are described in this section.
The timing parameters for CLKOUT[3:1] are also described in this section. The device has three output
clock pins (CLKOUT[3:1]). See Section 3.3 for more information on CLKOUT[3:1].
Note: Please ensure that the appropriate oscillator input pin (GIO81/OSCCFG) frequency range setting is
set correctly. For more details on this pin setting, see Section 3.7.6.
6.6.1MXI1 Oscillator
The MXI1 (typically 24 MHz, can also be 19.2 MHz, 27 MHz, or 36 MHz) oscillator provides the primary
reference clock for the device. The on-chip oscillator requires an external crystal connected across the
MXI1 and MXO1 pins, along with two load capacitors, as shown in Figure 6-5. The external crystal load
capacitors must be connected only to the oscillator ground pin (V
(VSS). Also, the PLL power pin (V
bead, L1 in the example circuit shown in Figure 6-5.
Note: If an external oscillator is to be used, the external oscillator clock signal should be connected to the
MXI1 pin with a 1.8V amplitude. The MXO1 should be left unconnected and the VSS_MX1 signal should
be connected to board ground (Vss).
DDA_PLL1
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
). Do not connect to board ground
SS_MX1
) should be connected to the power supply through a ferrite
The load capacitors, C1 and C2, should be chosen such that the equation is satisfied (typical values are
C1 = C2 = 10 pF). CL in the equation is the load specified by the crystal manufacturer. All discrete
components used to implement the oscillator circuit should be placed as close as possible to the
associated oscillator pins (MXI1 and MXO1) and to the V
Table 6-3. Switching Characteristics Over Recommended Operating Conditions for System Oscillator
PARAMETERMINTYPMAXUNIT
Start-up time (from power up until oscillating at stable frequency)2ms
Oscillation frequency19.2/24/2MHz
Crystal ESR19 - 30 MHz60Ω
30 - 36 MHz40Ω
Frequency stability+/-50ppm
7/36
6.6.2Clock PLL Electrical Data/Timing (Input and Output Clocks)
Table 6-4. Timing Requirements for MXI1/CLKIN1
NO
.
1t
c(MXI1)
2t
w(MXI1H)
3t
w(MXI1L)
4t
t(MXI1)
5t
J(MXI1)
(1) The reference points for the rise and fall transitions are measured at VILMAX and VIHMIN.
(2) C = MXI1/CLKIN1 cycle time in ns. For example, when MXI1/CLKIN1 frequency is 24 MHz use C = 41.6 ns.
(3) tc(MXI1) = 52.083 ns, tc(MXI1) = 41.6 ns, tc(MXI1) = 37.037 ns, and tc(MXI1) = 27.7 ns are the only supported cycle times for
MXI1/CLKIN1.
Cycle time, MXI1/CLKIN127.752.083ns
Pulse duration, MXI1/CLKIN1 high0.45C0.55Cns
Pulse duration, MXI1/CLKIN1 low0.45C0.55Cns
Transition time, MXI1/CLKIN1.05Cns
Period jitter, MXI1/CLKIN1.02Cns
Table 6-5. Switching Characteristics Over Recommended Operating Conditions for CLKOUT0/CLKOUT1
(2)
(see Figure 6-7)
NO.PARAMETERUNIT
1t
C(CLKOUT0/CLKOUT1)
2t
w(CLKOUT0H/CLKOUT1H)
3t
w(CLKOUT0L/CLKOUT1L)
4t
t(CLKOUT0/CLKOUT1)
5t
d(MXI1H-CLKOUT0H/CLKOUT1H)
6t
d(MXI1L-CLKOUT0L/CLKOUT1L)
Cycle time, CLKOUT0/CLKOUT127.7ns
Pulse duration, CLKOUT0/CLKOUT1 high.45P.55Pns
Pulse duration, CLKOUT0/CLKOUT1 low.45P.55Pns
Transition time, CLKOUT0/CLKOUT13ns
Delay time, MXI1/CLKIN1 high to CLKOUT0/CLKOUT1
high
Delay time, MXI1/CLKIN1I low to CLKOUT0/CLKOUT1
low
SPRS668B–APRIL 2010–REVISED NOVEMBER 2010
DEVICE
MINTYPMAX
18ns
18ns
(1) The reference points for the rise and fall transitions are measured at VOLMAX and VOHMIN.
(2) P = 1/CLKOUT0/1 clock frequency in nanoseconds (ns). For example, when CLKOUT1 frequency is 24 MHz use P = 41.6 ns.
(1)
Figure 6-7. CLKOUT1 Timing
Table 6-6. Switching Characteristics Over Recommended Operating Conditions for CLKOUT2
Figure 6-8)
NO.PARAMETERUNIT
1t
C(CLKOUT2)
2t
w(CLKOUT2H)
3t
w(CLKOUT2L)
4t
t(CLKOUT2)
t
d(MXI1H-
5Delay time, MXI1/CLKIN1 high to CLKOUT2 high18ns
CLKOUT2H)
t
d(MXI1L-
6Delay time, MXI1/CLKIN1 low to CLKOUT2 low18ns
CLKOUT2L)
Cycle time, CLKOUT220ns
Pulse duration, CLKOUT2 high.45P.55Pns
Pulse duration, CLKOUT2 low.45P.55Pns
Transition time, CLKOUT23ns
MINTYPMAX
(1) The reference points for the rise and fall transitions are measured at VOLMAX and VOHMIN.
(2) P = 1/CLKOUT2 clock frequency in nanoseconds (ns). For example, when CLKOUT2 frequency is 8 MHz use P = 125 ns.
The device has an PRTCSS oscillator input/output pair (RTCXI/RTCXO) usable with external crystals or
ceramic resonators to provide clock inputs. The optimal frequency for the crystal is 32.768 kHz. The
electrical requirements and characteristics are described in this section. Figure 6-9 shows an example
circuit.
www.ti.com
Figure 6-9. RTCXI1 Oscillator
The load capacitors, C1 and C2, should be chosen such that the equation is satisfied (typical values are
C1 = C2 = 2 fF). CLin the equation below is the load specified by the crystal manufacturer. All discrete
components used to implement the oscillator circuit should be placed as close as possible to the
associated oscillator pins (RTCXI and RTCXO) and to the V
SS_32K
pin.
6.6.4PRTCSS Electrical Data/Timing
Table 6-7. Timing Requirements for RTCXI
NO.
1t
c(RTCXI)
2t
w(RTCXIH)
3t
w(RTCXIL)
(1) The reference points for the rise and fall transitions are measured at VILMAX and VIHMIN.
(2) C = MXI1/CLKIN1 cycle time in ns. For example, when MXI1/CLKIN1 frequency is 24 MHz use C = 41.6 ns.
Table 6-8. Switching Characteristics Over Recommended Operating Conditions for RTC Oscillator
PARAMETERMINTYPMAXUNIT
Start-up time (from power up until oscillating at stable frequency)0.852s
Oscillation frequency32.768kHz
Crystal ESR70kΩ
Frequency stability+/- 50ppm
The load capacitors, C1 and C2, should be chosen such that the equation is satisfied (typical values are
C1 = C2 = 2 fF). CL in the equation is the load specified by the crystal manufacturer. All discrete
components used to implement the oscillator circuit should be placed as close as possible to the
associated oscillator pins (RTCXI and RTCXO) and to the V
SS_MX1
pin.
6.7Power Management and Real Time Clock Subsystem (PRTCSS)
The Power Management and Real Time Clock Subsystem (PRTCSS) is used for calendar applications.
The PRTCSS has an independent power supply and can remain ON while the rest of the power supply is
turned OFF. The PRTCSS supports the following features:
•Real Time Clock (RTC)
– Simple day counter (Up to 89-years)
– To generate the Alarm event to check the RTC count
– 16-bit simple timer
– Watch-dog timer to generate the event for RTC-Sequencer
The following table lists the PRTCSS Interface registers (PRTCIF) and Table 6-10 lists the PRTCSS
registers which can only be accessed via the PRTCIF registers, their corresponding acronyms, and device
memory locations (offsets). For more details, see the TMS320DM36x PRTCSS User's Guide (literature
number SPRUFJ0).
Table 6-9. PRTC Interface (PRTCIF) Registers
OffsetAcronymRegister Description
0x0PIDPRTCIF peripheral ID register
0x4PRTCIF_CTRLPRTCIF control register
0x8PRTCIF_LDATAPRTCIF access lower data register
0xCPRTCIF_UDATAPRTCIF access upper data register
0x10PRTCIF_INTENPRTCIF interrupt enable register
0x14PRTCIF_INTFLGPRTCIF interrupt flag register
Table 6-10. Power Management and Real Time Clock Subsystem (PRTCSS) Registers
OffsetAcronymRegister Description
0x0GO_OUTGlobal output pin output data register
0x1GIO_OUTGlobal input/output pin output data register
0x2GIO_DIRGlobal input/output pin direction register
0x3GIO_INGlobal input/output pin input data register
Table 6-10. Power Management and Real Time Clock Subsystem (PRTCSS) Registers (continued)
OffsetAcronymRegister Description
0x4GIO_FUNCGlobal input/output pin function register
0x5GIO_RISE_INT_ENGIO rise interrupt enable register
0x6GIO_FALL_INT_ENGIO fall interrupt enable register
0x7GIO_RISE_INT_FLGGIO rise interrupt flag register
0x8GIO_FALL_INT_FLGGIO fall interrupt flag register
The GPIO peripheral provides general-purpose pins that can be configured as either inputs or outputs.
When configured as an output, a write to an internal register can control the state driven on the output pin.
When configured as an input, the state of the input is detectable by reading the state of an internal
register. In addition, the GPIO peripheral can produce CPU interrupts and EDMA events in different
interrupt/event generation modes. The GPIO peripheral provides generic connections to external devices.
The GPIO pins are grouped into banks of 16 pins per bank (i.e., bank 0 consists of GPIO [0:15]). There
are a total of 7 GPIO banks in the device, because the device has 104 GPIOs. For additional details on
GPIO pins voltage level and the associated power supply please see Table 6-11.
Table 6-11. GPIO Pin Voltage Level and Power Supply Reference
Voltage Level1.8 V or 3.3 V3.3 V1.8 V
Power Supply NameV
•Up to 7 GPIO pins dedicated to the PRTC Subsystem. These pins are labeled as PWRCTRIO[6:0].
Only PWRCTRIO[2:0] are connected to the GPIO module, labeled as GPIO[106:104]. For the PRTCSS
module the PWRCTRIO[6:0] pins support input and output functionality but for the GPIO module the
GPIO[106:104] pins support input functionality only. For more details please refer to Section 6.7.
•Interrupts:
– Up to 15 unique GPIO[15:0] interrupts from Bank 0.
– Up to 3 unique GPIO[106:104] interrupts from Bank 6, dedicated to the PRTC Subsystem. For
more details please refer to Section 6.7.
– Interrupts can be triggered by rising and/or falling edge, specified for each interrupt capable GPIO
signal
•DMA events:
– Up to 15 unique GPIO DMA events from Bank 0
•Set/clear functionality: Firmware writes 1 to corresponding bit position(s) to set or to clear GPIO
signal(s). This allows multiple firmware processes to toggle GPIO output signals without critical section
protection (disable interrupts, program GPIO, re-enable interrupts, to prevent context switching to
anther process during GPIO programming).
•Separate Input/Output registers
•Output register in addition to set/clear so that, if preferred by firmware, some GPIO output signals can
be toggled by direct write to the output register(s).
•Output register, when read, reflects output drive status. This, in addition to the input register reflecting
pin status, allows wired logic be implemented.
V
DD_AEMIF2_18_33
V
DD_ISIF18_33
V
DDS33
V
DD18_PRTCSS
For more detailed information on GPIOs, see the Documentation Support section for the General-Purpose
Input/Output (GPIO) Reference Guide.
10hDIR01GPIO Banks 0 and 1 Direction Register
14hOUT_DATA01GPIO Banks 0 and 1 Output Data Register
18hSET_DATA01GPIO Banks 0 and 1 Set Data Register
1ChCLR_DATA01GPIO Banks 0 and 1 Clear Data Register
20hIN_DATA01GPIO Banks 0 and 1 Input Data Register
24hSET_RIS_TRIGGPIO Set Rising Edge Interrupt Register
28hCLR_RIS_TRIGGPIO Clear Rising Edge Interrupt Register
2ChSET_FAL_TRIGGPIO Set Falling Edge Interrupt Register
30hCLR_FAL_TRIGGPIO Clear Falling Edge Interrupt Register
34hINTSTATGPIO Interrupt Status Register
GPIO Banks 2 and 3
38hDIR23GPIO Banks 2 and 3 Direction Register
3ChOUT_DATA23GPIO Banks 2 and 3 Output Data Register
40hSET_DATA23GPIO Banks 2 and 3 Set Data Register
44hCLR_DATA23GPIO Banks 2 and 3 Clear Data Register
48hIN_DATA23GPIO Banks 2 and 3 Input Data Register
GPIO Bank 4 and 5
60hDIR45GPIO Bank 4 and 5 Direction Register
64hOUT_DATA45GPIO Bank 4 and 5 Output Data Register
68hSET_DATA45GPIO Bank 4 and 5 Set Data Register
6ChCLR_DATA45GPIO Bank 4 and 5 Clear Data Register
70hIN_DATA45GPIO Bank 4 and 5 Input Data Register
GPIO Bank 6
88hDIR6GPIO Bank 6 Direction Register
8ChOUT_DATA6GPIO Bank 6 Output Data Register
90hSET_DATA6GPIO Bank 6 Set Data Register
94hCLR_DATA6GPIO Bank 6 Clear Data Register
98hIN_DATA6GPIO Bank 6 Input Data Register
Table 6-15. Timing Requirements for External Interrupts/EDMA Events
NO.UNIT
1t
w(ILOW)
2t
w(IHIGH)
(1) The pulse width given is sufficient to generate an interrupt or an EDMA event. However, if a user wants the device to recognize the
GPIO changes through software polling of the GPIO register, the GPIO duration must be extended to allow the device enough time to
access the GPIO register through the internal bus.
(2) P = PLLC1.SYSCLK4 period, where SYSCLK4 is an output clock of PLLC1. For more details, see Section 3.3, Device Clocking.
Width of the external interrupt pulse low2P
Width of the external interrupt pulse high2P
(1)
(see Figure 6-12)
DEVICE
MINMAX
(2)
(2)
ns
ns
Figure 6-12. GPIO External Interrupt Timing
6.9EDMA Controller
The EDMA controller handles all data transfers between memories and the device slave peripherals on
the device. These are summarized as follows:
The EDMA Controller consists of two major blocks: the Transfer Controller (TC) and the Channel
Controller (CC). The CC is a highly flexible Channel Controller that serves as the user interface and event
interface for the EDMA system. The CC supports 64-event channels and 8 QDMA channels. The CC
consists of a scalable Parameter RAM (PaRAM) that supports flexible ping-pong, circular buffering,
channel-chaining, auto-reloading, and memory protection.
The EDMA Channel Controller has the following features:
•Fully orthogonal transfer description
– Three transfer dimensions
– A-synchronized transfers: one dimension serviced per event
– AB- synchronized transfers: two dimensions serviced per event
– Independent indexes on source and destination
– Chaining feature allows 3-D transfer based on single event
•Flexible transfer definition
– Increment and constant addressing modes
– Linking mechanism allows automatic PaRAM set update
– Chaining allows multiple transfers to execute with one event
•Debug visibility
– Queue watermarking/threshold
– Error and status recording to facilitate debug
•64 DMA channels
– Event synchronization
– Manual synchronization (CPU(s) write to event set register)
– Chain synchronization (completion of one transfer chains to next)
•8 QDMA channels
– QDMA channels are triggered automatically upon writing to a PaRAM set entry
– Support for programmable QDMA channel to PaRAM mapping
•256 PaRAM sets
– Each PaRAM set can be used for a DMA channel, QDMA channel, or link set (remaining)
•Four transfer controllers/event queues. The system-level priority of these queues is user programmable
•16 event entries per event queue
•External events (for example, McBSP TX Evt and RX Evt)
The EDMA Transfer Controller has the following features:
www.ti.com
•Four transfer controllers
•64-bit wide read and write ports per channel
•Up to four in-flight transfer requests (TR)
•Programmable priority level
•Supports two dimensional transfers with independent indexes on source and destination (EDMA
Channel Controller manages the 3rd dimension)
•Support for increment and constant addressing modes
•Interrupt and error support
Parameter RAM: Each EDMA is specified by an eight word (32-byte) parameter table contained in
Parameter RAM (PaRAM) within the CC. The device provides 256 PaRAM entries, one for each of the 64
DMA channels and for 8 QDMA / Linked DMA entries.
DMA Channels: Can be triggered by: " External events (for example, McBSP TX Evt and RX Evt), "
Software writing a '1' to the given bit location, or channel, of the Event Set register, or, " Chaining to other
DMAs.
QDMA: The Quick DMA (QDMA) function is contained within the CC. The device implements 8 QDMA
channels. Each QDMA channel has a selectable PaRAM entry used to specify the transfer. A QDMA
transfer is submitted immediately upon writing of the "trigger" parameter (as opposed to the occurrence of
an event as with EDMA). The QDMA parameter RAM may be written by any Config bus master through
the Config Bus and by DMAs through the Config Bus bridge.
QDMA Channels: Triggered by a configuration bus write to a designated 'QDMA trigger word'. QDMAs
allow a minimum number of linear writes (optimized for GEM IDMA feature) to be issued to the CC to
force a series of transfers to take place.
6.9.1EDMA Channel Synchronization Events
The EDMA supports up to 64 EDMA channels which service peripheral devices and external memory.
Table 6-16 lists the source of EDMA synchronization events associated with each of the programmable
EDMA channels. For the device, the association of an event to a channel is fixed; each of the EDMA
channels has one specific event associated with it. These specific events are captured in the EDMA event
registers (ER, ERH) even if the events are disabled by the EDMA event enable registers (EER, EERH).
For more detailed information on the EDMA module and how EDMA events are enabled, captured,
processed, linked, chained, and cleared, etc., see the Document Support section for the Enhanced Direct
Memory Access (EDMA) Controller Reference Guide.
(1) In addition to the events shown in this table, each of the 64 channels can also be synchronized with the transfer completion or
intermediate transfer completion events. For more detailed information on EDMA event-transfer chaining, see the Document Support
section for the Enhanced Direct Memory Access (EDMA) Controller Reference Guide.
(2) The total number of EDMA events exceeds 64, which is the maximum value of the EDMA module. Therefore, several events are
multiplexed and you must use the register EDMA_EVTMUX in the System Control Module to select the event source for multiplexed
events. Refer to the TMS320DM36x DMSoC ARM Subsystem Reference Guide (literature number SPRUFG5) for more information on
the System Control Module register EDMA_EVTMUX.
0320hEEVALError Evaluate Register
0340hDRAE0DMA Region Access Enable Register for Region 0
0344hDRAEH0DMA Region Access Enable Register High for Region 0
...
0350hDRAE2DMA Region Access Enable Register for Region 2
0354hDRAEH2DMA Region Access Enable Register High for Region 2
0360hDRAE4DMA Region Access Enable Register for Region 4
0364hDRAEH4DMA Region Access Enable Register High for Region 4
0368hDRAE5DMA Region Access Enable Register for Region 5
036ChDRAEH5DMA Region Access Enable Register High for Region 5
0380hQRAE0QDMA Region Access Enable Register for Region 0
0388hQRAE2QDMA Region Access Enable Register for Region 2
0390hQRAE4
0394hQRAE5
2E00h-2E94hShadow Region 7 Channel Registers
4000h-4FFFh—Parameter RAM (PaRAM)
Table 6-18 shows an abbreviation of the set of registers which make up the parameter set for each of 512
EDMA events. Each of the parameter register sets consist of 8 32-bit word entries. Table 6-19 shows the
parameter set entry registers with relative memory address locations within each of the parameter sets.
0x01C0 4000 - 0x01C0 401FParameters Set 0 (8 32-bit words)
0x01C0 4020 - 0x01C0 403FParameters Set 1 (8 32-bit words)
0x01C0 4040 - 0x01C0 405FParameters Set 2 (8 32-bit words)
0x01C0 4060 - 0x01C0 407FParameters Set 3 (8 32-bit words)
0x01C0 4080 - 0x01C0 409FParameters Set 4 (8 32-bit words)
0x01C0 40A0 - 0x01C0 40BFParameters Set 5 (8 32-bit words)
......
0x01C0 7FC0 - 0x01C0 7FDFParameters Set 510 (8 32-bit words)
0x01C0 7FE0 - 0x01C0 7FFFParameters Set 511 (8 32-bit words)
HEX OFFSET ADDRESS
WITHIN THE PARAMETER SET
0x0000OPTOption
0x0004SRCSource Address
0x0008A_B_CNTA Count, B Count
0x000CDSTDestination Address
0x0010SRC_DST_BIDXSource B Index, Destination B Index
0x0014LINK_BCNTRLDLink Address, B Count Reload
0x0018SRC_DST_CIDXSource C Index, Destination C Index