System-On-Chip (DMSoC)
– Up to 216-MHz ARM926EJ-S™ Clock Rate
– Digital HDTV (720p/1080i) output for
connection to external encoder– 32K-Byte RAM
– Video Processing Subsystem– 8K-Byte ROM
•Hardware IPIPE for Real-Time Image– Little Endian
Processing
•Up to 14-bit CCD/CMOS Digital Interface
•Histogram Module
•Resize Image 1/16x to 8xProcessing
•Hardware On-Screen Display•Up to 14-bit CCD/CMOS Digital Interface
•Up to 75-MHz Pixel Clock•16-/8-bit Generic YcBcR-4:2 Interface
•Composite NTSC/PAL video encoder
output•10-/8-bit CCIR6565/BT655 Interface
– Peripherals include DDR and mDDR SDRAM,•Up to 75-MHz Pixel Clock
2 MMC/SD/SDIO and SmartMedia Flash Card
Interfaces, USB 2.0, 3 UARTs and 3 SPIs
– Enhanced Direct-Memory-Access (EDMA)
– Configurable Power-Saving Modes
– On-Chip ARM ROM Bootloader (RBL) to Boot
From NAND Flash, MMC/SD, or UART
– 3.3-V and 1.8-V I/O, 1.3-V Core
– Debug Interface Support
– Up to 104 General-Purpose I/O (GPIO) Pins
– 337-Pin Ball Grid Array at 65 nm Process
Technology
• High-Performance Digital Media
System-on-Chip (DMSoC)
– 135-, 216-MHz ARM926EJ-S™ Clock Rate
– Fully Software-Compatible With ARM™
– Extended Temperature 135- and 216-MHz
Devices are Available
• ARM926EJ-S Core
– Support for 32-Bit and 16-Bit (Thumb Mode)
Instruction Sets
– DSP Instruction Extensions and Single Cycle
MAC
– ARM® Jazelle® Technology
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.
2Windows is a trademark of Microsoft.
3All other 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 testing of all parameters.
– Two Multimedia Card (MMC) / Secure Digital• Four Pulse Width Modulator (PWM) Outputs
(SD/SDIO)
– SmartMedia
• Four RTO (Real Time Out) Outputs
• Up to 104 General-Purpose I/O (GPIO) Pins
• Enhanced Direct-Memory-Access (EDMA)(Multiplexed with Other Device Functions)
Controller (64 Independent Channels)
• On-Chip ARM ROM Bootloader (RBL) to Boot
• USB Port with Integrated 2.0 High-Speed PHYfrom NAND Flash (with SPI EEPROM Boot
that Supportsoption), MMC/SD, or UART
– USB 2.0 Full and High-Speed Device• Configurable Power-Saving Modes
– USB 2.0 Low, Full, and High-Speed Host• Crystal or External Clock Input (typically
• Three 64-Bit General-Purpose Timers (each
24 MHz or 36 MHz)
configurable as two 32-bit timers)• Flexible PLL Clock Generators
• One 64-Bit Watch Dog Timer• Debug Interface Support
• Three UARTs (One fast UART with RTS and– IEEE-1149.1 (JTAG)
CTS Flow Control)Boundary-Scan-Compatible
• Three Serial Port Interfaces (SPI) each with two– ETB™ (Embedded Trace Buffer™) with
Chip-Selects4K-Bytes Trace Buffer memory
• One Master/Slave Inter-Integrated Circuit (I2C)– Device Revision ID Readable by ARM
Bus®
• 337-Pin Ball Grid Array (BGA) Package
• Two Audio Serial Port (ASP)(ZCE Suffix), 0.65-mm Ball Pitch
– I2S and TDM I2S• 90nm Process Technology
– AC97 Audio Codec Interface• 3.3-V and 1.8-V I/O, 1.3-V Internal
– S/PDIF via Software• Community Resources
– Standard Voice Codec Interface (AIC12)– TI E2E Community
– SPI Protocol (Master Mode Only)– TI Embedded Processors Wiki
The DM335 processor is a low-cost, low-power processor providing advanced graphical user interface for
display applications that do not require video compression and decompression. Coupled with a video
processing subsystem (VPSS) that provides 720p display, the DM335 processor is powered by a
135/216-MHz ARM926EJ-S core so developers can create feature-rich graphical user interfaces allowing
customers to interact with their portable, electronic devices such as video-enabled universal remote
controls, Internet radio, e-books, video doorbells, and digital telescopes. The new DM335 is packed with
the same peripherals as its predecessor, the TMS320DM355 device, including high-speed USB 2.0
on-the-go, external memory interface (EMIF), mobile DDR/DDR2, two SDIO ports, three UART Ports, two
Audio Serial Ports, three SPI Ports, and SLC/MCL NAND Flash memory support. These peripherals help
customers create DM335 processor-based designs that add video and audio excitement to a wide range
of today's static user-interface applications while keeping silicon costs and power consumption low. The
new digital media processor is completely scalable with the DM355 processor and Digital Video Evaluation
Board (DVEVM), allowing customers to utilize their same code for their new DM335 processor focused
designs.
The new DM335 device delivers a sophisticated suite of capabilities allowing for flexible image capture
and display. Through its user interface technology, such as a four-level on-screen display, developers are
able to create picture-within-picture and video-within-video as well as innovative graphic user interfaces.
This is especially important for portable products that require the use of button or touch screen, such as
portable karaoke, video surveillance and electronic gaming applications. Additional advanced capture and
imaging technologies include support for CCD/CMOS image sensors, resize capability and video
stabilization. The 1280-by-960-pixel digital LCD connection runs on a 75-MHz pixel clock and supports TV
composite output for increased expandability. This highly integrated device is packaged in a 13 x 13 mm,
337 pin , 0.65 mm pitch BGA package.
SPRS528C–JULY 2008–REVISED JUNE 2010
The DM335 processor core is an ARM926EJ-S RISC processor. The ARM926EJ-S is a 32-bit processor
core that performs 32-bit and 16-bit instructions and processes 32-bit, 16-bit, and 8-bit data. The core
uses pipelining so that all parts of the processor and memory system can operate continuously. The ARM
core incorporates:
•A coprocessor 15 (CP15) and protection module
•Data and program Memory Management Units (MMUs) with table look-aside buffers.
•Separate 16K-byte instruction and 8K-byte data caches. Both are four-way associative with virtual
index virtual tag (VIVT).
The DM335 device has a Video Processing Subsystem (VPSS) with two configurable video/imaging
peripherals:
•A Video Processing Front-End (VPFE)
•A Video Processing Back-End (VPBE)
The VPFE port provides an interface for CCD/CMOS imager modules and video decoders. The VPBE
provides hardware On Screen Display (OSD) support and composite NTSC/PAL and digital LCD output.
The DM335 peripheral set includes:
•An inter-integrated circuit (I2C) Bus interface
•Two audio serial ports (ASP)
•Three 64-bit general-purpose timers each configurable as two independent 32-bit timers
•A 64-bit watchdog timer
•Up to 104-pins of general-purpose input/output (GPIO) with programmable interrupt/event generation
modes, multiplexed with other peripherals
•Three UARTs with hardware handshaking support on one UART
•Two Multi-Media Card / Secure Digital (MMC/SD/SDIO) interfaces
•Wireless interfaces (Bluetooth, WLAN, WUSB) through SDIO
•A USB 2.0 full and high-speed device and host interface
•Two external memory interfaces:
– An asynchronous external memory interface (AEMIF) for slower memories/peripherals such as
NAND and OneNAND,
– A high speed synchronous memory interface for DDR2/mDDR.
For software development support the DM335 has a complete set of ARM development tools which
include: C compilers, assembly optimizers to simplify programming and scheduling, and a Windows™
debugger interface for visibility into source code execution.
1.3Functional Block Diagram
The below figure shows the functional block diagram of the DM335 device.
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
This data sheet revision history highlights the technical changes made to the SPRS528B device-specific
data sheet to make it an SPRS528C revision.
Scope: Applicable updates to the DM335 device family, specifically relating to the DM335 device, have
been incorporated. The A135 and A216 DM335 devices both support extended temperature.
GlobalAdded SPI EEPROM Boot option to NAND.
Section 1.1Changed Feature bullet from NAND Flash to NAND Flash (with SPI EEPROM Boot option).
Section 2.4Table 2-9 and Table 2-11:
Table 3-15Updated BTSEL Function and NAND configuration in table.
Table 3-16Updated table:
Section 3.12Added Section 3.12.2, "RBL NAND Boot Process" and associated Standard and Compatibility
Section 3.12.1Added ARM ROM Boot - SPI boot in NAND Mode bullet and sub-bullets.
Figure 3-6Added SPI Flash to Diagram.
Section 4.2Added last row to table including table note.
Section 4.3Updated/Changed the following values in Section 4.3:
Table 5-5Changed parameter 4 on table and added table note.
Table 5-6Changed parameter 4 on table and added table note.
Table 5-45Changed parameter 4 on table and added table note.
Section 5.7.1.3Added note to Table 5-14.
www.ti.com
Revision History
Revision C Updates
ADDS/CHANGES/DELETES
•Added "Used to drive boot status LED signal (active low) in ROM boot modes." to pin number
P16.
•Deleted "Used to drive boot status LED signal (active low) in ROM boot modes." from pin
number V19.
•Updated/Changed "(/2 or /1 programmable)" to "POSTDIV" and added "(/2 or /1
programmable)" to 2nd row.
Table 2-3 shows the memory map address ranges of the device. Table 2-3 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, USB, and VPSS.
Table 2-3. DM335 ARM Configuration Bus Access to Peripherals (continued)
Reserved0x0C00 00000x0FFF FFFF64M√√
2.3Pin 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.3.1Pin Map (Bottom View)
Figure 2-1 through Figure 2-4 show the pin assignments in four quadrants (A, B, C, and D). Note that
micro-vias are not required. Contact your TI representative for routing recommendations.
The pin functions tables (Table 2-4 through Table 2-22) identify the external signal names, the associated
pin (ball) numbers along with the mechanical package designator, the pin type, whether the pin has any
internal pullup or pulldown resistors, and a functional pin description. For more detailed information on
device configuration, peripheral selection, multiplexed/shared pins, and debugging considerations, see
Section 3. For the list of all pin in chronological order see Section 2.20
2.4.1Image Data Input - Video Processing Front End
The CCD Controller module in the Video Processing Front End has an external signal interface for image
data input. It supports YUV (YC) inputs as well as Bayer RGB and complementary input signals (I.e.,
image data input).
The definition of the CCD controller data input signals depend on the input mode selected.
•In 16-bit YCbCr mode, the Cb and Cr signals are multiplexed on the Cl signals and the order is
configurable (i.e., Cb first or Cr first).
•In 8-bit YCbCr mode, the Y, Cb, and Cr signals are multiplexed and not only is the order selectable,
but also the half of the bus used.
Table 2-4. CCD Controller Signals for Each Input Mode
CIN5/•YCC 16-bit: Time multiplexed between chroma: CB/SR[05]
GIO099/PD
SPI2_SDENV
M3I/O/Z
A[0]
CIN4/•YCC 16-bit: Time multiplexed between chroma: CB/SR[04]
GIO098/PD
SPI2_SDENV
L4I/O/Z
A[1]
CIN3/PD
GIO097/V
CIN2/PD
GIO096/V
CIN1/PD
GIO095/V
CIN0/PD
GIO094/V
YIN7/PD
GIO093V
YIN6/PD
GIO092V
J4I/O/Z
J5I/O/Z
L3I/O/Z
J3I/O/Z
L5I/O/Z
M4I/O/Z
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
Standard CCD/CMOS input: NOT USED
•YCC 16-bit: Time multiplexed between chroma: CB/SR[07]
PD
V
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[07]
SPI: SPI2 Clock
GIO: GIO[101]
Standard CCD/CMOS input: NOT USED
•YCC 16-bit: Time multiplexed between chroma: CB/SR[06]
PD
V
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[06]
SPI: SPI2 Data Out
GIO: GIO[100]
Standard CCD/CMOS input: Raw[13]
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
DD_VIN
multiplexed between luma and chroma of the upper channel. Y/CB/CR[05]
SPI: SPI2 Chip Select
GIO: GIO[099]
Standard CCD/CMOS input: Raw[12]
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
DD_VIN
multiplexed between luma and chroma of the upper channel. Y/CB/CR[04]
SPI: SPI2 Data In
GIO: GIO[098]
Standard CCD/CMOS input(AFE): Raw[11]
•YCC 16-bit: Time multiplexed between chroma: CB/SR[03]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[03]
GIO: GIO[097]
Standard CCD/CMOS input: Raw[10]
•YCC 16-bit: Time multiplexed between chroma: CB/SR[02]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[02]
GIO: GIO[097]
Standard CCD/CMOS input: Raw[09]
•YCC 16-bit: Time multiplexed between chroma: CB/SR[01]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[01]
GIO: GIO[095]
Standard CCD/CMOS input: Raw[08]
•YCC 16-bit: Time multiplexed between chroma: CB/SR[00]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[00]
GIO: GIO[094]
Standard CCD/CMOS input: Raw[07]
•YCC 16-bit: Time multiplexed between chroma: Y[07]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[07]
GIO: GIO[093]
Standard CCD/CMOS input: Raw[06]
•YCC 16-bit: Time multiplexed between chroma: Y[06]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[06]
GIO: GIO[092]
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal.
(2) PD = internal pull-down, PU = internal pull-up. (To pull up a signal to the opposite supply rail, a 1 kΩ resistor should be used.)
(3) Specifies the operating I/O supply voltage for each signal. See Section 5.3 , Power Supplies for more detail.
N5I/O/Zoutput (master mode). Tells the CCDC when a new line starts.
R4I/O/Z(master mode). Tells the CCDC when a new frame starts.
CAM_WEN
_FIELD\R5I/O/Z
GIO083
PCLK/PDPixel clock input (strobe for lines C17 through Y10)
GIO082V
T3I/O/Z
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
Standard CCD/CMOS input: Raw[05]
•YCC 16-bit: Time multiplexed between chroma: Y[05]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[05]
GIO: GIO[091]
Standard CCD/CMOS input: Raw[04]
•YCC 16-bit: Time multiplexed between chroma: Y[04]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[04]
GIO: GIO[090]
Standard CCD/CMOS input: Raw[03]
•YCC 16-bit: Time multiplexed between chroma: Y[03]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[03]
GIO: GIO[089]
Standard CCD/CMOS input: Raw[02]
•YCC 16-bit: Time multiplexed between chroma: Y[02]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[02]
GIO: GIO[088]
Standard CCD/CMOS input: Raw[01]
•YCC 16-bit: Time multiplexed between chroma: Y[01]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[01]
GIO: GIO[087]
Standard CCD/CMOS input: Raw[00]
•YCC 16-bit: Time multiplexed between chroma: Y[00]
DD_VIN
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is time
multiplexed between luma and chroma of the upper channel. Y/CB/CR[00]
GIO: GIO[086]
Horizontal synchronization signal that can be either an input (slave mode) or an
DD_VIN
GIO: GIO[085]
Vertical synchronization signal that can be either an input (slave mode) or an output
DD_VIN
GIO: GIO[084]
Write enable input signal is used by external device (AFE/TG) to gate the DDR
output of the CCDC module. Alternately, the field identification input signal is used
PDby external device (AFE/TG) to indicate which of two frames is input to the CCDC
V
DD_VIN
module for sensors with interlaced output. CCDC handles 1- or 2-field sensors in
hardware.
GIO: GIO[083]
DD_VIN
GIO: GIO[0082]
www.ti.com
2.5Image Data Output - Video Processing Back End (VPBE)
The Video Encoder/Digital LCD interface module in the video processing back end has an external signal
interface for digital image data output as described in Table 2-7 and Table 2-8.
The digital image data output signals support multiple functions / interfaces, depending on the display
mode selected. The following table describes these modes. Parallel RGB mode with more than RGB565
signals requires enabling pin multiplexing to support (i.e., for RGB666 mode).
E4I/O/ZV
RTO3
COUT1-B4 /Digital Video Out: VENC settings determine function
GIO075 /F3I/O/ZV
PWM3APWM3A
COUT0-B3 /Digital Video Out: VENC settings determine function
GIO074 /F4I/O/ZV
PWM3BPWM3B
HSYNC /PDVideo Encoder: Horizontal Sync
GIO073V
VSYNC /PDVideo Encoder: Vertical Sync
GIO072V
F5I/O/Z
G5I/O/Z
FIELD /Video Encoder: Field identifier for interlaced display formats
GIO070 /GIO: GIO[070]
R2 /Digital Video Out: R2
H4I/O/ZV
PWM3CPWM3C
EXTCLK /
GIO069 /PD
B2 /V
G3I/O/ZGIO: GIO[069]
PWM3D
VCLK /Video Encoder: Video Output Clock
GIO068GIO: GIO[068]
H3I/O/ZV
(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 5.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 DM335: YOUT(0-7),COUT(0-7), HSYNC,VSYNC,LCD_OE,FIELD,EXTCLK,VCLK. The trace lengths
should be minimized.
Digital Video Out: VENC settings determine function
Digital Video Out: VENC settings determine function
Digital Video Out: VENC settings determine function
Digital Video Out: VENC settings determine function
Digital Video Out: VENC settings determine function
Digital Video Out: VENC settings determine function
Digital Video Out: VENC settings determine function
Digital Video Out: VENC settings determine function
Digital Video Out: VENC settings determine function GIO: GIO[081] PWM0
Digital Video Out: VENC settings determine function GIO: GIO[080] PWM1
Digital Video Out: VENC settings determine function GIO: GIO[079] PWM2A RTO0
Digital Video Out: VENC settings determine function GIO: GIO[078] PWM2B RTO1
Digital Video Out: VENC settings determine function GIO: GIO[077] PWM2C RTO2
Digital Video Out: VENC settings determine function GIO: GIO[076] PWM2D RTO3
GIO: GIO[075]
GIO: GIO[074]
GIO: GIO[073]
GIO: GIO[072]
Video Encoder: External clock input, used if clock rates > 27 MHz are needed, e.g.
EM_A13/Async EMIF: Address bus bit[13]
GIO067/V19I/O/ZGIO: GIO[67]
BTSEL[1]System: BTSEL[1:0] sampled at power-on-reset to determine boot method.
EM_A12/Async EMIF: Address bus bit[12]
GIO066/U19I/O/ZGIO: GIO[66]
BTSEL[0]System: BTSEL[1:0] sampled at power-on-reset to determine boot method.
EM_A11/
GIO065/R16I/O/Z
AECFG[3]
EM_A10/GIO: GIO[64]
GIO064/R18I/O/ZAECFG[3:0] sampled at power-on-reset to AECFG configuration. AECFG[2:1]
AECFG[2]sets default for PinMux2_EM_BA0: AEMIF EM_BA0 definition (EM_BA0,
EM_A09/GIO: GIO[63]
GIO063/P17I/O/ZAECFG[3:0] sampled at power-on-reset to AECFG configuration. AECFG[2:1]
AECFG[1]sets default for PinMux2_EM_BA0: AEMIF EM_BA0 definition (EM_BA0,
EM_A08/
GIO062/T19I/O/Z
AECFG[0]•PinMux2_EM_A0_BA1: AEMIF address width (OneNAND or NAND)
EM_A07/
GIO061
P16I/O/ZV
(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 5.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.)
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
PD
V
DD
PD
V
DD
Async EMIF: Address bus bit[11]
PUGIO: GIO[65]
V
DD
AECFG[3:0] sampled at power-on-reset to AECFG configuration. AECFG[3] sets
default for PinMux2_EM_D15_8: AEMIF default bus width (16 or 8 bits)
Async EMIF: Address bus bit[10]
PU
V
DD
EM_A14, GIO[054], rsvd)
Async EMIF: Address bus bit[09]
PD
V
DD
EM_A14, GIO[054], rsvd)
Async EMIF: Address bus bit[08]
GIO: GIO[62]
AECFG[0] sets default for:
V
PD
DD
•PinMux2_EM_A13_3: AEMIF address width (OneNAND or NAND)
Async EMIF: Address bus bit[07]
DD
GIO: GIO[61]
Used to drive boot status LED signal (active low) in ROM boot modes.
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 outputs:
•DDR_DQM[1] - For DDR_DQ[15:8]
•DDR_DQM[0] - 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 DDR when writing and inputs when
reading.
•DDR_DQS[1] - For DDR_DQ[15:8]
•DDR_DQS[0] - For DDR_DQ[7:0]
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
(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 5.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.)
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: Voltage input for the SSTL_18 I/O buffers. Note even in the case of
mDDR an external resistor divider connected to this pin is necessary.
DDR: Ground for the DDR DLL
DDR: Power (3.3 V) for the DDR DLL
DDR: Reference output for drive strength calibration of N and P channel
outputs. Tie to ground via 50 ohm resistor @ 0.5% tolerance.
_DATA0 /MMCSD1: DATA0
GIO019 /A18I/O/ZV
UART2_TUART2: Transmit Data
XD
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
GIO:GIO[000] is sampled at reset and stored in the GIO0_RESET bit of the
BOOTCFG register.
DD
Active low during MMC/SD boot (can be used as MMC/SD power control).
Can be used as external clock input for Timer 3.
Note: The GIO000 pin must be held high during NAND boot for the boot
process to fuction properly.
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
GIO: GIO[001] Can be used as external clock input for Timer 3.
GIO: GIO[002] Can be used as external clock input for Timer 3.
GIO: GIO[003] Can be used as external clock input for Timer 3.
GIO: GIO[004]
GIO: GIO[005]
GIO: GIO[006]
GIO: GIO[007]
SPI0: Chip Select 1
SPI1: Data Out
GIO: GIO[008]
SPI1: Data In -OR- SPI1: Chip Select 1 GIO: GIO[009]
SPI1: Clock GIO:
GIO[010]
SPI1: Chip Select 0
GIO: GIO[011]
UART1: Transmit Data
GIO: GIO[012]
UART1: Receive Data
GIO: GIO[013]
GIO: GIO[019]
SPRS528C–JULY 2008–REVISED JUNE 2010
(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 5.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.)
COUT6G3 /Digital Video Out: VENC settings determine function GIO: GIO[080]
GIO080 /PWM1
D2I/O/ZV
PWM1
COUT7-
G4 /Digital Video Out: VENC settings determine function GIO: GIO[081]
GIO081 /PWM0
C2I/O/ZV
PWM0
PCLK /PD
GIO082V
T3I/O/ZPixel clock input (strobe for lines CI7 through YI0) GIO: GIO[082]
CAM_WEoutput of the CCDC module. Alternately, the field identification input signal is
N_FIELD /R5I/O/Zused by external device (AFE/TG) to indicate the which of two frames is input to
GIO083the CCDC module for sensors with interlaced output. CCDC handles 1- or 2-field
CAM_VD /PD
GIO084V
CAM_HD /PD
GIO085V
YIN0 /PDY[00] YCC 08-bit (which allows for 2 simultaneous decoder inputs), it is time
GIO086V
YIN1 /PDY[01] YCC 08-bit (which allows for 2 simultaneous decoder inputs), it is time
GIO087V
YIN2 /PDY[02] YCC 08-bit (which allows for 2 simultaneous decoder inputs), it is time
GIO088V
YIN3 /PDY[03] YCC 08-bit (which allows for 2 simultaneous decoder inputs), it is time
GIO089V
YIN4 /PDY[04] YCC 08-bit (which allows for 2 simultaneous decoder inputs), it is time
GIO090V
YIN5 /PDY[05] YCC 08-bit (which allows for 2 simultaneous decoder inputs), it is time
GIO091V
YIN6 /PDY[06] YCC 08-bit (which allows for 2 simultaneous decoder inputs), it is time
GIO092V
YIN7 /PDY[07] YCC 08-bit (which allows for 2 simultaneous decoder inputs), it is time
GIO093V
CIN0 /PD
GIO094V
R4I/O/Zoutput (master mode). Tells the CCDC when a new frame starts.
N5I/O/Zoutput (master mode). Tells the CCDC when a new line starts.
P5I/O/Z
P2I/O/Z
P4I/O/Z
R3I/O/Z
P3I/O/Z
M5I/O/Z
M4I/O/Z
L5I/O/Z
J3I/O/Zinputs), it is time multiplexed between luma and chroma of the upper channel.
TYPE
(1)
OTHER
DD_VOUT
DD_VOUT
DD_VIN
(2) (3)
DESCRIPTION
Write enable input signal is used by external device (AFE/TG) to gate the DDR
PD
V
DD_VIN
sensors in hardware. GIO: GIO[083]
Vertical synchronization signal that can be either an input (slave mode) or an
DD_VIN
GIO: GIO[084]
Horizontal synchronization signal that can be either an input (slave mode) or an
DD_VIN
GIO: GIO[085]
Standard CCD/CMOS input: raw[00] YCC 16-bit: time multiplexed between luma:
DD_VIN
multiplexed between luma and chroma of the lower channel. Y/CB/CR[00]
GIO: GIO[086]
Standard CCD/CMOS input: raw[01] YCC 16-bit: time multiplexed between luma:
DD_VIN
multiplexed between luma and chroma of the lower channel. Y/CB/CR[01]
GIO: GIO[087]
Standard CCD/CMOS input: raw[02] YCC 16-bit: time multiplexed between luma:
DD_VIN
multiplexed between luma and chroma of the lower channel. Y/CB/CR[02]
GIO: GIO[088]
Standard CCD/CMOS input: raw[03] YCC 16-bit: time multiplexed between luma:
DD_VIN
multiplexed between luma and chroma of the lower channel. Y/CB/CR[03]
GIO: GIO[089]
Standard CCD/CMOS input: raw[04] YCC 16-bit: time multiplexed between luma:
DD_VIN
multiplexed between luma and chroma of the lower channel. Y/CB/CR[04]
GIO: GIO[090]
Standard CCD/CMOS input: raw[05] YCC 16-bit: time multiplexed between luma:
DD_VIN
multiplexed between luma and chroma of the lower channel. Y/CB/CR[05]
GIO: GIO[091]
Standard CCD/CMOS input: raw[06] YCC 16-bit: time multiplexed between luma:
DD_VIN
multiplexed between luma and chroma of the lower channel. Y/CB/CR[06]
GIO: GIO[092]
Standard CCD/CMOS input: raw[07] YCC 16-bit: time multiplexed between luma:
DD_VIN
multiplexed between luma and chroma of the lower channel. Y/CB/CR[07]
GIO: GIO[093]
Standard CCD/CMOS input: raw[08] YCC 16-bit: time multiplexed between
chroma: CB/CR[00] YCC 08-bit (which allows for 2 simultaneous decoder
L3I/O/Zinputs), it is time multiplexed between luma and chroma of the upper channel.
J5I/O/Zinputs), it is time multiplexed between luma and chroma of the upper channel.
J4I/O/Zinputs), it is time multiplexed between luma and chroma of the upper channel.
CIN4 /
GIO098 /
SPI2_SDIPD
/V
L4I/O/Zinputs), it is time multiplexed between luma and chroma of the upper channel.
SPI2_SDE
NA[1]
CIN5 /
GIO099 /PD
SPI2_SDEV
M3I/O/Zinputs), it is time multiplexed between luma and chroma of the upper channel.
NA[0]
CIN6 /
GIO100 /PD
SPI2_SDV
K5I/O/Zinputs), it is time multiplexed between luma and chroma of the upper channel.
O
CIN7 /
GIO101 /PD
SPI2_SCLV
N3I/O/Zinputs), it is time multiplexed between luma and chroma of the upper channel.
K
SPI0_SDISPI0: Data In
/ GIO102GIO: GIO[102]
A12I/O/ZV
SPI0_SDE
NA[0] /B12I/O/ZV
GIO103
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
Standard CCD/CMOS input: raw[09] YCC 16-bit: time multiplexed between
chroma: CB/CR[01] YCC 08-bit (which allows for 2 simultaneous decoder
DD_VIN
Y/CB/CR[01]
GIO: GIO[095]
Standard CCD/CMOS input: raw[10] YCC 16-bit: time multiplexed between
chroma: CB/CR[02] YCC 08-bit (which allows for 2 simultaneous decoder
DD_VIN
Y/CB/CR[02]
GIO: GIO[096]
Standard CCD/CMOS input: raw[11] YCC 16-bit: time multiplexed between
chroma: CB/CR[03] YCC 08-bit (which allows for 2 simultaneous decoder
DD_VIN
Y/CB/CR[03]
GIO: GIO[097]
Standard CCD/CMOS input: raw[12] YCC 16-bit: time multiplexed between
chroma: CB/CR[04] YCC 08-bit (which allows for 2 simultaneous decoder
DD_VIN
Y/CB/CR[04] SPI: SPI2 Data In -OR- SPI2 Chip select 1.
GIO: GIO[098]
Standard CCD/CMOS input: raw[13] YCC 16-bit: time multiplexed between
chroma: CB/CR[05] YCC 08-bit (which allows for 2 simultaneous decoder
DD_VIN
Y/CB/CR[05] SPI: SPI2 Chip Select 0.
GIO: GIO[99]
Standard CCD/CMOS input: NOT USED YCC 16-bit: time multiplexed between
chroma: CB/CR[06] YCC 08-bit (which allows for 2 simultaneous decoder
DD_VIN
Y/CB/CR[06] SPI: SPI2 Data Out
GIO: GIO[100]
Standard CCD/CMOS input: NOT USED YCC 16-bit: time multiplexed between
chroma: CB/CR[07] YCC 08-bit (which allows for 2 simultaneous decoder
DD_VIN
Y/CB/CR[07] SPI: SPI2 Clock
GIO: GIO[101]
DD
DD
SPI0: Chip Select 0
GIO: GIO[103]
www.ti.com
2.9Multi-Media Card/Secure Digital (MMC/SD) Interfaces
The DM335 includes two Multi-Media Card/Secure Digital card interfaces that are compatible with the
MMC/SD and SDIO protocol.
Table 2-12. MMC/SD Terminal Functions
TERMINAL
NAMENO.
MMCSD0_
CLK
MMCSD0_
CMD
MMCSD0_
DATA0
A15I/O/ZV
C14I/O/ZV
B14I/O/ZV
(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 5.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.)
The Universal Serial Bus (USB) interface supports the USB2.0 High-Speed protocol and includes dual-role
Host/Slave support. However, no charge pump is included.
Table 2-13. USB Terminal Functions
TERMINAL
NAMENO.
USB_DPA7A I/O/ZV
USB_DMA6A I/O/ZV
USB_R1C7A I/O/Z
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground, A = Analog signal.
(2) Specifies the operating I/O supply voltage for each signal. See Section 5.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.)
USB D+ (differential signal pair).
When USB is not used, this signal should be connected to V
USB D- (differential signal pair).
When USB is not used, this signal should be connected to V
USB reference current output
Connect to V
as possible.
SS_USB_REF
via 10K ohm , 1% resistor placed as close to the device
When USB is not used, this signal should be connected to V
Submit Documentation Feedback
Product Folder Link(s): TMS320DM335
SS_USB
SS_USB
SS_USB
.
.
.
TMS320DM335
SPRS528C–JULY 2008–REVISED JUNE 2010
Table 2-13. USB Terminal Functions (continued)
TERMINAL
NAMENO.
USB_IDD5A I/O/ZV
USB_VBUSE5A I/O/ZV
USB_DRVVBUSC5O/ZV
V
SS_USB_REF
V
DDA33_USB
V
DDA33_USB_PLL
V
DDA13_USB
V
DDD13_USB
C8GNDV
J8PWRV
B6PWRV
H7PWRV
C6PWRV
TYPE
(1)
OTHER
(2) (3)
DDA33_USB
DD
DD
DD
DD
DD
DD
DD
www.ti.com
DESCRIPTION
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.
When USB is not used, this signal should be connected to V
SS_USB
.
For host or device mode operation, tie the VBUS/USB power signal to the USB
connector.
When used in OTG mode operation, tie VBUS to the external charge pump and
to the VBUS signal on the USB connector.
When the USB is not used, tie VBUS to V
SS_USB
.
Digital output to control external 5 V supply
When USB is not used, this signal should be left as a No Connect.
USB Ground Reference
Connect directly to ground and to USB_R1 via 10K ohm, 1% resistor placed as
close to the device as possible.
Analog 3.3 V power USBPHY
When USB is not used, this signal should be connected to V
SS_USB
.
Common mode 3.3 V power for USB PHY (PLL)
When USB is not used, this signal should be connected to V
SS_USB
.
Analog 1.3 V power for USB PHY
When USB is not used, this signal should be connected to V
SS_USB
.
Digital 1.3 V power for USB PHY
When USB is not used, this signal should be connected to V
SS_USB
.
2.11 Audio Interfaces
The DM335 includes two Audio Serial Ports (ASP ports), which are backward compatible with other TI
ASP serial ports and provide I2S audio interface. One interface is multiplexed with GIO signals.
TERMINAL
NAMENO.
ASP0_CL
KR/F17I/O/ZV
GIO026
ASP0_CL
KX /F18I/O/ZV
GIO029
ASP0_DR
/E18I/O/ZV
GIO027
ASP0_DX
/H15I/O/ZV
GIO030
ASP0_FS
R /F16I/O/ZV
GIO025
ASP0_FS
X /G17I/O/ZV
GIO028
ASP1_CL
KR
D18I/O/ZV
TYPE
(1)
OTHER
Table 2-14. ASP Terminal Functions
(2) (3)
DD
DD
DD
DD
DD
DD
DD
DESCRIPTION
ASP0: Receive Clock
GIO: GIO[026]
ASP0: Transmit Clock
GIO: GIO[029]
ASP0: Receive DataF
GIO: GIO[027]
ASP0: Transmit Data
GIO: GIO[030]
ASP0: Receive Frame Synch
GIO: GIO[025]
ASP0: Transmit Frame SynchGIO: GIO[028]
ASP1: Receive Clock
(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 5.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.)
(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 5.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.)
TYPE
(1)
OTHER
DD
DD
DD
DD
(2) (3)
DESCRIPTION
UART0: Receive data. Used for UART boot mode
UART0: Transmit data. Used for UART boot mode
The DM335 includes an I2C two-wire serial interface for control of external peripherals. This interface is
multiplexed with GIO signals.
Table 2-16. I2C Terminal Functions
TERMINAL
NAMENO.
I2C_SDA/I2C: Serial data
GIO015GIO: GIO015
I2C_SCL/I2C: Serial clock
GIO014GIO: GIO014
R13I/O/ZV
R14I/O/ZV
(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 5.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.)
TYPE
(1)
OTHER
DD
DD
(2) (3)
DESCRIPTION
2.14 Serial Interface
The DM335 includes three independent serial ports. These interfaces are multiplexed with GIO and other
signals.
SPI0_SDENA[1]SPI0: Chip select 1
SPI0_SDI/SPI0: Data in
GIO102GIO: GIO[102]
B12I/O/ZV
C17I/O/ZV
A12I/O/ZV
SPI0_SDOB11I/O/ZV
SPI1_SCLK/SPI1: Clock
GIO010GIO: GIO[010]
SPI1_SDENA[0]/
GIO011
C13I/O/ZV
E13I/O/ZV
SPI1_SDI/SPI1: Data in or
GIO009/A13I/O/ZV
SPI1_SDENA[1]GIO: GIO[09]
SPI1_SDO/SPI1: Data out
GIO008GIO: GIO[008]
E12I/O/ZV
CIN7/
GIO101/N3I/O/Z
SPI2_SCLK
CIN5/
GIO099/M3I/O/Z
SPI2_SDENA[0]
OTHER
(3)
DD
DD
DD
DD
DD
DD
DD
DD
DD
PD
V
DD_VIN
PD
V
DD_VIN
(2)
DESCRIPTION
SPI0: Clock
SPI0: Data out
SPI1: Chip select 0
GIO: GIO[011] - Active low during MMC/SD boot (can be used as
MMC/SD power control)
SPI1: Chip select 1
Standard CCD/CMOS input: Not used
•YCC 16-bit: time multiplexed between chroma. CB/CR[07]
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is
time multiplexed between luma and chroma of the upper channel.
Y/CB/CR[07]
SPI: SPI2 clock
GIO: GIO[101]
Standard CCD/CMOS input: Raw[13]
•YCC 16-bit: time multiplexed between chroma. CB/CR[05]
•YCC 8-bit (which allows for two simultaneous decoder inputs), it is
time multiplexed between luma and chroma of the upper channel.
Y/CB/CR[07]
SPI: SPI2 chip select 0
GIO: GIO[099]
www.ti.com
(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 5.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.)
(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 5.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.)
TYPE
(1)
OTHER
DD
DD
DD
DD
DD
(2) (3)
DESCRIPTION
Crystal input for system oscillator (24 MHz or 36 MHz)
Output for system oscillator (24 MHz or 36 MHz). When the MX02 is not used,
the MX02 signal can be left open.
Crystal input for video oscillator (27 MHz) Optional, use only if 27MHz derived
DD
from MXI1 and PLL does not provide sufficient performance for Video DAC.
When the MXI2 is not used and powered down, the MXI2 signal should be left
as a No Connect
Output for video oscillator (27 MHz) Optional, use only if 27MHz derived from
DD
MXI1 and PLL does not provide sufficient performance for Video DAC When the
MXO2 is not used and powered down, the MXO2 signal should be left as a No
Connect.
The DM335 provides Real Time Output (RTO) interface.
Table 2-19. RTO Terminal Functions
TERMINAL
NAMENO.
COUT5G2 /Digital Video Out: VENC settings determine function GIO: GIO[079]
GIO079 /C1I/O/ZV
PWM2A /RTO0
RTO0
COUT4B7 /Digital Video Out: VENC settings determine function GIO: GIO[078]
GIO078 /D3I/O/ZV
PWM2B /RTO1
RTO1
COUT3B6 /Digital Video Out: VENC settings determine function GIO: GIO[077]
GIO077 /E3I/O/ZV
PWM2C /RTO2
RTO2
COUT2B5 /Digital Video Out: VENC settings determine function GIO: GIO[076]
GIO076 /E4I/O/ZV
PWM2D /RTO3
RTO3
(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 5.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.)
TYPE
(1)
OTHER
DD_VOUT
DD_VOUT
DD_VOUT
DD_VOUT
(2) (3)
DESCRIPTION
PWM2A
PWM2B
PWM2C
PWM2D
www.ti.com
2.17 Pulse Width Modulator (PWM) Interface
The DM335 provides Pulse Width Modulator (PWM) interface.
Table 2-20. PWM Terminal Functions
TERMINAL
NAMENO.
COUT7G4 /Digital Video Out: VENC settings determine function GIO: GIO[081]
GIO081 /PWM0
C2I/O/ZV
PWM0
COUT6-
G3 /Digital Video Out: VENC settings determine function GIO: GIO[080]
GIO080 /PWM1
D2I/O/ZV
PWM1
COUT5-
G2 /Digital Video Out: VENC settings determine function GIO: GIO[079]
GIO079 /C1I/O/ZV
PWM2A /RTO0
RTO0
COUT4B7 /Digital Video Out: VENC settings determine function GIO: GIO[078]
GIO078 /D3I/O/ZV
PWM2B /RTO1
RTO1
TYPE
(1)
OTHER
DD_VOUT
DD_VOUT
DD_VOUT
DD_VOUT
(2) (3)
DESCRIPTION
PWM2A
PWM2B
(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 5.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.)
COUT3B6 /Digital Video Out: VENC settings determine function GIO: GIO[077]
GIO077 /E3I/O/ZV
PWM2C /RTO2
RTO2
COUT2B5 /Digital Video Out: VENC settings determine function GIO: GIO[076]
GIO076 /E4I/O/ZV
PWM2D /RTO3
RTO3
COUT1B4 /Digital Video Out: VENC settings determine function GIO: GIO[075]
GIO075 /PWM3A
F3I/O/ZV
PWM3A
COUT0-
B3 /Digital Video Out: VENC settings determine function GIO: GIO[074]
GIO074 /PWM3B
F4I/O/ZV
PWM3B
FIELD /
GIO070 /
R2 /
H4I/O/ZV
PWM3C
EXTCLK /
GIO069 /PD
B2 /V
G3I/O/Ze.g. 74.25 MHz for HDTV digital output GIO: GIO[069] Digital Video Out: B2
PWM3D
TYPE
(1)
OTHER
DD_VOUT
DD_VOUT
DD_VOUT
DD_VOUT
(2) (3)
DESCRIPTION
PWM2C
PWM2D
Video Encoder: Field identifier for interlaced display formats GIO: GIO[070]
DD_VOUT
Digital Video Out: R2
PWM3C
Video Encoder: External clock input, used if clock rates > 27 MHz are needed,
DD_VOUT
PWM3D
2.18 System Configuration Interface
The DM335 provides interfaces for system configuration and boot load.
Table 2-21. System/Boot Terminal Functions
TERMINAL
NAMENO.
EM_A13/Async EMIF: Address bus bit 13
GIO067/V19I/O/ZGIO: GIO[067]
BTSEL[1]System: BTSEL[1:0] sampled at power-on-reset to determine boot method.
EM_A12/Async EMIF: Address bus bit 12
GIO066/U19I/O/ZGIO: GIO[066]
BTSEL[0]System: BTSEL[1:0] sampled at power-on-reset to determine boot method.
EM_A11/GIO: GIO[065]
GIO065/R16I/O/ZSystem: AECFG[3:0] sampled a power-on-reset to set AEMIF configuration.
AECFG[3]AECFG[3] sets default fo PinMux2.EM_D15_8. AEMIF default bus width (16 or 8
EM_A10/GIO: GIO[064]
GIO064/R18I/O/ZSystem: AECFG[3:0] sampled a power-on-reset to set AEMIF configuration.
AECFG[2]AECFG[2:1] sets default fo PinMux2.EM_BA0. AEMIF EM_BA0 definition:
EM_A09/GIO: GIO[063]
GIO063/P17I/O/ZSystem: AECFG[3:0] sampled a power-on-reset to set AEMIF configuration.
AECFG[1]AECFG[2:1] sets default fo PinMux2.EM_BA0. AEMIF EM_BA0 definition:
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
PD
V
DD
PD
V
DD
Async EMIF: Address bus bit 11
PU
V
DD
bits).
Async EMIF: Address bus bit 10
PU
V
DD
(EM,_BA0, EM_A14, GIO[054], rsvd)
Async EMIF: Address bus bit 09
PD
V
DD
(EM,_BA0, EM_A14, GIO[054], rsvd)
(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 5.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.)
EM_A08/
GIO062/T19I/O/Z
AECFG[0]•PinMux2.EM_A0_BA1 - AEMIF address width (OneNAND, or NAND)
TYPE
(1)
OTHER
(2) (3)
DESCRIPTION
Async EMIF: Address bus bit 08
GIO: GIO[062]
System: AECFG[0] sets default for:
V
PD
DD
•PinMux2.EM_A13_3 - AEMIF address width (OneNAND, or NAND)
2.19 Emulation
The emulation interface allow software and hardware debugging.
Table 2-22. Emulation Terminal Functions
TERMINAL
NAMENO.
TCKE10IV
TDID9IJTAG test data input
TDOE9OV
TMSD8IJTAG test mode select
TRSTC9IJTAG test logic reset (active low)
RTCKE11OV
EMU0E8I/O/ZEMU[1:0] = 00 - Force Debug Scan chain (ARM and ARM ETB TAPs connected)
EMU1E7I/O/ZEMU[1:0] = 00 - Force Debug Scan chain (ARM and ARM ETB TAPs connected)
(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 5.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.)
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]
SPI: SPI2 Data In -OR- SPI2 Chip select 1
GIO: GIO[098]
(4)
Mux Control
(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 5.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 DM335: YOUT(0-7),COUT(0-7), HSYNC,VSYNC,LCD_OE,FIELD,EXTCLK,VCLK. The trace lengths
should be minimized.
CAM_HD /N5I/OCCDCV
GIO085/ GIOeither an input (slave mode) or an outputHD
(1)
ID
Supply
DD_VIN
(2)
PD
(3)
State
PDinHorizontal synchronization signal that can be PINMUX0[11].CAM_
(master mode). Tells the CCDC when a new
line starts.
GIO: GIO[085]
CAM_VD /R4I/OCCDCV
GIO084/ GIOeither an input (slave mode) or an outputVD
DD_VIN
PDinVertical synchronization signal that can bePINMUX0[12].CAM_
(master mode). Tells the CCDC when a new
frame starts.
GIO: GIO[084]
CAM_WEN_FIER5I/OCCDCV
LD / GIO083/ GIOdevice (AFE/TG) to gate the DDR output ofWEN
DD_VIN
PDinWrite enable input signal is used by external PINMUX0[13].CAM_
the CCDC module.
Alternately, the field identification inputplus
signal is used by external device (AFE/TG)
to indicate the which of two frames is input
to the CCDC module for sensors with
interlaced output. CCDC handles 1- or
2-field sensors in hardware.
GIO: GIO[083]CCDC.MODE[7].CC
PCLK / GIO082T3I/OCCDCV
/ GIOYI0)
DD_VIN
PDinPixel clock input (strobe for lines CI7 through PINMUX0[14].PCLK
out L DDR Data Clock
out H DDR Complementary Data Clock
out H DDR Row Address Strobe
out H DDR Column Address Strobe
out H DDR Write Enable (active low)
out H DDR Chip Select (active low)
out L DDR Clock Enable
inData mask outputs: DDR_DQM1: For
DDR_DQ[15:8]
inData mask outputs: DDR_DQM0: For
DDR_DQ[7:0]
inData strobe input/outputs for each byte of
the 16 bit data bus used to synchronize the
data transfers. Output to DDR when writing
and inputs when reading.
1Gb DDR2 memories.
out L DDR Address Bus bit 13
out L DDR Address Bus bit 12
out L DDR Address Bus bit 11
out L DDR Address Bus bit 10
out L DDR Address Bus bit 09
out L DDR Address Bus bit 08
out L DDR Address Bus bit 07
out L DDR Address Bus bit 06
out L DDR Address Bus bit 05
out L DDR Address Bus bit 04
out L DDR Address Bus bit 03
out L DDR Address Bus bit 02
out L DDR Address Bus bit 01
out L DDR Address Bus bit 00
inDDR Data Bus bit 15
inDDR Data Bus bit 14
inDDR Data Bus bit 13
inDDR Data Bus bit 12
inDDR Data Bus bit 11
inDDR Data Bus bit 10
inDDR Data Bus bit 09
inDDR Data Bus bit 08
inDDR Data Bus bit 07
inDDR Data Bus bit 06
inDDR Data Bus bit 05
inDDR Data Bus bit 04
inDDR Data Bus bit 03
inDDR Data Bus bit 02
inDDR Data Bus bit 01
inDDR Data Bus bit 00
outDDR: Loopback signal for external DQS
DDR_DQGATE1 with same constraints as
used for DDR clock and data.
DDR_V17I/ODDRV
DQGATE1gating. Route to DDR and back to
RSV04M1AReserved. This signal should be left as a No
I/O/ZConnect or connected to VSS.
RSV05N2AReserved. This signal should be connected
I/O/Zto VSS.
RSV06M2PWRReserved. This signal should be connected
to VSS.
RSV07K2GNDReserved. This signal should be connected
to VSS.
NCH8No connect
V
DD_VIN
V
DD_VIN
V
DD_VIN
V
DD_VOUT
V
DD_VOUT
V
DD_VOUT
V
DD_DDR
V
DD_DDR
V
DD_DDR
V
DD_DDR
V
DD_DDR
V
DD_DDR
V
DD_DDR
V
DD_DDR
V
DD_DDR
V
DD_DDR
V
DDA_PLL1
V
DDA_PLL2
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
CV
DD
P6PWRPower for Digital Video Input IO (3.3 V)
P7PWRPower for Digital Video Input IO (3.3 V)
P8PWRPower for Digital Video Input IO (3.3 V)
F6PWRPower for Digital Video Output IO (3.3 V)
F7PWRPower for Digital Video Output IO (3.3 V)
F8PWRPower for Digital Video Output IO (3.3 V)
M9PWRPower for DDR I/O (1.8 V)
P9PWRPower for DDR I/O (1.8 V)
P10PWRPower for DDR I/O (1.8 V)
P11PWRPower for DDR I/O (1.8 V)
P12PWRPower for DDR I/O (1.8 V)
P13PWRPower for DDR I/O (1.8 V)
P14PWRPower for DDR I/O (1.8 V)
R9PWRPower for DDR I/O (1.8 V)
R12PWRPower for DDR I/O (1.8 V)
T14PWRPower for DDR I/O (1.8 V)
G12PWRAnalog Power for PLL1 (1.3 V)
H9PWRAnalog Power for PLL2 (1.3 V)
A1PWRCore power (1.3 V)
A10PWRCore power (1.3 V)
B19PWRCore power (1.3 V)
C4PWRCore power (1.3 V)
G6PWRCore power (1.3 V)
G11PWRCore power (1.3 V)
H10PWRCore power (1.3 V)
H13PWRCore power (1.3 V)
H17PWRCore power (1.3 V)
J11PWRCore power (1.3 V)
J12PWRCore power (1.3 V)
J13PWRCore power (1.3 V)
K6PWRCore power (1.3 V)
K11PWRCore power (1.3 V)
K12PWRCore power (1.3 V)
L11PWRCore power (1.3 V)
L12PWRCore power (1.3 V)
N6PWRCore power (1.3 V)
R7PWRCore power (1.3 V)
R8PWRCore power (1.3 V)
F10PWRPower for Digital IO (3.3 V)
F11PWRPower for Digital IO (3.3 V)
F12PWRPower for Digital IO (3.3 V)
F13PWRPower for Digital IO (3.3 V)
F14PWRPower for Digital IO (3.3 V)
G14PWRPower for Digital IO (3.3 V)
K15PWRPower for Digital IO (3.3 V)
L13PWRPower for Digital IO (3.3 V)
M10PWRPower for Digital IO (3.3 V)
M11PWRPower for Digital IO (3.3 V)
M12PWRPower for Digital IO (3.3 V)
M13PWRPower for Digital IO (3.3 V)
N11PWRPower for Digital IO (3.3 V)
N12PWRPower for Digital IO (3.3 V)
C10GNDSystem oscillator (24 MHz) - ground
TI offers an extensive line of development tools for DM335 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 DM335 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 TMS320DM335 DMSoC multiprocessor
system debug) EVM (Evaluation Module)
For a complete listing of development-support tools for the TMS320DM335 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.
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).
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:
SPRS528C–JULY 2008–REVISED JUNE 2010
"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.
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 DM335 DMSoC platform
member.
ZCE = 337-pin plastic BGA, with Pb-free soldered balls
DEVICE
(B)
( )
SILICON REVISION
SPEED GRADE
135 or 13 = 135 MHz
216 or 21 = 216 MHz
( )
( )
TEMPERATURE RANGE (DEFAULT: 0°C TO 85°C)
Blank = 0
A = -40to 100 , extended temperature
°C to 85°C, commercial temperature
°C°C
A. BGA = Ball Grid Array
B. For actual device part numbers (P/Ns) and ordering information, contact your nearest TI Sales representative.
C. For more information on silicon revision, see(literature number SPRZ287).TMS320DM335 DMSoC Silicon Errata
(C)
TMS320DM335
SPRS528C–JULY 2008–REVISED JUNE 2010
Figure 2-5. Device Nomenclature
2.21.3 Device Documentation
2.21.3.1 Related Documentation From Texas Instruments
The following documents describe the TMS320DM335 Digital Media System-on-Chip (DMSoC). Copies of
these documents are available on the internet at www.ti.com.
www.ti.com
SPRS528TMS320DM335 Digital Media System-on-Chip (DMSoC) Data ManualThis document
describes the overall TMS320DM335 system, including device architecture and features,
memory map, pin descriptions, timing characteristics and requirements, device mechanicals,
etc.
SPRZ287TMS320DM335 DMSoC Silicon Errata Describes the known exceptions to the functional
specifications for the TMS320DM335 DMSoC.
SPRUFX7TMS320DM335 Digital Media System-on-Chip (DMSoC) ARM Subsystem Reference
Guide This document describes the ARM Subsystem in the TMS320DM335 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.
SPRUFZ1TMS320DM335 Digital Media System-on-Chip (DMSoC) Asynchronous External
Memory Interface (EMIF) Reference Guide This document describes the asynchronous
external memory interface (EMIF) in the TMS320DM335 Digital Media System-on-Chip
(DMSoC). The EMIF supports a glueless interface to a variety of external devices.
SPRUFY9TMS320DM335 Digital Media System-on-Chip (DMSoC) Universal Serial Bus (USB)
Controller Reference Guide This document describes the universal serial bus (USB)
SPRUFZ3TMS320DM335 Digital Media System-on-Chip (DMSoC) Audio Serial Port (ASP)
controller in the TMS320DM335 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.
Reference Guide This document describes the operation of the audio serial port (ASP)
audio interface in the TMS320DM335 Digital Media System-on-Chip (DMSoC). The primary
audio modes that are supported by the ASP are the AC97 and IIS modes. In addition to the
primary audio modes, the ASP supports general serial port receive and transmit operation,
but is not intended to be used as a high-speed interface.
SPRUFY1TMS320DM335 Digital Media System-on-Chip (DMSoC) Serial Peripheral Interface (SPI)
SPRUFY2TMS320DM335 Digital Media System-on-Chip (DMSoC) Universal Asynchronous
SPRUFY3TMS320DM335 Digital Media System-on-Chip (DMSoC) Inter-Integrated Circuit (I2C)
SPRS528C–JULY 2008–REVISED JUNE 2010
Reference Guide This document describes the serial peripheral interface (SPI) in the
TMS320DM335 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
shift registers, display drivers, SPI EPROMs and analog-to-digital converters.
Receiver/Transmitter (UART) Reference Guide This document describes the universal
asynchronous receiver/transmitter (UART) peripheral in the TMS320DM335 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.
Peripheral Reference Guide This document describes the inter-integrated circuit (I2C)
peripheral in the TMS320DM335 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. External components attached to
this 2-wire serial bus can transmit and receive up to 8-bit wide data to and from the DMSoC
through the I2C peripheral. This document assumes the reader is familiar with the I2C-bus
specification.
SPRUFY5TMS320DM335 Digital Media System-on-Chip (DMSoC) Multimedia Card (MMC)/Secure
Digital (SD) Card Controller Reference Guide This document describes the multimedia
card (MMC)/secure digital (SD) card controller in the TMS320DM335 Digital Media
System-on-Chip (DMSoC). The MMC/SD card is used in a number of applications to provide
removable data storage. The MMC/SD controller provides an interface to external MMC and
SD cards. The communication between the MMC/SD controller and MMC/SD card(s) is
performed by the MMC/SD protocol.
SPRUFZ20 TMS320DM335 Digital Media System-on-Chip (DMSoC) Enhanced Direct Memory
Access (EDMA) Controller Reference Guide This document describes the operation of the
enhanced direct memory access (EDMA3) controller in the TMS320DM335 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.
SPRUFY0TMS320DM335 Digital Media System-on-Chip (DMSoC) 64-bit Timer Reference Guide
This document describes the operation of the software-programmable 64-bit timers in the
TMS320DM335 Digital Media System-on-Chip (DMSoC). Timer 0, Timer 1, and Timer 3 are
used as general-purpose (GP) timers and can be programmed in 64-bit mode, dual 32-bit
unchained mode, or dual 32-bit chained mode; Timer 2 is used only as a watchdog timer.
The GP timer modes can be used to generate periodic interrupts or enhanced direct memory
access (EDMA) synchronization events and Real Time Output (RTO) events (Timer 3 only).
The watchdog timer mode is used to provide a recovery mechanism for the device in the
event of a fault condition, such as a non-exiting code loop.
SPRUFY8TMS320DM335 Digital Media System-on-Chip (DMSoC) General-Purpose Input/Output
(GPIO) Reference Guide This document describes the general-purpose input/output (GPIO)
peripheral in the TMS320DM335 Digital Media System-on-Chip (DMSoC). The GPIO
peripheral provides dedicated general-purpose pins that can be configured as either inputs
or outputs. When configured as an input, you can detect the state of the input by reading the
state of an internal register. When configured as an output, you can write to an internal
register to control the state driven on the output pin.
SPRUFY6TMS320DM335 Digital Media System-on-Chip (DMSoC) Pulse-Width Modulator (PWM)
(DDR2/mDDR) Memory Controller Reference Guide This document describes the
DDR2/mDDR memory controller in the TMS320DM335 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.
SPRUFX8TMS320DM335 Digital Media System-on-Chip (DMSoC) Video Processing Front End
(VPFE) Reference Guide This document describes the Video Processing Front End (VPFE)
in the TMS320DM335 Digital Media System-on-Chip (DMSoC).
SPRUFX9TMS320DM335 Digital Media System-on-Chip (DMSoC) Video Processing Back End
(VPBE) Reference Guide This document describes the Video Processing Back End (VPBE)
in the TMS320DM335 Digital Media System-on-Chip (DMSoC).
SPRUFY7TMS320DM335 Digital Media System-on-Chip (DMSoC) Real-Time Out (RTO) Controller
Reference Guide This document describes the Real Time Out (RTO) controller in the
TMS320DM335 Digital Media System-on-Chip (DMSoC).
SPRAAL2Implementing DDR2/mDDR PCB Layout on the TMS320DM335 DMSoC This provides
board design recommendations and guidelines for DDR2 and mobile DDR.
This section provides a detailed overview of the DM335 device.
3.1ARM Subsystem Overview
The ARM Subsystem contains components required to provide the ARM926EJ-S (ARM) master control of
the overall DM335 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.
3.1.1Components of the ARM Subsystem
The ARM Subsystem in DM335 consists of the following components:
– Image Pipe (IPIPE)
– H3A Engine (Hardware engine for computing Auto-focus, Auto white balance, and Auto exposure)
•Video Processing Back End (VPBE)
– On Screen Display (OSD)
– Video Encoder Engine (VENC)
Figure 3-1 shows the functional block diagram of the DM335 ARM Subsystem.
www.ti.com
3.2ARM926EJ-S RISC CPU
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
•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
3.2.1CP15
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.
3.2.2MMU
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
SPRS528C–JULY 2008–REVISED JUNE 2010
3.2.3Caches 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.
3.2.4Tightly 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 options include—NAND (with SPI EEPROM Boot option), SPI,
UART and MMC/SD. 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.
www.ti.com
3.2.5Advanced 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.
3.2.6Embedded Trace Macrocell (ETM) and Embedded Trace Buffer (ETB)
To support real-time trace, the ARM926EJ-S processor provides an interface to enable connection of an
Embedded Trace Macrocell (ETM). The ARM926ES-J Subsystem in DM335 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 DM335 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.
3.3Memory Mapping
The ARM memory map is shown in Table 2-2 and Table 2-3. This section describes the memories and
interfaces within the ARM's memory map.
3.3.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.
The ARM has access to the following External memories:
•DDR2 / mDDR Synchronous DRAM
•Asynchronous EMIF / OneNAND
•NAND Flash
•Flash card devices:
– MMC/SD
– xD
– SmartMedia
3.3.3Peripherals
The ARM has access to all of the peripherals on the DM335 device.
3.4ARM Interrupt Controller (AINTC)
The DM335 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
SPRS528C–JULY 2008–REVISED JUNE 2010
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.
3.4.1Interrupt Mapping
The AINTC takes up to 64 ARM device interrupts and maps them to either the IRQ or to the FIQ of the
ARM. Each interrupt is also assigned one of 8 priority levels (2 for FIQ, 6 for IRQ). For interrupts with the
same priority level, the priority is determined by the hardware interrupt number (the lowest number has the
highest priority). Table 3-1 shows the connection of device interrupts to the ARM.
(1) The total number of interrupts in DM335 exceeds 64, which is the maximum value of the AINTC module. Therefore, several interrupts
are multiplexed and you must use the register ARM_INTMUX in the System Control Module to select the interrupt source for multiplexed
interrupts. Refer to the TMS320DM335 Digital Media System-on-Chip (DMSoC) ARM Subsystem Reference Guide (literature number
SPRUFX7 ) for more information on the System Control Module register ARM_INTMUX.
The DM335 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. The reference clock drives two separate PLL controllers (PLLC1 and PLLC2). PLLC1
generates the clocks required by the ARM, VPBE,VPSS, and peripherals. PLL2 generates the clock
required by the DDR PHY. A block diagram of DM335's clocking architecture is shown in Figure 3-2 . The
PLLs are described further in Section 3.6.
3.5.2Supported Clocking Configurations for DM335-135
This section describes the only supported device clocking configurations for DM335-135. The DM335
supports either 24 MHz (typical) or 36 MHz reference clock (crystal or external oscillator input).
Configurations are shown for both cases.
3.5.2.1Supported Clocking Configurations for DM335-135 (24 MHz reference)
3.5.2.1.1 DM335-135 PLL1 (24 MHz reference)
All supported clocking configurations for DM335-135 PLL1 with 24 MHz reference clock are shown in
3.5.3Supported Clocking Configurations for DM335-216
This section describes the only supported device clocking configurations for DM335-216. The DM335
supports either 24 MHz (typical) or 36 MHz reference clock (crystal or external oscillator input).
Configurations are shown for both cases.
3.5.3.1Supported Clocking Configurations for DM335-216 (24 MHz reference)
3.5.3.1.1 DM335-216 PLL1 (24 MHz reference)
All supported clocking configurations for DM335-216 PLL1 with 24 MHz reference clock are shown in
The Video Processing Back End (VPBE) is a sub-module of the Video Processing Subsystem (VPSS).
The VPBE is designed to interface with a variety of LCDs and an internal DAC module. There are two
asynchronous clock domains in the VPBE: an internal clock domain and an external clock domain. The
internal clock domain is driven by the VPSS clock (PLL1 SYSCLK4). The external clock domain is
configurable; you can select one of five source:
•24 MHz crystal input at MXI1
•27 MHz crystal input at MXI2 (optional feature, not typically used)
See the TMS320DM335 Digital Media System-on-Chip (DMSoC) Video Processing Back End (VPBE)
Reference Guide (literature number SPRUFX9) for complete information on VPBE clocking.
3.5.4.2USB Clocking
The USB Controller is driven by two clocks: an output clock of PLL1 (SYSCLK2) and an output clock of
the USB PHY.
For proper USB 2.0 function, SYSCLK2 must be greater than 60 MHz.
The USB PHY takes an input clock that is configurable by the USB PHY clock source bits (PHYCLKSRC)
in the USB PHY control register (USB_PHY_CTL) in the System Control Module. When a 24 MHz crystal
is used at MXI1/MXO1, set PHYCLKSRC to 0. This will present a 24 MHz clock to the USB PHY. When a
36 MHz crystal is used at MXI1/MXO1, set PHYCLKSRC to 1. This will present a 12 MHz clock (36 MHz
divided internally by three) to the USB PHY. The USB PHY is capable of accepting only 24 MHz and 12
MHz; thus you must use either a 24 MHz or 36 MHz crystal at MXI1/MXO1. See the TMS320DM335Digital Media System-on-Chip (DMSoC) Universal Serial Bus (USB) Controller Reference Guide (literature
number SPRUFY9) for more information. See the TMS320DM335 Digital Media System-on-Chip (DMSoC)ARM Subsystem Reference Guide (literature number SPRUFX7) for more information on the System
Control Module.
This section describes the PLL Controllers for PLL1 and PLL2. See the TMS320DM335 Digital Media
System-on-Chip (DMSoC) ARM Subsystem Reference Guide (literature number SPRUFX7) for more
information on the PLL controllers.
3.6.1PLL Controller Module
The DM335 has two PLL controllers that provide clocks to different components of the chip. PLL controller
1 (PLLC1) provides clocks to most of the components of the chip. PLL controller 2 (PLLC2) provides
clocks to the DDR PHY.
As a module, the PLL controller provides the following:
•Glitch-free transitions (on changing PLL settings)
•Domain clocks alignment
•Clock gating
•PLL bypass
•PLL power down
The various clock outputs given by the PLL controller are as follows:
•Domain clocks: SYSCLKn
•Bypass domain clock: SYSCLKBP
•Auxiliary clock from reference clock: AUXCLK
www.ti.com
Various dividers that can be used are as follows:
•Pre-PLL divider: PREDIV
•Post-PLL divider: POSTDIV
•SYSCLK divider: PLLDIV1, …, PLLDIVn
•SYSCLKBP divider: BPDIV
Multipliers supported are as follows:
PLLC1 provides most of the DM335 clocks. Software controls PLLC1 operation through the PLLC1
registers. The following list, Table 3-10, and Figure 3-3 describe the customizations of PLLC1 in the
DM335.
•Provides primary DM335 system clock
•Software configurable
•Accepts clock input or internal oscillator input
•PLL pre-divider value is fixed to (/8)
•PLL multiplier value is programmable
•PLL post-divider
•Only SYSCLK[4:1] are used
•SYSCLK1 divider value is fixed to (/2)
•SYSCLK2 divider value is fixed to (/4)
•SYSCLK3 divider value is programmable
•SYSCLK4 divider value is programmable to (/4) or (/2)
•SYSCLKBP divider value is fixed to (/3)
•SYSCLK1 is routed to the ARM Subsystem
•SYSCLK2 is routed to peripherals
•SYSCLK3 is routed to the VPBE module
•SYSCLK4 is routed to the VPSS module
•AUXCLK is routed to peripherals with fixed clock domain and also to the output pin CLKOUT1
•SYSCLKBP is routed to the output pin CLKOUT2
SPRS528C–JULY 2008–REVISED JUNE 2010
Table 3-10. PLLC1 Output Clocks
Output ClockUsed ByPLLDIVNotes
SYSCLK1ARM Subsystem/2Fixed divider
SYSCLK2Peripherals/4Fixed divider
SYSCLK3VPBE (VENC module)/nProgrammable divider (used to get 27
PLLC2 provides the DDR PHY clock and CLKOUT3. Software controls PLLC2 operation through the
PLLC2 registers. The following list, Table 3-11, and Figure 3-4 describe the customizations of PLLC2 in
the DM335.
•Provides DDR PHY clock and CLKOUT3
•Software configurable
•Accepts clock input or internal oscillator input (same input as PLLC1)
In the DM335 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
– Control module resets
•Supports IcePick emulation features: power, clock, and reset
For more information on the PSC, see the TMS320DM335 Digital Media System-on-Chip (DMSoC) ARMSubsystem Reference Guide (literature number SPRUFX7).
www.ti.com
Figure 3-5. DM335 Power and Sleep Controller (PSC)
3.8System Control Module
The DM335’s 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 and fast NAND boot control
•Bandwidth Management
– Bus master DMA priority control
For more information on the System Control Module refer to the TMS320DM335 Digital Media
System-on-Chip (DMSoC) ARM Subsystem Reference Guide (literature number SPRUFX7).
3.9Pin Multiplexing
The DM335 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
DM335 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-12.
Table 3-12. Peripheral Pin Mux Overview
PeripheralMuxed WithPrimary FunctionSecondary FunctionTertiary Function
VPFE (video in)GPIO and SPI2VPFE (video in)SPI2GPIO
VPBE (video out)GPIO, PWM, and RTOVPBE (video out)PWM and RTOGPIO
AEMIFGPIOAEMIFGPIOnone
ASP0GPIOASP0GPIOnone
MMC/SD1GPIO and UART2MMC/SD1GPIOUART2
CLKOUTGPIOCLKOUTGPIOnone
I2CGPIOI2CGPIOnone
UART1GPIOUART1GPIOnone
SPI1GPIOSPI1GPIOnone
SPI0GPIOSPI0GPIOnone
3.9.1Hardware Controlled Pin Multiplexing
Use the Asynchronous EMIF configuration pins (AECFG[3:0]) for hardware pin mux control. AECFG[3:0]
control the partitioning of the AEMIF addresses and GPIOs at reset, which allows you to properly
configure the number of AEMIF address pins required by the boot device while unused addresses pins are
available as GPIOs. These settings may be changed by software after reset by programming the PinMux2
register The PinMux2 register is in the System Control Module. As shown in Table 3-13, the number of
address bits enabled on the AEMIF is selectable from 0 to 16. Pins that are not assigned to another
peripheral and not enabled as address signals become GPIOs (except EM_A[2:1]). The enabled address
signals are always contiguous from EM_BA[1] upwards; bits cannot be skipped. The exception to this are
EM_A[2:1]. These signals (can be used to) represent the ALE and CLE signals for the NAND Flash mode
of the AEMIF and are always enabled. Note that EM_A[0] does not represent the lowest AEMIF address
bit. DM335 supports only 16-bit and 8-bit data widths for the AEMIF. In 16-bit mode, EM_BA[1] represents
the LS address bit (the half-word address) and EM_BA[0] represents the MS address bit (A[14]). In 8-bit
mode, EM_BA[1:0] represent the 2 LS address bits. Note that additional selections are available by
programming the PinMux2 register in software after boot. Note that AECFG selection of ‘0010’ selects
OneNAND interface. The AEMIF needs to operate in the half-rate mode (full_rate = 0) to meet frequency
requirements. Software should not change the PINMUX2 register setting to affect the AEMIF rate
operation. A soft reset of the AEMIF should be performed any time a rate change is made.
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. Refer to the TMS320DM335 DigitalMedia System-on-Chip (DMSoC) ARM Subsystem Reference Guide (literature number SPRUFX7) for
complete descriptions of the pin mux registers.
3.10 Device Reset
There are five types of reset in DM335. 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-14. They are further described in the
TMS320DM335 Digital Media System-on-Chip (DMSoC) ARM Subsystem Reference Guide (literature
number SPRUFX7).
Table 3-14. Reset Types
TypeInitiatorEffect
POR (Power-On-Reset)RESET pin low and TRST lowTotal reset of the chip (cold reset). Resets all modules
Warm ResetRESET pin low and TRST high (initiated by ARMResets all modules including memory, except ARM
emulator).emulation.
Max ResetARM emulator or Watchdog Timer (WDT).Same effect as warm reset.
System ResetARM emulatorResets all modules except memory and ARM
Module ResetARM softwareResets a specific module. Allows the ARM to
emulation. It is a soft reset that maintains memory
contents and does not affect or reset clocks or power
states.
independently reset any module. Module reset is
intended as a debug tool not as a tool to use in
production.
3.11 Default 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.
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.12 for more information on the boot process.
3.11.1 Device Configuration Pins
The device configuration pins are described in Table 3-15. 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.8.
BTSEL[1:0]Selects ARM boot modeEM_A[13:12]00If any ROM boot mode is selected, GIO61
00 = Boot from ROM (NAND(NAND)is used to indicated boot status.
with SPI EEPROM bootIf NAND boot is selected, CE0 is used for
option)NAND and SPI0 is used for SPI boot
01 = Boot from AEMIFoption. Use AECFG[3:0] to configure
10 = Boot from ROMAEMIF pins for NAND.
(MMC/SD)If AEMIF boot is selected, CE0 is used for
11 = Boot from ROM (UART)AEMIF device (OneNAND, ROM). Use
AECFG[3:0]Selects AEMIF pinEM_A[11:8]1101Selects the AEMIF pin configuration. Refer
configuration(NAND)to pin-muxing information in Section 3.9.1.
internal
AECFG[3:0] to configure AEMIF pins for
NAND.
If MMC/SD boot is selected, MMC/SD0 is
used.
Note that AECFG[3:0] affects both AEMIF
(BTSEL[1:0]=01) and NAND
(BTSEL[1:0]=00) boot modes.
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.5
and Section 3.6. The default state of the PLLs is reflected in the default state of the register bits in the
PLLC registers. Refer to the TMS320DM335 Digital Media System-on-Chip (DMSoC) ARM SubsystemReference Guide (literature number SPRUFX7) for PLLC register descriptions.
3.11.3 Power Domain and Module State Configuration
Only a subset of modules are enabled after reset by default. Table 3-16 shows which modules are
enabled after reset. Table 3-16 as shows that the following modules are enabled depending on the
sampled state of the device configuration pins: EDMA (CC and TC0), AEMIF, MMC/SD0, UART0, and
Timer0. For example, UART0 is enabled after reset when the device configuration pins (BTSEL[1:0] = 11 Enable UART) select UART boot mode. For more information on module configuration refer to .
The input pins BTSEL[1:0] determine whether the ARM will boot from its ROM or from the Asynchronous
EMIF (AEMIF). When ROM boot is selected (BTSEL[1:0] = 00, 10, or 11), a jump to the start of internal
ROM (address 0x0000: 8000) is forced into the first fetched instruction word. The embedded ROM boot
loader code (RBL) then performs certain configuration steps, reads the BOOTCFG register to determine
the desired boot method, and branches to the appropriate boot routine (i.e., a NAND/SPI, MMC/SD, or
UART loader routine).
www.ti.com
If AEMIF boot is selected (BTSEL[1:0] = 01), a jump to the start of AEMIF (address 0x0200: 0000) is
forced into the first fetched instruction word. The ARM then continues executing from external
asynchronous memory using the default AEMIF timings until modified by software.
For AEMIF boot, the OneNAND must be connected to the first AEMIF chip select space
(EM_CE0). Also, the AEMIF does not support direct execution from NAND Flash.
Boot modes are further described in Section 3.12.
3.11.5 AEMIF Configuration
3.11.5.1 AEMIF Pin Configuration
The input pins AECFG[3:0] determine the AEMIF configuration immediately after reset. Use AECFG[3:0]
to properly configure the pins of the AEMIF. Refer to the section on pin multiplexing in Section 3.9.
Also, see the TMS320DM335 Digital Media System-on-Chip (DMSoC) Asynchronous External MemoryInterface (EMIF) Reference Guide (SPRUFZ1) for more information on the AEMIF.
3.11.5.2 AEMIF Timing Configuration
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 MXI1, the AEMIF is configured to run at 6 MHz/88 which equals approximately 68 kHz by default.
See the TMS320DM335 Digital Media System-on-Chip (DMSoC) Asynchronous External MemoryInterface (EMIF) Reference Guide (SPRUFZ1) for more information on the AEMIF.
The DM335 ARM can boot from either Async EMIF (AEMIF/OneNand) or from ARM ROM, as determined
by the setting of the device configuration pins BTSEL[1:0]. The BTSEL[1:0] pins can define the ROM boot
mode further as well.
The boot selection pins (BTSEL[1: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[1:0] = 01,
indicating AEMIF (AEMIF/OneNand) boot. See Section 3.11.1 for information on the boot selection pins.
3.12.1 Boot Modes Overview
DM335’s ARM ROM boot loader (RBL) executes when the BTSEL[1:0] pins indicate a condition other than
the normal ARM EMIF boot.
•If BTSEL[1:0] = 01 - Asynchronous EMIF (AEMIF) boot. 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.
•In NAND mode if SPI boot fails, then NAND mode is tried. If NAND boot fails, then MMC/SD mode is
tried.
•If MMC/SD boot fails, then MMC/SD boot is tried again.
•If UART boot fails, then UART boot is tried again.
•RBL uses GIO61 to indicate boot status (can use to blink LED):
– After reset, GIO61 is initially driven low (e.g LED off)
– If NAND boot fails, then GIO61 shall toggle at 4Hz while MMC/SD boot is tried.
– If MMC/SD boot fails, then GIO61 shall toggle at 4Hz while MMC/SD boot is retried.
– If UART boot fails, then GIO61 shall toggle at 2Hz while UART boot is retried.
– When boot is successful, just before program control is given to UBL, GIO61 is driven high (e.g.
LED on).
– DM335 Timer0 shall be used to accurately toggle GIO61 at 4Hz and 2Hz.
•ARM ROM Boot - SPI boot in NAND Mode
– No support for a full firmware boot. Instead, copies a second stage User Boot Loader (UBL) from
SPI to ARM Internal RAM (AIM) and transfers control to the user software.
– Support for 16 and 24 bit SPI EEPROMs
– Support for up to 30KB UBL (32KB - ~2KB for RBL stack)
– RBL 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 - NAND Mode (See Section 3.12.2 for a full explanation of the differences between
Standard Mode and Compatibility 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 8192 bytes in Standard Mode and 2048 bytes in
Compatibility Mode
Note: At the time of documentation for this device, 8192-byte devices were not available for testing.
The code does contain support for these devices; however, it has not yet been tested.
– 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
Notes:
– See Section 3.12.2 for a full explanation of the differences between Standard Mode and
Compatibility Mode.
– The GIO000 pin must be held high during NAND boot for the boot process to fuction properly.
•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)
•ARM ROM Boot - UART mode
– 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)
www.ti.com
The general boot sequence is shown in Figure 3-6. For more information, refer to the TMS320DM335
Digital Media System-on-Chip (DMSoC) ARM Subsystem Reference Guide (literature number SPRUFX7).
– The RBL contains an internal table with a list of known NAND devices. Table 3-23 shows the
devices contained in the tables.
– If the device ID is not found in the table, then the RBL use the fourth byte of the NAND to decode
this to obtain the necessary parameters.
•Once a device ID is identified, the first 24 blocks of the NAND are read sequentially starting with page
0 with an offset of 512 bytes. The purpose of the read is to locate a magic number which will identify
the revision of the silicon. Table 3-18 contains magic numbers and their functions. In addition to the
modes listed in Table 3-18, the magic number will determine whether the device runs in Standard or
Compatibility mode. Magic numbers of the form 0xA1ACEDxx place the device in Compatibility mode,
while magic numbers of the form 0xA1BCEDxx place the device in Standard mode. This should be
kept in mind when reviewing the values in Table 3-18.
•If a Compatibility mode magic number is read, then the device enters compatibility mode. In
compatibility mode, NAND layout is identical to that used in previous revisions of the silicon as shown
in Table 3-19. Only 512-byte small blocks and 2048-byte big blocks are supported.
•If a Standard mode magic number is read, the NAND layout is as shown in Table 3-20: 512-bytes
small block and 2048- and 4096- big block devices are supported. 8192-block devices are also
supported. Note: At the time of production of this document revision, only 4096-block devices were
available for testing.
•Once a magic number is identified, the User Boot Loader (UBL) is loaded from the NAND, stored to
internal RAM, and executed.
www.ti.com
Table 3-17. NAND Devices in NAND Device ID Table
DEVICE IDPAGES PER BLOCKBYTES PER PAGEBLOCK SHIFT VALUENUMBER OF ADDRESS
Table 3-17. NAND Devices in NAND Device ID Table (continued)
0xAC642048+64225
0xDC642048+64225
0xB1642048+64225
0xC1642048+64225
Table 3-18. UBL Signature and Special Modes for NAND Boot Mode
MODEVALUE
UBL_MAGIC_SAFE0xA1AC ED00Safe boot mode
UBL_MAGIC_DMA0xA1AC ED11DMA boot mode
UBL_MAGIC_IC0xA1AC ED22I Cache boot mode
UBL_MAGIC_FAST0xA1AC ED33Fast EMIF boot mode
UBL_MAGIC_DMA_IC0xA1AC ED44DMA + I Cache boot mode
UBL_MAGIC_DMA_IC_FAST0xA1AC ED55DMA + I Cache + Fast EMIF boot mode
UBL_MAGIC_SPI_PARAMS0xA1AC EDAANAND parameters from SPI EEPROM
(1) The values listed only apply when operating in compatibility mode. These values follow the form 0xA1BCEDxx when operating in
standard mode.
Example: UBL_MAGIC_SAFE VALUE = 0xA1ACED00; Safe boot mode will configure the device to run in safe boot mode and in
compatibility mode. However, when using standard mode, the value should be 0xA1BCD00.
16 bytes ECC Data64 bytes ECC Data128 bytes ECC Data
3.13 Power Management
The DM335 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 timeline 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 DM335 includes several power management features which are briefly described in
Table 3-17. Refer to the TMS320DM335 Digital Media System-on-Chip (DMSoC) ARM SubsystemReference Guide (literature number SPRUFX7) for more information on power management.
Module clock disableModule clocks can be disabled to reduce switching power
Module clock frequency scalingModule clock frequency can be scaled to reduce switching power
PLL power-downThe PLLs can be powered-down when not in use to reduce
ARM Sleep Mode
ARM Wait-for-Interrupt sleep modeDisable ARM clock to reduce active power
System Sleep Modes
Deep Sleep modeStop all device clocks and power down internal oscillators to reduce
I/O Management
USB Phy power-downThe USB Phy can be powered-down to reduce USB I/O power
DAC power-downThe DAC's can be powered-down to reduce DAC power
DDR self-refresh and power downThe DDR / mDDR device can be put into self-refresh and power
switching power
active power to a minimum. Registers and memory are preserved.
The DM335 uses a 64-bit crossbar architecture to control access between device processors, subsystems
and peripherals. It includes an EDMA Controller consisting of a DMA Transfer Controller (TC) and a DMA
Channel Controller (CC). The TC provides two DMA channels for transfer between slave peripherals. The
CC provides a user and event interface to the EDMA system. It includes up to 64 event channels to which
all system synchronization events can be mapped and 8 auto submit “quick” channels (QDMA). In most
ways, these channels are identical. A channel refers to a specific ‘event’ that can cause a transfer to be
submitted to the TC as a Transfer Request.
3.14.1 Crossbar Connections
There are five transfer masters (TCs have separate read and write connections) connected to the
crossbar; ARM, the Video Processing Sub-system (VPSS), the master peripherals (USB), and two EDMA
transfer controllers. These can be connected to four separate slave ports; ARM, the DDR EMIF, and CFG
bus peripherals. Not all masters may connect to all slaves. Connection paths are indicated by √ at
intersection points shown in Table 3-22
Table 3-22. Crossbar Connection Matrix
Slave Module
DMA MasterARM InternalConfig Bus Registers and MemoryDDR EMIF Memory
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
•128 PaRAM sets
– Each PaRAM set can be used for a DMA channel, QDMA channel, or link set (remaining)
•Two transfer controllers/event queues. The system-level priority of these queues is user programmable
•16 event entries per event queue
•External events (for example, ASP TX Evt and RX Evt)
The EDMA Transfer Controller has the following features:
www.ti.com
•Two 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 (EDMA3CC
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. DM335 provides 128 PaRAM entries, one for each of the 64
DMA channels and for 64 QDMA / Linked DMA entries.
DMA Channels: Can be triggered by: " External events (for example, ASP 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. DM335 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.
3.14.2.1EDMA Channel Synchronization Events
The EDMA supports up to 64 EDMA channels which service peripheral devices and external memory.
Table 3-23 lists the source of EDMA synchronization events associated with each of the programmable
EDMA channels. For the DM335 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 TMS320DM335 Digital Media
System-on-Chip (DMSoC) 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 TMS320DM335 DigitalMedia System-on-Chip (DMSoC) Enhanced Direct Memory Access (EDMA) Controller Reference Guide (literature number SPRUFZ20).
(2) The total number of EDMA events in DM335 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 TMS320DM335 Digital Media System-on-Chip (DMSoC) ARM Subsystem Reference Guide (literature number
SPRUFX7) for more information on the System Control Module register EDMA_EVTMUX.
4.1Absolute Maximum Ratings Over Operating Case Temperature Range
(Unless Otherwise Noted)
Supply voltage ranges
Input voltage rangesAll 3.3 V I/Os-0.5 V to 3.8 V
Clamp current for input or output
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
(3) Clamp current flows from an input or output pad to a supply rail through a clamp circuit or an intrinsic diode. Positive current results from
an applied input or output voltage that is more than 0.5 V higher (more positive) than the supply voltage,
VDD/V
DDA_PLL1/2/VDD_USB/VDD_DDR
(more negative) than the VSSvoltage..
(1) (2)
All 1.3 V supplies-0.5 V to 1.7 V
All digital 1.8 V supplies-0.5 V to 2.5 V
All analog 1.8 V supplies-0.5 V to 1.89 V
All 3.3 V supplies-0.5 V to 4.4 V
All 1.8 V I/Os-0.5 V to 2.3 V
VBUS0.0 V to 5.5 V
(3)
SS.
I
clamp
Commercial T
c
Extended Temperature [A135/A216 devices] T
stg
-20 mA to 20 mA
c
-40°C to 100°C
-65°C to 150 °C
for dual-supply macros. Negative current results from an applied voltage that is more than 0.5 V less
(1) Oscillator ground must be kept separate from other grounds and connected directly to the crystal load capacitor ground (see
Section 5.5.1 ).
(2) 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
adhere to JESD79-2A standard, USB I/Os adhere to USB2.0 spec.
(3) See Section 5.9.2.4 . Also, resistors should be E-96 spec line (3 digits with 1% accuracy).
(4) Connect USB_R1 to V
(5) Whichever is smaller. P = the period of the applied signal. Maintaining transition times as fast as possible is recommended to improve
SS_USB_REF
noise immunity on input signals.
Supply voltage, Core1.2351.31.365V
Supply voltage, PLL11.2351.31.365V
Supply voltage, PLL21.2351.31.365V
Supply voltage, USB Digital1.2351.31.365V
Supply voltage, USB Analog1.2351.31.365V
Supply voltage, USB Analog3.1353.33.465V
Supply voltage, USB Common PLL3.1353.33.465V
Supply voltage, DDR2 / MDDR1.711.81.89V
Supply voltage, DDR DLL Analog3.1353.33.465V
Supply voltage, Digital video In3.1353.33.465V
Supply voltage, Digital Video Out3.1353.33.465V
Supply voltage, DAC Analog1.711.81.89V
Supply voltage, I/Os3.1353.33.465V
Supply ground, Core, USB Digital000V
Supply ground, PLL1000V
Supply ground, PLL2000V
Supply ground, USB000V
Supply ground, DLL000V
Supply ground, DAC Analog000V
MXI1 osc ground
MXI2 osc ground
High-level input voltage
Low-level input voltage
(1)
(1)
(2)
(2)
000V
000V
2V
0.8V
DAC reference voltage450mV
DAC full-scale current adjust resistor2550Ω
Output resistor499Ω
Bypass capacitor0.1mF
Output resistor (ROUT), between TVOUT and VFB
pins
1070
Feedback resistor, between VFB and IOUT pins.1000
DAC full-scale current adjust resistor2550Ω
Bypass capacitor0.1mA
(4)
9.91010.1kΩ
Commercial085°C
Operating case temperature range
Extended
[A135/A216-40100°C
devices]
Transition time, 10% - 90%, All
Inputs (unless otherwise specified in0.25P or 10
the electrical data sections)
via 10K ohm, 1% resistor placed as close to the device as possible.
4.3Electrical Characteristics Over Recommended Ranges of Supply Voltage and
Operating Case Temperature (Unless Otherwise Noted)
PARAMETERTEST CONDITIONS
(3) (4)
(2)
(2)
VDD=MIN, IOH=MAX2.4
VDD=MIN, IOL=MAX0.6
VI= VSSto V
VI= VSSto V
VI= VSSto V
DD
DD
DD
VOH= 2.4 V-4000mA
VOL= 0.6 V4000
V
Voltage
Output
CurrentCurrent sink of high-level output
Input/Outputcurrent
OH
V
OL
I
I
I
I(pullup)
I
I(pulldown)
I
OH
I
OL
High-level output voltage
Low-level output voltage
Input current for I/O without
internal pull-up/pull-down
Input current for I/O with
internal pull-up
(3) (4)
Input current for I/O with
internal pull-down
Current sink of low-level output
current
VO= VDDor VSS; internal pull
I
OZ
I/O off-state output current
disabled
VO= VDDor VSS; internal pull
enabled
C
CapacitancepF
I
C
O
Input capacitance4
Output capacitance4
ResolutionResolution10Bits
R
= 499 Ω, Video buffer
INLIntegral non-linearity, best fit1LSB
DAC
DNLDifferential non-linearity0.5LSB
Compliance Output compliance rangeIFS = 1.4 mA, R
V
OH(VIDBUF)
Video BufferV
V
OL(VIDBUF)
Output high voltage (top of 75%
NTSC or PAL colorbar)
(5)
Output low voltage (bottom of
sync tip)
LOAD
disabled
R
= 499 Ω, Video buffer
LOAD
disabled
LOAD
(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 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 Section 2.4 or Section 2.20 for pin descriptions.
(4) To pull up a signal to the opposite supply rail, a 1 kΩ resistor is recommended.
(5) 100% color bars are not supported. 100% color bars require 1.2 V peak-to-peak. The video buffer only provides 1.0 V peak-to-peak.
5DM335 Peripheral Information and Electrical Specifications
5.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 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.
Figure 5-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.
5.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 5-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 5-3. Rise and Fall Transition Time Voltage Reference Levels
5.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.
In order to ensure device reliability, the DM335 requires the following power supply power-on and
power-off sequences. See table Table 5-1 for a description of DM335 power supplies.
Power-On:
1. Power on 1.3 V: CVDD, V
2. Power on 1.8 V: V
3. Power on 3.3 V: D
You may power-on the 1.8 V and 3.3 V power supplies simultaneously.
Power-Off:
1. Power off 3.3 V: D
2. Power off 1.8 V: V
3. Power off 1.3 V: CVDD, V
You may power-off the 1.8 V and 3.3 V power supplies simultaneously.
Power-off the 1.8v/3.3V supply before or within 10usec of power-off of the 1.3 V supply.
Note that when booting the DM335 from OneNAND, you must ensure that the OneNAND device is ready
with valid program instructions before the DM335 attempts to read program instructions from it. In
particular, before you release DM335 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.
DD_DDR
, V
VDD
, V
VDD
DD_DDR
DDA_PLL1/2
, V
DDA33_DDRDLL
DDA33_DDRDLL
, V
DDA_PLL1/2
, V
DDA18_DAC
DDA18_DAC
, V
DDD13_USB
, V
DDA33_USB
, V
DDA33_USB
DDD13_USB
, V
DDA13_USB
, V
DDA33_USB_PLL
, V
DDA33_USB_PLL
, V
DDA13_USB
, V
, V
DD_VIN
DD_VIN
, V
DD_VOUT
, V
DD_VOUT
www.ti.com
5.3.1.1Power-Supply Design Considerations
Core and I/O supply voltage regulators should be located close to the DM335 to minimize inductance and
resistance in the power delivery path. Additionally, when designing for high-performance applications
utilizing the DM335 device, the PC board should include separate power planes for core, I/O, and ground,
all bypassed with high-quality low-ESL/ESR capacitors.
5.3.1.2Power-Supply Decoupling
In order to properly decouple the supply planes from system noise, place as many capacitors (caps) as
possible close to DM335. These caps need to be close to the DM335 power pins, no more than 1.25 cm
maximum distance to be effective. Physically smaller caps, such as 0402, are better because of their
lower parasitic inductance. Proper capacitance values are also important. Small bypass caps (near 560
pF) should be closest to the power pins. Medium bypass caps (220 nF or as large as can be obtained in a
small package) should be next closest. TI recommends no less than 8 small and 8 medium caps per
supply be placed immediately next to the BGA vias, using the "interior" BGA space and at least the
corners of the "exterior".
Larger caps for each supply can be placed further away for bulk decoupling. Large bulk caps (on the order
of 100 mF) should be furthest away, but still as close as possible. Large caps for each supply should be
placed outside of the BGA footprint.
Any cap selection needs to be evaluated from a yield/manufacturing point-of-view. As with the selection of
any component, verification of capacitor availability over the product’s production lifetime should be
considered. See also Section 5.5.1 and Section 5.5.2 for additional recommendations on power supplies
for the oscillator/PLL supplies.