PRODUCTION DATA information is current as of publication date.
Products conform to specifications per the terms of the Texas
Instruments standard warranty. Production processing does not
necessarily include testing of all parameters.
Unified Cache/Mapped RAM, and 192K Byte
Additional L2 Mapped RAM
• Device Configuration
– Boot Mode: HPI, 8/16/32 Bit ROM Boot
– Endianness: Little Endian, Big Endian
– Glueless Interface to SRAM, EPROM, Flash,
Memory Space
• Enhanced Direct Memory Access (EDMA)
Controller (16 Independent Channels)
• 16 Bit Host Port Interface (HPI)
• Two Multichannel Audio Serial Ports (McASPs)
– Two Independent Clock Zones Each
(One TX and One RX)
– Eight Serial Data Pins Per Port: Individually
Assignable to any of the Clock Zones
– Wide Variety of I2S™ and Similar Bit Stream
Formats
– Integrated Digital Audio Interface Transmitter
(DIT)
– Extensive Error Checking and Recovery
• Two Inter-Integrated Circuit Bus (I2C™ Bus)
Multi-Master and Slave Interfaces
• Two Multichannel Buffered Serial Ports:
– Serial Peripheral Interface (SPI)
– High Speed TDM Interface
– AC97 Interface
• Two 32 Bit General Purpose Timers
• Dedicated GPIO Module With 16 Pins (External
Interrupt Capable)
• Flexible Phase Locked Loop (PLL) Based Clock
Generator Module
• IEEE-1149.1 (JTAG)
(1)
Boundary-Scan
Compatible
• 272 Ball, Ball Grid Array Package (GDP)
• 0.13 μm/6 Level Copper Metal Process
– CMOS Technology
• 3.3 V I/Os, 1.26 V Internal
(1) IEEE Standard 1149.1-1990 Standard-Test-Access Port and
Boundary Scan Architecture.
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.
PRODUCTION DATA information is current as of publication date.
Products conform to specifications per the terms of the Texas
Instruments standard warranty. Production processing does not
necessarily include testing of all parameters.
The TMS320C67x™ DSPs (including the SM320C6713 and SM320C6713B devices) compose the
floating-point DSP generation in the TMS320C6000™ DSP platform. The C6713 and C6713B devices are
based on the high-performance, advanced very-long-instruction-word (VLIW) architecture developed by
Texas Instruments (TI), making this DSP an excellent choice for multichannel and multifunction
applications. Throughout the remainder of this document, the SM320C6713 and SM320C6713B are
referred to as 320C67x or C67x or 13/13B where generic, and where specific, their individual full device
part numbers are used or abbreviated as C6713, C6713B, 13, or 13B, and so forth.
Operating at 225 MHz, the C6713/13B delivers up to 1350 million floating-point operations per second
(MFLOPS), 1800 million instructions per second (MIPS), and with dual fixed-/floating-point multipliers up to
450 million multiply-accumulate operations per second (MMACS).
Operating at 300 MHz, the C6713B delivers up to 1800 million floating-point operations per second
(MFLOPS), 2400 million instructions per second (MIPS), and with dual fixed-/floating-point multipliers up to
600 million multiply-accumulate operations per second (MMACS).
The C6713/13B has a rich peripheral set that includes two multichannel audio serial ports (McASPs), two
multichannel buffered serial ports (McBSPs), two inter-integrated circuit (I2C) buses, one dedicated
general-purpose input/output (GPIO) module, two general-purpose timers, a host-port interface (HPI), and
a glueless external memory interface (EMIF) capable of interfacing to SDRAM, SBSRAM, and
asynchronous peripherals.
The two McASP interface modules each support one transmit and one receive clock zone. Each of the
McASPs has eight serial data pins that can be individually allocated to any of the two zones. The serial
port supports time-division multiplexing on each pin from 2 to 32 time slots. The C6713/13B has sufficient
bandwidth to support all 16 serial data pins transmitting a 192-kHz stereo signal. Serial data in each zone
may be transmitted and received on multiple serial data pins simultaneously and formatted in a multitude
of variations on the Philips Inter-IC Sound (I2S) format.
In addition, the McASP transmitter may be programmed to output multiple S/PDIF, IEC60958, AES-3, and
CP-430 encoded data channels simultaneously, with a single RAM containing the full implementation of
user data and channel status fields.
The McASP also provides extensive error-checking and recovery features, such as the bad clock
detection circuit for each high-frequency master clock, which verifies that the master clock is within a
programmed frequency range.
The two I2C ports on the 320C6713/13B allow the DSP to easily control peripheral devices and
communicate with a host processor. In addition, the standard multichannel buffered serial port (McBSP)
may be used to communicate with serial peripheral interface (SPI™) mode peripheral devices.
SGUS049K–AUGUST 2003– REVISED APRIL 2011
The 320C6713/13B device has two boot modes—from the HPI or from external asynchronous ROM. For
more detailed information, see the Bootmode section of this data sheet.
The TMS320C67x DSP generation is supported by the TI eXpressDSP™ set of industry benchmark
development tools, including a highly optimizing C/C++ Compiler, the Code Composer Studio™ Integrated
Development Environment (IDE), JTAG-based emulation and real-time debugging, and the DSP/BIOS™
kernel.
Table 3-2 provides an overview of the C6713/C6713B DSPs. The table shows significant features of each
device, including the capacity of on-chip RAM, the peripherals, the execution time, and the package type
with pin count. For more details on the C67x™ DSP device part numbers and part numbering, see
Table 6-1 and Figure 6-1.
Table 3-2. Characteristics of the C6713 and C6713B Processor
HARDWARE FEATURES
EMIFSYSCLK3 or ECLKIN1 (32 bit)
EDMA
(16 channels)
Peripherals
Not all peripheral pins are available at the
same time. (For more details, see the
Device Configurations section.)
Peripheral performance is dependent on
chip-level configuration.
On-chip memorySize (Bytes)264K
CPU ID+CPU Rev IDControl Status Register (CSR[31:16])0x0203
BSDL fileFor the C6713/13B BSDL file, contact your field sales representative.
FrequencyMHz200
Timens5 ns
Package27 mm × 27 mm272-ball BGA (GDP)
Process technologyμm0.13
Product status
Product preview (PP)
Advance information (AI)
Production data (PD)
(1) AUXCLK is the McASP internal high-frequency clock source for serial transfers. SYSCLK2 is the McASP system clock used for the clock
check (high-frequency) circuit.
(2) PRODUCT PREVIEW information concerns products in the formative or design phase of development. Characteristic data and other
specifications are design goals. Texas Instruments reserves the right to change or discontinue these products without notice.
ADVANCE INFORMATION concerns new products in the sampling or preproduction phase of development. Characteristic data and
other specifications are subject to change without notice.
PRODUCTION DATA information is current as of publication date. Products conform to specifications per the terms of Texas
Instruments standard warranty. Production processing does not necessarily include testing of all parameters.
(2)
HPI (16 bit)SYSCLK21
McASPs2
I2CsSYSCLK22
McBSPsSYSCLK22
32-bit timers� of SYSCLK22
GPIO moduleSYSCLK21
Organization
Core (V)1.26 V (C6713/C6713B)
I/O (V)3.3 V
Prescaler/1, /2, /3, ..., /32
Postscaler/1, /2, /3, ..., /32
INTERNAL CLOCK
SOURCE
CPU clock frequency1
AUXCLK,
SYSCLK2
(1)
4K-Byte (KB) L1 program (L1P) cache
4KB L1 data (L1D) cache
64KB unified L2 cache/mapped RAM
192KB L2 mapped RAM
The 320C6713/13B floating-point digital signal processor is based on the C67x CPU. The CPU fetches
advanced very-long instruction words (VLIW) (256 bits wide) to supply up to eight 32-bit instructions to the
eight functional units during every clock cycle. The VLIW architecture features controls by which all eight
units do not have to be supplied with instructions if they are not ready to execute. The first bit of every
32-bit instruction determines if the next instruction belongs to the same execute packet as the previous
instruction, or whether it should be executed in the following clock as a part of the next execute packet.
Fetch packets are always 256 bits wide; however, the execute packets can vary in size. The
variable-length execute packets are a key memory-saving feature, distinguishing the C67x CPU from other
VLIW architectures.
The CPU features two sets of functional units. Each set contains four units and a register file. One set
contains functional units .L1, .S1, .M1, and .D1. The other set contains units .D2, .M2, .S2, and .L2. The
two register files each contain 16 32-bit registers for a total of 32 general-purpose registers. The two sets
of functional units, along with two register files, compose sides A and B of the CPU (see the Functional
Block and CPU (DSP Core) Diagram and Figure 4-1). The four functional units on each side of the CPU
can freely share the 16 registers belonging to that side. Additionally, each side features a single data bus
connected to all the registers on the other side, by which the two sets of functional units can access data
from the register files on the opposite side. While register access by functional units on the same side of
the CPU as the register file can service all the units in a single clock cycle, register access using the
register file across the CPU supports one read and one write per cycle.
www.ti.com
The C67x CPU executes all C62x instructions. In addition to C62x fixed-point instructions, the six out of
eight functional units (.L1, .S1, .M1, .M2, .S2, and .L2) also execute floating-point instructions. The
remaining two functional units (.D1 and .D2) also execute the new LDDW instruction, which loads 64 bits
per CPU side for a total of 128 bits per cycle.
Another key feature of the C67x CPU is the load/store architecture, where all instructions operate on
registers (as opposed to data in memory). Two sets of data-addressing units (.D1 and .D2) are
responsible for all data transfers between the register files and the memory. The data address driven by
the .D units allows data addresses generated from one register file to be used to load or store data to or
from the other register file. The C67x CPU supports a variety of indirect addressing modes using either
linear- or circular-addressing modes with 5- or 15-bit offsets. All instructions are conditional, and most can
access any one of the 32 registers. Some registers, however, are singled out to support specific
addressing or to hold the condition for conditional instructions (if the condition is not automatically true).
The two .M functional units are dedicated for multiplies. The two .S and .L functional units perform a
general set of arithmetic, logical, and branch functions with results available every clock cycle.
The processing flow begins when a 256-bit-wide instruction fetch packet is fetched from a program
memory. The 32-bit instructions destined for the individual functional units are chained together by 1 bits
in the least significant bit (LSB) position of the instructions. The instructions that are chained together for
simultaneous execution (up to eight in total) compose an execute packet. A 0 in the LSB of an instruction
breaks the chain, effectively placing the instructions that follow it in the next execute packet. If an execute
packet crosses the fetch-packet boundary (256 bits wide), the assembler places it in the next fetch packet,
while the remainder of the current fetch packet is padded with NOP instructions. The number of execute
packets within a fetch packet can vary from one to eight. Execute packets are dispatched to their
respective functional units at the rate of one per clock cycle and the next 256-bit fetch packet is not
fetched until all the execute packets from the current fetch packet have been dispatched. After decoding,
the instructions simultaneously drive all active functional units for a maximum execution rate of eight
instructions every clock cycle. While most results are stored in 32-bit registers, they can be subsequently
moved to memory as bytes or half-words as well. All load and store instructions are byte, half-word, or
word addressable.
Table 4-2 through Table 4-15 identify the peripheral registers for the C6713/C6713B devices by their
register names, acronyms, and hex address or hex address range. For more detailed information on the
register contents and bit names and their respective descriptions, see the specific peripheral reference
guide listed in the TMS320C6000 DSP Peripherals Overview Reference Guide (literature number
SPRU190).
Table 4-2. EMIF Registers
HEX ADDRESS RANGEACRONYMREGISTER NAME
0180 0000GBLCTLEMIF global control
0180 0004CECTL1EMIF CE1 space control
0180 0008CECTL0EMIF CE0 space control
0180 000C—Reserved
0180 0010CECTL2EMIF CE2 space control
0180 0014CECTL3EMIF CE3 space control
0180 0018SDCTLEMIF SDRAM control
0180 001CSDTIMEMIF SDRAM refresh control
0180 0020SDEXTEMIF SDRAM extension
Allows the user to control peripheral
selection. This register also offers the user
019C 0200DEVCFGDevice configuration
019C 0204−019F FFFF—Reserved
N/ACSRCPU control status register
Table 4-6. EDMA Parameter RAM
HEX ADDRESS RANGEACRONYMREGISTER NAME
01A0 0000 01A0 0017—Parameters for Event 0 (6 words) or Reload/Link parameters for other event
01A0 0018 01A0 002F—Parameters for Event 1 (6 words) or Reload/Link parameters for other event
01A0 0030 01A0 0047—Parameters for Event 2 (6 words) or Reload/Link parameters for other event
01A0 0048 01A0 005F—Parameters for Event 3 (6 words) or Reload/Link parameters for other event
01A0 0060 01A0 0077—Parameters for Event 4 (6 words) or Reload/Link parameters for other event
01A0 0078 01A0 008F—Parameters for Event 5 (6 words) or Reload/Link parameters for other event
01A0 0090 01A0 00A7—Parameters for Event 6 (6 words) or Reload/Link parameters for other event
01A0 00A8 01A0 00BF—Parameters for Event 7 (6 words) or Reload/Link parameters for other event
01A0 00C0 01A0 00D7—Parameters for Event 8 (6 words) or Reload/Link parameters for other event
01A0 00D8 01A0 00EF—Parameters for Event 9 (6 words) or Reload/Link parameters for other event
01A0 00F0 01A0 00107—Parameters for Event 10 (6 words) or Reload/Link parameters for other event
01A0 0108 01A0 011F—Parameters for Event 11 (6 words) or Reload/Link parameters for other event
01A0 0120 01A0 0137—Parameters for Event 12 (6 words) or Reload/Link parameters for other event
01A0 0138 01A0 014F—Parameters for Event 13 (6 words) or Reload/Link parameters for other event
01A0 0150 01A0 0167—Parameters for Event 14 (6 words) or Reload/Link parameters for other event
01A0 0168 01A0 017F—Parameters for Event 15 (6 words) or Reload/Link parameters for other event
01A0 0180 01A0 0197—Reload/link parameters for Event 0−15
01A0 0198 01A0 01AF—Reload/link parameters for Event 0−15
.........
01A0 07E0 01A0 07F7—Reload/link parameters for Event 0−15
01A0 07F8 01A0 07FF—Scratch pad area (two words)
(1) The C6713/13B device has 85 EDMA parameters total: 16 Event/Reload parameters and 69 Reload-only parameters.
control of the EMIF input clock source. For
more detailed information on the device
configuration register, see the Device
Configurations section of this data sheet.
Identifies which CPU and defines the silicon
revision of the CPU. This register also offers
the user control of device operation. For more
detailed information on the CPU Control
Status Register, see the CPU CSR Register
description section of this data sheet.
(1)
www.ti.com
For more details on the EDMA parameter RAM six-word parameter entry structure, see Figure 4-3.
3C00 0000−3C00 FFFF3C10 0000−3C10 FFFFRBUF/XBUFxdata bus. Used when RSEL or XSEL bits = 0 (these bits are located
01B4 C00001B5 0000MCASPPIDx
01B4 C00401B5 0004PWRDEMUxPower down and emulation management
01B4 C00801B5 0008—Reserved
01B4 C00C01B5 000C—Reserved
01B4 C01001B5 0010PFUNCxPin function
01B4 C01401B5 0014PDIRxPin direction
01B4 C01801B5 0018PDOUTxPin data out
01B4 C01C01B5 001CPDIN/PDSETxRead returns: PDIN
01B4 C02001B5 0020PDCLRxPin data clear
01B4 C024−01B4 C04001B5 0024−01B5 0040—Reserved
01B4 C04401B5 0044GBLCTLxGlobal control
01B4 C04801B5 0048AMUTExMute control
01B4 C04C01B5 004CDLBCTLxDigital loopback control
01B4 C05001B5 0050DITCTLxDIT mode control
01B4 C054−01B4 C05C01B5 0054−01B5 005C—Reserved
01B4 C06001B5 0060RGBLCTLx
01B4 C06401B5 0064RMASKxReceiver format unit bit mask
01B4 C06801B5 0068RFMTxReceive bit stream format
01B4 C06C01B5 006CAFSRCTLxReceive frame sync control
01B4 C07001B5 0070ACLKRCTLxReceive clock control
01B4 C07401B5 0074AHCLKRCTLxHigh-frequency receive clock control
01B4 C07801B5 0078RTDMxReceive TDM slot 0−31
01B4 C07C01B5 007CRINTCTLxReceiver interrupt control
01B4 C08001B5 0080RSTATxStatus − receiver
01B4 C08401B5 0084RSLOTxCurrent receive TDM slot
01B4 C08801B5 0088RCLKCHKxReceiver clock check control
01B4 C08C−01B4 C09C01B5 008C−01B5 009C—Reserved
01B4 C0A001B5 00A0XGBLCTLx
01B4 C0A401B5 00A4XMASKxTransmit format unit bit mask
01B4 C0A801B5 00A8XFMTxTransmit bit stream format
01B4 C0AC01B5 00ACAFSXCTLxTransmit frame sync control
01B4 C0B001B5 00B0ACLKXCTLxTransmit clock control
01B4 C0B401B5 00B4AHCLKXCTLxHigh-frequency Transmit clock control
01B4 C0B801B5 00B8XTDMxTransmit TDM slot 0−31
01B4 C0BC01B5 00BCXINTCTLxTransmit interrupt control
Table 4-10. McASP0 and McASP1 Registers (continued)
HEX ADDRESS RANGE
McASP0McASP1
01B4 C11401B5 0114DITCSRA5xLeft (even TDM slot) channel status register file
01B4 C11801B5 0118DITCSRB0xRight (odd TDM slot) channel status register file
01B4 C11C01B5 011CDITCSRB1xRight (odd TDM slot) channel status register file
01B4 C12001B5 0120DITCSRB2xRight (odd TDM slot) channel status register file
01B4 C12401B5 0124DITCSRB3xRight (odd TDM slot) channel status register file
01B4 C12801B5 0128DITCSRB4xRight (odd TDM slot) channel status register file
01B4 C12C01B5 012CDITCSRB5xRight (odd TDM slot) channel status register file
01B4 C13001B5 0130DITUDRA0xLeft (even TDM slot) user data register file
01B4 C13401B5 0134DITUDRA1xLeft (even TDM slot) user data register file
01B4 C13801B5 0138DITUDRA2xLeft (even TDM slot) user data register file
01B4 C13C01B5 013CDITUDRA3xLeft (even TDM slot) user data register file
01B4 C14001B5 0140DITUDRA4xLeft (even TDM slot) user data register file
01B4 C14401B5 0144DITUDRA5xLeft (even TDM slot) user data register file
01B4 C14801B5 0148DITUDRB0xRight (odd TDM slot) user data register file
01B4 C14C01B5 014CDITUDRB1xRight (odd TDM slot) user data register file
01B4 C15001B5 0150DITUDRB2xRight (odd TDM slot) user data register file
01B4 C15401B5 0154DITUDRB3xRight (odd TDM slot) user data register file
01B4 C15801B5 0158DITUDRB4xRight (odd TDM slot) user data register file
01B4 C15C01B5 015CDITUDRB5xRight (odd TDM slot) user data register file
01B4 C160−01B4 C17C01B5 0160−01B5 017C—Reserved
01B4 C18001B5 0180SRCTL0xSerializer 0 control
01B4 C18401B5 0184SRCTL1xSerializer 1 control
01B4 C18801B5 0188SRCTL2xSerializer 2 control
01B4 C18C01B5 018CSRCTL3xSerializer 3 control
01B4 C19001B5 0190SRCTL4xSerializer 4 control
01B4 C19401B5 0194SRCTL5xSerializer 5 control
01B4 C19801B5 0198SRCTL6xSerializer 6 control
01B4 C19C01B5 019CSRCTL7xSerializer 7 control
01B4 C1A0−01B4 C1FC01B5 01A0−01B5 01FC—Reserved
01B4 C20001B5 0200XBUF0xTransmit buffer for serializer 0 through configuration bus
01B4 C20401B5 0204XBUF1xTransmit buffer for serializer 1 through configuration bus
01B4 C20801B5 0208XBUF2xTransmit buffer for serializer 2 through configuration bus
01B4 C20C01B5 020CXBUF3xTransmit buffer for serializer 3 through configuration bus
01B4 C21001B5 0210XBUF4xTransmit buffer for serializer 4 through configuration bus
01B4 C21401B5 0214XBUF5xTransmit buffer for serializer 5 through configuration bus
01B4 C21801B5 0218XBUF6xTransmit buffer for serializer 6 through configuration bus
01B4 C21C01B5 021CXBUF7xTransmit buffer for serializer 7 through configuration bus
01B4 C220−01B4 C27C01B5 C220−01B5 027C—Reserved
01B4 C28001B5 0280RBUF0xReceive buffer for serializer 0 through configuration bus
01B4 C28401B5 0284RBUF1xReceive buffer for serializer 1 through configuration bus
01B4 C28801B5 0288RBUF2xReceive buffer for serializer 2 through configuration bus
01B4 C28C01B5 028CRBUF3xReceive buffer for serializer 3 through configuration bus
01B4 C29001B5 0290RBUF4xReceive buffer for serializer 4 through configuration bus
01B4 C29401B5 0294RBUF5xReceive buffer for serializer 5 through configuration bus
01B4 C29801B5 0298RBUF5xReceive buffer for serializer 6 through configuration bus
01B4 C29C01B5 029CRBUF7xReceive buffer for serializer 7 through configuration bus
01B4 C2A0−01B4 FFFF01B5 02A0−01B5 3FFF—Reserved
(1) The transmit buffers for serializers 0−7 are accessible to the CPU via the peripheral bus if the XSEL bit = 1 (XFMT register).
(2) The receive buffers for serializers 0−7 are accessible to the CPU via the peripheral bus if the RSEL bit = 1 (RFMT register).
A.These external pins are applicable to the GDP package only.
B.The GP[15:0] pins, through interrupt sharing, are external interrupt capable via GPINT0. For more details, see the
external interrupt sources section of this data sheet. For more details on interrupt sharing, see the TMS320C6000DSP Interrupt Selector Reference Guide (literature number SPRU646).
C. All of these pins are external interrupt sources. For more details see the External Interrupt Sources section of this
data sheet.
D. On multiplexed pins, boldface text denotes the active function of the pin for that particular peripheral module.
A.These external pins are applicable to the GDP package only.
B.On multiplexed pins, boldface text denotes the active function of the pin for that particular peripheral module.
A.The McASP Error Detect function detects underruns, overruns, early/late frame syncs, DMA errors, and external mute
input.
B.On multiplexed pins, boldface text denotes the active function of the pin for that particular peripheral module.
C. Boldface and italicized text within parentheses denotes the function of the pins in an audio system.
A.The McASP Error Detect function detects underruns, overruns, early/late frame syncs, DMA errors, and external mute
input.
B.On multiplexed pins, boldface text denotes the active function of the pin for that particular peripheral module.
C. Boldface and italicized text within parentheses denotes the function of the pins in an audio system.
On the C6713/13B devices, bootmode and certain device configurations/peripheral selections are
determinedatdevicereset,whileotherdeviceconfigurations/peripheralselectionsare
software-configurable via the device configurations register (DEVCFG) [address location 0x019C0200]
after device reset.
5.1Device Configurations at Device Reset
Table 5-1 describes the C6713 and C6713B device configuration pins, which are set up via internal or
external pullup/pulldown resistors through the HPI data pins (HD[4:3], HD8, HD12 [13B only]), and
CLKMODE0 pin. These configuration pins must be in the desired state until reset is released. For proper
device operation, do not oppose the HD [13, 11:9, 7, 1, 0] pins with external pullups/pulldowns at reset.
For more details on these device configuration pins, see the Terminal Functions table and the Debugging
Considerations section of this data sheet.
Table 5-1. Device Configurations Pins at Device Reset (HD[4:3], HD8, HD12 [13B only], and CLKMODE0)
CONFIGURATION
PIN
(2)
HD12
HD8B170 – System operates in Big Endian mode
HD[4:3]
(BOOTMODE)
CLKMODE0C4
(1) All other HD pins [HD [15, 13:9, 7:5, 2:0] (for 13) or HD [15, 13, 11:9, 7:5, 2:0] (for 13B)] have pullups/pulldowns (IPUs or IPDs). For
proper device operation of the HD [15, 13:9, 7, 1, 0] (for 13) or HD [13, 11:9, 7, 1, 0] (for 13B), do not oppose these pins with external
pullups/pulldowns at reset; however, the HD[6, 5, 2] (for 13) or HD[15, 6, 5, 2] (for 13B) pins can be opposed and driven during reset.
(2) IPD = Internal pulldown, IPU = Internal pullup. To oppose the supply rail on these IPD/IPU signal pins, use external pullup or pulldown
resistors no greater than 4.4 kΩ and 2.0 kΩ, respectively.
(2)
GDPFUNCTIONAL DESCRIPTION
EMIF Big Endian mode correctness (EMIFBE) [C6713B only]
For a C6713BGDP:
0 – The EMIF data will always be presented on the ED[7:0] side of the bus, regardless of the
endianess mode (Little/Big Endian).
1 –In Little Endian mode (HD8 = 1), the 8-bit or 16-bit EMIF data will be present on the
ED[7:0] side of the bus.
C15
For a C6713BPYP, when Big Endian mode is selected (LENDIAN = 0), for proper device operation the
EMIFBE pin must be externally pulled low.
This enhancement is not supported on the C6713 device.
For proper C6713 device operation, do not oppose the internal pullup (IPU) resistor on this pin.
This new functionality does not affect systems using the current default value of HD12 = 1. For more
detailed information on the big endian mode correctness, see the EMIF Big Endian Mode Correctness
[C6713B only] portion of this data sheet.
Device Endian mode (LEND)
Bootmode Configuration pins (BOOTMODE)
C19, C20
For more detailed information on these bootmode configurations, see the Bootmode section of this
data sheet.
Clock generator input clock source select
This pin must be pulled to the correct level even after reset.
In Big Endian mode (HD8 = 0), the 8-bit or 16-bit EMIF data will be present on the
ED[31:24] side of the bus [default].
1 – System operates in Little Endian mode (default)
00 – HPI boot/Emulation boot
01 – CE1 width 8-bit, asynchronous external ROM boot with default timings (default mode)
10 – CE1 width 16-bit, asynchronous external ROM boot with default timings
11 – CE1 width 32-bit, asynchronous external ROM boot with default timings
0 – Reserved. Do not use.
1 – CLKIN square wave [default]
Some C6713/13B peripherals share the same pins (internally MUXed) and are mutually exclusive (that is,
HPI, general-purpose input/output pins GP[15:8, 3, 1, 0], and McASP1).
•HPI, McASP1, and GPIO peripherals
The HPI_EN (HD14 pin) is latched at reset. This pin selects whether the HPI peripheral pins or
McASP1 peripheral pins and GP[15:8, 3, 1, 0] pins are functionally enabled (see Table 5-2).
Table 5-2. HPI_EN (HD14 Pin) Peripheral Selection (HPI or McASP1, and Select GPIO Pins)
PERIPHERALPERIPHERAL
PIN SELECTIONPINS SELECTED
HPI_ENMcASP1 and
(HD14 Pin) [173, C14]GP[15:8, 3, 1, 0]
0✓are enabled. All multiplexed HPI/McASP1 and HPI/GPIO pins function as
1✓
(1) The HPI_EN (HD[14]) pin cannot be controlled via software.
HPI
www.ti.com
(1)
DESCRIPTION
HPI_EN = 0
HPI pins are disabled; McASP1 peripheral pins and GP[15:8, 3, 1, 0] pins
McASP1 and GPIO pins, respectively. To use the GPIO pins, the
appropriate bits in the GPEN and GPDIR registers need to be configured.
HPI_EN = 1
HPI pins are enabled; McASP1 peripheral pins and GP[15:8, 3, 1, 0] pins
are disabled [default]. All multiplexed HPI/McASP1 and HPI/GPIO pins
function as HPI pins.
5.3Peripheral Selection/Device Configurations Via the DEVCFG Control Register
The device configuration register (DEVCFG) allows the user to control the pin availability of the McBSP0,
McBSP1, McASP0, I2C1, and timer peripherals. The DEVCFG register also offers the user control of the
EMIF input clock source and the timer output pins. For more detailed information on the DEVCFG register
control bits, see Table 5-3 and Table 5-4.
Table 5-4. Device Configuration Register (DEVCFG) Selection Bit Descriptions
BIT NO.NAMEDESCRIPTION
31:5ReservedReserved. Do not write non-zero values to these bit locations.
EMIF input clock source bit.
4EKSRC
3TOUT1SEL
2TOUT0SEL
1MCBSP0DISACLKX0, AXR0[0], AXR0[1], AFSR0, and AFSX0) are disabled (default).
0MCBSP1DIS
Determines which clock signal is used as the EMIF input clock.
0 = SYSCLK3 (from the clock generator) is the EMIF input clock source (default).
1 = ECLKIN external pin is the EMIF input clock source.
Timer 1 output (TOUT1) pin function select bit.
Selects the pin function of the TOUT1/AXR0[4] external pin independent of the rest of the peripheral
selection bits in the DEVCFG register.
0 = The pin functions as a Timer 1 output (TOUT1) pin (default).
1 = The pin functions as the McASP0 transmit/receive data pin 4 (AXR0[4]). The Timer 1 module
is still active.
Timer 0 output (TOUT0) pin function select bit.
Selects the pin function of the TOUT0/AXR0[2] external pin independent of the rest of the peripheral
selection bits in the DEVCFG register.
0 = The pin functions as a Timer 0 output (TOUT0) pin (default).
1 = The pin functions as the McASP0 transmit/receive data pin 2 (AXR0[2]). The Timer 0 module
is still active.
Multichannel Buffered Serial Port 0 (McBSP0) disable bit.
Selects whether McBSP0 or the McASP0 multiplexed peripheral pins are enabled or disabled.
ACLKX0, AXR0[0], AXR0[1], AFSR0, and AFSX0) are enabled.
Multichannel Buffered Serial Port 1 (McBSP1) disable bit.
Selects whether McBSP1 or I2C1 and McASP0 multiplexed peripheral pins are enabled or disabled.
0 = McBSP1 peripheral pins are enabled, I2C1 peripheral pins (SCL1 and SDA1) and McASP0
peripheral pins (AXR0[7:5] and AMUTE0) are disabled (default)
1 = McBSP1 peripheral pins are disabled, I2C1 peripheral pins (SCL1 and SDA1) and McASP0
peripheral pins (AXR0[7:5] and AMUTE0) are enabled.
5.4Multiplexed Pins
Multiplexed (MUXed) pins are pins that are shared by more than one peripheral and are internally
multiplexed. Most of these pins are configured by software via the device configuration register
(DEVCFG), and the others (specifically, the HPI pins) are configured by external pullup/pulldown resistors
only at reset. The MUXed pins that are configured by software can be programmed to switch
functionalities at any time. The MUXed pins that are configured by external pullup/pulldown resistors are
mutually exclusive; only one peripheral has primary control of the function of these pins after reset.
Table 5-5 summarizes the peripheral pins affected by the HPI_EN (HD14 pin) and DEVCFG register.
Table 5-6 identifies the multiplexed pins on the C6713/13B devices, shows the default (primary) function
and the default settings after reset, and describes the pins, registers, etc., necessary to configure the
specific multiplexed functions.
AHCLKX1
AHCLKR1GP[0:1],
ACLKX1GP[3],
ACLKR1GP[8:15]
AFSX1abc
AFSR1Plus:
AMUTE1GP[2]
AXR1[0]ctrl’d by
toGP2EN bit
AXR1[7]
I2C0I2C1
NO
TOUT0
(1)
NO
TOUT1
NO
GP[0:1],
GP[3],
GP[8:15]
www.ti.com
ED[7:0];
HD8 = 1/0
ED[7:0} side
[HD8 = 1 (Little)]
ED[31:24] side
[HD8 = 0 (Big)]
(1) Gray blocks indicate that the peripheral is not affected by the selection bit.
(2) The McASP0 pins, AXR0[3] and AHCLKX0, are shared with the timer input pins, TINP0 and TINP1, respectively. See Table 5-6 for
more detailed information.
(3) For more detailed information on endianness correction, see the EMIF Big Endian Mode Correctness [C6713B only] section of this data
GP2EN = 0 (GPEN register bit)When the CLKOUT2 pin is enabled, the CLK2EN bit in the
GP[2] function disabled, CLKOUT2 EMIF global control register (GBLCTL) controls the
enabledCLKOUT2 pin.
CLK2EN = 0: CLKOUT2 held high
CLK2EN = 1: CLKOUT2 enabled to clock [default].
CLKS0/AHCLKR0K3By default, McBSP0 peripheral pins are enabled upon
DR0/AXR0[0]J1
DX0/AXR0[1]H2
FSR0/AFSR0J3 McBSP0 pin function
FSX0/AFSX0H1
CLKR0/ACLKR0H3
CLKX0/ACLKX0G3
CLKS1/SCL1E1
DR1/SDA1M2
DX1/AXR0[5]L2
FSR1/AXR0[7]M3
CLKR1/AXR0[6]M1
CLKX1/AMUTE0L3
HINT/GP[1]J20
HD15/GP[15]B14
HD14/GP[14]C14
HD13/GP[13]A15
HD12/GP[12]C15
HD11/GP[11]A16
HD10/GP[10]B16
HD9/GP[9]C16
HD8/GP[8]B17GPIO pins, an external pulldown resistor must be provided
HD7/GP[3]A18
HD4/GP[0]C19
HD1/AXR1[7]D20
HD0/AXR1[4]E20
HCNTL1/AXR1[1]G19
HCNTL0/AXR1[3]G18GPxEN = 1:GP[x] pin enabled.
HR/W/AXR1[0]G20GPxDIR = 0:GP[x] pin is an input.
HDS1/AXR1[6]E19GPxDIR = 1:GP[x] pin is an output.
HDS2/AXR1[5]F18
HCS/AXR1[2]F20McASP1 pin direction is controlled by the PDIR[x] bits in
HD6/AHCLKR1C17
HD5/AHCLKX1B18
HD3/AMUTE1C20
HD2/AFSX1D18
HHWIL/AFSR1H20
HRDY/ACLKR1H19
HAS/ACLKX1E18
DEFAULT
No FunctionTo use these software-configurable GPIO pins, the
GPxDIR = 0 (input)GPxEN bits in the GP Enable Register and the GPxDIR
GP5EN = 0 (disabled)bits in the GP Direction Register must be properly
GP4EN = 0 (disabled)configured.
[(GPEN register bits)
GP[x] function disabled]
MCBSP1DIS = 0reset (I2C1 and McASP0 pins are disabled).
McBSP1 pin function
HPI(HPI enabled)
pin functionMcASP1 pins and 11 GPIO pins
(DEVCFG register bit)abc
I2C1 and McASP0 pinsTo enable the I2C1 and McASP0 peripheral pins, the
disabled, McBSP1 pins enabledMCBSP1DIS bit in the DEVCFG register must be set to 1
HPI_EN (HD14 pin) = 1
are disabled.
GPxEN = 1:GP[x] pin enabled.
GPxDIR = 0: GP[x] pin is an input.
GPxDIR = 1: GP[x] pin is an output.
To use AMUTEIN0/1 pin function, the GP[5]/GP[4] pins
must be configured as an input, the INEN bit set to 1, and
the polarity through the INPOL bit selected in the
associated McASP AMUTE register.
reset (McASP0 pins are disabled).
abc
To enable the McASP0 peripheral pins, the MCBSP0DIS
bit in the DEVCFG register must be set to 1 (disabling the
McBSP0 peripheral pins).
By default, McBSP1 peripheral pins are enabled upon
(disabling the McBSP1 peripheral pins).
By default, the HPI peripheral pins are enabled at reset.
McASP1 peripheral pins and eleven GPIO pins are
disabled.
To enable the McASP1 peripheral pins and the eleven
on the HD14 pin setting HPI_EN = 0 at reset.
GP enable register and the GPxDIR bits in the GP
direction register must be properly configured. To use
these software-configurable GPIO pins, the GPxEN bits in
the
It is recommended that external connections be provided to peripheral selection/device configuration pins,
including HD[14, 8, 12 (for 13B only), 4, 3], and CLKMODE0. Although internal pullup resistors exist on
these pins, providing external connectivity adds convenience to the user in debugging and flexibility in
switching operating modes.
Internal pullup/pulldown resistors also exist on the non−configuration pins on the HPI data bus (HD[15,
13:9, 7:5, 2:0] (for 13) and HD[15, 13, 11:9, 7:5, 2:0] (for 13B)). For proper device operation of the HD[15,
13:9, 7, 1, 0] (for13) or HD[13, 11:9, 7, 1, 0] (for 13B), do not oppose the internal pullup/pulldown resistors
on these non-configuration pins with external pullup/pulldown resistors at reset. If an external controller
provides signals to these HD[15, 13:9, 7, 1, 0] (for 13) or HD[13, 11:9, 7, 1, 0] (for 13B) non-configuration
pins, these signals must be driven to the default state of the pins at reset, or not be driven at all. For the
list of routed out, 3-stated, or not-driven pins recommended for external pullup/pulldown resistors, and
internal pullup/pulldown resistors for all devices pins, etc., see Terminal Functions. However, the HD[6, 5,
2] (for 13) or HD[15, 6, 5, 2] (for 13B) non-configuration pins can be opposed and driven during reset.
For the internal pullup/pulldown resistors for all device pins, see the Terminal Functions table.
6TERMINAL FUNCTIONS
The Terminal Functions table identifies the external signal names, the associated pin (ball) numbers along
with the mechanical package designator, the pin type (I, O/Z, or I/O/Z), whether the pin has any internal
pullup/pulldown resistors and a functional pin description. For more detailed information on device
configuration, peripheral selection, multiplexed/shared pins, and debugging considerations, see the Device
CLKINA3IIPDClock input
CLKOUT2/GP[2]Y12O/ZIPD
CLKOUT3D10OIPDClock output programmable by OSCDIV1 register in the PLL controller
CLKMODE0C4IIPU
PLLHVC5A
TMSB7IIPUJTAG test-port mode select
TDOA8O/ZIPUJTAG test-port data out
TDIA7IIPUJTAG test-port data in
TCKA6IIPUJTAG test-port clock
TRSTB6IIPD
EMU5B12I/O/ZIPUEmulation pin 5. Reserved for future use, leave unconnected.
EMU4C11I/O/ZIPUEmulation pin 4. Reserved for future use, leave unconnected.
EMU3B10I/O/ZIPUEmulation pin 3. Reserved for future use, leave unconnected.
EMU2D3I/O/ZIPUEmulation pin 2. Reserved for future use, leave unconnected.
EMU1B9
EMU0D9
RESETA13I—Device reset. When using boundary scan mode, drive the EMU[1:0] and RESET pins low.
NMIC13IIPD
GP[7](EXT_INT7)E3General-purpose input/output pins (I/O/Z), which also function as external interrupts
GP[6](EXT_INT6)D2
GP[5](EXT_INT5)/
AMUTEIN0
GP[4](EXT_INT4)/
AMUTEIN1
HINT/GP[1]J20O/ZIPUHost interrupt (from DSP to host) (O) [default] or this pin can be programmed as a GP[1] pin (I/O/Z)
HCNTL1/AXR1[1]G19IIPUHost control: Selects between control, address, or data registers (I) [default] or McASP1 data pin 1 (I/O/Z)
HCNTL0/AXR1[3]G18IIPUHost control: Selects between control, address, or data registers (I) [default] or McASP1 data pin 3 (I/O/Z)
HHWIL/AFSR1H20IIPU
HR/W/AXR1[0]G20IIPUHost read or write select (I) [default] or McASP1 data pin 0 (I/O/Z)
NO.
GDP
C1
C2
(1)
IPD/IPU
(3)
I/O/ZIPU
I/O/ZIPU
(2)
CLOCK/PLL CONFIGURATION
Clock output at half of device speed (O/Z) [default] (SYSCLK2 internal signal from the clock generator) or this pin can be programmed
as GP[2] pin (I/O/Z).
Clock generator input clock source select
0: Reserved, do not use
1: CLKIN square wave [default]
For proper device operation, this pin must be either left unconnected or externally pulled up with a 1-kΩ resistor.
Analog power (3.3 V) for PLL (PLL filter)
JTAG EMULATION
JTAG test-port reset. For IEEE Std 1149.1 JTAG compatibility, see the IEEE 1149.1 JTAG Compatibility Statement section of this data
sheet.
Emulation [1:0]
•Select the device functional mode of operation
Operation: EMU[1:0]:
00Boundary Scan/Functional Mode (see note)
01Reserved
10Reserved
11Emulation/Functional Mode [default] (see the IEEE 1149.1 JTAG Compatibility Statement of this data
sheet)
The DSP can be placed in Functional mode when the EMU[1:0] pins are configured for either boundary scan or emulation.
Note: When the EMU[1:0] pins are configured for boundary scan mode, the internal pulldown (IPD) on the TRST signal must not be
opposed to operate in functional mode.
For the boundary scan mode, drive EMU[1:0] and RESET pins low.
RESETS AND INTERRUPTS
Nonmaskable interrupt
•Edge-driven (rising edge)
•Edge-driven
•Polarity independently selected via the external interrupt polarity register bits (EXTPOL.[3:0]), in addition to the GPIO registers.
GP[4] and GP[5] pins also function as AMUTEIN1 McASP1 mute input and AMUTEIN0 McASP0 mute input, respectively, if enabled by
the INEN bit in the associated McASP AMUTE register.
HOST-PORT INTERFACE (HPI)
Host half-word select: First or second half-word (not necessarily high or low order) (I) [default] or McASP1 receive frame sync
or left/right clock (LRCLK) (I/O/Z).
DESCRIPTION
www.ti.com
(1) I = Input, O = Output, Z = High impedance, S = Supply voltage, GND = Ground
(2) IPD = Internal pulldown, IPU = Internal pullup. [These IPD/IPU signal pins feature a 13-kΩ resistor (approximate) for the IPD or 18-kΩ
resistor (approximate) for the IPU. An external pullup or pulldown resistor no greater than 4.4 kΩ and 2.0 kΩ, respectively, should be
used to pull a signal to the opposite supply rail.]
HD6/AHCLKR1C17I/O/ZIPUHost-port data pin 6 (I/O/Z) [default] or McASP1 receive high-frequency master clock (I/O/Z)
HD5/AHCLKX1B18I/O/ZIPUHost-port data pin 5 (I/O/Z) [default] or McASP1 transmit high-frequency master clock (I/O/Z)
HD4/GP[0]C19I/O/ZIPDHost-port data pin 4 (I/O/Z) [default] or this pin can be programmed as a GP[0] pin (I/O/Z)
HD3/AMUTE1C20I/O/ZIPUHost-port data pin 3 (I/O/Z) [default] or McASP1 mute output (O/Z)
HD2/AFSX1D18I/O/ZIPUHost-port data pin 2 (I/O/Z) [default] or McASP1 transmit frame sync or left/right clock (LRCLK) (I/O/Z)
HD1/AXR1[7]D20I/O/ZIPUHost-port data pin 1 (I/O/Z) [default] or McASP1 data pin 7 (I/O/Z)
HD0/AXR1[4]E20I/O/ZIPUHost-port data pin 0 (I/O/Z) [default] or McASP1 data pin 4 (I/O/Z)
HAS/ACLKX1E18IIPUHost address strobe (I) [default] or McASP1 transmit bit clock (I/O/Z)
HCS/AXR1[2]F20IIPUHost chip select (I) [default] or McASP1 data pin 2 (I/O/Z)
HDS1/AXR1[6]E19IIPUHost data strobe 1 (I) [default] or McASP1 data pin 6 (I/O/Z)
HDS2/AXR1[5]F18IIPUHost data strobe 2 (I) [default] or McASP1 data pin 5 (I/O/Z)
HRDY/ACLKR1H19O/ZIPDHost ready (from DSP to host) (O) [default] or McASP1 receive bit clock (I/O/Z)
Other HD pins (HD [15, 13:9, 7:5, 2:0] have pullups/pulldowns (IPUs/IPDs). For proper device operation, do not oppose these pins
with external pullups/pulldowns at reset; however, the HD[15, 6, 5, 2] pins can be opposed and driven at reset. For more details, see
the Device Configurations section of this data sheet.
EMIF—COMMON SIGNALS TO ALL TYPES OF MEMORY
Memory space enables
•Only one asserted during any external data access
Byte-enable control
•Decoded from the two lowest bits of the internal address
•Byte-write enables for most types of memory
•Can be directly connected to SDRAM read and write mask signal (SDQM)
EMIF—BUS ARBITRATION
EMIF—ASYNCHRONOUS/SYNCHRONOUS MEMORY CONTROL
EMIF output clock depends on the EKSRC bit (DEVCFG.[4]) and on EKEN bit (GBLCTL.[5]).
EKSRC = 0 ECLKOUT is based on the internal SYSCLK3 signal from the clock generator (default).
EKEN = 0 ECLKOUT held low
EKEN = 1 ECLKOUT enabled to clock (default)
DESCRIPTION
(4)
(4)
(4)
(4) To maintain signal integrity for the EMIF signals, serial termination resistors should be inserted into all EMIF output signal lines.
EA21U18
EA20Y18
EA19W17
EA18Y16
EA17V16
EA16Y15
EA15W15
EA14Y14
EA13W14The EMIF adjusts the address based on memory width:
EA12V14Width Pins Address
EA11W133221:2 21 through 2
EA10V101621:2 20 through 1
EA9Y9821:2 19 through 0
EA8V9
EA7Y8For more details on address width adjustments, see the External Memory Interface (EMIF) chapter of the TMS320C6000 Peripherals
EA6W8
EA5V8
EA4W7
EA3V7
EA2Y6
NO.
GDP
(1)
IPD/IPU
O/ZIPU
(2)
EMIF—ADDRESS
External address (word, half-word, and byte address)
HD3/AMUTE1C20I/O/ZIPUHost-port data pin 3 (I/O/Z) [default] or McASP1 mute output (O/Z)
HRDY/ACLKR1H19I/O/ZIPUHost ready (from DSP to host) (O) [default] or McASP1 receive bit clock (I/O/Z)
HD6/AHCLKR1C17I/O/ZIPUHost-port data pin 6 (I/O/Z) [default] or McASP1 receive high-frequency master clock (I/O/Z)
HAS/ACLKX1E18I/O/ZIPUHost address strobe (I) [default] or McASP 1 transmit bit clock (I/O/Z)
HD5/AHCLKX1B18I/O/ZIPUHost-port data pin 5 (I/O/Z) [default] or McASP1 transmit high-frequency master clock (I/O/Z)
HHWIL/AFSR1H20I/O/ZIPU
HD2/AFSX1D18I/O/ZIPUHost-port data pin 2 (I/O/Z) [default] or McASP1 transmit frame sync or left/right clock (LRCLK) (I/O/Z)
HD1/AXR1[7]D20I/O/ZIPUHost-port data pin 1 (I/O/Z) [default] or McASP1 TX/RX data pin 7 (I/O/Z)
HDS1/AXR1[6]E19I/O/ZIPUHost data strobe 1 (I) [default] or McASP1 TX/RX data pin 6 (I/O/Z)
HDS2/AXR1[5]F18I/O/ZIPUHost data strobe 2 (I) [default] or McASP1 TX/RX data pin 5 (I/O/Z)
HD0/AXR1[4]E20I/O/ZIPUHost-port data pin 0 (I/O/Z) [default] or McASP1 TX/RX data pin 4 (I/O/Z)
HCNTL0/AXR1[3]G18I/O/ZIPUHost control − selects between control, address, or data registers (I) [default] or McASP1 TX/RX data pin 3 (I/O/Z)
HCS/AXR1[2]F20I/O/ZIPUHost chip select (I) [default] or McASP1 TX/RX data pin 2 (I/O/Z)
HCNTL1/AXR1[1]G19I/O/ZIPUHost control − selects between control, address, or data registers (I) [default] or McASP1 TX/RX data pin 1 (I/O/Z)
HR/W/AXR1[0]G20I/O/ZIPUHost read or write select (I) [default] or McASP1 TX/RX data pin 0 (I/O/Z)
NO.
GDP
C2I/O/ZIPUGeneral-purpose input/output pin 4 and external interrupt 4 (I/O/Z) [default] or McASP1 mute input (I/O/Z)
(1)
I/O/ZIPUExternal data pins (ED[31:16] pins applicable to GDP package only)
(2)
IPD/IPU
EMIF—DATA
MULTICHANNEL AUDIO SERIAL PORT 1 (McASP1)
Host half-word select − first or second half-word (not necessarily high or low order) (I) [default] or McASP1 receive frame sync or
left/right clock (LRCLK) (I/O/Z)
(5)
DESCRIPTION
(5) To maintain signal integrity for the EMIF signals, serial termination resistors should be inserted into all EMIF output signal lines.
CLKX1/AMUTE0L3I/O/ZIPDMcBSP1 transmit clock (I/O/Z) [default] or McASP0 mute output (O/Z)
CLKR0/ACLKR0H3I/O/ZIPDMcBSP0 receive clock (I/O/Z) [default] or McASP0 receive bit clock (I/O/Z)
TINP1/AHCLKX0F2I/O/ZIPDTimer 1 input (I) [default] or McBSP0 transmit high-frequency master clock (I/O/Z)
CLKX0/ACLKX0G3I/O/ZIPDMcBSP0 transmit clock (I/O/Z) [default] or McASP0 transmit bit clock (I/O/Z)
CLKS0/AHCLKR0K3I/O/ZIPDMcBSP0 external clock source (as opposed to internal) (I) [default] or McASP0 receive high-frequency master clock (I/O/Z)
FSR0/AFSR0J3I/O/ZIPDMcBSP0 receive frame sync (I/O/Z) [default] or McASP0 receive frame sync or left/right clock (LRCLK) (I/O/Z)
FSX0/AFSX0H1I/O/ZIPDMcBSP0 transmit frame sync (I/O/Z) [default] or McASP0 transmit frame sync or left/right clock (LRCLK) (I/O/Z)
FSR1/AXR0[7]M3I/O/ZIPDMcBSP1 receive frame sync (I/O/Z) [default] or McASP0 TX/RX data pin 7 (I/O/Z)
CLKR1/AXR0[6]M1I/O/ZIPDMcBSP1 receive clock (I/O/Z) [default] or McASP0 TX/RX data pin 6 (I/O/Z)
DX1/AXR0[5]L2I/O/ZIPUMcBSP1 transmit data (O/Z) [default] or McASP0 TX/RX data pin 5 (I/O/Z)
TOUT1/AXR0[4]F1I/O/ZIPDTimer 1 output (O) [default] or McASP0 TX/RX data pin 4 (I/O/Z)
TINP0/AXR0[3]G2I/O/ZIPDTimer 0 input (I) [default] or McASP0 TX/RX data pin 3 (I/O/Z)
TOUT0/AXR0[2]G1I/O/ZIPDTimer 0 output (O) [default] or McASP0 TX/RX data pin 2 (I/O/Z)
DX0/AXR0[1]H2I/O/ZIPUMcBSP0 transmit data (O/Z) [default] or McASP0 TX/RX data pin 1 (I/O/Z)
DR0/AXR0[0]J1I/O/ZIPUMcBSP0 receive data (I) [default] or McASP0 TX/RX data pin 0 (I/O/Z)
TOUT1/AXR0[4]F1OIPDTimer 1 output (O) [default] or McASP0 TX/RX data pin 4 (I/O/Z)
TINP1/AHCLKX0F2IIPD
TOUT0/AXR0[2]G1OIPDTimer 0 output (O) [default] or McASP0 TX/RX data pin 2 (I/O/Z)
TINP0/AXR0[3]G2IIPDTimer 0 input (I) [default] or McASP0 TX/RX data pin 3 (I/O/Z)
CLKS1/SCL1E1I—
CLKR1/AXR0[6]M1I/O/ZIPDMcBSP1 receive clock (I/O/Z) [default] or McASP0 TX/RX data pin 6 (I/O/Z)
CLKX1/AMUTE0L3I/O/ZIPDMcBSP1 transmit clock (I/O/Z) [default] or McASP0 mute output (O/Z)
DR1/SDA1M2I—
DX1/AXR0[5]L2O/ZIPUMcBSP1 transmit data (O/Z) [default] or McASP0 TX/RX data pin 5 (I/O/Z)
FSR1/AXR0[7]M3I/O/ZIPDMcBSP1 receive frame sync (I/O/Z) [default] or McASP0 TX/RX data pin 7 (I/O/Z)
FSX1L1I/O/ZIPDMcBSP1 transmit frame sync
CLKS0/AHCLKR0K3IIPDMcBSP0 external clock source (as opposed to internal) (I) [default] or McASP0 receive high-frequency master clock (I/O/Z)
CLKR0/ACLKR0H3I/O/ZIPDMcBSP0 receive clock (I/O/Z) [default] or McASP0 receive bit clock (I/O/Z)
CLKX0/ACLKX0G3I/O/ZIPDMcBSP0 transmit clock (I/O/Z) [default] or McASP0 transmit bit clock (I/O/Z)
DR0/AXR0[0]J1IIPUMcBSP0 receive data (I) [default] or McASP0 TX/RX data pin 0 (I/O/Z)
DX0/AXR0[1]H2O/ZIPUMcBSP0 transmit data (O/Z) [default] or McASP0 TX/RX data pin 1 (I/O/Z)
FSR0/AFSR0J3I/O/ZIPDMcBSP0 receive frame sync (I/O/Z) [default] or McASP0 receive frame sync or left/right clock (LRCLK) (I/O/Z)
FSX0/AFSX0H1I/O/ZIPDMcBSP0 transmit frame sync (I/O/Z) [default] or McASP0 transmit frame sync or left/right clock (LRCLK) (I/O/Z)
CLKS1/SCL1E1I/O/Z—this pin is used as an I2C pin, the value of the pullup resistor depends on the number of devices connected to the I2C bus. For more
DR1/SDA1M2I/O/Z—
SCL0N1I/O/Z—
NO.
GDP
C1I/O/ZIPUGeneral-purpose input/output pin 5 and external interrupt 5 (I/O/Z) [default] or McASP0 mute input (I/O/Z)
(1)
(2)
IPD/IPU
MULTICHANNEL AUDIO SERIAL PORT 0 (McASP0)
TIMER1
Timer 1 input (I) [default] or McBSP0 transmit high-frequency master clock (I/O/Z). This pin defaults as Timer 1 input (I) and McASP
transmit high−frequency master clock input (I).
TIMER0
MULTICHANNEL BUFFERED SERIAL PORT 1 (McBSP1)
McBSP1 external clock source (as opposed to internal) (I) [default] or I2C1 clock (I/O/Z). This pin does not have an internal pullup or
pulldown. When this pin is used as a McBSP pin, this pin should either be driven externally at all times or be pulled up with a 10-kΩ
resistor to a valid logic level. Because it is common for some ICs to 3-state their outputs at times, a 10-kΩ pullup resistor may be
desirable even when an external device is driving the pin.
McBSP1 receive data (I) [default] or I2C1 data (I/O/Z). This pin does not have an internal pullup or pulldown. When this pin is used as
a McBSP pin, this pin should either be driven externally at all times or be pulled up with a 10-kΩ resistor to a valid logic level. Because
it is common for some ICs to 3-state their outputs at times, a 10-kΩ pullup resistor may be desirable even when an external device is
driving the pin.
MULTICHANNEL BUFFERED SERIAL PORT 0 (McBSP0)
INTER-INTEGRATED CIRCUIT 1 (I2C1)
McBSP1 external clock source (as opposed to internal) (I) [default] or I2C1 clock (I/O/Z). This pin must be externally pulled up. When
details, see the Philips I2C Specification Revision 2.1 (January 2000).
McBSP1 receive data (I) [default] or I2C1 data (I/O/Z). This pin must be externally pulled up. When this pin is used as an I2C pin, the
value of the pullup resistor depends on the number of devices connected to the I2C bus. For more details, see the Philips I2C
Specification Revision 2.1 (January 2000).
INTER-INTEGRATED CIRCUIT 0 (I2C0)
I2C0 clock. This pin must be externally pulled up. When this pin is used as an I2C pin, the value of the pull-up resistor depends on the
number of devices connected to the I2C bus. For more details, see the Philips I2C Specification Revision 2.1 (January 2000).
HD15/GP[15]B14I/O/ZIPUHost-port data pins (I/O/Z) [default] or general-purpose input/output pins (I/O/Z) and some function as boot configuration pins at reset.
HD14/GP[14]C14I/O/ZIPU
HD13/GP[13]A15I/O/ZIPU
HD12/GP[12]C15I/O/ZIPU
HD11/GP[11]A16I/O/ZIPU
HD10/GP[10]B16I/O/ZIPU
HD9/GP[9]C16I/O/ZIPU
AMUTEIN1
HD7/GP[3]A18I/O/ZIPUHost-port data pin 7 (I/O/Z) [default] or general-purpose input/output pin 3 (I/O/Z)
CLKOUT2/GP[2]Y12I/O/ZIPDClock output at half of device speed (O/Z) [default] or this pin can be programmed as GP[2] pin
HINT/GP[1]J20OIPUHost interrupt (from DSP to host) (O) [default] or this pin can be programmed as a GP[1] pin (I/O/Z)
HD4/GP[0]C19I/O/ZIPDHost-port data pin 4 (I/O/Z) [default] or this pin can be programmed as a GP[0] pin (I/O/Z)
RSVA5O/ZIPUReserved. (Leave unconnected; do not connect to power or ground.)
RSVB5A
RSVC12O—Reserved. (Leave unconnected; do not connect to power or ground.)
RSVD7O/ZIPDReserved. (Leave unconnected; do not connect to power or ground.)
RSVD12I—
RSVA12——
RSVB11——
DV
DD
NO.
GDP
C1I/O/ZIPU
C2I/O/ZIPU
A17
B3
B8
B13
C10
D1
D16
D19
F3
H18
J2
M18
R1
R18S—
T3
U5
U7
U12
U16
V13
V15
V19
W3
W9
W12
Y7
Y17
(1)
(6)
(2)
IPD/IPU
I2C0 data. This pin must be externally pulled up. When this pin is used as an I2C pin, the value of the pull-up resistor depends on the
number of devices connected to the I2C bus. For more details, see the Philips I2C Specification Revision 2.1 (January 2000).
GENERAL-PURPOSE INPUT/OUTPUT (GPIO)
•Used for transfer of data, address, and control
•Also controls initialization of DSP modes at reset via pullup/pulldown resistors
abc
As general-purpose input/output (GP[x]) functions, these pins are software configurable through registers. The GPxEN bits in the GP
Enable register and the GPxDIR bits in the GP Direction register must be properly configured:
abc
GPxEN = 1; GP[x] pin is enabled.
GPxDIR = 0; GP[x] pin is an input.
GPxDIR = 1; GP[x] pin is an output.
abc
For the functionality description of the Host-port data pins or the boot configuration pins, see the Host-Port Interface (HPI) portion of
this table.
General-purpose input/output pins (I/O/Z) that also function as external interrupts
•Edge-driven
•Polarity independently selected via the External Interrupt Polarity Register bits (EXTPOL.[3:0])
abc
GP[4] and GP[5] pins also function as AMUTEIN1 McASP1 mute input and AMUTEIN0 McASP0 mute input, respectively, if enabled by
the INEN bit in the associated McASP AMUTE register.
RESERVED FOR TEST
—Reserved. (Leave unconnected; do not connect to power or ground.)
Reserved. This pin does not have an IPU. For proper C6713 device operation, the D12 pin must be externally pulled down with a
10-kΩ resistor.
Reserved. For new designs, it is recommended that this pin be connected directly to CVDD(core power). For old designs, this can be
left unconnected.
Reserved. For new designs, it is recommended that this pin be connected directly to VSS(ground). For old designs, this pin can be left
unconneced.
SUPPLY VOLTAGE PINS
3.3-V supply voltage
(see the Power-Supply Decoupling section of this data sheet)
(1) Shaded pin numbers denote the center thermal balls.
(1)
(2)
IPD/IPU
Ground pins
grounds and thermal relief (thermal dissipation).
(1)
. The center thermal balls (J9−J12, K9−K12, L9−L12, M9−M12) [shaded] are all tied to ground and act as both electrical
SGUS049K–AUGUST 2003– REVISED APRIL 2011
DESCRIPTION
GROUND PINS
6.1Development Support
TI offers an extensive line of development tools for the TMS320C6000™ DSP platform, including tools to
evaluate the performance of the processors, generate code, develop algorithm implementations, and fully
integrate and debug software and hardware modules.
The following products support development of C6000™ DSP-based applications:
•Code Composer Studio™ Integrated Development Environment (IDE), including Editor
•C/C++/Assembly Code Generation, and Debug plus additional development tools
•Scalable, Real-Time Foundation Software ( DSP/BIOS™), which provides the basic run-time target
software needed to support any DSP application.
Hardware Development Tools
•Extended Development System ( XDS™) Emulator (supports C6000 DSP multiprocessor system
debug)
•EVM (evaluation module)
For a complete listing of development-support tools for the TMS320C6000 DSP platform, visit the Texas
Instruments web site at www.ti.com. For information on pricing and availability, contact the nearest TI field
sales office or authorized distributor.
6.2Device and Development-Support Tool Nomenclature
To designate the stages in the product development cycle, TI assigns prefixes to the part numbers of all
TMS320™ DSP devices and support tools. Each TMS320 DSP commercial family member has one of
three prefixes: SMX, TMP, or SM/SMJ. TI recommends two of three possible prefix designators for
support tools: TMDX and TMDS. These prefixes represent evolutionary stages of product development
fromengineeringprototypes(SMX/TMDX)throughfullyqualifiedproductiondevices/tools
(SM/SMJ/TMDS).
www.ti.com
6.2.1Device Development Evolutionary Flow
SMXPreproduction device that is not necessarily representative of the final device
electrical specifications
TMPFinal silicon die that conforms to the device electrical specifications but has not
completed quality and reliability verification
SM/SMJFully qualified production device
6.2.2Support Tool Development Evolutionary Flow
TMDXDevelopment-support product that has not yet completed Texas Instruments
internal qualification testing
TMDSFully qualified development-support product
SMX and TMP devices and TMDX development-support tools are shipped with appropriate disclaimers
describing their limitations and intended uses. Experimental devices (SMX) may not be representative of a
final product and TI reserves the right to change or discontinue these products without notice.
SM/SMJ devices and TMDS development-support tools have been characterized fully, and the quality and
reliability of the device have been demonstrated fully. TI’s standard warranty applies.
Predictions show that prototype devices (SMX or TMP) have a greater failure rate than the standard
production devices. TI recommends that these devices not be used in any production system because
their expected end-use failure rate still is undefined. Only qualified production devices are to be used.
TI device nomenclature also includes a suffix with the device family name. This suffix indicates the
package type (for example, GDP), the temperature range (for example, blank is the default commercial
temperature range), and the device speed range in megahertz (for example, 20 is 200 MHz).
Figure 6-1 provides a legend for reading the complete device name for any TMS320C6000 DSP family
Blank = 0°C to 90°C (commercial temperature)
A= 40°C to 105°C (extended temperature)
M = –55°C to 125°C (extended temperature)
S = -55°C to 105°C (extended temperature)
-
=
=
NOTE (1): BGA = Ball Grid Array
QFP = Quad Flatpack
For actual device part numbers (P/Ns) and ordering information, see the Mechanical Data section of this
the TI website (www.ti.com).
document or
SM320C6713-EP
SM320C6713B-EP
www.ti.com
Table 6-1. 320C6713 and C6713B Device Part Numbers (P/Ns) and Ordering Information
DEVICE ORDERABLE P/N
C6713B
SM32C6713BGDPA20EP200 MHz/1200 MFlops1.26 V3.3 V–40°C to 105°C
SM32C6713BGDPM30EP300 MHz/1800 MFlops1.4V3.3V–55°C to 125°C
SM32C6713BGDPS20EP200 MHz/1200 MFlops1.26 V3.3 V–55°C to 105°C
(1) For the most current package and ordering information, see the Package Option Addendum at the end of this document, or see the TI
Web site at www.ti.com.
(2) Package drawings, standard packing quantities, thermal data, symbolization, and PCB design guidelines are available at
Extensive documentation supports all the TMS320 DSP family generations of devices from product
announcement through applications development. The types of documentation available include data
sheets, such as this document with design specifications complete user’s reference guides for all devices
and tools, technical briefs, development-support tools, on-line help, and hardware and software
applications. The following is a brief, descriptive list of support documentation specific to the C6000 DSP
devices, except where noted, all documents are accessible through the TI web site at www.ti.com.
•TMS320C6000™ CPU and Instruction Set Reference Guide (literature number SPRU189) describes
the C6000 CPU (DSP core) architecture, instruction set, pipeline, and associated interrupts.
TMS320C6000™ DSP Peripherals Overview Reference Guide [hereafter referred to as the C6000
PRG Overview] (literature number SPRU190) provides an overview and briefly describes the
functionality of the peripherals available on the C6000 DSP platform of devices. This document also
includes a table listing the peripherals available on the C6000 devices along with literature numbers
and hyperlinks to the associated peripheral documents. These C6713/13B peripherals are similar to
the peripherals on the TMS320C6711 and TMS320C64x devices; therefore, see the TMS320C6711
(C6711 or C67x) peripheral information and, in some cases (where indicated), see the TMS320C6711
(C6711 or C671x) peripheral information and, in some cases (where indicated), see the C64x
information in the C6000™ PRG Overview (literature number SPRU190).
•TMS320DA6000™ DSP Multichannel Audio Serial Port (McASP) Reference Guide (literature number
SPRU041) describes the functionality of the McASP peripherals available on the C6713/13B device.
(literature number SPRU233) describes the functionality of the PLL peripheral available on the
C6713/13B device.
•TMS320C6000™ DSP Inter-Integrated Circuit (I2C) Module Reference Guide (literature number
SPRU175) describes the functionality of the I2C peripherals available on the C6713/13B device.
•The PowerPAD ™Thermally-Enhanced Package Technical Brief (literature number SLMA002) focuses
on the specifics of integrating a PowerPAD package into the printed circuit board (PCB) design to
make optimum use of the thermal efficiencies designed into the PowerPAD package.
•TMS320C6000™ Technical Brief (literature number SPRU197) gives an introduction to the C62x™/
C67x™ devices, associated development tools, and third-party support.
•Migrating from TMS320C6211(B)/C6711(B) to TMS320C6713 application report (literature number
SPRA851) indicates the differences and describes the issues of interest related to the migration from
the TI TMS320C6211(B)/C6711(B) GFN package to the TMS320C6713 GDP package.
•TMS320C6713, TMS320C6713B Digital Signal Processors Silicon Errata (literature number SPRZ191)
describes the known exceptions to the functional specifications for particular silicon revisions of the
TMS320C6713 and TMS320C6713B devices.
SPRA889) discusses the power consumption for user applications with the TMS320C6713/13B,
TMS320C6712C/12D, and TMS320C6711C/11D DSP devices.
•Using IBIS Models for Timing Analysis application report (literature number SPRA839) describes how
to properly use IBIS models to attain accurate timing analysis for a given system.
www.ti.com
The tools support documentation is electronically available within the Code Composer Studio Integrated
Development Environment (IDE). For a complete listing of C6000 DSP latest documentation, visit the
Texas Instruments web site at www.ti.com. Also, see the TI web site for the application report, How ToBegin Development Today With the TMS320C6713 Floating-Point DSP (literature number SPRA809),
which describes in more detail the similarities/differences between the C6713 and C6711 C6000 DSP
devices.
This section provides the register information for the device.
7.1CPU Control Status Register (CSR) Description
The CPU CSR contains the CPU ID and CPU Revision ID (bits 16−31), as well as the status of the device
power-down modes [PWRD field (bits 15−10)], program and data cache control modes, the endian bit
(EN, bit 8), and the global interrupt enable (GIE, bit 0) and previous GIE (PGIE, bit 1). Figure 7-1 and
Table 7-1 identify the bit fields in the CPU CSR.
For more detailed information on the bit fields in the CPU CSR, see the TMS320C6000 DSP Peripherals
Overview Reference Guide (literature number SPRU190) and the TMS320C6000 CPU and Instruction Set
Reference Guide (literature number SPRU189).
31:24CPU ID
23:16REVISION ID
15:10PWRDControl power-down modes. The values are always read as zero.
9SATSaturate bit.
8ENEndian bit. This bit is read-only. Depicts the device endian mode.
7:5PCCProgram cache control mode.
4:2DCCData cache control mode.
1PGIEPrevious GIE (global interrupt enable); saves the Global Interrupt Enable (GIE) when an interrupt is taken.
0GIEGlobal interrupt enable bit.
CPU ID + REV ID. Read only. Identifies which CPU is used and defines the silicon revision of the CPU.
CPU ID + REVISION ID (31:16) are combined for a value of: 0x0203 for C6713/13B
000000 = No power down (default)
001001 = PD1, wake up by an enabled interrupt
010001 = PD1, wake up by an enabled or not enabled interrupt
011010 = PD2, wake up by a device reset
011100 = PD3, wake up by a device reset
Others = Reserved
Set when any unit performs a saturate. This bit can be cleared only by the MVC instruction and can be set only
by a functional unit. The set by the a functional unit has priority over a clear (by the MVC instruction) if they
occur on the same cycle. The saturate bit is set one full cycle (one delay slot) after a saturate occurs. This bit
will not be modified by a conditional instruction whose condition is false.
0 = Big Endian mode
1 = Little Endian mode [default]
L1D, Level 1 program cache
000/010 = Cache enabled/cache accessed and updated on reads
All other PCC values are reserved.
L1D, Level 1 data cache
000/010 = Cache enabled/2-way cache
All other DCC values are reserved.
Allows for proper nesting of interrupts.
0 = Previous GIE value is 0 (default).
1 = Previous GIE value is 1.
Enables (1) or disables (0) all interrupts except the reset interrupt and NMI (nonmaskable interrupt).
0 = Disables all interrupts (except the reset interrupt and NMI) [default].
1 = Enables all interrupts (except the reset interrupt and NMI).
The C6713B device includes an enhancement to the CCFG register. A P bit (CCFG.31) allows the
programmer to select the priority of accesses to L2 memory originating from the transfer crossbar (TC)
over accesses originating from the L1D memory system. An important class of TC accesses is EDMA
transfers, which move data to or from the L2 memory. While the EDMA normally has no issue accessing
L2 memory because of the high hit rates on the L1D memory system, there are pathological cases where
certain CPU behavior could block the EDMA from accessing the L2 memory for long enough to cause a
missed deadline when transferring data to a peripheral such as the McASP or McBSP. This can be
avoided by setting the P bit to 1 because the EDMA will assume a higher priority than the L1D memory
system when accessing L2 memory.
For more detailed information on the P-bit function and for silicon advisories concerning EDMA L2
memory accesses blocked, see the TMS320C6713, TMS320C6713B Digital Signal Processors SiliconErrata (literature number SPRZ191).
The C67x DSP core supports 16 prioritized interrupts, which are listed in Table 7-3. The highest priority
interrupt is INT_00 (dedicated to RESET), while the lowest priority is INT_15. The first four interrupts are
non-maskable and fixed. The remaining interrupts (4−15) are maskable and default to the interrupt source
listed in Table 7-3. However, their interrupt source may be reprogrammed to any one of the sources listed
in Table 7-4 (Interrupt Selector). Table 7-4 lists the selector value corresponding to each of the alternate
interrupt sources. The selector choice for interrupts 4−15 is made by programming the corresponding
fields (listed in Table 7-3) in the MUXH (address 0x019C0000) and MUXL (address 0x019C0004)
registers.
(1) Interrupt events GPINT4, GPINT5, GPINT6, and GPINT7 are outputs from the GPIO module (GP).
They originate from the device pins GP[4](EXT_INT4)/AMUTEIN1, GP[5](EXT_INT5)/AMUTEIN0,
GP[6](EXT_INT6), and GP[7](EXT_INT7). These pins can be used as edge-sensitive EXT_INTx with
polarity controlled by the External Interrupt Polarity Register (EXTPOL.[3:0]). The corresponding pins
must first be enabled in the GPIO module by setting the corresponding enable bits in the GP Enable
Register (GPEN.[7:4]), and configuring them as inputs in the GP Direction Register (GPDIR.[7:4]).
These interrupts can be controlled through the GPIO module in addition to the simple EXTPOL.[3:0]
bits. For more information on interrupt control via the GPIO module, see the TMS320C6000™ DSPGeneral-Purpose Input/Output (GPIO) Reference Guide (literature number SPRU584).
(1) Interrupt events GPINT4, GPINT5, GPINT6, and GPINT7 are outputs from the GPIO module (GP).
They originate from the device pins GP[4](EXT_INT4)/AMUTEIN1, GP[5](EXT_INT5)/AMUTEIN0,
GP[6](EXT_INT6), and GP[7](EXT_INT7). These pins can be used as edge-sensitive EXT_INTx with
polarity controlled by the External Interrupt Polarity Register (EXTPOL.[3:0]). The corresponding pins
must first be enabled in the GPIO module by setting the corresponding enable bits in the GP Enable
Register (GPEN.[7:4]), and configuring them as inputs in the GP Direction Register (GPDIR.[7:4]).
These interrupts can be controlled through the GPIO module in addition to the simple EXTPOL.[3:0]
bits. For more information on interrupt control via the GPIO module, see the TMS320C6000™ DSPGeneral-Purpose Input/Output (GPIO) Reference Guide (literature number SPRU584).
INTERRUPT EVENTMODULE
(1)
(1)
(1)
(1)
GPIO
GPIO
GPIO
GPIO
7.4External Interrupt Sources
The C6713/13B device supports many external interrupt sources as indicated in Table 7-5. Control of the
interrupt source is done by the associated module and is made available by enabling the corresponding
binary interrupt selector value (see Table 7-4 shaded rows). Because of pin multiplexing and module
usage, not all external interrupt sources are available at the same time.
GP[9]GPINT0GPIO
GP[8]GPINT0GPIO
GP[7]GPINT0 or GPINT7GPIO
GP[6]GPINT0 or GPINT6GPIO
GP[5]GPINT0 or GPINT5GPIO
GP[4]GPINT0 or GPINT4GPIO
GP[3]GPINT0GPIO
GP[2]GPINT0GPIO
GP[1]GPINT0GPIO
GP[0]GPINT0GPIO
7.5EDMA Module and EDMA Selector
www.ti.com
The C67x EDMA supports up to 16 EDMA channels. Four of the 16 channels (channels 8−11) are
reserved for EDMA chaining, leaving 12 EDMA channels available to service peripheral devices.
The EDMA selector registers that control the EDMA channels servicing peripheral devices are located at
addresses 0x01A0FF00 (ESEL0), 0x01A0FF04 (ESEL1), and 0x01A0FF0C (ESEL3). These EDMA
selector registers control the mapping of the EDMA events to the EDMA channels. Each EDMA event has
an assigned EDMA selector code (see Table 7-7). By loading each EVTSELx register field with an EDMA
selector code, users can map any desired EDMA event to any specified EDMA channel. Table 7-6 lists the
default EDMA selector value for each EDMA channel.
See Table 7-8 and Table 7-11 for the EDMA Event Selector registers and their associated bit descriptions.
29:24The EVTSEL0 through EVTSEL15 bits correspond to channels 0 to 15, respectively. These EVTSELx
21:16fields are user selectable. By configuring the EVTSELx fields to the EDMA selector value of the desired
13:8EDMA sync event number (see Table 7-7), users can map any EDMA event to the EDMA channel.
5:0abc
ReservedReserved. Read only, writes have no effect.
EDMA event selection bits for channel x. Allows mapping of the EDMA events to the EDMA channels.
abc
EVTSELx
For example, if EVTSEL15 is programmed to 00 0001b (the EDMA selector code for TINT0), channel 15
is triggered by Timer 0 TINT0 events.
The 320C6713/13B includes a PLL and a flexible PLL controller peripheral consisting of a prescaler (D0)
and four dividers (OSCDIV1, D1, D2, and D3). The PLL controller is able to generate different clocks for
different parts of the system (that is, DSP core, peripheral data bus, external memory interface, McASP,
and other peripherals). Figure 8-1 shows the PLL, the PLL controller, and the clock generator logic.
www.ti.com
A.Dividers D1 and D2 must never be disabled. Never write a '0' to the D1EN or D2EN bits in the PLLDIV1 and PLLDIV2
registers.
B.Place all PLL external components (C1, C2, and the EMI filter) as close to the C67x DSP device as possible. For the
best performance, TI recommends that all the PLL external components be on a single side of the board without
jumpers, switches, or components other than the ones shown.
C. For reduced PLL jitter, maximize the spacing between switching signals and the PLL external components (C1, C2,
and the EMI filter).
D. The 3.3-V supply for the EMI filter must be from the same 3.3-V power plane supplying the I/O voltage, DVDD.
E.EMI filter manufacturer TDK part number ACF451832-333, -223, -153, -103. Panasonic part number EXCCET103U.
The PLL reset time is the amount of wait time needed when resetting the PLL (writing PLLRST = 1), for
the PLL to properly reset, before bringing the PLL out of reset (writing PLLRST = 0). For the PLL reset
time value, see Table 8-1. The PLL lock time is the amount of time from when PLLRST = 0 with PLLEN =
0 (PLL out of reset, but still bypassed) to when the PLLEN bit can be safely changed to 1 (switching from
bypass to the PLL path); see Table 8-1 and Figure 8-1.
Under some operating conditions, the maximum PLL lock time may vary from the specified typical value.
For the PLL lock time values, see Table 8-1.
Table 8-1. PLL Lock and Reset Times
MINTYPMAXUNIT
PLL lock time75187.5μs
PLL reset time125ns
Table 8-2 shows the C6713/13B device CLKOUT signals, how and by what register control bits they are
derived, and what is the default settings. For more details on the PLL, see the PLL and Clock Generator
Logic diagram (Figure 8-1).
Table 8-2. CLKOUT Signals, Default Settings, and Control
ON (ENABLED);EKSRC = 0 (DEVCFG.[4])To select ECLKIN source:
derived from SYSCLK3EKEN = 1 (EMIF GBLCTL.[5])EKSRC = 1 (DEVCFG.[4]) and
D2EN = 1 (PLLDIV2.[15])
CK2EN = 1 (EMIF GBLCTL.[3])
SGUS049K–AUGUST 2003– REVISED APRIL 2011
DESCRIPTION
SYSCLK3 selected [default].
EKEN = 1 (EMIF GBLCTL.[5])
The input clock (CLKIN) is directly available to the McASP modules as AUXCLK for use as an internal
high-frequency clock source. The input clock (CLKIN) may also be divided down by a programmable
divider OSCDIV1 (/1, /2, /3, ..., /32) and output on the CLKOUT3 pin for other use in the system.
Figure 8-1 shows that the input clock source may be divided down by divider PLLDIV0 (/1, /2, ..., /32) and
then multiplied up by a factor of x4, x5, x6, and so on, up to x25.
Either the input clock (PLLEN = 0) or the PLL output (PLLEN = 1) then serves as the high-frequency
reference clock for the rest of the DSP system. The DSP core clock, the peripheral bus clock, and the
EMIF clock may be divided down from this high-frequency clock (each with a unique divider). For
example, with a 30-MHz input if the PLL output is configured for 450 MHz, the DSP core may be operated
at 225 MHz (/2), while the EMIF may be configured to operate at a rate of 75 MHz (/6). Note that there is
a specific minimum and maximum reference clock (PLLREF) and output clock (PLLOUT) for the block
labeled PLL in Figure 8-1, as well as for the DSP core, peripheral bus, and EMIF. The clock generator
must not be configured to exceed any of these constraints (certain combinations of external clock input,
internal dividers, and PLL multiply ratios might not be supported). See Table 8-3 for the PLL clocks input
and output frequency ranges.
(1) SYSCLK2 rate must be exactly half of SYSCLK1.
(2) See also the Electrical Specification (timing requirements and switching characteristics parameters) in
the Input and Output Clocks section of this data sheet.
(3) When the McASP module is not used, the AUXCLK maximum frequency can be any frequency up to
the CLKIN maximum frequency.
The EMIF itself may be clocked by an external reference clock via the ECLKIN pin or can be generated
on-chip as SYSCLK3. SYSCLK3 is derived from divider D3 off of PLLOUT (see Figure 8-1). The EMIF
clock selection is programmable via the EKSRC bit in the DEVCFG register.
The settings for the PLL multiplier and each of the dividers in the clock generation block may be
reconfigured via software at run time. If either the input to the PLL changes due to D0, CLKMODE0, or
CLKIN, or if the PLL multiplier is changed, then software must enter bypass first and stay in bypass until
the PLL has had enough time to lock (see electrical specifications). For the programming procedure, see
the TMS320C6000™ DSP Software-Programmable Phase-Locked Loop (PLL) Controller Reference Guide
(literature number SPRU233).
(1) (2)
www.ti.com
(3)
MHz
SYSCLK2 is the internal clock source for peripheral bus control. SYSCLK2 (Divider D2) must be
programmed to be half of the SYSCLK1 rate. For example, if D1 is configured to divide-by-2 mode (/2),
then D2 must be programmed to divide-by-4 mode (/4). SYSCLK2 is also tied directly to CLKOUT2 pin
(see Figure 8-1).
During the programming transition of Divider D1 and Divider D2 (resulting in SYSCLK1 and SYSCLK2
output clocks, see Figure 8-1), the order of programming the PLLDIV1 and PLLDIV2 registers must be
observed to ensure that SYSCLK2 always runs at half the SYSCLK1 rate or slower. For example, if the
divider ratios of D1 and D2 are to be changed from /1, /2 (respectively) to /5, /10 (respectively) then, the
PLLDIV2 register must be programmed before the PLLDIV1 register. The transition ratios become /1, /2;
/1, /10; and then /5, /10. If the divider ratios of D1 and D2 are to be changed from /3, /6 to /1, /2, then the
PLLDIV1 register must be programmed before the PLLDIV2 register. The transition ratios, for this case,
become /3, /6; /1, /6; and then /1, /2. The final SYSCLK2 rate must be exactly half of the SYSCLK1 rate.
Note that Divider D1 and Divider D2 must always be enabled (that is, D1EN and D2EN bits are set to 1 in
the PLLDIV1 and PLLDIV2 registers).
The PLL Controller registers should be modified only by the CPU or via emulation. The HPI should not be
used to directly access the PLL Controller registers.
For detailed information on the clock generator (PLL Controller registers) and the associated software bit
descriptions, see Table 8-4 through Table 8-11.
9MULTICHANNEL AUDIO SERIAL PORT (McASP) PERIPHERALS
The 320C6713/13B device includes two multichannel audio serial port (McASP) interface peripherals
(McASP1 and McASP0). The McASP is a serial port optimized for the needs of multichannel audio
applications. With two McASP peripherals, the 320C6713/13B device is capable of supporting two
completely independent audio zones simultaneously.
Each McASP consists of a transmit and receive section. These sections can operate completely
independently with different data formats, separate master clocks, bit clocks, and frame syncs or
alternatively, the transmit and receive sections may be synchronized. Each McASP module also includes
a pool of 16 shift registers that may be configured to operate as either transmit data, receive data, or
general-purpose I/O (GPIO).
The transmit section of the McASP can transmit data in either a time division multiplexed (TDM)
synchronous serial format or in a digital audio interface (DIT) format where the bit stream is encoded for
S/PDIF, AES-3, IEC-60958, and CP-430 transmission. The receive section of the McASP supports the
TDM synchronous serial format.
Each McASP can support one transmit data format (either a TDM format or DIT format) and one receive
format at a time. All transmit shift registers use the same format and all receive shift registers use the
same format. However, the transmit and receive formats need not be the same.
Both the transmit and receive sections of the McASP also support burst mode, which is useful for
non-audio data (for example, passing control information between two DSPs).
TheMcASPperipheralshaveadditionalcapabilityforflexibleclockgeneration,anderror
detection/handling, as well as error management.
9.1McASP Block Diagram
Figure 9-1 shows the major blocks along with external signals of the 320C6713/13B McASP1 and
McASP0 peripherals, and shows the eight serial data [AXR] pins for each McASP. Each McASP also
includes full general-purpose I/O (GPIO) control, so any pins not needed for serial transfers can be used
for general-purpose I/O.
9.2Multichannel Time Division Multiplexed (TDM) Synchronous Transfer Mode
The McASP supports a multichannel TDM synchronous transfer mode for both transmit and receive.
Within this transfer mode, a wide variety of serial data formats are supported, including formats compatible
with devices using the Inter-Integrated Sound (IIS) protocol.
TDM synchronous transfer mode is typically used when communicating between integrated circuits, such
as between a DSP and one or more ADC, DAC, codec, or S/PDIF receiver devices. In multichannel
applications, it is typical to find several devices operating synchronized with each other. For example, to
provide six analog outputs, three stereo DAC devices would be driven with the same bit clock and frame
sync, but each stereo DAC would use a different McASP serial data pin carrying stereo data (two TDM
time slots, left and right).
The TDM synchronous serial transfer mode utilizes several control signals and one or more serial data
signals:
•A bit clock signal (ACLKX for transmit, ACKLR for receive)
•A frame sync signal (AFSX for transmit, AFSR for receive)
•An (optional) high-frequency master clock (AHCLKX for transmit, AHCLKR for receive) from which the
bit clock is derived
•One or more serial data pins (AXR for transmit and for receive)
Except for the optional high-frequency master clock, all of the signals in the TDM synchronous serial
transfer mode protocol are synchronous to the bit clocks (ACLKX and ACLKR).
In the TDM synchronous transfer mode, the McASP continually transmits and receives data periodically
(since audio ADCs and DACs operate at a fixed-data rate). The data is organized into frames, and the
beginning of a frame is marked by a frame sync pulse on the AFSX, AFSR pin.
In a typical audio system, one frame is transferred per sample period. To support multiple channels, the
choices are to either include more time slots per frame (and therefore operate with a higher bit clock) or to
keep the bit clock period constant and use additional data pins to transfer the same number of channels.
For example, a particular six-channel DAC might require three McASP serial data pins; transferring two
channels of data on each serial data pin during each sample period (frame). Another similar DAC may be
designed to use only a single McASP serial data pin, but clocked three times faster and transferring six
channels of data per sample period. The McASP is flexible enough to support either type of DAC, but a
transmitter cannot be configured to do both at the same time.
For multiprocessor applications, the McASP supports any number of time slots per frame (between 2 and
32), and includes the ability to disable transfers during specific time slots.
In addition, to support S/PDIF, AES-3, IEC-60958, and CP-430 receiver chips whose natural block
(McASP frame) size is 384 samples; the McASP receiver supports a 384 time slot mode. The advantage
to using the 384 time slot mode is that interrupts may be generated synchronous to the S/PDIF, AES-3,
IEC-60958, and CP-430 receivers; for example, the last slot interrupt.
9.3Burst Transfer Mode
The McASP also supports a burst transfer mode, which is useful for non-audio data (for example, passing
control information between two DSPs). Burst transfer mode uses a synchronous serial format similar to
TDM, except the frame sync is generated for each data word transferred. In addition, frame sync
generation is not periodic or time driven as in TDM mode, but rather data driven.
9.4Supported Bit Stream Formats for TDM and Burst Transfer Modes
The serial data pins support a wide variety of formats. In the TDM and burst synchronous modes, the data
may be transmitted/received with the following options:
•Time slots per frame: 1 (burst/data driven), or 2,3...32 (TDM/time driven)
•Time slot size: 8, 12, 16, 20, 24, 28, 32 bits per time slot
•Data size: 8, 12, 16, 20, 24, 28, 32 bits (must be less than or equal to time slot)
•Data alignment within time slot: left or right justified
•Bit order: MSB or LSB first
•Unused bits in time slot: Padded with 0, 1 or extended with value of another bit
•Time slot delay from frame sync: 0-, 1-, or 2-bit delay
The data format can be programmed independently for transmit and receive, and for McASP0 versus
McASP1. In addition, the McASP can automatically realign the data as processed natively by the DSP
(any format on a nibble boundary) adjusting the data in hardware to any of the supported serial bit stream
formats (TDM, burst, and DIT modes). This adjustment reduces the amount of bit manipulation that the
DSP must perform and simplifies software architecture.
9.5Digital Audio Interface Transmitter (DIT) Transfer Mode (Transmitter Only)
The McASP transmit section may also be configured in DIT mode where it outputs data formatted for
transmission over an S/PDIF, AES-3, IEC-60958, or CP-430 standard link. These standards encode the
serial data such that the equivalent of clock and frame sync are embedded within the data stream. DIT
transfer mode is used as an interconnect between audio components and can transfer multichannel digital
audio data over a single optical or coaxial cable.
www.ti.com
From an internal DSP standpoint, the McASP operation in DIT transfer mode is similar to the two-time-slot
TDM mode, but the data transmitted is output as a bi-phase mark encoded bit stream with preamble,
channel status, user data, validity, and parity automatically stuffed into the bit stream by the McASP
module. The McASP includes separate validity bits for even/odd subframes and two 384-bit register file
modules to hold channel status and user data bits.
DIT mode requires (at a minimum):
•One serial data pin (if the AUXCLK is used as the reference (see Figure 8-1)
OR
•One serial data pin plus either the AHCLKX or ACLKX pin (if an external clock is needed)
If additional serial data pins are used, each McASP may be used to transmit multiple encoded bit streams
(one per pin). However, the bit streams will all be synchronized to the same clock and the user data,
channel status, and validity information carried by each bit stream will be the same for all bit streams
transmitted by the same McASP module.
The McASP can also automatically realign the data as processed by the DSP (any format on a nibble
boundary) in DIT mode; reducing the amount of bit manipulation that the DSP must perform and
simplifying software architecture.
The McASP transmit and receive clock generators are identical. Each clock generator can accept a
high-frequency master clock input (on the AHCLKX and AHCLKR pins).
The transmit and receive bit clocks (on the ACLKX and ACLKR pins) can also be sourced externally or
can be sourced internally by dividing down the high-frequency master clock input (programmable factor /1,
/2, /3, ... /4096). The polarity of each bit clock is individually programmable.
The frame sync pins are AFSX (transmit) and AFSR (receive). A typical usage for these pins is to carry
the left-right clock (LRCLK) signal when transmitting and receiving stereo data. The frame sync signals
are individually programmable for either internal or external generation, either bit or slot length, and either
rising or falling edge polarity.
Some examples of the things that a system designer can use the McASP clocking flexibility for are:
•Input a high-frequency master clock (for example, 512 fSof the receiver) and receive with an internally
generated bit clock ratio of /8, while transmitting with an internally generated bit clock ratio of /4 or /2.
(An example application would be to receive data from a DVD at 48 kHz but output up-sampled or
decoded audio at 96 kHz or 192 kHz.)
•Transmit/receive data based on sample rate (for example, 44.1 kHz) using McASP0 while transmitting
and receiving at a different sample rate (for example, 48 kHz) on McASP1.
•Use the DSP on-board AUXCLK to supply the system clock when the input source is an A/D converter.
9.7McASP Error Handling and Management
SGUS049K–AUGUST 2003– REVISED APRIL 2011
To support the design of a robust audio system, the McASP module includes error-checking capability for
the serial protocol, data underrun, and data overrun. In addition, each McASP includes a timer that
continually measures the high-frequency master clock every 32 SYSCLK2 clock cycles. The timer value
can be read to get a measurement of the high-frequency master clock frequency and has a min-max
range setting that can raise an error flag if the high-frequency master clock goes out of a specified range.
The user would read the high-frequency transmit master clock measurement (AHCLKX0 or AHCLKX1) by
reading the XCNT field of the XCLKCHK register and the user would read the high-frequency receive
master clock measurement (AHCLKR0 or AHCLKR1) by reading the RCNT field of the RCLKCHK
register.
Upon the detection of any one or more of the above errors (software selectable) or the assertion of the
AMUTE_IN pin, the AMUTE output pin may be asserted to a high or low level (selectable) to immediately
mute the audio output. In addition, an interrupt may be generated if enabled based on any one or more of
the error sources.
The McASP transmitter and receiver sections each generate an event on every time slot. This event can
be serviced by an interrupt or by the EDMA controller.
When using interrupts to service the McASP, each shift register buffer has a unique address in the McASP
registers space (see Table 4-1).
When using the EDMA to service the McASP, the McASP DATA Port space, shown in Table 4-1, is
accessed. In this case, the address least-significant bits are ignored. Writes to any address in this range
access the transmitting buffers in order from lowest (serializer 0) to highest (serializer 15), skipping over
disabled and receiving serializers. Likewise, reads from any address in this space access the receiving
buffers in the same order but skip over disabled and transmitting buffers.
9.9I2C
Having two I2C modules on the 320C6713/13B simplifies system architecture, since one module may be
used by the DSP to control local peripherals ICs (DACs, ADCs, etc.) while the other may be used to
communicate with other controllers in a system or to implement a user interface.
I2C ports are compatible with Philips I2C Specification Revision 2.1 (January 2000).
The 320C6713/13B also includes two I2C serial ports for control purposes. Each I2C port supports:
•Fast mode up to 400 Kbps (no fail-safe I/O buffers)
•Noise filter to remove noise 50 ns or less
•7- and 10-bit device addressing modes
•Master (transmit/receive) and slave (transmit/receive) functionality
•Events: DMA, interrupt, or polling
•Slew-rate limited open-drain output buffers
www.ti.com
NOTE
Figure 9-2 shows a block diagram of the I2Cx module.
This section discusses the logic and power-supply configuration of the SM320C6713-EP and
SM320C6713B-EP.
10.1 General-Purpose Input/Output (GPIO)
To use the GP[15:0] software-configurable GPIO pins, the GPxEN bits in the GP enable (GPEN) register
and the GPxDIR bits in the GP direction (GPDIR) register must be properly configured.
GPxEN = 1GP[x] pin is enabled.
GPxDIR = 0GP[x] pin is an input.
GPxDIR = 1GP[x] pin is an output.
where x represents one of the 15 through 0 GPIO pins.
Figure 10-1 shows the GPIO enable bits in the GPEN register for the C6713/13B device. To use any of
the GPx pins as general-purpose input/output functions, the corresponding GPxEN bit must be set to 1
(enabled). Default values are device-specific, so refer to Figure 10-1 for the C6713/13B default
configuration.
31242316
Reserved
R-0
15141312111098
GP15ENGP14ENGP13ENGP12ENGP11ENGP10ENGP9ENGP8EN
R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0
76543210
GP7ENGP6ENGP5ENGP4ENGP3ENGP2ENGP1ENGP0EN
R/W-1R/W-1R/W-1R/W-1R/W-0R/W-0R/W-0R/W-0
Legend: R/W = Readable/Writeable; -n = value after reset, -x = undefined value after reset
Figure 10-2 shows the GPIO direction bits in the GPIO Direction (GPDIR) register. This register
determines if a given GPIO pin is an input or an output providing the corresponding GPxEN bit is enabled
(set to 1) in the GPEN register. By default, all the GPIO pins are configured as input pins.
For more detailed information on general-purpose inputs/outputs (GPIOs), see the TMS320C6000 DSP
General-Purpose Input/Output (GPIO) Reference Guide (literature number SPRU584).
10.2 Power-Down Mode Logic
Figure 10-3 shows the power-down mode logic on the C6713/13B.
SGUS049K–AUGUST 2003– REVISED APRIL 2011
A.External input clocks, with the exception of CLKIN and CLKOUT3, are not gated by the power-down mode logic.
Figure 10-3. Power-Down Mode Logic
10.2.1 Triggering, Wake-Up, and Effects
The device includes a programmable PLL which allows software control of PLL bypass via the PLLEN bit
in the PLLCSR register. With this enhanced functionality come some additional considerations when
entering power-down modes.
The power-down modes (PD2 and PD3) function by disabling the PLL to stop clocks to the C6713 device.
However, if the PLL is bypassed (PLLEN = 0), the device will still receive clocks from the external clock
input (CLKIN). Therefore, bypassing the PLL makes the power-down modes PD2 and PD3 ineffective.
The PLL needs to be enabled by writing a “1” to PLLEN bit (PLLCSR.0) before being able to enter either
PD3 (CSR.11) or PD2 (CSR.10) in order for these modes to have an effect.
For the TMS320C6713B device it is recommended to use the PLLPWDN bit (PLLCSR.1) to enter a deep
power−down state equivalent to PD3 since the PLLPWDN bit takes full advantage of the PLL power−down
feature.
The power-down modes (PD1, PD2 and PD3) and their wake-up methods are programmed by setting the
PWRD field (bits 15−10) of the control status register (CSR). The PWRD field of the CSR is shown in
Figure 10-4 and described in Table 10-1. When writing to the CSR, all bits of the PWRD field should be
set at the same time. Logic 0 should be used when writing to the reserved bit (bit 15) of the PWRD field.
The CSR is discussed in detail in the TMS320C6000 CPU and Instruction Set Reference Guide (literature
number SPRU189).
A delay of up to nine clock cycles may occur after the instruction that sets the PWRD bits in the CSR
before the PD mode takes effect. As best practice, NOPs should be padded after the PWRD bits are set in
the CSR to account for this delay.
If PD1 mode is terminated by a non-enabled interrupt, the program execution returns to the instruction
where PD1 took effect. If PD1 mode is terminated by an enabled interrupt, the interrupt service routine will
be executed first, then the program execution returns to the instruction where PD1 took effect. In the case
with an enabled interrupt, the GIE bit in the CSR and the NMIE bit in the interrupt enable register (IER)
must also be set for the interrupt service routine to execute; otherwise, execution returns to the instruction
where PD1 took effect upon PD1 mode termination by an enabled interrupt.
PD2 and PD3 modes can only be aborted by device reset. Table 10-1 summarizes all the power-down
modes.
Table 10-1. Characteristics of the Power-Down Modes
PRWD FIELDPOWER-DOWN
(BITS 15−10)MODE
000000No power down——
001001PD1
010001PD1
011010PD2
011100PD3
All othersReserved——
(1) When entering PD2 and PD3, all functional I/Os remain in the previous state. However, for peripherals that are asynchronous in nature
or peripherals with an external clock source, output signals may transition in response to stimulus on the inputs. Under these conditions,
peripherals will not operate according to specifications.
(1)
(1)
WAKE-UP METHODEFFECT ON CHIP OPERATION
Wake by an enabledCPU halted (except for the interrupt logic)
interruptPower-down mode blocks the internal clock inputs at the
Wake by an enabled or
non-enabled interrupt
Wake by a device resethalted. All register and internal RAM contents are preserved.
Wake by a device reset
boundary of the CPU, preventing most of the CPU logic from
switching. During PD1, EDMA transactions can proceed
between peripherals and internal memory.
Output clock from PLL is halted, stopping the internal clock
structure from switching and resulting in the entire chip being
All functional I/O freeze in the last state when the PLL clock is
turned off.
Input clock to the PLL stops generating clocks. All register and
internal RAM contents are preserved. All functional I/O freeze
in the last state when the PLL clock is turned off. Following
reset, the PLL needs time to relock, just as it does following
power up. Wake-up from PD3 takes longer than wake-up from
PD2 because the PLL needs to be relocked, just as it does
following power up. It is recommended to use the PLLPWDN
bit (PLLCSR.1) as an alternative to PD3.
10.3 Power-Supply Sequencing
TI DSPs do not require specific power sequencing between the core supply and the I/O supply. However,
systems should be designed to ensure that neither supply is powered up for extended periods of time
(>1 second) if the other supply is below the proper operating voltage.
System-level design considerations, such as bus contention, may require supply sequencing to be
implemented. In this case, the core supply should be powered up before, and powered down after, the I/O
buffers. This is to ensure that the I/O buffers receive valid inputs from the core before the output buffers
are powered up, thus preventing bus contention with other chips on the board.
10.3.2 Power-Supply Design Considerations
A dual-power supply with simultaneous sequencing can be used to eliminate the delay between core and
I/O power up. A Schottky diode can also be used to tie the core rail to the I/O rail (see Figure 10-5).
SGUS049K–AUGUST 2003– REVISED APRIL 2011
Figure 10-5. Schottky Diode Diagram
Core and I/O supply voltage regulators should be located close to the DSP (or DSP array) to minimize
inductance and resistance in the power delivery path. Additionally, when designing for high-performance
applications utilizing the C6000 platform of DSPs, the printed circuit board (PCB) should include separate
power planes for core, I/O, and ground, all bypassed with high-quality low-ESL/ESR capacitors.
10.4 Power-Supply Decoupling
To properly decouple the supply planes from system noise, place as many capacitors (caps) as possible
close to the DSP. Assuming 0603 caps, the user should be able to fit a total of 60 caps—30 for the core
supply and 30 for the I/O supply. These caps need to be close (no more than 1.25-cm maximum distance)
to the DSP to be effective. Physically smaller caps are better, such as 0402, but the size needs to be
evaluated from a yield/manufacturing point-of-view. Parasitic inductance limits the effectiveness of the
decoupling capacitors; therefore, physically smaller capacitors should be used while maintaining the
largest available capacitance value. As with the selection of any component, verification of capacitor
availability over the product’s production lifetime needs to be considered.
10.5 IEEE Std 1149.1 JTAG Compatibility Statement
The 320C6713/13B DSP requires that both TRST and RESET resets be asserted upon power up to be
properly initialized. While RESET initializes the DSP core, TRST initializes the DSP emulation logic. Both
resets are required for proper operation.
NOTE
TRST is synchronous and must be clocked by TCLK; otherwise, BSCAN may not respond as
expected after TRST is asserted.
While both TRST and RESET need to be asserted upon power-up, only RESET needs to be released for
the DSP to boot properly. TRST may be asserted indefinitely for normal operation, keeping the JTAG port
interface and DSP emulation logic in the reset state.
TRST only needs to be released when it is necessary to use a JTAG controller to debug the DSP or
exercise the DSP boundary scan functionality.
The TMS320C6713B DSP includes an internal pulldown (IPD) on the TRST pin to ensure that TRST will
always be asserted upon power up and the DSP’s internal emulation logic will always be properly
initialized when this pin is not routed out. 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 an
external pullup resistor on TRST. When using this type of JTAG controller, assert TRST to initialize the
DSP after powerup and externally drive TRST high before attempting any emulation or boundary scan
operations.
Following the release of RESET, the low-to-high transition of TRST must be “seen” to latch the state of
EMU1 and EMU0. The EMU[1:0] pins configure the device for either boundary scan mode or emulation
mode. For more detailed information, see the terminal functions section of this data sheet.
Note: The DESIGN−WARNING section of the TMS320C6713B BSDL file contains
information and constraints regarding proper device operation while in boundary scan mode.
For more detailed information on the C6713B JTAG emulation, see the TMS320C6000 DSP Designing for
JTAG Emulation Reference Guide (literature number SPRU641).
www.ti.com
NOTE
10.6 EMIF Device Speed
The maximum EMIF speed on the C6713/13B device is 100 MHz. TI recommends utilizing I/O buffer
information specification (IBIS) to analyze all ac timings to determine if the maximum EMIF speed is
achievable for a given board layout. To properly use IBIS models to attain accurate timing analysis for a
given system, see the application report Using IBIS Models for Timing Analysis (literature number
SPRA839).
For ease of design evaluation, Table 10-2 contains IBIS simulation results showing the maximum
EMIF-SDRAM interface speeds for the given example boards (TYPE) and SDRAM speed grades. Timing
analysis should be performed to verify that all ac timings are met for the specified board layout. Other
configurations are also possible, but again, timing analysis must be done to verify proper ac timings.
To maintain signal integrity, serial termination resistors should be inserted into all EMIF output signal lines
(see the Terminal Functions table for the EMIF output signals).
200-MHz 32-bit SDRAM (−5)cannot meet EMIF input hold
MAXIMUM ACHIEVABLE
output hold time on these SDRAM
speed grades cannot meet EMIF
input hold time requirement.
For short traces, EMIF cannot
requirement.
For short traces, EMIF cannot
requirement.
SDRAM data output hold time
requirement.
(1)
(1)
(1)
(1)
10.7 EMIF Big Endian Mode Correctness (C6713B Only)
The HD8 pin device endian mode (LENDIAN) selects the endian mode of operation (Little or Big Endian).
For the C6713/13B device Little Endian is the default setting.
The C6713B HD12 pin (EMIF Big Endian Mode Correctness) [EMIFBE] enhancement allows the flexibility
to change the EMIF data placement on the EMIF bus.
When using the default setting of HD12 = 1 for the C6713B, the EMIF will present 8-bit or 16-bit data on
the ED[7:0] side of the bus if using Little Endian mode (HD8 = 1), and to the ED[31:24] side of the bus if
using Big Endian mode. Figure 10-6 shows the mapping of 16-bit and 8-bit C6713B devices.
When HD12 = 0 for the C6713B, enabling EMIF endianness correction, the EMIF will present 8-bit or
16-bit data on the ED[7:0] side of the bus, regardless of the endianess mode (see Figure 10-7)
This new C6713B endianness correction functionality does not affect systems using the default value of
HD12 = 1.
This new C6713B feature does not affect systems operating in Little Endian mode.
10.8 Bootmode
The C6713/13B device resets using the active-low signal RESET and the internal reset signal. While
RESET is low, the internal reset is also asserted and the device is held in reset and is initialized to the
prescribed reset state. Refer to Reset Timing for reset timing characteristics and states of device pins
during reset. The release of the internal reset signal (see the Reset phase 3 discussion in the RESET
Timing section of this data sheet) starts the processor running with the prescribed device configuration
and boot mode.
www.ti.com
32-Bit Device in Any Endianness Mode
16-Bit Device in Any Endianness Mode
8-Bit Device in
Any Endianness Mode
The C6713/13B has three types of boot modes:
•Host boot
If host boot is selected, upon release of internal reset, the CPU is internally stalled while the remainder
of the device is released. During this period, an external host can initialize the CPU memory space as
necessary through the host interface, including internal configuration registers, such as those that
control the EMIF or other peripherals. Once the host is finished with all necessary initialization, it must
set the DSPINT bit in the HPIC register to complete the boot process. This transition causes the boot
configuration logic to bring the CPU out of the stalled state. The CPU then begins execution from
address 0. The DSPINT condition is not latched by the CPU, because it occurs while the CPU is still
internally stalled. Also, DSPINT brings the CPU out of the stalled state only if the host boot process is
selected. All memory may be written to and read by the host. This allows for the host to verify what it
sends to the DSP if required. After the CPU is out of the stalled state , the CPU needs to clear the
DSPINT; otherwise, no more DSPINTs can be received.
•Emulation boot
Emulation boot mode is a variation of host boot. In this mode, it is not necessary for a host to load
code or to set DSPINT to release the CPU from the stalled state. Instead, the emulator will set DSPINT
if it has not been previously set so that the CPU can begin executing code from address 0. Before
beginning execution, the emulator sets a breakpoint at address 0. This prevents the execution of
invalid code by halting the CPU before executing the first instruction. Emulation boot is a good tool in
the debug phase of development.
•EMIF boot (using default ROM timings)
Upon the release of internal reset, the 1K-Byte ROM code located in the beginning of CE1 is copied to
address 0 by the EDMA using the default ROM timings, while the CPU is internally stalled. The data
should be stored in the endian format that the system is using. The boot process also lets you choose
the width of the ROM. In this case, the EMIF automatically assembles consecutive 8-bit bytes or 16-bit
half-words to form the 32-bit instruction words to be copied. The transfer is automatically done by the
EDMA as a single-frame block transfer from the ROM to address 0. After completion of the block
transfer, the CPU is released from the stalled state and start running from address 0.
over operating case temperature range (unless otherwise noted)
Supply voltage range, CV
Supply voltage range, DV
Input voltage range−0.3 to DVDD+ 0.5V
Output voltage range−0.3 to DVDD+ 0.5V
Operating case temperature range T
Storage temperature range, T
(1) Stresses beyond those listed under absolute maximum ratings may cause permanent damage to the device. These are stress ratings
only, and functional operation of the device at these or any other conditions beyond those indicated under recommended operating
conditions is not implied. Exposure to absolute-maximum-rated conditions for extended periods may affect device reliability.
(2) All voltage values are with respect to VSS.
(3) Long-term high temperature storage and/or extended use at maximum recommended operating conditions may result in a reduction of
overall device life. See http://ti.com/ep_quality for additional information on enhanced product packaging.
DD
DD
(2)
(2)
C
stg
11.2 Recommended Operating Conditions
CV
DV
V
(C – D)
V
(D – C)
V
IH
V
IL
I
OH
I
OL
V
OS
Supply voltage,
DD
core referenced to V
Supply voltage, I/O referenced to V
DD
SS
Maximum supply voltage difference, CVDD− DV
Maximum supply voltage difference, DVDD− CV
High-level
input voltage
Low-level
input voltage
(2)
C6713
High-level
outputmA
current
C6713B
C6713
(2)
(2)
Low-level
outputmA
current
C6713B
(2)
Maximum voltage during overshoot (See Figure 11-4)4
All signals except CLKS1/SCL1, DR1/SDA1, SCL0, SDA0, and
RESET
3.133.33.47V
1.32V
2.75V
2
CLKS1/SCL1, DR1/SDA1, SCL0, SDA0, and RESET2
All signals except CLKS1/SCL1, DR1/SDA1, SCL0, SDA0, and0.8
RESET
CLKS1/SCL1, DR1/SDA1, SCL0, SDA0, and RESET0.3 ×
DV
DD
All signals except ECLKOUT, CLKOUT2, CLKOUT3,
CLKS1/SCL1, DR1/SDA1, SCL0, and SDA0
–8
ECLKOUT, CLKOUT2, and CLKOUT3–16
All signals except ECLKOUT, CLKOUT2, CLKS1/SCL1,
DR1/SDA1, SCL0, and SDA0
–8
ECLKOUT and CLKOUT2–16
All signals except ECLKOUT, CLKOUT2, CLKOUT3,
CLKS1/SCL1, DR1/SDA1, SCL0, and SDA0
ECLKOUT, CLKOUT2, and CLKOUT316
CLKS1/SCL1, DR1/SDA1, SCL0, and SDA03
All signals except ECLKOUT, CLKOUT2, CLKS1/SCL1,
DR1/SDA1, SCL0, and SDA0
ECLKOUT and CLKOUT216
CLKS1/SCL1, DR1/SDA1, SCL0, and SDA03
°C
V
V
V
8
8
(3)
V
(1) The core supply should be powered up before, and powered down after, the I/O supply. Systems should be designed to ensure that
neither supply is powered up for an extended period of time if the other supply is below the proper operating voltage.
(2) Refers to dc (or steady state) currents only; actual switching currents are higher. For more details, see the device-specific IBIS models.
(3) The absolute maximum ratings should not be exceeded for more than 30% of the cycle period.
Maximum voltage during undershoot (See Figure 11-5)–0.7
(3)
A version–40105
T
C
Operating case temperatureS version–55105°C
M version–55125
11.3 Electrical Characteristics
(1)
over recommended ranges of supply voltage and operating case temperature (unless otherwise noted)
PARAMETERTEST CONDITIONSMINTYPMAXUNIT
High-level outputAll signals except SCL1, SDA1,
V
OH
voltageSCL0, and SDA0
Low-level output
V
OL
voltage
All signals except SCL1, SDA1,
SCL0, and SDA0
SCL1, SDA1, SCL0, and SDA0IOL= MAX0.4
All signals except SCL1, SDA1,
I
Input currentVI= VSSto DV
I
SCL0, and SDA0
SCL1, SDA1, SCL0, and SDA0±10
All signals except SCL1, SDA1,
I
Off-state output currentVO= DVDDor 0 VμA
OZ
SCL0, and SDA0
SCL1, SDA1, SCL0, and SDA0±10
I
Core supply current
DD2V
I
I/O supply current
DD3V
(2)
(2)
CIInput capacitance7pF
CoOutput capacitance7pF
(1) For test conditions shown as MIN, MAX, or NOM, use the appropriate value specified in the recommended operating conditions table.
(2) Measured with average activity (50% high/50% low power) at 25°C case temperature and 100-MHz EMIF. This model represents a
device performing high-DSP-activity operations 50% of the time, and the remainder performing low-DSP-activity operations. The
high/low-DSP-activity models are defined as follows:
• High DSP activity model:
• CPU: 8 instructions/cycle with 2 LDDW instructions [L1 data memory: 128 bits/cycle via LDDW instructions; L1 program memory:
11.4.4 Timing Parameters and Board Routing Analysis
The timing parameter values specified in this data sheet do not include delays by board routings. As a good
board design practice, such delays must always be taken into account. Timing values may be adjusted by
increasing/decreasing such delays. TI recommends utilizing the available I/O buffer information specification
(IBIS) models to analyze the timing characteristics correctly. To properly use IBIS models to attain accurate
timing analysis for a given system, see the Using IBIS Models for Timing Analysis application report (literature
number SPRA839). If needed, external logic hardware such as buffers may be used to compensate any timing
differences.
For inputs, timing is most impacted by the round-trip propagation delay from the DSP to the external device and
from the external device to the DSP. This round-trip delay tends to negatively impact the input setup time margin,
but also tends to improve the input hold time margins (see Table 11-1 and Figure 11-6).
Figure 11-6 represents a general transfer between the DSP and an external device. The figure also represents
board route delays and how they are perceived by the DSP and the external device.
Table 11-1. Board-Level Timings Example (see
Figure 11-6)
NO.DESCRIPTION
1Clock route delay
2Minimum DSP hold time
3Minimum DSP setup time
4External device hold time requirement
5External device setup time requirement
6Control signal route delay
7External device hold time
8External device access time
9DSP hold time requirement
10DSP setup time requirement
11Data route delay
(1) The reference points for the rise and fall transitions are measured at VILMAX and VIHMIN.
(2) C = CLKIN cycle time in nanoseconds (ns). For example, when CLKIN frequency is 40 MHz, use C = 25 ns.
(3) See the PLL and PLL Controller section of this data sheet.
over recommended operating conditions (see Figure 11-8)
NO.PARAMETERMINMAXUNIT
1t
2t
3t
4t
(1) The reference points for the rise and fall transitions are measured at VOLMAX and VOHMIN.
(2) C2 = CLKOUT2 period in ns. CLKOUT2 period is determined by the PLL controller output SYSCLK2 period, which must be set to CPU
(1) The reference points for the rise and fall transitions are measured at VOLMAX and VOHMIN.
(2) C3 = CLKOUT3 period in ns. CLKOUT3 period is a divide-down of the CPU clock, configurable via the RATIO field in the PLLDIV3
register.
67136713B
MINMAXMINMAX
Figure 11-9. CLKOUT3
Table 11-5. Timing Requirements for ECLKIN
(1)
See Figure 11-10
NO.MINMAXUNIT
1t
2t
3t
4t
c(EKI)
w(EKIH)
w(EKIL)
t(EKI)
Cycle time, ECLKIN10ns
Pulse duration, ECLKIN high4.5ns
Pulse duration, ECLKIN low4.5ns
Transition time, ECLKIN3ns
(1) The reference points for the rise and fall transitions are measured at VILMAX and VIHMIN.
over recommended operating conditions (see Figure 11-11)
NO.PARAMETERMINMAXUNIT
1t
2t
3t
4t
5t
6t
(1) The reference points for the rise and fall transitions are measured at VOLMAX and VOHMIN.
(2) E = ECLKIN period in ns
(3) EH is the high period of ECLKIN in ns and EL is the low period of ECLKIN in ns.
c (EKO)
w (EKOH)
w (EKOL)
t (EKO)
d (EKIH-EKOH)
d (EKIL-EKOL)
Cycle time, ECLKOUTE – 0.9E + 0.9ns
Pulse duration, ECLKOUT highEH – 0.9EH + 0.9ns
Pulse duration, ECLKOUT lowEL – 0.9EL + 0.9ns
Transition time, ECLKOUT2ns
Delay time, ECLKIN high to ECLKOUT high16.5ns
Delay time, ECLKIN low to ECLKOUT low16.5ns
(1) To ensure data setup time, simply program the strobe width wide enough. ARDY is internally synchronized. The ARDY signal is
recognized in the cycle for which the setup and hold time is met. To use ARDY as an asynchronous input, the pulse width of the ARDY
signal should be wide enough (for example, pulse width = 2E) to ensure setup and hold time is met.
are programmed via the EMIF CE space control registers.
(3) E = ECLKOUT period in ns
Setup time, EDx valid before ARE high6.5ns
Hold time, EDx valid after ARE high1ns
Setup time, ARDY valid before ECLKOUT high3ns
ARDY valid after ECLKOUT high2.3ns
Table 11-8. Switching Characteristics for Asynchronous Memory Cycles
over recommended operating condition (see Figure 11-12 and Figure 11-13)
are programmed via the EMIF CE space control registers.
(2) E = ECLKOUT period in ns
(3) Select signals include CEx, BE[3:0], EA[21:2], and AOE.
Output setup time, select signals valid to ARE lowRS*E – 1.7ns
Output hold time, ARE high to select signals invalidRH*E – 1.7ns
Delay time, ECLKOUT high to ARE valid1.57ns
Output setup time, select signals valid to AWE lowWS*E – 1.7ns
Output hold time, AWE high to select signals and EDx invalidWH*E – 1.7ns
Delay time, ECLKOUT high to AWE valid1.57ns
Output setup time, ED valid to AWE low(WS – 1)*E – 1.7ns
Table 11-9. Timing Requirements for Synchronous-Burst SRAM Cycles
See Figure 11-14
NO.MINMAXUNIT
6t
7t
su(EDV-EKOH)
h(EKOH-EDV)
(1) The C6713/13B SBSRAM interface takes advantage of the internal burst counter in the SBSRAM. Accesses default to incrementing
4-word bursts, but random bursts and decrementing bursts are done by interrupting bursts in progress. All burst types can sustain
continuous data flow.
Setup time, read EDx valid before ECLKOUT high1.5ns
Hold time, read EDx valid after ECLKOUT high2.5ns
Table 11-10. Switching Characteristics for Synchronous-Burst SRAM Cycles
over recommended operating conditions (see Figure 11-14 and Figure 11-15)
NO.PARAMETERMINMAXUNIT
1t
d (EKOH-CEV)
2t
d (EKOH-BEV)
3t
d (EKOH-BEIV)
4t
d (EKOH-EAV)
5t
d (EKOH-EAIV)
8t
d (EKOH-ADSV)
9t
d (EKOH-OEV)
10t
11t
12t
d (EKOH-EDV)
d (EKOH-EDIV)
d (EKOH-WEV)
(1) The C6713/13B SBSRAM interface takes advantage of the internal burst counter in the SBSRAM. Accesses default to incrementing
4-word bursts, but random bursts and decrementing bursts are done by interrupting bursts in progress. All burst types can sustain
continuous data flow.
(2) ARE/SDCAS/SSADS, AOE/SDRAS/SSOE, and AWE/SDWE/SSWE operate as SSADS, SSOE, and SSWE, respectively, during
SBSRAM accesses.
Delay time, ECLKOUT high to CEx valid1.27ns
Delay time, ECLKOUT high to BEx valid7ns
Delay time, ECLKOUT high to BEx invalid1.2ns
Delay time, ECLKOUT high to EAx valid7ns
Delay time, ECLKOUT high to EAx invalid1.2ns
Delay time, ECLKOUT high to ARE/SDCAS/SSADS valid1.27ns
Delay time, ECLKOUT high to AOE/SDRAS/SSOE valid1.27ns
Delay time, ECLKOUT high to EDx valid7ns
Delay time, ECLKOUT high to EDx invalid1.2ns
Delay time, ECLKOUT high to AWE/SDWE/SSWE valid1.27ns