3 (EDMA3)• Two External Memory Interfaces:
– Two External Memory Interfaces– EMIFA
– Three Configurable 16550 type UART•NOR (8-/16-Bit-Wide Data)
Modules
– Two Serial Peripheral Interfaces (SPI)
– Multimedia Card (MMC)/Secure Digital (SD)Space
Card Interface with Secure Data I/O (SDIO)
– Two Master/Slave Inter-Integrated Circuit
– USB 2.0 OTG Port With Integrated PHYAddress Space
– Three Multichannel Audio Serial Ports• Three Configurable 16550 type UART Modules:
– 10/100 Mb/s Ethernet MAC (EMAC)– UART0 With Modem Control Signals
– One 64-Bit General-Purpose Timer– 16-byte FIFO
– One 64-bit General-Purpose/Watchdog Timer– 16x or 13x Oversampling Option
– Three Enhanced Pulse Width Modulators– Autoflow control signals (CTS, RTS) on
– Three 32-Bit Enhanced Capture Modules
• Applications
– Industrial Automation
– Home Automation
– Test and Measurement
– Portable Data Terminals
– Educational Consoles
– Power Protection Systems
• 375/456-MHz ARM926EJ-S™ RISC Core
– 32-Bit and 16-Bit (Thumb®) Instructions
– Single Cycle MAC
– ARM®Jazelle®Technology
– EmbeddedICE-RT™ for Real-Time Debug
• ARM9 Memory Architecture
– 16K-Byte Instruction Cache
– 16K-Byte Data Cache
– 8K-Byte RAM (Vector Table)
– 64K-Byte ROM
• Two Serial Peripheral Interfaces (SPI) Each
With One Chip-Select
• Programmable Real-Time Unit Subsystem
(PRUSS)
– Two Independent Programmable Realtime
Unit (PRU) Cores
•32-Bit Load/Store RISC architecture
•4K Byte instruction RAM per core
•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
– Dedicated interrupt controller
– Dedicated switched central resource
• Multimedia Card (MMC)/Secure Digital (SD)
Card Interface with Secure Data I/O (SDIO)
• Two Master/Slave Inter-Integrated Circuit (I2C
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.
2ARM926EJ-S, EmbeddedICE-RT, ETM9, CoreSight are trademarks of ARM Limited.
3ARM, 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.
• One Host-Port Interface (HPI) With 16-Bit-Wide• Three Enhanced Pulse Width Modulators
Muxed Address/Data Bus For High Bandwidth(eHRPWM):
• USB 1.1 OHCI (Host) With Integrated PHY– Dedicated 16-Bit Time-Base Counter With
(USB1)Period And Frequency Control
• USB 2.0 OTG Port With Integrated PHY (USB0)– 6 Single Edge, 6 Dual Edge Symmetric or 3
– 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
Dual Edge Asymmetric Outputs
– Dead-Band Generation
– PWM Chopping by High-Frequency Carrier
– Trip Zone Input
ISOC) Rx and Tx• Three 32-Bit Enhanced Capture Modules
• 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
(eCAP):
– Configurable as 3 Capture Inputs or 3
Auxiliary Pulse Width Modulator (APWM)
outputs
– Single Shot Capture of up to Four Event
Time-Stamps
• Two 32-Bit Enhanced Quadrature Encoder
Pulse Modules (eQEP)
The device is a low-power ARM microprocessor based on an ARM926EJ-S™.
The device 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 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 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 port (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.
www.ti.com
The Ethernet Media Access Controller (EMAC) provides an efficient interface between the device 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 device 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 device has a complete set of development tools for the ARM. These include C compilers and a
Windows™ debugger interface for visibility into source code execution.
This data manual revision history highlights the changes made to the SPRS637A device-specific data
manual to make it an SPRS637B revision.
Table 2-1. Revision History
ADDITIONS/MODIFICATIONS/DELETIONS
Global - Changed SPI td(SCSL_SPC)S min from P to 2P
Global - Replaced all "CLKIN" references with "OSCIN"
Global - Updated SPI Electrical parameters
Added Section 5.3, Notes on Recommended Power-On Hours (POH).
Section 6.5- Updated "All pins are tri-stated with the exception of RESETOUT which remains active through the reset sequence" to " 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."
The ARM926EJ-S RISC CPU is compatible with other ARM9 CPUs from ARM Holdings plc.
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.
SPRS637B–FEBRUARY 2010–REVISED AUGUST 2010
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 (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.
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
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.
www.ti.com
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.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 device also includes the
Embedded Trace Buffer (ETB). The ETM consists of two parts:
•Trace Port provides real-time trace capability for the ARM9.
•Triggering facilities provide trigger resources, which include address and data comparators, counter,
and sequencers.
The device trace port is not pinned out and is instead only connected to the Embedded Trace Buffer. The
ETB has a 4KB buffer memory. ETB enabled debug tools are required to read/interpret the captured trace
data.
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, EMIFA, EMIFB, and the additional
128K byte on chip SRAM. Likewise almost all of the on chip peripherals are accessible to the ARM by
default.
See Table 3-2 for a detailed top level device memory map that includes the ARM memory space.
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.5.1Pin Map (Bottom View)
Figure 3-1 shows the pin assignments for the ZKB package.
Table 3-3 to Table 3-23 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.6.1Device Reset and JTAG
Table 3-3. 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
www.ti.com
3.6.2High-Frequency Oscillator and PLL
Table 3-4. 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
(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
No.
ZKB
(1)
PULL
(2)
MUXEDDESCRIPTION
enhanced capture
0 input or
auxiliary PWM 0
output
enhanced capture
1 input or
auxiliary PWM 1
output
enhanced capture
2 input or
auxiliary PWM 2
output
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
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
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
SPI1_ENA/UART2_RXD/GP5[12]R4IIPUUART2 receive data
SPI1_SCS[0]/UART2_TXD/GP5[13]P4OIPU
(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) As these signals are internally pulled down while the device is in reset, it is necessary to externally pull them high with resistors if
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-18. 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
No.
ZKB
RMII
MDIO
(1)
PULL
(2)
McASP0, GPIO
MUXEDDESCRIPTION
EMAC 50-MHz
clock input or output
EMAC RMII receiver
error
EMAC RMII receive
data
EMAC RMII carrier
sense data valid
EMAC RMII transmit
enable
EMAC RMII trasmit
data
3.6.18 Multimedia Card/Secure Digital (MMC/SD)
Table 3-20. Multimedia Card/Secure Digital (MMC/SD) Terminal Functions
(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
PIN No.
ZKB
(1)
PULL
(2)
EMIFA, UHPI,
GPIO
EMIFA, GPIO
EMIFA, UHPI,
GPIO
EMIFA, GPIO
MUXEDDESCRIPTION
LCD data bus
LCD AC bias enable
chip select
3.6.20 Reserved and No Connect
Table 3-22. Reserved and No Connect Terminal Functions
SIGNAL NAMETYPE
RSV1F7PWRReserved. (Leave unconnected, do not connect to power or ground.)
RSV2B1PWR
NCF3-No Connect (leave unconnected)
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 of peripherals supporting this function.
Many registers are accessible only by a host (ARM) when it is operating in its privileged mode. (ex. from
the kernel, but not from user space code).
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 Junction 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
Storage temperature range, T
Operating Junction Temperature ranges,
T
J
(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, 1.2V-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.
(default)-55°C to 150°C
Commercial (default)0°C to 90°C
Industrial (D version)-40°C to 90°C
Extended (A version)-40°C to 105°C
Automotive (T version)-40°C to 125°C
Transition time, 10%-90%, All Inputs (unless otherwise specified in
the electrical data sections)
ARM Operating Frequency (SYSCLK6)
(1)
, RTC_VSS
(1) 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.
(2) 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.
(3) 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 and 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.USB0_VDDA33 is not required if USB0 is 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.
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.
SPRS637B–FEBRUARY 2010–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.
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 3-stated with the exception of RESETOUT which
remains active through the reset sequence. 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.
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)
t
d(RSTH-
4cycles
RESETOUTH)
(1) RESETOUT is multiplexed with other pin functions. See the Terminal Functions table, Table 3-3 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 reset4096
RESET high to RESETOUT high; Power-on Reset6192
(1),(2)
)
(3)
Figure 6-4. Power-On Reset (RESET and TRST active) Timing
The 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
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
c(OSCIN)
c(OSCIN)
Transition time, OSCIN0.25P or 10
Period jitter, OSCIN0.02Pns
The device 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 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 processor 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.
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.
6.7.3PLL Controller 0 Registers
Table 6-6. PLL Controller 0 Registers
BYTE
ADDRESS
0x01C1 1000REVIDRevision Identification Register
0x01C1 10E4RSTYPEReset Type Status Register
0x01C1 1100PLLCTLPLL Control Register
0x01C1 1104OCSELOBSCLK Select Register
0x01C1 1110PLLMPLL Multiplier Control Register
0x01C1 1114PREDIVPLL Pre-Divider Control Register
0x01C1 1118PLLDIV1PLL Controller Divider 1 Register
0x01C1 1140ALNCTLPLL Controller Clock Align Control Register
0x01C1 1144DCHANGEPLLDIV Ratio Change Status Register
0x01C1 1148CKENClock Enable Control Register
The ARM9 CPU core supports 2 direct interrupts: FIQ and IRQ. The ARM Interrupt Controller extends the
number of interrupts to 100, and provides features like programmable masking, priority, hardware nesting
support, and interrupt vector generation.
6.8.1.1ARM Interrupt Controller (AINTC) Interrupt Signal Hierarchy
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 the device
System Interrupt assignments for the device are listed in Table 6-7
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 device 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.
www.ti.com
The memory map for the GPIO registers is shown in Table 6-9.
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
(1) The pulse width given is sufficient to generate a CPU interrupt or an EDMA event. However, if a user wants to have the device
recognize the GPIx changes through software polling of the GPIO register, the GPIx duration must be extended to allow the device
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-11. 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-12. 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 device recognize the
GPIO changes through software polling of the GPIO register, the GPIO duration must be extended to allow the device enough time to
access the GPIO register through the internal bus.
(2) 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-15 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-16 shows the
parameter set entry registers with relative memory address locations within each of the parameter sets.
Table 6-15. EDMA Parameter Set RAM
BYTE ADDRESSDESCRIPTION
0x01C0 4000 - 0x01C0 401FParameters Set 0 (8 32-bit words)
0x01C0 4020 - 0x01C0 403FParameters Set 1 (8 32-bit words)
0x01C0 4040 - 0x01C0 405FParameters Set 2 (8 32-bit words)
0x01C0 4060 - 0x01C0 407FParameters Set 3 (8 32-bit words)
0x01C0 4080 - 0x01C0 409FParameters Set 4 (8 32-bit words)
0x01C0 40A0 - 0x01C0 40BFParameters Set 5 (8 32-bit words)
......
0x01C0 4FC0 - 0x01C0 4FDFParameters Set 126 (8 32-bit words)
0x01C0 4FE0 - 0x01C0 4FFFParameters Set 127 (8 32-bit words)
Table 6-16. 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
EMIFA is one of two external memory interfaces supported on the device. It is primarily intended to
support asynchronous memory types, such as NAND and NOR flash and Asynchronous SRAM. However
the 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.
www.ti.com
6.11.2 EMIFA Synchronous DRAM Memory Support
The device 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. Powerdown mode achieves even lower power, except the processor 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-18 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.
The following EMIFB Functional Block Diagram 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-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-25 , 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-25, page size/column size (not indicated in
the table) is varied to get the required addressability range.
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.
Table 6-26. EMIFB Controller Registers
BYTE ADDRESSACRONYMREGISTER DESCRIPTION
0xB000 0000MIDRModule ID Register
0xB000 0008SDCFGSDRAM Configuration Register
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
The MPU performs memory protection checking. It receives requests from a bus master in the system and
checks the address against the fixed and programmable regions to see if the access is allowed. If allowed,
the transfer is passed unmodified to its output bus (to the targeted address). If the transfer is illegal (fails
the protection check) then the MPU does not pass the transfer to the output bus but rather services the
transfer internally back to the input bus (to prevent a hang) returning the fault status to the requestor as
well as generating an interrupt about the fault. The following features are supported by the MPU:
•Provides memory protection for fixed and programmable address ranges
•Supports multiple programmable address region
•Supports secure and debug access privileges
•Supports read, write, and execute access privileges
•Supports privid(8) associations with ranges
•Generates an interrupt when there is a protection violation, and saves violating transfer parameters
•MMR access is also protected
Table 6-29. MPU1 Configuration Registers
MPU1
BYTE ADDRESS
0x01E1 4000REVIDRevision ID
0x01E1 4004CONFIGConfiguration
0x01E1 4010IRAWSTATInterrupt raw status/set
0x01E1 4014IENSTATInterrupt enable status/clear
0x01E1 4018IENSETInterrupt enable
0x01E1 401CIENCLRInterrupt enable clear
0x01E1 4020 - 0x01E1 41FF-Reserved
0x01E1 4200PROG1_MPSARProgrammable range 1, start address
0x01E1 4204PROG1_MPEARProgrammable range 1, end address
0x01E1 4208PROG1_MPPAProgrammable range 1, memory page protection attributes
0x01E1 420C - 0x01E1 420F-Reserved
0x01E1 4210PROG2_MPSARProgrammable range 2, start address
0x01E1 4214PROG2_MPEARProgrammable range 2, end address
0x01E1 4218PROG2_MPPAProgrammable range 2, memory page protection attributes
0x01E1 421C - 0x01E1 421F-Reserved
0x01E1 4220PROG3_MPSARProgrammable range 3, start address
0x01E1 4224PROG3_MPEARProgrammable range 3, end address
0x01E1 4228PROG3_MPPAProgrammable range 3, memory page protection attributes
0x01E1 422C - 0x01E1 422F-Reserved
0x01E1 4230PROG4_MPSARProgrammable range 4, start address
0x01E1 4234PROG4_MPEARProgrammable range 4, end address
0x01E1 4238PROG4_MPPAProgrammable range 4, memory page protection attributes
0x01E1 423C - 0x01E1 423F-Reserved
0x01E1 4240PROG5_MPSARProgrammable range 5, start address
0x01E1 4244PROG5_MPEARProgrammable range 5, end address
0x01E1 4248PROG5_MPPAProgrammable range 5, memory page protection attributes
0x01E1 424C - 0x01E1 424F-Reserved
0x01E1 4250PROG6_MPSARProgrammable range 6, start address
0x01E1 4254PROG6_MPEARProgrammable range 6, end address
0x01E1 4258PROG6_MPPAProgrammable range 6, memory page protection attributes
0x01E14300FLTADDRRFault address
0x01E1 4304FLTSTATFault status
0x01E1 4308FLTCLRFault clear
0x01E1 430C - 0x01E1 4FFF-Reserved
ACRONYMREGISTER DESCRIPTION
Table 6-30. MPU2 Configuration Registers
MPU2
BYTE ADDRESS
0x01E1 5000REVIDRevision ID
0x01E1 5004CONFIGConfiguration
0x01E1 5010IRAWSTATInterrupt raw status/set
0x01E1 5014IENSTATInterrupt enable status/clear
0x01E1 5018IENSETInterrupt enable
0x01E1 501CIENCLRInterrupt enable clear
0x01E1 5020 - 0x01E1 50FF-Reserved
0x01E1 5100FXD_MPSARFixed range start address
0x01E1 5104FXD_MPEARFixed range end start address
0x01E1 5108FXD_MPPAFixed range memory page protection attributes
0x01E1 510C - 0x01E1 51FF-Reserved
0x01E1 5200PROG1_MPSARProgrammable range 1, start address
0x01E1 5204PROG1_MPEARProgrammable range 1, end address
0x01E1 5208PROG1_MPPAProgrammable range 1, memory page protection attributes
0x01E1 520C - 0x01E1 520F-Reserved
0x01E1 5210PROG2_MPSARProgrammable range 2, start address
0x01E1 5214PROG2_MPEARProgrammable range 2, end address
0x01E1 5218PROG2_MPPAProgrammable range 2, memory page protection attributes
0x01E1 521C - 0x01E1 521F-Reserved
0x01E1 5220PROG3_MPSARProgrammable range 3, start address
0x01E1 5224PROG3_MPEARProgrammable range 3, end address
0x01E1 5228PROG3_MPPAProgrammable range 3, memory page protection attributes
0x01E1 522C - 0x01E1 522F-Reserved
0x01E1 5230PROG4_MPSARProgrammable range 4, start address
0x01E1 5234PROG4_MPEARProgrammable range 4, end address
0x01E1 5238PROG4_MPPAProgrammable range 4, memory page protection attributes
0x01E1 523C - 0x01E1 523F-Reserved
0x01E1 5240PROG5_MPSARProgrammable range 5, start address
0x01E1 5244PROG5_MPEARProgrammable range 5, end address
0x01E1 5248PROG5_MPPAProgrammable range 5, memory page protection attributes
0x01E1 524C - 0x01E1 524F-Reserved
0x01E1 5250PROG6_MPSARProgrammable range 6, start address
0x01E1 5254PROG6_MPEARProgrammable range 6, end address
0x01E1 5258PROG6_MPPAProgrammable range 6, memory page protection attributes
0x01E1 525C - 0x01E1 525F-Reserved
0x01E1 5260PROG7_MPSARProgrammable range 7, start address
0x01E1 5264PROG7_MPEARProgrammable range 7, end address
0x01E1 5268PROG7_MPPAProgrammable range 7, memory page protection attributes
0x01E1 5270PROG8_MPSARProgrammable range 8, start address
0x01E1 5274PROG8_MPEARProgrammable range 8, end address
0x01E1 5278PROG8_MPPAProgrammable range 8, memory page protection attributes
0x01E1 527C - 0x01E1 527F-Reserved
0x01E1 5280PROG9_MPSARProgrammable range 9, start address
0x01E1 5284PROG9_MPEARProgrammable range 9, end address
0x01E1 5288PROG9_MPPAProgrammable range 9, memory page protection attributes
0x01E1 528C - 0x01E1 528F-Reserved
0x01E1 5290PROG10_MPSARProgrammable range 10, start address
0x01E1 5294PROG10_MPEARProgrammable range 10, end address
0x01E1 5298PROG10_MPPAProgrammable range 10, memory page protection attributes
0x01E1 529C - 0x01E1 529F-Reserved
0x01E1 52A0PROG11_MPSARProgrammable range 11, start address
0x01E1 52A4PROG11_MPEARProgrammable range 11, end address
0x01E1 52A8PROG11_MPPAProgrammable range 11, memory page protection attributes
0x01E1 52AC - 0x01E1 52AF-Reserved
0x01E1 52B0PROG12_MPSARProgrammable range 12, start address
0x01E1 52B4PROG12_MPEARProgrammable range 12, end address
0x01E1 52B8PROG12_MPPAProgrammable range 12, memory page protection attributes
0x01E1 52BC - 0x01E1 52FF-Reserved
0x01E1 5300FLTADDRRFault address
0x01E1 5304FLTSTATFault status
0x01E1 5308FLTCLRFault clear
The device includes an MMCSD controller which is compliant with MMC V4.0, Secure Digital Part 1
Physical Layer Specification V1.1 and Secure Digital Input Output (SDIO) V2.0 specifications.
The MMC/SD Controller has following features:
•MultiMediaCard (MMC) support
•Secure Digital (SD) Memory Card support
•MMC/SD protocol support
•SDIO protocol support
•Programmable clock frequency
•512 bit Read/Write FIFO to lower system overhead
•Slave EDMA transfer capability
The device MMC/SD Controller does not support SPI mode.
6.14.2MMCSD Peripheral Register Description(s)
Table 6-31. Multimedia Card/Secure Digital (MMC/SD) Card Controller Registers
BYTEACRONYMREGISTER DESCRIPTION
ADDRESS
0x01C4 0000MMCCTLMMC Control Register
0x01C4 0004MMCCLKMMC Memory Clock Control Register
0x01C4 0008MMCST0MMC Status Register 0
Table 6-33. Switching Characteristics Over Recommended Operating Conditions for MMC/SD Module
No.PARAMETERMINMAXUNIT
7f
(CLK)
8f
(CLK_ID)
9t
W(CLKL)
10t
W(CLKH)
11t
r(CLK)
12t
f(CLK)
13t
d(CLKL-CMD)
14t
d(CLKL-DAT)
Setup time, MMCSD_CMD valid before MMCSD_CLK high3.2ns
Hold time, MMCSD_CMD valid after MMCSD_CLK high1.5ns
Setup time, MMCSD_DATx valid before MMCSD_CLK high3.2ns
Hold time, MMCSD_DATx valid after MMCSD_CLK high1.5ns
(see Figure 6-24 through Figure 6-27)
Operating frequency, MMCSD_CLK052MHz
Identification mode frequency, MMCSD_CLK0400KHz
Pulse width, MMCSD_CLK low6.5ns
Pulse width, MMCSD_CLK high6.5ns
Rise time, MMCSD_CLK3ns
Fall time, MMCSD_CLK3ns
Delay time, MMCSD_CLK low to MMCSD_CMD transition-4.52.5ns
Delay time, MMCSD_CLK low to MMCSD_DATx transition-4.52ns
The Ethernet Media Access Controller (EMAC) provides an efficient interface between the device 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, with hardware flow control and quality of service (QOS) support.
The EMAC controls the flow of packet data from the device to the PHY. The MDIO module controls PHY
configuration and status monitoring.
Both the EMAC and the MDIO modules interface to the device through a custom interface that allows
efficient data transmission and reception. This custom interface is referred to as the EMAC control
module, and is considered integral to the EMAC/MDIO peripheral. The control module is also used to
multiplex and control interrupts.
6.15.1EMAC Peripheral Register Description(s)
Table 6-34. Ethernet Media Access Controller (EMAC) Registers
BYTE ADDRESSACRONYMREGISTER DESCRIPTION
0x01E2 3000TXREVTransmit Revision Register
0x01E2 3004TXCONTROLTransmit Control Register
0x01E2 3008TXTEARDOWNTransmit Teardown Register
0x01E2 3010RXREVReceive Revision Register
0x01E2 3014RXCONTROLReceive Control Register
0x01E2 3018RXTEARDOWNReceive Teardown Register
0x01E2 3080TXINTSTATRAWTransmit Interrupt Status (Unmasked) Register
0x01E2 3084TXINTSTATMASKEDTransmit Interrupt Status (Masked) Register
0x01E2 3088TXINTMASKSETTransmit Interrupt Mask Set Register
0x01E2 3094MACEOIVECTORMAC End Of Interrupt Vector Register
0x01E2 30A0RXINTSTATRAWReceive Interrupt Status (Unmasked) Register
0x01E2 30A4RXINTSTATMASKEDReceive Interrupt Status (Masked) Register
0x01E2 30A8RXINTMASKSETReceive Interrupt Mask Set Register
0x01E2 326CFRAME65T127Transmit and Receive 65 to 127 Octet Frames Register
0x01E2 3270FRAME128T255Transmit and Receive 128 to 255 Octet Frames Register
0x01E2 3274FRAME256T511Transmit and Receive 256 to 511 Octet Frames Register
0x01E2 3278FRAME512T1023Transmit and Receive 512 to 1023 Octet Frames Register
0x01E2 327CFRAME1024TUPTransmit and Receive 1024 to 1518 Octet Frames Register
0x01E2 3280NETOCTETSNetwork Octet Frames Register
0x01E2 3284RXSOFOVERRUNSReceive FIFO or DMA Start of Frame Overruns Register
0x01E2 3288RXMOFOVERRUNSReceive FIFO or DMA Middle of Frame Overruns Register
0x01E2 328CRXDMAOVERRUNSReceive DMA Start of Frame and Middle of Frame Overruns Register
Table 6-36. EMAC Control Module Registers
BYTE ADDRESSACRONYMREGISTER DESCRIPTION
0x01E2 2000REVEMAC Control Module Revision Register
0x01E2 2004SOFTRESETEMAC Control Module Software Reset Register
0x01E2 200CINTCONTROLEMAC Control Module Interrupt Control Register
0x01E2 0000 - 0x01E2 1FFFEMAC Local Buffer Descriptor Memory
Table 6-38. RMII Timing Requirements
No.PARAMETERMINTYPMAX UNIT
1tc(REFCLK)Cycle Time, RMII_MHZ_50_CLK
2tw(REFCLKH)Pulse Width, RMII_MHZ_50_CLK High713ns
3tw(REFCLKL)Pulse Width, RMII_MHZ_50_CLK Low713ns
6tsu(RXD-REFCLK)Input Setup Time, RXD Valid before RMII_MHZ_50_CLK High4ns
7th(REFCLK-RXD)Input Hold Time, RXD Valid after RMII_MHZ_50_CLK High2ns
8tsu(CRSDV-REFCLK)Input Setup Time, CRSDV Valid before RMII_MHZ_50_CLK High4ns
9th(REFCLK-CRSDV)Input Hold Time, CRSDV Valid after RMII_MHZ_50_CLK High2ns
10tsu(RXER-REFCLK)Input Setup Time, RXER Valid before RMII_MHZ_50_CLK High4ns
11th(REFCLKR-RXER)Input Hold Time, RXER Valid after RMII_MHZ_50_CLK High2ns
(1) Per the RMII industry specification, the RMII reference clock (RMII_MHZ_50_CLK) must have jitter tolerance of 50 ppm or less.
(1)
20ns
Table 6-39. RMII Switching Characteristics
No.PARAMETERMINTYPMAX UNIT
4td(REFCLK-TXD)Output Delay Time, RMII_MHZ_50_CLK High to TXD Valid2.513ns
5td(REFCLK-TXEN)Output Delay Time, RMII_MHZ_50_CLK High to TXEN Valid2.513ns
The Management Data Input/Output (MDIO) module continuously polls all 32 MDIO addresses in order to
enumerate all PHY devices in the system.
The Management Data Input/Output (MDIO) module implements the 802.3 serial management interface to
interrogate and control Ethernet PHY(s) using a shared two-wire bus. Host software uses the MDIO
module to configure the auto-negotiation parameters of each PHY attached to the EMAC, retrieve the
negotiation results, and configure required parameters in the EMAC module for correct operation. The
module is designed to allow almost transparent operation of the MDIO interface, with very little
maintenance from the core processor. Only one PHY may be connected at any given time.
6.16.1 MDIO Registers
For a list of supported MDIO registers see Table 6-40 [MDIO Registers].
Table 6-40. MDIO Register Memory Map
BYTE ADDRESSACRONYMREGISTER DESCRIPTION
0x01E2 4000REVRevision Identification Register
0x01E2 4004CONTROLMDIO Control Register
0x01E2 4008ALIVEMDIO PHY Alive Status Register
0x01E2 400CLINKMDIO PHY Link Status Register
0x01E2 4010LINKINTRAWMDIO Link Status Change Interrupt (Unmasked) Register
0x01E2 4014LINKINTMASKEDMDIO Link Status Change Interrupt (Masked) Register
0x01E2 4018–Reserved
0x01E2 4020USERINTRAWMDIO User Command Complete Interrupt (Unmasked) Register
0x01E2 4024USERINTMASKEDMDIO User Command Complete Interrupt (Masked) Register
0x01E2 4028USERINTMASKSETMDIO User Command Complete Interrupt Mask Set Register
0x01E2 402CUSERINTMASKCLEAR MDIO User Command Complete Interrupt Mask Clear Register
0x01E2 4030 - 0x01E2 407C–Reserved
0x01E2 4080USERACCESS0MDIO User Access Register 0
0x01E2 4084USERPHYSEL0MDIO User PHY Select Register 0
0x01E2 4088USERACCESS1MDIO User Access Register 1
0x01E2 408CUSERPHYSEL1MDIO User PHY Select Register 1
6.16.2 Management Data Input/Output (MDIO) Electrical Data/Timing
Table 6-41. Timing Requirements for MDIO Input (see Figure 6-29 and Figure 6-30)
No.PARAMETERMINMAXUNIT
1t
c(MDIO_CLK)
2t
w(MDIO_CLK)
3t
t(MDIO_CLK)
4t
su(MDIO-MDIO_CLKH)
5t
h(MDIO_CLKH-MDIO)
Cycle time, MDIO_CLK400ns
Pulse duration, MDIO_CLK high/low180ns
Transition time, MDIO_CLK5ns
Setup time, MDIO_D data input valid before MDIO_CLK high10ns
Hold time, MDIO_D data input valid after MDIO_CLK high10ns
Figure 6-29. MDIO Input Timing
Table 6-42. Switching Characteristics Over Recommended Operating Conditions for MDIO Output
(see Figure 6-30)
No.PARAMETERMINMAXUNIT
7t
d(MDIO_CLKL-MDIO)
Delay time, MDIO_CLK low to MDIO_D data output valid0100ns
Receive Bit Clock
Receive Left/Right Clock or Frame Sync
Transmit Master Clock
Transmit Bit Clock
Transmit Left/Right Clock or Frame Sync
Transmit/Receive Serial Data Pin
Transmit/Receive Serial Data Pin
Transmit/Receive Serial Data Pin
Error Detection
The McASPs DO NOT have
dedicated AMUTEINx pins.
AM1707
www.ti.com
SPRS637B–FEBRUARY 2010–REVISED AUGUST 2010
6.17 Multichannel Audio Serial Ports (McASP0, McASP1, and McASP2)
The McASP serial port is specifically designed for multichannel audio applications. Its key features are:
•Flexible clock and frame sync generation logic and on-chip dividers
•Up to sixteen transmit or receive data pins and serializers
•Large number of serial data format options, including:
– TDM Frames with 2 to 32 time slots per frame (periodic) or 1 slot per frame (burst)
– Time slots of 8,12,16, 20, 24, 28, and 32 bits
– First bit delay 0, 1, or 2 clocks
– MSB or LSB first bit order
– Left- or right-aligned data words within time slots
•DIT Mode (optional) with 384-bit Channel Status and 384-bit User Data registers
•Extensive error checking and mute generation logic
•All unused pins GPIO-capable
•Transmit & Receive FIFO Buffers for each McASP. Allows the McASP to operate at a higher sample
rate by making it more tolerant to DMA latency.
•Dynamic Adjustment of Clock Dividers
– Clock Divider Value may be changed without resetting the McASP
The three McASPs on the device are configured with the following options:
64 Word RXAXR1[11:10], AXR1[8:0], AHCLKR1, ACLKR1, AFSR1, AHCLKX1, ACLKX1, AFSX1,
64 Word TXAMUTE1
16 Word RX
16 Word TX
Figure 6-31. McASP Block Diagram
Submit Documentation Feedback
Product Folder Link(s): AM1707
ADVANCEINFORMATION
AM1707
SPRS637B–FEBRUARY 2010–REVISED AUGUST 2010
www.ti.com
6.17.1 McASP Peripheral Registers Description(s)
Registers for the McASP are summarized in Table 6-44. The registers are accessed through the
peripheral configuration port. The receive buffer registers (RBUF) and transmit buffer registers (XBUF) can
also be accessed through the DMA port, as listed in Table 6-45
Registers for the McASP Audio FIFO (AFIFO) are summarized in Table 6-46. Note that the AFIFO Write
FIFO (WFIFO) and Read FIFO (RFIFO) have independent control and status registers. The AFIFO control
registers are accessed through the peripheral configuration port.
Table 6-44. McASP Registers Accessed Through Peripheral Configuration Port
0x01D0 0088 0x01D0 4088 0x01D0 8088RCLKCHKReceive clock check control register
0x01D0 008C 0x01D0 408C 0x01D0 808CREVTCTLReceiver DMA event control register
0x01D0 00A0 0x01D0 40A0 0x01D0 80A0XGBLCTLTransmitter global control register. Alias of GBLCTL, only transmit bits are
0x01D0 00A4 0x01D0 40A4 0x01D0 80A4XMASKTransmit format unit bit mask register
0x01D0 00A8 0x01D0 40A8 0x01D0 80A8XFMTTransmit bit stream format register
0x01D0 00AC 0x01D0 40AC 0x01D0 80ACAFSXCTLTransmit frame sync control register
0x01D0 00B0 0x01D0 40B0 0x01D0 80B0ACLKXCTLTransmit clock control register
0x01D0 00B4 0x01D0 40B4 0x01D0 80B4 AHCLKXCTL Transmit high-frequency clock control register
0x01D0 00B8 0x01D0 40B8 0x01D0 80B8XTDMTransmit TDM time slot 0-31 register
0x01D0 00BC 0x01D0 40BC 0x01D0 80BCXINTCTLTransmitter interrupt control register
0x01D0 00C0 0x01D0 40C0 0x01D0 80C0XSTATTransmitter status register
0x01D0 00C4 0x01D0 40C4 0x01D0 80C4XSLOTCurrent transmit TDM time slot register
0x01D0 00C8 0x01D0 40C8 0x01D0 80C8XCLKCHKTransmit clock check control register
0x01D0 00CC 0x01D0 40CC 0x01D0 80CCXEVTCTLTransmitter DMA event control register
0x01D0 0100 0x01D0 4100 0x01D0 8100DITCSRA0Left (even TDM time slot) channel status register (DIT mode) 0
affected - allows receiver to be reset independently from transmitter
affected - allows transmitter to be reset independently from receiver
(2) Reads from XRBUF originate on peripheral configuration port only when RBUSEL = 1 in RFMT.
(3) Reads from XRBUF originate on peripheral configuration port only when RBUSEL = 1 in RFMT.
(1)
Transmit buffer register for serializer 6
(1)
Transmit buffer register for serializer 7
(1)
Transmit buffer register for serializer 8
(1)
Transmit buffer register for serializer 9
(1)
Transmit buffer register for serializer 10
(1)
Transmit buffer register for serializer 11
(1)
Transmit buffer register for serializer 12
(1)
Transmit buffer register for serializer 13
(1)
Transmit buffer register for serializer 14
(1)
Transmit buffer register for serializer 15
(2)
Receive buffer register for serializer 0
(2)
Receive buffer register for serializer 1
(2)
Receive buffer register for serializer 2
(2)
Receive buffer register for serializer 3
(3)
Receive buffer register for serializer 4
(3)
Receive buffer register for serializer 5
(3)
Receive buffer register for serializer 6
(3)
Receive buffer register for serializer 7
(3)
Receive buffer register for serializer 8
(3)
Receive buffer register for serializer 9
(3)
Receive buffer register for serializer 10
(3)
Receive buffer register for serializer 11
(3)
Receive buffer register for serializer 12
(3)
Receive buffer register for serializer 13
(3)
Receive buffer register for serializer 14
(3)
Receive buffer register for serializer 15
www.ti.com
Table 6-45. McASP Registers Accessed Through DMA Port
McASP0McASP1McASP2
BYTEBYTEBYTEACRONYMREGISTER DESCRIPTION
ADDRESSADDRESSADDRESS
Receive buffer DMA port address. Cycles through receive
Read
Accesses
01D0 200001D0 600001D0 A000RBUFserializers. Starts at the lowest serializer at the beginning of
serializers, skipping over transmit serializers and inactive
each time slot. Reads from DMA port only if XBUSEL = 0 in
XFMT.
Transmit buffer DMA port address. Cycles through transmit
Writeserializers, skipping over receive and inactive serializers.
AccessesStarts at the lowest serializer at the beginning of each time
01D0 200001D0 600001D0 A000XBUF
slot. Writes to DMA port only if RBUSEL = 0 in RFMT.
Table 6-46. McASP AFIFO Registers Accessed Through Peripheral Configuration Port
ACLKR0 external output – McASP0 ACLKRCTL.CLKRM = 0, PDIR.ACLKR = 1
(2) P = SYSCLK2 period
(3) McASP0 ACLKXCTL.ASYNC=1: Receiver is clocked by its own ACLKR0
(4) McASP0 ACLKXCTL.ASYNC=0: Receiver is clocked by transmitter's ACLKX0
Cycle time, AHCLKR0 external, AHCLKR0 input25
Cycle time, AHCLKX0 external, AHCLKX0 input25
Pulse duration, AHCLKR0 external, AHCLKR0 input12.5
Pulse duration, AHCLKX0 external, AHCLKX0 input12.5
Cycle time, ACLKR0 external, ACLKR0 inputgreater of 2P or 25
Cycle time, ACLKX0 external, ACLKX0 inputgreater of 2P or 25
Pulse duration, ACLKR0 external, ACLKR0 input12.5
Pulse duration, ACLKX0 external, ACLKX0 input12.5
Setup time, AFSR0 input to ACLKR0 internal
(3)
Setup time, AFSX0 input to ACLKX0 internal9.4
Setup time, AFSR0 input to ACLKR0 external input
(3)
Setup time, AFSX0 input to ACLKX0 external input2.9
Setup time, AFSR0 input to ACLKR0 external output
(3)
Setup time, AFSX0 input to ACLKX0 external output2.9
Hold time, AFSR0 input after ACLKR0 internal
(3)
Hold time, AFSX0 input after ACLKX0 internal-1.2
Hold time, AFSR0 input after ACLKR0 external input
(3)
Hold time, AFSX0 input after ACLKX0 external input0.9
Hold time, AFSR0 input after ACLKR0 external output
(3)
Hold time, AFSX0 input after ACLKX0 external output0.9
Setup time, AXR0[n] input to ACLKR0 internal
Setup time, AXR0[n] input to ACLKX0 internal
Setup time, AXR0[n] input to ACLKR0 external input
Setup time, AXR0[n] input to ACLKX0 external input
Setup time, AXR0[n] input to ACLKR0 external output
Setup time, AXR0[n] input to ACLKX0 external output
Hold time, AXR0[n] input after ACLKR0 internal
Hold time, AXR0[n] input after ACLKX0 internal
Hold time, AXR0[n] input after ACLKR0 external input
Hold time, AXR0[n] input after ACLKX0 external input
Hold time, AXR0[n] input after ACLKR0 external output
Hold time, AXR0[n] input after ACLKX0 external output