– Enhanced Direct-Memory-Access Controller• C674x Two Level Cache Memory Architecture
3 (EDMA3)
– 128K-Byte RAM Shared Memory
– Two External Memory Interfaces
– Three Configurable 16550 type UART
Modules
– LCD Controller
– Two Serial Peripheral Interfaces (SPI)
– Multimedia Card (MMC)/Secure Digital (SD)
– Two Master/Slave Inter-Integrated Circuit
– One Host-Port Interface (HPI)
– USB 1.1 OHCI (Host) With Integrated PHY
(USB1)
• Applications
– Industrial DiagnosticsSupport
– Test and measurement– 64 General-Purpose Registers (32 Bit)
– Military Sonar/ Radar– Six ALU (32-/40-Bit) Functional Units
– Medical measurement•Supports 32-Bit Integer, SP (IEEE Single
– Professional Audio
• Software Support
– TI DSP/BIOS™
– Chip Support Library and DSP Library
• ARM926EJ-S Core
– 32-Bit and 16-Bit (Thumb®) Instructions
– DSP Instruction Extensions
– Single Cycle MAC
– ARM®Jazelle®Technology
– EmbeddedICE-RT™ for Real-Time Debug
• ARM9 Memory Architecture
• C674x Instruction Set Features
– Superset of the C67x+™ and C64x+™ ISAs
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.
2DSP/BIOS, C67x+, TMS320C6000, C6000 are trademarks of Texas Instruments.
3ARM926EJ-S, EmbeddedICE-RT, ETM9, CoreSight are trademarks of ARM Limited.
4ARM, Jazelle are registered trademarks of ARM Limited.
ADVANCE INFORMATION concerns new products in the sampling
or preproduction phaseof development. Characteristic dataand other
specifications are subjectto change without notice.
32-Bit Multiplies, Four 16 x 16-Bit– Dedicated switched central resource
Multiplies, or Eight 8 x 8-Bit Multiplies per
Clock Cycle, and Complex Multiples
– Instruction Packing Reduces Code Size
– All Instructions Conditional
– Hardware Support for Modulo Loop
Operation
– Protected Mode Operation
– Exceptions Support for Error Detection and
Program Redirection
• 128K-Byte RAM Shared Memory
• 3.3V LVCMOS IOs (except for USB interfaces)
• Two External Memory Interfaces:
– EMIFA
•NOR (8-/16-Bit-Wide Data)
•NAND (8-/16-Bit-Wide Data)
•16-Bit SDRAM With 128MB Address
Space
– EMIFB
•32-Bit or 16-Bit SDRAM With 256MB
Address Space
• Three Configurable 16550 type UART Modules:
– UART0 With Modem Control Signals
– Autoflow control signals (CTS, RTS) on
UART0 only
– 16-byte FIFO
• USB 1.1 OHCI (Host) With Integrated PHY
(USB1)
• USB 2.0 OTG Port With Integrated PHY (USB0)
– USB 2.0 High-/Full-Speed Client
– USB 2.0 High-/Full-/Low-Speed Host
– End Point 0 (Control)
– End Points 1,2,3,4 (Control, Bulk, Interrupt or
ISOC) Rx and Tx
• Three Multichannel Audio Serial Ports:
– Six Clock Zones and 28 Serial Data Pins
– Supports TDM, I2S, and Similar Formats
– DIT-Capable (McASP2)
– FIFO buffers for Transmit and Receive
• 10/100 Mb/s Ethernet MAC (EMAC):
– IEEE 802.3 Compliant (3.3-V I/O Only)
– RMII Media Independent Interface
– Management Data I/O (MDIO) Module
• Real-Time Clock With 32 KHz Oscillator and
Separate Power Rail
• One 64-Bit General-Purpose Timer
(Configurable as Two 32-Bit Timers)
• One 64-bit General-Purpose/Watchdog Timer
(Configurable as Two 32-bit General-Purpose
Timers)
• Three Enhanced Pulse Width Modulators
– 16x or 13x Oversampling Option(eHRPWM):
• LCD Controller– Dedicated 16-Bit Time-Base Counter With
• Two Serial Peripheral Interfaces (SPI) Each
Period And Frequency Control
With One Chip-Select– 6 Single Edge, 6 Dual Edge Symmetric or 3
• Multimedia Card (MMC)/Secure Digital (SD)
Dual Edge Asymmetric Outputs
Card Interface with Secure Data I/O (SDIO)– Dead-Band Generation
• Two Master/Slave Inter-Integrated Circuit (I2C– PWM Chopping by High-Frequency Carrier
Bus™)
• One Host-Port Interface (HPI) With 16-Bit-Wide
Muxed Address/Data Bus For High Bandwidth
• Programmable Real-Time Unit Subsystem
(PRUSS)
– Trip Zone Input
• Three 32-Bit Enhanced Capture Modules
(eCAP):
– Configurable as 3 Capture Inputs or 3
Auxiliary Pulse Width Modulator (APWM)
– Two Independent Programmable Realtimeoutputs
Unit (PRU) Cores
– Single Shot Capture of up to Four Event
•32-Bit Load/Store RISC architectureTime-Stamps
•4K Byte instruction RAM per core• Two 32-Bit Enhanced Quadrature Encoder
•512 Bytes data RAM per core
•PRU Subsystem (PRUSS) can be disabled
via software to save power
– Standard power management mechanism
•Clock gating
•Entire subsystem under a single PSC
clock gating domain
The OMAP-L137 is a low-power applications processor based on an ARM926EJ-S™ and a C674x DSP
core. It consumes significantly lower power than other members of the TMS320C6000™ platform of
DSPs.
The OMAP-L137 enables OEMs and ODMs to quickly bring to market devices featuring robust operating
systems support, rich user interfaces, and high processing performance life through the maximum
flexibility of a fully integrated mixed processor solution.
The dual-core architecture of the OMAP-L137 provides benefits of both DSP and Reduced Instruction Set
Computer (RISC) technologies, incorporating a high-performance TMS320C674x DSP core and an
ARM926EJ-S core.
The ARM926EJ-S is a 32-bit RISC processor core that performs 32-bit or 16-bit instructions and
processes 32-bit, 16-bit, or 8-bit data. The core uses pipelining so that all parts of the processor and
memory system can operate continuously.
The ARM core has a coprocessor 15 (CP15), protection module, and Data and program Memory
Management Units (MMUs) with table look-aside buffers. It has separate 16K-byte instruction and
16K-byte data caches. Both are four-way associative with virtual index virtual tag (VIVT). The ARM core
also has a 8KB RAM (Vector Table) and 64KB ROM.
The OMAP-L137 DSP core uses a two-level cache-based architecture. The Level 1 program cache (L1P)
is a 32KB direct mapped cache and the Level 1 data cache (L1D) is a 32KB 2-way set-associative cache.
The Level 2 program cache (L2P) consists of a 256KB memory space that is shared between program
and data space. L2 memory can be configured as mapped memory, cache, or combinations of the two.
Although the DSP L2 is accessible by ARM and other hosts in the system, an additional 128KB RAM
shared memory is available for use by other hosts without affecting DSP performance.
www.ti.com
The peripheral set includes: a 10/100 Mb/s Ethernet MAC (EMAC) with a Management Data Input/Output
(MDIO) module; two inter-integrated circuit (I2C) bus interfaces; 3 multichannel audio serial ports (McASP)
with 16/12/4 serializers and FIFO buffers; 2 64-bit general-purpose timers each configurable (one
configurable as watchdog); a configurable 16-bit host port interface (HPI) ; up to 8 banks of 16 pins of
general-purpose input/output (GPIO) with programmable interrupt/event generation modes, multiplexed
with other peripherals; 3 UART interfaces (one with RTS and CTS); 3 enhanced high-resolution pulse
width modulator (eHRPWM) peripherals; 3 32-bit enhanced capture (eCAP) module peripherals which can
be configured as 3 capture inputs or 3 auxiliary pulse width modulator (APWM) outputs; 2 32-bit enhanced
quadrature pulse (eQEP) peripherals; and 2 external memory interfaces: an asynchronous and SDRAM
external memory interface (EMIFA) for slower memories or peripherals, and a higher speed memory
interface (EMIFB) for SDRAM.
The Ethernet Media Access Controller (EMAC) provides an efficient interface between the OMAP-L137
and the network. The EMAC supports both 10Base-T and 100Base-TX, or 10 Mbits/second (Mbps) and
100 Mbps in either half- or full-duplex mode. Additionally an Management Data Input/Output (MDIO)
interface is available for PHY configuration.
The HPI, I2C, SPI, USB1.1 and USB2.0 ports allow the OMAP-L137 to easily control peripheral devices
and/or communicate with host processors.
The rich peripheral set provides the ability to control external peripheral devices and communicate with
external processors. For details on each of the peripherals, see the related sections later in this document
and the associated peripheral reference guides.
The OMAP-L137 has a complete set of development tools for both the ARM and DSP. These include C
compilers, a DSP assembly optimizer to simplify programming and scheduling, and a Windows™
debugger interface for visibility into source code execution.
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
This data manual revision history highlights the changes made to the SPRS563C device-specific data
manual to make it an SPRS563D revision.
Table 2-1. Revision History
ADDITIONS/MODIFICATIONS/DELETIONS
Global - Replaced all "CLKIN" references with "OSCIN"
Global - Updated td(SCSL_SPC)S min from P to 2P
Global - Made changes in the document to reflect the following detail.
"The DSP L2 ROM is used for boot purposes and cannot be programmed with application code".
Global - Updated the pin map graphics to fix typos.
Global - Added PRUSS content
Global - Updated SPI Electrical parameters
Section 1.1, Features - Updated "One 64-bit General-Purpose Timer (Watch Dog)" to "One 64-bit General-Purpose/Watchdog Timer
(Configurable as Two 32-bit General-Purpose Timers)"
Section 5.1, Absolute Maximum Ratings - Removed the references to USB0_VDDA12
Added Section 5.3
Updated the EMIFA Asynchronous Memory Timing Diagrams in Section 6.11.5.
Added "During emulation, the emulator will maintain TRST high so only warm reset (not POR) is available during emulation debug and
Table 3-1. Characteristics of the OMAP-L137 Processor (continued)
HARDWARE FEATURESOMAP-L137
CPU FrequencyMHz
Voltage
Package17 mm x 17 mm, 256-Ball 1 mm pitch, PBGA (ZKB)
Product Status
(1) ADVANCE INFORMATION concerns new products in the sampling or preproduction phase of development. Characteristic data and
other specifications are subject to change without notice.
PRODUCTION DATA information is current as of publication date. Products conform to specifications per the terms of the Texas
Instruments standard warranty. Production processing does not necessarily include testing of all parameters.
(1)
Core (V)1.2V / 1.3V
I/O (V)3.3 V / 1.8 V (1.8 V for USB only)
Product Preview (PP),
Advance Information
(AI),
or Production Data
(PD)
674x DSP at 375 MHz(1.2V) or 456 MHz (1.3V)
ARM926 at 375 MHz(1.2V) or 456 MHz (1.3V)
375 MHz Versions -PD
456 MHz Version - AI
3.2Device Compatibility
The ARM926EJ-S RISC CPU is compatible with other ARM9 CPUs from ARM Holdings plc.
The C674x DSP core is code-compatible with the C6000™ DSP platform and supports features of both
the C64x+ and C67x+ DSP families.
3.3ARM Subsystem
The ARM Subsystem includes the following features:
•ARM926EJ-S RISC processor
•ARMv5TEJ (32/16-bit) instruction set
•Little endian
•System Control Co-Processor 15 (CP15)
•MMU
•16KB Instruction cache
•16KB Data cache
•Write Buffer
•Embedded Trace Module and Embedded Trace Buffer (ETM/ETB)
•ARM Interrupt controller
3.3.1ARM926EJ-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:
•Separate instruction and data (internal RAM) interfaces
•Separate instruction and data AHB bus interfaces
•Embedded Trace Module and Embedded Trace Buffer (ETM/ETB)
For more complete details on the ARM9, refer to the ARM926EJ-S Technical Reference Manual, available
at http://www.arm.com
3.3.2CP15
The ARM926EJ-S system control coprocessor (CP15) is used to configure and control instruction and
data caches, 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.3.3MMU
A single set of two level page tables stored in main memory is used to control the address translation,
permission checks and memory region attributes for both data and instruction accesses. The MMU uses a
single unified Translation Lookaside Buffer (TLB) to cache the information held in the page tables. The
MMU features are:
•Standard ARM architecture v4 and v5 MMU mapping sizes, domains and access protection scheme.
•Access permissions for large pages and small pages can be specified separately for each quarter of
the page (subpage permissions)
•Hardware page table walks
•Invalidate entire TLB, using CP15 register 8
•Invalidate TLB entry, selected by MVA, using CP15 register 8
•Lockdown of TLB entries, using CP15 register 10
www.ti.com
3.3.4Caches and Write Buffer
The size of the Instruction cache is 16KB, Data cache is 16KB. 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.
SPRS563D–SEPTEMBER 2008–REVISED AUGUST 2010
3.3.5Advanced High-Performance Bus (AHB)
The ARM Subsystem uses the AHB port of the ARM926EJ-S to connect the ARM to the Config bus and
the external memories. Arbiters are employed to arbitrate access to the separate D-AHB and I-AHB by the
Config Bus and the external memories bus.
3.3.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 ARM926EJ-S Subsystem in the OMAP-L137 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 OMAP-L137 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.
This device uses ETM9™ version r2p2 and ETB version r0p1. Documentation on the ETM and ETB is
available from ARM Ltd. Reference the ' CoreSight™ ETM9™ Technical Reference Manual, revision r0p1'
and the 'ETM9 Technical Reference Manual, revision r2p2'.
3.3.7ARM Memory Mapping
By default the ARM has access to most on and off chip memory areas, including the DSP Internal
memories, EMIFA, EMIFB, and the additional 128K byte on chip shared SRAM. Likewise almost all of the
on chip peripherals are accessible to the ARM by default.
See Table 3-4 for a detailed top level OMAP-L137 memory map that includes the ARM memory space.
The C674x Central Processing Unit (CPU) consists of eight functional units, two register files, and two
data paths as shown in Figure 3-2. The two general-purpose register files (A and B) each contain
32 32-bit registers for a total of 64 registers. The general-purpose registers can be used for data or can be
data address pointers. The data types supported include packed 8-bit data, packed 16-bit data, 32-bit
data, 40-bit data, and 64-bit data. Values larger than 32 bits, such as 40-bit-long or 64-bit-long values are
stored in register pairs, with the 32 LSBs of data placed in an even register and the remaining 8 or
32 MSBs in the next upper register (which is always an odd-numbered register).
The eight functional units (.M1, .L1, .D1, .S1, .M2, .L2, .D2, and .S2) are each capable of executing one
instruction every clock cycle. The .M functional units perform all multiply operations. The .S and .L units
perform a general set of arithmetic, logical, and branch functions. The .D units primarily load data from
memory to the register file and store results from the register file into memory.
The C674x CPU combines the performance of the C64x+ core with the floating-point capabilities of the
C67x+ core.
Each C674x .M unit can perform one of the following each clock cycle: one 32 x 32 bit multiply, one 16 x
32 bit multiply, two 16 x 16 bit multiplies, two 16 x 32 bit multiplies, two 16 x 16 bit multiplies with
add/subtract capabilities, four 8 x 8 bit multiplies, four 8 x 8 bit multiplies with add operations, and four
16 x 16 multiplies with add/subtract capabilities (including a complex multiply). There is also support for
Galois field multiplication for 8-bit and 32-bit data. Many communications algorithms such as FFTs and
modems require complex multiplication. The complex multiply (CMPY) instruction takes for 16-bit inputs
and produces a 32-bit real and a 32-bit imaginary output. There are also complex multiplies with rounding
capability that produces one 32-bit packed output that contain 16-bit real and 16-bit imaginary values. The
32 x 32 bit multiply instructions provide the extended precision necessary for high-precision algorithms on
a variety of signed and unsigned 32-bit data types.
SPRS563D–SEPTEMBER 2008–REVISED AUGUST 2010
The .L Unit (or Arithmetic Logic Unit) now incorporates the ability to do parallel add/subtract operations on
a pair of common inputs. Versions of this instruction exist to work on 32-bit data or on pairs of 16-bit data
performing dual 16-bit add and subtracts in parallel. There are also saturated forms of these instructions.
The C674x core enhances the .S unit in several ways. On the previous cores, dual 16-bit MIN2 and MAX2
comparisons were only available on the .L units. On the C674x core they are also available on the .S unit
which increases the performance of algorithms that do searching and sorting. Finally, to increase data
packing and unpacking throughput, the .S unit allows sustained high performance for the quad 8-bit/16-bit
and dual 16-bit instructions. Unpack instructions prepare 8-bit data for parallel 16-bit operations. Pack
instructions return parallel results to output precision including saturation support.
Other new features include:
•SPLOOP - A small instruction buffer in the CPU that aids in creation of software pipelining loops where
multiple iterations of a loop are executed in parallel. The SPLOOP buffer reduces the code size
associated with software pipelining. Furthermore, loops in the SPLOOP buffer are fully interruptible.
•Compact Instructions - The native instruction size for the C6000 devices is 32 bits. Many common
instructions such as MPY, AND, OR, ADD, and SUB can be expressed as 16 bits if the C674x
compiler can restrict the code to use certain registers in the register file. This compression is
performed by the code generation tools.
•Instruction Set Enhancement - As noted above, there are new instructions such as 32-bit
multiplications, complex multiplications, packing, sorting, bit manipulation, and 32-bit Galois field
multiplication.
•Exceptions Handling - Intended to aid the programmer in isolating bugs. The C674x CPU is able to
detect and respond to exceptions, both from internally detected sources (such as illegal op-codes) and
from system events (such as a watchdog time expiration).
•Privilege - Defines user and supervisor modes of operation, allowing the operating system to give a
basic level of protection to sensitive resources. Local memory is divided into multiple pages, each with
read, write, and execute permissions.
•Time-Stamp Counter - Primarily targeted for Real-Time Operating System (RTOS) robustness, a
free-running time-stamp counter is implemented in the CPU which is not sensitive to system stalls.
For more details on the C674x CPU and its enhancements over the C64x architecture, see the following
documents:
•TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide (literature number SPRU732)
•TMS320C64x Technical Overview (literature number SPRU395)
A. On .M unit, dst2 is 32 MSB.
B. On .M unit, dst1 is 32 LSB.
C. On C64x CPU .M unit, src2 is 32 bits; on C64x+ CPU .M unit, src2 is 64 bits.
D. On .L and .S units, odd dst connects to odd register files and even dst connects to even register files.
The DSP memory map is shown in Section 3.5.
By default the DSP also has access to most on and off chip memory areas, with the exception of the ARM
RAM, ROM, and AINTC interrupt controller. The DSP also boots first, and must release the ARM from
reset before the ARM can execute any code.
Additionally, the DSP megamodule includes the capability to limit access to its internal memories through
its SDMA port; without needing an external MPU unit.
3.4.2.1ARM Internal Memories
The DSP does not have access to the ARM internal memory.
3.4.2.2External Memories
The DSP has access to the following External memories:
•Asynchronous EMIF / SDRAM / NAND / NOR Flash (EMIFA)
•SDRAM (EMIFB)
3.4.2.3DSP Internal Memories
The DSP has access to the following DSP memories:
•L2 RAM
•L1P RAM
•L1D RAM
www.ti.com
3.4.2.4C674x CPU
The C674x core uses a two-level cache-based architecture. The Level 1 Program cache (L1P) is 32 KB
direct mapped cache and the Level 1 Data cache (L1D) is 32 KB 2-way set associated cache. The Level 2
memory/cache (L2) consists of a 256 KB memory space that is shared between program and data space.
L2 memory can be configured as mapped memory, cache, or a combination of both.
Table 3-2 shows a memory map of the C674x CPU cache registers for the device.
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.
3.6.1Pin Map (Bottom View)
Figure 3-3 shows the pin assignments for the ZKB package.
Table 3-5 to Table 3-25 identify the external signal names, the associated pin/ball numbers along with the
mechanical package designator, the pin type (I, O, IO, OZ, or PWR), whether the pin/ball has any internal
pullup/pulldown resistors, whether the pin/ball is configurable as an IO in GPIO mode, and a functional pin
description.
3.7.1Device Reset and JTAG
Table 3-5. Reset and JTAG Terminal Functions
SIGNAL NAMETYPE
RESETG3IDevice reset inputAMUTE0/ RESETOUTL4O
TMSJ1IIPUJTAG test mode select
TDIJ2IIPUJTAG test data input
TDOJ3OIPDJTAG test data output
TCKH3IIPUJTAG test clock
TRSTJ4IIPDJTAG test reset
EMU[0]/GP7[15]J5I/OIPUEmulation Signal
RTCK/GP7[14]K1I/OIPDJTAG Test Clock Return Clock Output
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: For multiplexed pins where functions have different types (ie., input versus output), the table reflects the pin function direction for
that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
(3) Open drain mode for RESETOUT function.
PIN NO
ZKB
(1)
(3)
(2)
PULL
RESET
IPDReset output. Multiplexed with McASP0 mute output.
JTAG
DESCRIPTION
3.7.2High-Frequency Oscillator and PLL
Table 3-6. High-Frequency Oscillator and PLL Terminal Functions
RTC_CVDDG1PWRRTC module core power (isolated from rest of chip CVDD)
RTC_XIH1ILow-frequency (32-kHz) oscillator receiver for real-time clock
RTC_XOH2OLow-frequency (32-kHz) oscillator driver for real-time clock
RTC_V
ss
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: For multiplexed pins where functions have different types (ie., input versus output), the table reflects the pin function direction for
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
ACLKX0/ECAP0/APWM0/GP2[12]C5I/OIPDMcASP0, GPIOinput or auxiliary
ACLKR0/ECAP1/APWM1/GP2[15]B4I/OIPDMcASP0, GPIOinput or auxiliary
ACLKR1/ECAP2/APWM2/GP4[12]L2I/OIPDMcASP1, GPIOinput or auxiliary
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
ACLKX1/EPWM0A/GP3[15]K3I/OIPD
AHCLKX1/EPWM0B/GP3[14]K2I/OIPDeHRPWM0 B output
AMUTE1/EPWMTZ/GP4[14]D4I/OIPD
AFSX1/EPWMSYNCI/EPWMSYNCO/GP4[10]K4I/OIPD
AXR1[8]/EPWM1A/GP4[8]M2I/OIPD
AXR1[7]/EPWM1B/GP4[7]M3I/OIPDeHRPWM1 B output
AMUTE1/EPWMTZ/GP4[14]D4I/OIPD
AXR1[6]/EPWM2A/GP4[6]M4I/OIPD
AXR1[5]/EPWM2B/GP4[5]N1I/OIPDeHRPWM2 B output
AMUTE1/EPWMTZ/GP4[14]D4I/OIPD
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
PIN NO
ZKB
eHRPWM0
eHRPWM1
eHRPWM2
(1)
PULL
(2)
MUXEDDESCRIPTION
eHRPWM0 A output
McASP1, GPIO
McASP1, eHRPWM1,eHRPWM0 trip zone
GPIO, eHRPWM2input
McASP1, eHRPWM0,eHRPWM0 module or
GPIOsync output to external
McASP1, GPIO
McASP1, eHRPWM1,eHRPWM1 trip zone
GPIO, eHRPWM2input
McASP1, GPIO
McASP1, eHRPWM1,eHRPWM2 trip zone
GPIO, eHRPWM2input
AXR1[4]/EQEP1B/GP4[4]N2IIPD
SPI0_CLK/EQEP1I/GP5[2]/BOOT[2]T5IIPDeQEP1 index
SPI1_CLK/EQEP1S/GP5[7]/BOOT[7]T6IIPDeQEP1 strobe
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
(1) Boot decoding will be defined in the ROM datasheet.
(2) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(3) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
UART0_RXD/I2C0_SDA/TM64P0_IN12/GP5[8]/BOOT[8]R3I/OIPUI2C0 serial data
UART0_TXD/I2C0_SCL/TM64P0_OUT12/GP5[9]/BOOT[9]P3I/OIPUI2C0 serial clock
SPI1_SIMO[0]/I2C1_SDA/GP5[6]/BOOT[6]N5I/OIPUI2C1 serial data
SPI1_SOMI[0]/I2C1_SCL/GP5[5]/BOOT[5]P5I/OIPUI2C1 serial clock
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
No external pins. The Timer1 peripheral signals are not pinned out as external pins.
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
Table 3-20. Universal Serial Bus (USB) Terminal Functions
PIN
SIGNAL NAMETYPE
USB0_DMG4ANAUSB0 PHY data minus
USB0_DPF4ANAUSB0 PHY data plus
USB0_VDDA33H5PWRNAUSB0 PHY 3.3-V supply
USB0_VDDA18E3PWRNAUSB0 PHY 1.8-V supply input
USB0_VDDA12
USB0_IDD2ANAUSB0 PHY identification (mini-A or mini-B plug)
USB0_VBUSD3ANAUSB0 bus voltage
USB0_DRVVBUS/GP4[15]E40IPDGPIOUSB0 controller VBUS control output
AHCLKX0/AHCLKX2/USB_REFCLKIN/
GP2[11]
USB1_DMB3ANAUSB1 PHY data minus
USB1_DPA3ANAUSB1 PHY data plus
USB1_VDDA33C1PWRNAUSB1 PHY 3.3-V supply
USB1_VDDA18C2PWRNAUSB1 PHY 1.8-V supply
AHCLKX0/AHCLKX2/USB_REFCLKIN/
GP2[11]
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
(3) Core power supply LDO output for USB PHY. This pin must be connected via a 0.22 uF capacitor to VSS.
AXR0[8]/MDIO_D/GP3[8]B6I/OIPUMDIO serial data
AXR0[7]/MDIO_CLK/GP3[7]A6OIPDMDIO clock
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
(1) I = Input, O = Output, I/O = Bidirectional, Z = High impedance, PWR = Supply voltage, GND = Ground, A = Analog signal.
Note: The pin type shown refers to the input, output or high-impedance state of the pin function when configured as the the signal name
highlighted in bold. All multiplexed signals may enter a high-impedance state when the configured function is input-only or the configured
function supports high-Z operation. All GPIO signals can be used as input or output. For multiplexed pins where functions have different
types (ie., input versus output), the table reflects the pin function direction for that particular peripheral.
(2) IPD = Internal Pulldown resistor, IPU = Internal Pullup resistor
This device supports a variety of boot modes through an internal ROM bootloader. This device does not
support dedicated hardware boot modes; therefore, all boot modes utilize the internal ROM. The input
states of the BOOT pins are sampled and latched into the BOOTCFG register, which is part of the system
configuration (SYSCFG) module, when device reset is deasserted. Boot mode selection is determined by
the values of the BOOT pins
The following boot modes are supported:
•NAND Flash boot
– 8-bit NAND
•NOR Flash boot
– NOR Direct boot (8-bit or 16-bit)
– NOR Legacy boot (8-bit or 16-bit)
– NOR AIS boot (8-bit or 16-bit)
The following system level features of the chip are controlled by the SYSCFG peripheral:
•Readable Device, Die, and Chip Revision ID
•Control of Pin Multiplexing
•Priority of bus accesses different bus masters in the system
•Capture at power on reset the chip BOOT[15:0] pin values and make them available to software
•Special case settings for peripherals:
– Locking of PLL controller settings
– Default burst sizes for EDMA3 TC0 and TC1
– Selection of the source for the eCAP module input capture (including on chip sources)
– McASP AMUTEIN selection and clearing of AMUTE status for the three McASP peripherals
– Control of the reference clock source and other side-band signals for both of the integrated USB
PHYs
– Clock source selection for EMIFA and EMIFB
•Selects the source of emulation suspend signal (from either ARM or DSP) of peripherals supporting
this function.
•Control of on-chip inter-processor interrupts for signaling between ARM and DSP
Many registers are accessible only by a host (ARM or DSP) when it is operating in its privileged mode.
(ex. from the kernel, but not from user space code).
SPRS563D–SEPTEMBER 2008–REVISED AUGUST 2010
Table 4-1. System Configuration (SYSCFG) Module Register Access
Proper board design should ensure that input pins to the device always be at a valid logic level and not
floating. This may be achieved via pullup/pulldown resistors. The device features internal pullup (IPU) and
internal pulldown (IPD) resistors on most pins to eliminate the need, unless otherwise noted, for external
pullup/pulldown resistors.
An external pullup/pulldown resistor needs to be used in the following situations:
•Boot and Configuration Pins: If the pin is both routed out and 3-stated (not driven), an external
pullup/pulldown resistor is strongly recommended, even if the IPU/IPD matches the desired value/state.
•Other Input Pins: If the IPU/IPD does not match the desired value/state, use an external
pullup/pulldown resistor to pull the signal to the opposite rail.
For the boot and configuration pins, if they are both routed out and 3-stated (not driven), it is strongly
recommendedthatanexternalpullup/pulldownresistorbeimplemented.Although,internal
pullup/pulldown resistors exist on these pins and they may match the desired configuration value,
providing external connectivity can help ensure that valid logic levels are latched on these device boot and
configuration pins. In addition, applying external pullup/pulldown resistors on the boot and configuration
pins adds convenience to the user in debugging and flexibility in switching operating modes.
Tips for choosing an external pullup/pulldown resistor:
•Consider the total amount of current that may pass through the pullup or pulldown resistor. Make sure
to include the leakage currents of all the devices connected to the net, as well as any internal pullup or
pulldown resistors.
•Decide a target value for the net. For a pulldown resistor, this should be below the lowest VILlevel of
all inputs connected to the net. For a pullup resistor, this should be above the highest VIHlevel of all
inputs on the net. A reasonable choice would be to target the VOLor VOHlevels for the logic family of
the limiting device; which, by definition, have margin to the VILand VIHlevels.
•Select a pullup/pulldown resistor with the largest possible value; but, which can still ensure that the net
will reach the target pulled value when maximum current from all devices on the net is flowing through
the resistor. The current to be considered includes leakage current plus, any other internal and
external pullup/pulldown resistors on the net.
•For bidirectional nets, there is an additional consideration which sets a lower limit on the resistance
value of the external resistor. Verify that the resistance is small enough that the weakest output buffer
can drive the net to the opposite logic level (including margin).
•Remember to include tolerances when selecting the resistor value.
•For pullup resistors, also remember to include tolerances on the IO supply rail.
•For most systems, a 1-kΩ resistor can be used to oppose the IPU/IPD while meeting the above
criteria. Users should confirm this resistor value is correct for their specific application.
•For most systems, a 20-kΩ resistor can be used to compliment the IPU/IPD on the boot and
configuration pins while meeting the above criteria. Users should confirm this resistor value is correct
for their specific application.
•For more detailed information on input current (II), and the low-/high-level input voltages (VILand VIH)
for the device, see Section 5.2, Recommended Operating Conditions.
•For the internal pullup/pulldown resistors for all device pins, see the peripheral/system-specific terminal
functions table.
5.1Absolute Maximum Ratings Over Operating Case Temperature Range
(Unless Otherwise Noted)
Supply voltage ranges
Input voltage ranges
Output voltage ranges
Clamp Currentrails. Limit clamp current that flows through the I/O's internal diode
Operating Junction Temperature ranges,
T
J
Storage temperature range, T
(1) Stresses beyond those listed under "absolute maximum ratings" may cause permanent damage to the device. These are stress ratings
only, and functional operation of the device at these or any other conditions beyond those indicated under "recommended operating
conditions" is not implied. Exposure to absolute-maximum-rated conditions for extended periods may affect device reliability.
(2) All voltage values are with respect to VSS, PLL0_VSSA, OSCVSS, RTC_VSS
(3) Up to a max of 24 hours.
stg
(1)
Core-0.5 V to 1.4 V
(CVDD, RVDD, RTC_CVDD, PLL0_VDDA )
I/O, 1.8V-0.5 V to 2 V
(USB0_VDDA18, USB1_VDDA18)
I/O, 3.3V-0.5 V to 3.8V
(DVDD, USB0_VDDA33, USB1_VDDA33)
VII/O, CVDD-0.3 V to CVDD + 0.3V
(OSCIN, RTC_XI)
VII/O, 3.3V-0.3V to DVDD + 0.3V
(Steady State)
VII/O, 3.3VDVDD + 20%
(Transient)up to 20% of Signal
VII/O, USB 5V Tolerant Pins:5.25V
(USB0_DM, USB0_DP, USB0_ID, USB1_DM, USB1_DP)
VII/O, USB0 VBUS5.50V
VOI/O, 3.3V-0.5 V to DVDD + 0.3V
(Steady State)
VOI/O, 3.3V20% of DVDD for up to
(Transient Overshoot/Undershoot)20% of the signal period
Input or Output Voltages 0.3V above or below their respective power±20mA
protection cells.
Commercial0°C to 90°C
Industrial (D suffix )-40°C to 90°C
Extended (A suffix)-40°C to 105°C
Automotive (T suffix)-40°C to 125°C
(default)-55°C to 150°C
Transition time, 10%-90%, All Inputs (unless otherwise specified
in the electrical data sections)
Operating ambient
temperature range
DSP and ARM
Operating Frequency
(SYSCLK1,6)
(1) The RTC provides an option for isolating the RTC_CVDD from the CVDD to reduce current leakage when the RTC is powered
independently. If these power supplies are not isolated (CTRL.SPLITPOWER=0), RTC_CVDD must be equal to or greater than CVDD.
If these power supplies are isolated (CTRL.SPLITPOWER=1), RTC_CVDD may be lower than CVDD.
(2) When an external crystal is used, oscillator (OSC_VSS, RTC_VSS) ground must be kept separate from other grounds and connected
directly to the crystal load capacitor ground. These pins are shorted to VSS on the device itself and should not be connected to VSS on
the circuit board. If a crystal is not used and the clock input is driven directly, then the oscillator VSS may be connected to board ground.
(3) These I/O specifications do not apply to USB I/Os. USB0 I/Os adhere to USB2.0 specification. USB1 I/Os adhere to USB1.1
specification.
(4) Whichever is smaller. P = the period of the applied signal. Maintaining transition times as fast as possible is recommended to improve
The information in the section below is provided solely for your convenience and does not extend or
modify the warranty provided under TI’s standard terms and conditions for TI semiconductor products.
To avoid significant degradation, the device power-on hours (POH) must be limited to the following:
Table 5-1. Recommended Power-On Hours
SiliconOperating JunctionPower-On Hours [POH]
RevisionTemperature (Tj)(hours)
A300 MHz0 to 90 °C1.2V100,000
B375 MHz0 to 90 °C1.2V100,000
B375 MHz-40 to 105 °C1.2V75,000
B375 MHz-40 to 125 °C1.2V20,000
B456 MHz0 to 90 °C1.3V100,000
B456 MHz-40 to 90 °C1.3V100,000
(1) 100,000 POH can be achieved at this temperature condition if the device operation is limited to 345 MHz.
Note: Logic functions and parameter values are not assured out of the range specified in the recommended
operating conditions.
The above notations cannot be deemed a warranty or deemed to extend or modify the warranty under
TI’s standard terms and conditions for TI semiconductor products.
(1) These I/O specifications apply to regular 3.3V IOs and do not apply to USB0 or USB1 unless specifically indicated. USB0 I/Os adhere to
the USB 2.0 specification. USB1 I/Os adhere to the USB 1.1 specification.
(2) IIapplies to input-only pins and bi-directional pins. For input-only pins, IIindicates the input leakage current. For bi-directional pins, I
indicates the input leakage current and off-state (Hi-Z) output leakage current.
(3) Applies only to pins with an internal pullup (IPU) or pulldown (IPD) resistor.
(4) IOZapplies to output-only pins, indicating off-state (Hi-Z) output leakage current.
6Peripheral Information and Electrical Specifications
6.1Parameter Information
6.1.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 and the input signals are driven between 0V and the appropriate IO supply rail for the signal.
Figure 6-1. Test Load Circuit for AC Timing Measurements
www.ti.com
The load capacitance value stated is only for characterization and measurement of AC timing signals. This
load capacitance value does not indicate the maximum load the device is capable of driving.
6.1.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
Figure 6-2. Input and Output Voltage Reference Levels for AC Timing Measurements
All rise and fall transition timing parameters are referenced to VILMAX and VIHMIN for input clocks,
VOLMAX and VOHMIN for output clocks.
Figure 6-3. Rise and Fall Transition Time Voltage Reference Levels
6.2Recommended Clock and Control Signal Transition Behavior
All clocks and control signals must transition between VIHand VIL(or between VILand VIH) in a monotonic
manner.
6.3Power Supplies
6.3.1Power-on Sequence
The device should be powered-on in the following order:
•1) RTC (RTC_CVDD) may be powered from an external device (such as a battery) prior to all other
supplies being applied or powered-up at the same time as CVDD. If the RTC is not used, RTC_CVDD
should be connected to CVDD. RTC_CVDD should not be left unpowered while CVDD is powered.
•2a) CVDD core logic supply
•2b) Other 1.2V logic supplies (RVDD, PLL0_VDDA). Groups 2a) and 2b) may be powered up together
or 2a) first followed by 2b).
•3) All 1.8V IO supplies (USB0_VDDA18, USB1_VDDA18).
•4) All digital IO and analog 3.3V PHY supplies (DVDD, USB0_VDDA33, USB1_VDDA33).
USB0_VDDA33 and USB1_VDDA33 are not required if both USB0 and USB1 are not used and may
be left unconnected.
Group 3) and group 4) may be powered on in either order [3 then 4, or 4 then 3] but group 4) must be
powered-on after the core logic supplies.
There is no specific required voltage ramp rate for any of the supplies.
RESET must be maintained active until all power supplies have reached their nominal values.
6.3.2Power-off Sequence
The power supplies can be powered-off in any order as long as the 3.3V supplies do not remain powered
with the other supplies unpowered.
6.4Unused USB0 (USB2.0) and USB1 (USB1.1) Pin Configurations
If one or both USB modules on the device are not used, then some of the power supplies to those
modules may not be required. This can eliminate the requirement for a 1.8V power supply to the USB
modules. The required pin configurations for unused USB modules are shown below.
Table 6-1. Unused USB0 and USB1 Pin Configurations
SIGNAL NAMEConfigurationConfiguration
(When USB0 and USB1 are not used)(When USB0 is used
and USB1 is not used)
USB0_DMNo connectUse as USB0 function
USB0_DPNo connectUse as USB0 function
USB0_VDDA33No connect3.3V
USB0_VDDA18No connect1.8V
USB0_IDNo connectUse as USB0 function
USB0_VBUSNo connectUse as USB0 function
USB0_DRVVBUS/GP4[15]No connect or use as alternate functionUse as USB0 or alternate function
USB0_VDDA12No connectInternal USB0 PHY output connected to an
A power-on reset (POR) is required to place the device in a known good state after power-up. Power-On
Reset is initiated by bringing RESET and TRST low at the same time. POR sets all of the device internal
logic to its default state. All pins are tri-stated with the exception of RESETOUT, which remains active
through the reset sequence, and RTCK/GP7[14]. If an emulator is driving TCK into the device during
reset, then RTCK/GP7[14] will drive out RTCK. If TCK is not being driven into the device during reset,
then RTCK/GP7[14] will drive low.RESETOUT is an output for use by other controllers in the system that
indicates the device is currently in reset.
While both TRST and RESET need to be asserted upon power up, only RESET needs to be released for
the device to boot properly. TRST may be asserted indefinitely for normal operation, keeping the JTAG
port interface and device's emulation logic in the reset state.
TRST only needs to be released when it is necessary to use a JTAG controller to debug the device or
exercise the device's boundary scan functionality. Note: TRST is synchronous and must be clocked by
TCK; otherwise, the boundary scan logic may not respond as expected after TRST is asserted.
RESET must be released only in order for boundary-scan JTAG to read the variant field of IDCODE
correctly. Other boundary-scan instructions work correctly independent of current state of RESET. For
maximum reliability, the device includes an internal pulldown on the TRST pin to ensure that TRST will
always be asserted upon power up and the device's internal emulation logic will always be properly
initialized.
SPRS563D–SEPTEMBER 2008–REVISED AUGUST 2010
JTAG controllers from Texas Instruments actively drive TRST high. However, some third-party JTAG
controllers may not drive TRST high but expect the use of a pullup resistor on TRST. When using this type
of JTAG controller, assert TRST to intialize the device after powerup and externally drive TRST high
before attempting any emulation or boundary scan operations.
RTCK is maintained active through a POR.
A summary of the effects of Power-On Reset is given below:
•All internal logic (including emulation logic and the PLL logic) is reset to its default state
•Internal memory is not maintained through a POR
•RESETOUT goes active
•All device pins go to a high-impedance state
•The RTC peripheral is not reset during a POR. A software sequence is required to reset the RTC.
CAUTION: A watchdog reset triggers a POR.
6.5.2Warm Reset
A warm reset provides a limited reset to the device. Warm Reset is initiated by bringing only RESET low
(TRST is maintained high through a warm reset). Warm reset sets certain portions of the device to their
default state while leaving others unaltered. All pins are tri-stated with the exception of RESETOUT, which
remains active through the reset sequence, and RTCK/GP7[14]. If an emulator is driving TCK into the
device during reset, then RTCK/GP7[14] will drive out RTCK. If TCK is not being driven into the device
during reset, then RTCK/GP7[14] will drive low. RESETOUT is an output for use by other controllers in the
system that indicates the device is currently in reset.
During emulation, the emulator will maintain TRST high and hence only warm reset (not POR) is available
during emulation debug and development.
RTCK is maintained active through a warm reset.
A summary of the effects of Warm Reset is given below:
•All internal logic (except for the emulation logic and the PLL logic) is reset to its default state
•Internal memory is maintained through a warm reset
•RESETOUT goes active
•All device pins go to a high-impedance state
•The RTC peripheral is not reset during a warm reset. A software sequence is required to reset the
RTC.
6.5.3Reset Electrical Data Timings
Table 6-2 assumes testing over the recommended operating conditions.
Table 6-2. Reset Timing Requirements (
No.PARAMETERMINMAXUNIT
1t
w(RSTL)
2t
su(BPV-RSTH)
3t
h(RSTH-BPV)
4t
d(RSTH-
RESETOUTH)
(1) RESETOUT is multiplexed with other pin functions. See the Terminal Functions table, Table 3-5 for details.
(2) For power-on reset (POR), the reset timings in this table refer to RESET and TRST together. For warm reset, the reset timings in this
table refer to RESET only (TRST is held high).
(3) OSCIN cycles.
Pulse width, RESET/TRST low100ns
Setup time, boot pins valid before RESET/TRST high20ns
Hold time, boot pins valid after RESET/TRST high20ns
RESET high to RESETOUT high; Warm reset4096cycles
RESET high to RESETOUT high; Power-on Reset6192
(1),(2)
)
(3)
Figure 6-4. Power-On Reset (RESET and TRST active) Timing
The OMAP-L137 device includes two choices to provide an external clock input, which is fed to the
on-chip PLL to generate high-frequency system clocks. These options are illustrated in Figure 6-6 and
Figure 6-7. For input clock frequencies between 12 and 20 MHz, a crystal with 80 ohm max ESR is
recommended. For input clock frequencies between 20 and 30 MHz, a crystal with 60 ohm max ESR is
recommended. Typical load capacitance values are 10-20 pF, where the load capacitance is the series
combination of C1 and C2.
•Figure 6-6 illustrates the option that uses on-chip 1.2V oscillator with external crystal circuit.
•Figure 6-7 illustrates the option that uses an external 1.2V clock input.
(1) Whichever is smaller. P = the period of the applied signal. Maintaining transition times as fast as possible is recommended to improve
noise immunity on input signals.
OSCIN frequency range (OSCIN)1250MHz
Cycle time, external clock driven on OSCIN20ns
Pulse width high, external clock on OSCIN0.4 t
Pulse width low, external clock on OSCIN0.4 t
Transition time, OSCIN0.25P or 10
The OMAP-L137 has one PLL controller that provides clock to different parts of the system. PLL0 provides
clocks (though various dividers) to most of the components of the device.
The PLL controller provides the following:
•Glitch-Free Transitions (on changing clock settings)
•Domain Clocks Alignment
•Clock Gating
•PLL power down
The various clock outputs given by the controller are as follows:
•Domain Clocks: SYSCLK [1:n]
•Auxiliary Clock from reference clock source: AUXCLK
Various dividers that can be used are as follows:
•Post-PLL Divider: POSTDIV
•SYSCLK Divider: D1, ¼, Dn
Various other controls supported are as follows:
•PLL Multiplier Control: PLLM
•Software programmable PLL Bypass: PLLEN
www.ti.com
6.7.1PLL Device-Specific Information
The OMAP-L137 DSP generates the high-frequency internal clocks it requires through an on-chip PLL.
The PLL requires some external filtering components to reduce power supply noise as shown in
Figure 6-8.
Figure 6-8. PLL External Filtering Components
The input to the PLL is either from the on-chip oscillator (OSCIN pin) or from an external clock on the
OSCIN pin. The PLL outputs seven clocks that have programmable divider options. Figure 6-9 illustrates
the PLL Topology.
The PLL is disabled by default after a device reset. It must be configured by software according to the
allowable operating conditions listed in Table 6-5 before enabling the DSP to run from the PLL by setting
PLLEN = 1.
(1) The multiplier values must be chosen such that the PLL output frequency (at PLLOUT) is between 300 and 600 MHz, but the frequency
PLLRST: Assertion time during
initialization
Lock time: The time that the application
has to wait for the PLL to acquire locksOSCIN
before setting PLLEN, after changingcycles
PREDIV, PLLM, or OSCIN
PLL input frequency
( PLLREF)
(1)
going into the SYSCLK dividers (after the post divider) cannot exceed the maximum clock frequency defined for the device at a given
voltage operating point.
Default
Value
(1)
x20x4x32
6.7.2Device Clock Generation
PLL0 is controlled by PLL Controller 0. The PLLC0 manages the clock ratios, alignment, and gating for the
system clocks to the chip. The PLLC is responsible for controlling all modes of the PLL through software,
in terms of pre-division of the clock inputs, multiply factor within the PLL, and post-division for each of the
chip-level clocks from the PLL output. The PLLC also controls reset propagation through the chip, clock
alignment, and test points.
0x01C1 1140ALNCTLPLL Controller Clock Align Control Register
0x01C1 1144DCHANGEPLLDIV Ratio Change Status Register
0x01C1 1148CKENClock Enable Control Register
The OMAP-L137 devices have a large number of interrupts to service the needs of its many peripherals
and subsystems. Both the ARM and C674x CPUs are capable of servicing these interrupts equally. The
interrupts can be selectively enabled or disabled in either of the controllers. Also, the ARM and DSP can
communicate with each other through interrupts controlled by registers in the SYSCFG module.
6.8.1ARM CPU Interrupts
The ARM9 CPU core supports 2 direct interrupts: FIQ and IRQ. The ARM Interrupt Controller on the
OMAP-L13x extends the number of interrupts to 100, and provides features like programmable masking,
priority, hardware nesting support, and interrupt vector generation. The OMAP-L13x ARM Interrupt
controller is enhanced from previous devices like the DM6446 and DM355.
6.8.1.1ARM Interrupt Controller (AINTC) Interrupt Signal Hierarchy
On OMAP-L13x, the ARM Interrupt controller organizes interrupts into the following hierarchy:
•Peripheral Interrupt Requests
– Individual Interrupt Sources from Peripherals
•100 System Interrupts
– One or more Peripheral Interrupt Requests are combined (fixed configuration) to generate a
System Interrupt.
– After prioritization, the AINTC will provide an interrupt vector based unique to each System Interrupt
•32 Interrupt Channels
– Each System Interrupt is mapped to one of the 32 Interrupt Channels
– Channel Number determines the first level of prioritization, Channel 0 is highest priority and 31
lowest.
– If more than one system interrupt is mapped to a channel, priority within the channel is determined
by system interrupt number (0 highest priority)
•Host Interrupts (FIQ and IRQ)
– Interrupt Channels 0 and 1 generate the ARM FIQ interrupt
– Interrupt Channels 2 through 31 Generate the ARM IRQ interrupt
•Debug Interrupts
– Two Debug Interrupts are supported and can be used to trigger events in the debug subsystem
– Sources can be selected from any of the System Interrupts or Host Interrupts
www.ti.com
6.8.1.2AINTC Hardware Vector Generation
The AINTC also generates an interrupt vector in hardware for both IRQ and FIQ host interrupts. This may
be used to accelerate interrupt dispatch. A unique vector is generated for each of the 100 system
interrupts. The vector is computed in hardware as:
VECTOR = BASE + (SYSTEM INTERRUPT NUMBER × SIZE)
Where BASE and SIZE are programmable. The computed vector is a 32-bit address which may
dispatched to using a single instruction of type LDR PC, [PC, #-<offset_12>] at the FIQ and IRQ vector
locations (0xFFFF0018 and 0xFFFF001C respectively).
6.8.1.3AINTC Hardware Interrupt Nesting Support
Interrupt nesting occurs when an interrupt service routine re-enables interrupts, to allow the CPU to
interrupt the ISR if a higher priority event occurs. The AINTC provides hardware support to facilitate
interrupt nesting. It supports both global and per host interrupt (FIQ and IRQ in this case) automatic
nesting. If enabled, the AINTC will automatically update an internal nesting register that temporarily masks
interrupts at and below the priority of the current interrupt channel. Then if the ISR re-enables interrupts;
only higher priority channels will be able to interrupt it. The nesting level is restored by the ISR by writing
to the nesting level register on completion. Support for nesting can be enabled/disabled by software, with
the option of automatic nesting on a global or per host interrupt basis; or manual nesting.
6.8.1.4AINTC System Interrupt Assignments on OMAP-L137
System Interrupt assignments for the OMAP-L137 are listed in Table 6-7
The C674x DSP interrupt controller combines device events into 12 prioritized interrupts. The source for
each of the 12 CPU interrupts is user programmable and is listed in Table 6-9. Also, the interrupt
controller controls the generation of the CPU exception, NMI, and emulation interrupts. Table 6-10
summarizes the C674x interrupt controller registers and memory locations.
Table 6-9. OMAP-L137 DSP Interrupts
EVT#INTERRUPT NAMESOURCE
0EVT0C674x Int Ctl 0
1EVT1C674x Int Ctl 1
2EVT2C674x Int Ctl 2
3EVT3C674x Int Ctl 3
4T64P0_TINT12Timer64P0 - TINT12
5SYSCFG_CHIPINT2SYSCFG_CHIPSIG Register
6-Reserved
7EHRPWM0HiResTimer/PWM0 Interrupt
8EDMA3_CC0_INT1EDMA3 Channel Controller 0 Region 1 interrupt
The GPIO peripheral provides general-purpose pins that can be configured as either inputs or outputs.
When configured as an output, a write to an internal register can control the state driven on the output pin.
When configured as an input, the state of the input is detectable by reading the state of an internal
register. In addition, the GPIO peripheral can produce CPU interrupts and EDMA events in different
interrupt/event generation modes. The GPIO peripheral provides generic connections to external devices.
The GPIO pins are grouped into banks of 16 pins per bank (i.e., bank 0 consists of GPIO [0:15]).
The OMAP-L137 GPIO peripheral supports the following:
•Up to 128 Pins on ZKB package configurable as GPIO
•External Interrupt and DMA request Capability
– Every GPIO pin may be configured to generate an interrupt request on detection of rising and/or
falling edges on the pin.
– The interrupt requests within each bank are combined (logical or) to create eight unique bank level
interrupt requests.
– The bank level interrupt service routine may poll the INTSTATx register for its bank to determine
which pin(s) have triggered the interrupt.
– GPIO Banks 0, 1, 2, 3, 4, 5, 6, and 7 Interrupts assigned to ARM INTC Interrupt Requests 42, 43,
•Set/clear functionality: Firmware writes 1 to corresponding bit position(s) to set or to clear GPIO
signal(s). This allows multiple firmware processes to toggle GPIO output signals without critical section
protection (disable interrupts, program GPIO, re-enable interrupts, to prevent context switching to
anther process during GPIO programming).
•Separate Input/Output registers
•Output register in addition to set/clear so that, if preferred by firmware, some GPIO output signals can
be toggled by direct write to the output register(s).
•Output register, when read, reflects output drive status. This, in addition to the input register reflecting
pin status and open-drain I/O cell, allows wired logic be implemented.
SPRS563D–SEPTEMBER 2008–REVISED AUGUST 2010
The memory map for the GPIO registers is shown in Table 6-11. See the OMAP-L137 ApplicationsProcessor DSP Peripherals Overview Reference Guide. – Literature Number SPRUGA6 for more details.
0x01E2 6010DIR01GPIO Banks 0 and 1 Direction Register
0x01E2 6014OUT_DATA01GPIO Banks 0 and 1 Output Data Register
0x01E2 6018SET_DATA01GPIO Banks 0 and 1 Set Data Register
0x01E2 601CCLR_DATA01GPIO Banks 0 and 1 Clear Data Register
0x01E2 6020IN_DATA01GPIO Banks 0 and 1 Input Data Register
0x01E2 6024SET_RIS_TRIG01GPIO Banks 0 and 1 Set Rising Edge Interrupt Register
0x01E2 6028CLR_RIS_TRIG01GPIO Banks 0 and 1 Clear Rising Edge Interrupt Register
0x01E2 602CSET_FAL_TRIG01GPIO Banks 0 and 1 Set Falling Edge Interrupt Register
0x01E2 6030CLR_FAL_TRIG01GPIO Banks 0 and 1 Clear Falling Edge Interrupt Register
0x01E2 6034INTSTAT01GPIO Banks 0 and 1 Interrupt Status Register
0x01E2 6038DIR23GPIO Banks 2 and 3 Direction Register
0x01E2 603COUT_DATA23GPIO Banks 2 and 3 Output Data Register
0x01E2 6040SET_DATA23GPIO Banks 2 and 3 Set Data Register
0x01E2 6044CLR_DATA23GPIO Banks 2 and 3 Clear Data Register
0x01E2 6048IN_DATA23GPIO Banks 2 and 3 Input Data Register
0x01E2 604CSET_RIS_TRIG23GPIO Banks 2 and 3 Set Rising Edge Interrupt Register
0x01E2 6050CLR_RIS_TRIG23GPIO Banks 2 and 3 Clear Rising Edge Interrupt Register
0x01E2 6054SET_FAL_TRIG23GPIO Banks 2 and 3 Set Falling Edge Interrupt Register
0x01E2 6058CLR_FAL_TRIG23GPIO Banks 2 and 3 Clear Falling Edge Interrupt Register
0x01E2 605CINTSTAT23GPIO Banks 2 and 3 Interrupt Status Register
0x01E2 6060DIR45GPIO Banks 4 and 5 Direction Register
0x01E2 6064OUT_DATA45GPIO Banks 4 and 5 Output Data Register
0x01E2 6068SET_DATA45GPIO Banks 4 and 5 Set Data Register
0x01E2 606CCLR_DATA45GPIO Banks 4 and 5 Clear Data Register
0x01E2 6070IN_DATA45GPIO Banks 4 and 5 Input Data Register
0x01E2 6074SET_RIS_TRIG45GPIO Banks 4 and 5 Set Rising Edge Interrupt Register
0x01E2 6078CLR_RIS_TRIG45GPIO Banks 4 and 5 Clear Rising Edge Interrupt Register
0x01E2 607CSET_FAL_TRIG45GPIO Banks 4 and 5 Set Falling Edge Interrupt Register
0x01E2 6080CLR_FAL_TRIG45GPIO Banks 4 and 5 Clear Falling Edge Interrupt Register
0x01E2 6084INTSTAT45GPIO Banks 4 and 5 Interrupt Status Register
0x01E2 6088DIR67GPIO Banks 6 and 7 Direction Register
0x01E2 608COUT_DATA67GPIO Banks 6 and 7 Output Data Register
0x01E2 6090SET_DATA67GPIO Banks 6 and 7 Set Data Register
0x01E2 6094CLR_DATA67GPIO Banks 6 and 7 Clear Data Register
0x01E2 6098IN_DATA67GPIO Banks 6 and 7 Input Data Register
0x01E2 609CSET_RIS_TRIG67GPIO Banks 6 and 7 Set Rising Edge Interrupt Register
0x01E2 60A0CLR_RIS_TRIG67GPIO Banks 6 and 7 Clear Rising Edge Interrupt Register
0x01E2 60A4SET_FAL_TRIG67GPIO Banks 6 and 7 Set Falling Edge Interrupt Register
0x01E2 60A8CLR_FAL_TRIG67GPIO Banks 6 and 7 Clear Falling Edge Interrupt Register
0x01E2 60ACINTSTAT67GPIO Banks 6 and 7 Interrupt Status Register
(1) The pulse width given is sufficient to generate a CPU interrupt or an EDMA event. However, if a user wants to have OMAP-L137
recognize the GPIx changes through software polling of the GPIO register, the GPIx duration must be extended to allow OMAP-L137
enough time to access the GPIO register through the internal bus.
(2) C=SYSCLK4 period in ns.
Pulse duration, GPn[m] as input high2C
Pulse duration, GPn[m] as input low2C
Table 6-13. Switching Characteristics Over Recommended Operating Conditions for GPIO Outputs
(see Figure 6-10)
No.PARAMETERMINMAXUNIT
3t
w(GPOH)
4t
w(GPOL)
(1) This parameter value should not be used as a maximum performance specification. Actual performance of back-to-back accesses of the
GPIO is dependent upon internal bus activity.
(2) C=SYSCLK4 period in ns.
Pulse duration, GPn[m] as output high2C
Pulse duration, GPn[m] as output low2C
Table 6-14. Timing Requirements for External Interrupts
No.PARAMETERMINMAXUNIT
1t
w(ILOW)
2t
w(IHIGH)
(1) The pulse width given is sufficient to generate an interrupt or an EDMA event. However, if a user wants to have OMAP-L137 recognize
the GPIO changes through software polling of the GPIO register, the GPIO duration must be extended to allow OMAP-L137 enough
time to access the GPIO register through the internal bus.
(2) C=SYSCLK4 period in ns.
Width of the external interrupt pulse low2C
Width of the external interrupt pulse high2C
0x01C0 0320EEVALError Evaluate Register
0x01C0 0340DRAE0DMA Region Access Enable Register for Region 0
0x01C0 0348DRAE1DMA Region Access Enable Register for Region 1
0x01C0 0350DRAE2DMA Region Access Enable Register for Region 2
0x01C0 0358DRAE3DMA Region Access Enable Register for Region 3
0x01C0 0380QRAE0QDMA Region Access Enable Register for Region 0
0x01C0 0384QRAE1QDMA Region Access Enable Register for Region 1
0x01C0 0388QRAE2QDMA Region Access Enable Register for Region 2
0x01C0 038CQRAE3QDMA Region Access Enable Register for Region 3
0x01C0 0400 - 0x01C0 043CQ0E0-Q0E15Event Queue Entry Registers Q0E0-Q0E15
0x01C0 0440 - 0x01C0 047CQ1E0-Q1E15Event Queue Entry Registers Q1E0-Q1E15
0x01C0 0600QSTAT0Queue 0 Status Register
0x01C0 0604QSTAT1Queue 1 Status Register
0x01C0 0620QWMTHRAQueue Watermark Threshold A Register
0x01C0 0640CCSTATEDMA3CC Status Register
(1) On previous architectures, the EDMA3TC priority was controlled by the queue priority register (QUEPRI) in the EDMA3CC
memory-map. However for this device, the priority control for the transfer controllers is controlled by the chip-level registers in the
System Configuration Module. You should use the chip-level registers and not QUEPRI to configure the TC priority.
Table 6-17 shows an abbreviation of the set of registers which make up the parameter set for each of 128
EDMA events. Each of the parameter register sets consist of 8 32-bit word entries. Table 6-18 shows the
parameter set entry registers with relative memory address locations within each of the parameter sets.
Table 6-17. EDMA Parameter Set RAM
BYTE ADDRESS RANGEDESCRIPTION
0x01C0 4000 - 0x01C0 401FParameters Set 0 (8 32-bit words)
0x01C0 4020 - 0x01C0 403FParameters Set 1 (8 32-bit words)
0x01C0 4040 - 0x01cC0 405FParameters Set 2 (8 32-bit words)
0x01C0 4060 - 0x01C0 407FParameters Set 3 (8 32-bit words)
0x01C0 4080 - 0x01C0 409FParameters Set 4 (8 32-bit words)
0x01C0 40A0 - 0x01C0 40BFParameters Set 5 (8 32-bit words)
......
0x01C0 4FC0 - 0x01C0 4FDFParameters Set 126 (8 32-bit words)
0x01C0 4FE0 - 0x01C0 4FFFParameters Set 127 (8 32-bit words)
Table 6-18. Parameter Set Entries
BYTE OFFSET ADDRESS
WITHIN THE PARAMETER SET
0x0000OPTOption
0x0004SRCSource Address
0x0008A_B_CNTA Count, B Count
0x000CDSTDestination Address
0x0010SRC_DST_BIDXSource B Index, Destination B Index
0x0014LINK_BCNTRLDLink Address, B Count Reload
0x0018SRC_DST_CIDXSource C Index, Destination C Index
0x001CCCNTC Count
EMIFA is one of two external memory interfaces supported on the OMAP-L137 . It is primarily intended to
support asynchronous memory types, such as NAND and NOR flash and Asynchronous SRAM. However
on OMAP-L137 EMIFA also provides a secondary interface to SDRAM.
6.11.1 EMIFA Asynchronous Memory Support
EMIFA supports asynchronous:
•SRAM memories
•NAND Flash memories
•NOR Flash memories
The EMIFA data bus width is up to 16-bits on the ZKB package. The device supports up to fifteen address
lines and an external wait/interrupt input. Up to four asynchronous chip selects are supported by EMIFA
(EMA_CS[5:2]) . All four chip selects are available on the ZKB package.
Each chip select has the following individually programmable attributes:
•Data Bus Width
•Read cycle timings: setup, hold, strobe
•Write cycle timings: setup, hold, strobe
•Bus turn around time
•Extended Wait Option With Programmable Timeout
•Select Strobe Option
•NAND flash controller supports 1-bit and 4-bit ECC calculation on blocks of 512 bytes.
SPRS563D–SEPTEMBER 2008–REVISED AUGUST 2010
6.11.2 EMIFA Synchronous DRAM Memory Support
The OMAP-L137 ZKB package supports 16-bit SDRAM in addition to the asynchronous memories listed in
Section 6.11.1. It has a single SDRAM chip select (EMA_CS[0]). SDRAM configurations that are
supported are:
•One, Two, and Four Bank SDRAM devices
•Devices with Eight, Nine, Ten, and Eleven Column Address
•CAS Latency of two or three clock cycles
•Sixteen Bit Data Bus Width
•3.3V LVCMOS Interface
Additionally, the SDRAM interface of EMIFA supports placing the SDRAM in Self Refresh and Powerdown
Modes. Self Refresh mode allows the SDRAM to be put into a low power state while still retaining memory
contents; since the SDRAM will continue to refresh itself even without clocks from the DSP. Powerdown
mode achieves even lower power, except the DSP must periodically wake the SDRAM up and issue
refreshes if data retention is required.
Finally, note that the EMIFA does not support Mobile SDRAM devices. Table 6-20 below shows the
supported SDRAM configurations for EMIFA.
EMIFA supports SDRAM up to 100 MHz with up to two SDRAM or asynchronous memory loads.
Additional loads will limit the SDRAM operation to lower speeds and the maximum speed should be
confirmed by board simulation using IBIS models.
Input setup time, read data valid on EMA_D[15:0] before EMA_CLK rising1.3ns
Input hold time, read data valid on EMA_D[15:0] after EMA_CLK rising1.5ns
Cycle time, EMIF clock EMA_CLK10ns
Pulse width, EMIF clock EMA_CLK high or low3ns
Delay time, EMA_CLK rising to EMA_CS[0] valid7ns
Output hold time, EMA_CLK rising to EMA_CS[0] invalid1ns
Delay time, EMA_CLK rising to EMA_WE_DQM[1:0] valid7ns
Output hold time, EMA_CLK rising to EMA_WE_DQM[1:0] invalid1ns
Delay time, EMA_CLK rising to EMA_A[12:0] and EMA_BA[1:0] valid7ns
Output hold time, EMA_CLK rising to EMA_A[12:0] and EMA_BA[1:0]
invalid
1ns
Delay time, EMA_CLK rising to EMA_D[15:0] valid7ns
Output hold time, EMA_CLK rising to EMA_D[15:0] invalid1ns
Delay time, EMA_CLK rising to EMA_RAS valid7ns
Output hold time, EMA_CLK rising to EMA_RAS invalid1ns
Delay time, EMA_CLK rising to EMA_CAS valid7ns
Output hold time, EMA_CLK rising to EMA_CAS invalid1ns
Delay time, EMA_CLK rising to EMA_WE valid7ns
Output hold time, EMA_CLK rising to EMA_WE invalid1ns
Delay time, EMA_CLK rising to EMA_D[15:0] 3-stated7ns
Output hold time, EMA_CLK rising to EMA_D[15:0] driving1ns
Cycle time, EMIFA module clock10ns
Pulse duration, EM_WAIT assertion and deassertion2Ens
READS
12t
su(EMDV-EMOEH)
13t
h(EMOEH-EMDIV)
14t
su (EMOEL-EMWAIT)
Setup time, EM_D[15:0] valid before EM_OE high3ns
Hold time, EM_D[15:0] valid after EM_OE high0ns
Setup Time, EM_WAIT asserted before end of Strobe Phase
(2)
4E+3ns
WRITES
28t
su (EMWEL-EMWAIT)
Setup Time, EM_WAIT asserted before end of Strobe Phase
(2)
4E+3ns
(1) E = EMA_CLK period or in ns. EMA_CLK is selected either as SYSCLK3 or the PLL output clock divided by 4.5. As an example, when
SYSCLK3 is selected and set to 100MHz, E=10ns.
(2) Setup before end of STROBE phase (if no extended wait states are inserted) by which EM_WAIT must be asserted to add extended
wait states. Figure 6-16 and Figure 6-17 describe EMIF transactions that include extended wait states inserted during the STROBE
phase. However, cycles inserted as part of this extended wait period should not be counted; the 4E requirement is to the start of where
the HOLD phase would begin if there were no extended wait cycles.
MEWC = Maximum external wait cycles. These parameters are programmed via the Asynchronous Bank and Asynchronous Wait Cycle
Configuration Registers. These support the following range of values: TA[4-1], RS[16-1], RST[64-1], RH[8-1], WS[16-1], WST[64-1],
WH[8-1], and MEW[1-256].
(2) E = EMA_CLK period or in ns. EMA_CLK is selected either as SYSCLK3 or the PLL output clock divided by 4.5. As an example, when
SYSCLK3 is selected and set to 100MHz, E=10ns.
(3) EWC = external wait cycles determined by EMA_WAIT input signal. EWC supports the following range of values EWC[256-1]. Note that
the maximum wait time before timeout is specified by bit field MEWC in the Asynchronous Wait Cycle Configuration Register.
Figure 6-18 illustrates a high-level view of the EMIFB and its connections within the device. Multiple
requesters have access to EMIFB through a switched central resource (indicated as crossbar in the
figure). The EMIFB implements a split transaction internal bus, allowing concurrence between reads and
writes from the various requesters.
Figure 6-18. EMIFB Functional Block Diagram
www.ti.com
EMIFB supports a 3.3V LVCMOS Interface.
6.12.1 EMIFB SDRAM Loading Limitations
EMIFB supports SDRAM up to 133 MHz with up to two SDRAM or asynchronous memory loads.
Additional loads will limit the SDRAM operation to lower speeds and the maximum speed should be
confirmed by board simulation using IBIS models.
Figure 6-19 shows an interface between the EMIFB and a 2M × 16 × 4 bank SDRAM device. In addition,
Figure 6-20 shows an interface between the EMIFB and a 2M × 32 × 4 bank SDRAM device and
Figure 6-21 shows an interface between the EMIFB and two 4M × 16 × 4 bank SDRAM devices. Refer to
Table 6-27, as an example that shows additional list of commonly-supported SDRAM devices and the
required connections for the address pins. Note that in Table 6-27, page size/column size (not indicated in
the table) is varied to get the required addressability range.
Cycle time, EMIF clock EMB_CLK7.5ns
Pulse width, EMIF clock EMB_CLK high or low3ns
Delay time, EMB_CLK rising to EMB_CS[0] valid5.1ns
Output hold time, EMB_CLK rising to EMB_CS[0] invalid0.9ns
Delay time, EMB_CLK rising to EMB_WE_DQM[3:0] valid5.1ns
Output hold time, EMB_CLK rising to EMB_WE_DQM[3:0] invalid0.9ns
Delay time, EMB_CLK rising to EMB_A[12:0] and EMB_BA[1:0] valid5.1ns
Output hold time, EMB_CLK rising to EMB_A[12:0] and EMB_BA[1:0] invalid0.9ns
Delay time, EMB_CLK rising to EMB_D[31:0] valid5.1ns
Output hold time, EMB_CLK rising to EMB_D[31:0] invalid0.9ns
Delay time, EMB_CLK rising to EMB_RAS valid5.1ns
Output hold time, EMB_CLK rising to EMB_RAS invalid0.9ns
Delay time, EMB_CLK rising to EMB_CAS valid5.1ns
Output hold time, EMB_CLK rising to EMB_CAS invalid0.9ns
Delay time, EMB_CLK rising to EMB_WE valid5.1ns
Output hold time, EMB_CLK rising to EMB_WE invalid0.9ns
Delay time, EMB_CLK rising to EMB_D[31:0] 3-stated5.1ns
Output hold time, EMB_CLK rising to EMB_D[31:0] driving0.9ns