The Tiva™ C Series TM4C1294 Connected LaunchPad Evaluation Board (EK-TM4C1294XL) is a low-cost
evaluation platform for ARM® Cortex™-M4F-based microcontrollers. The Connected LaunchPad design
highlights the TM4C1294NCPDT microcontroller with its on-chip 10/100 Ethernet MAC and PHY, USB 2.0,
hibernation module, motion control pulse-width modulation and a multitude of simultaneous serial
connectivity. The Connected LaunchPad also features two user switches, four user LEDs, dedicated reset
and wake switches, a breadboard expansion option and two independent BoosterPack XL expansion
connectors. The pre-programmed quickstart application on the Connected LaunchPad also enables
remote monitoring and control of the evaluation board from an internet browser anywhere in the world.
The web interface is provided by 3rd party, Exosite. Each Connected LaunchPad is enabled on the
Exosite platform allowing users to create and customize their own Internet-of-Things applications.
Figure 1-1 shows a photo of the Connected LaunchPad with key features highlighted.
Figure 1-1. Tiva C Series Connected LaunchPad Evaluation Board
Tiva is a trademark of Texas Instruments.
All other trademarks are the property of their respective owners.
4
Board OverviewSPMU365A–March 2014–Revised March 2014
The Connected LaunchPad Evaluation Kit contains the following items:
•Tiva™ C Series TM4C1294 Evaluation Board (EK-TM4C1294XL)
•Retractable Ethernet cable
•USB Micro-B plug to USB-A plug cable
•README First document
1.2Using the Connected LaunchPad
The recommended steps for using the Connected LaunchPad Evaluation Kit are:
1. Follow the README First document included in the kit. The README First helps you get the
Connected LaunchPad up and running in minutes. Within just a few minutes you can be controlling and
monitoring the Connected LaunchPad through the internet using Exosite and the pre-programmed
quickstart application.
2. Experiment with BoosterPacks. This evaluation kit conforms to the latest revision of the BoosterPack
pinout standard. It has two independent BoosterPack connections to enable a multitude of expansion
opportunities.
3. Take the first step towards developing your own applications. The Connected LaunchPad is
supported by TivaWare for C Series. After installing TivaWare, look in the installation directory for
examples\boards\ek-tm4c1294xl. You can find pre-configured example applications for this board as
well as for this board with selected BoosterPacks. Alternately, use Energīa for a wiring frameworkbased cross-platform, fast-prototyping environment that works with this and other TI LaunchPads. See
Chapter 3 of this document for more details about software development. TivaWare can be
downloaded from the TI website at http://www.ti.com/tool/sw-tm4c. Energīa can be found at
http://energia.nu.
4. Customize and integrate the hardware to suit your end application. This evaluation kit can be
used as a reference for building your own custom circuits based on Tiva C microcontrollers or as a
foundation for expansion with your custom BoosterPack or other circuit. This manual can serve as a
starting point for this endeavor.
5. Get Trained. You can also download hours of written and video training materials on this and related
LaunchPads. Visit the Tiva C Series LaunchPad Workshop Wiki for more information.
6. More Resources. See the TI MCU LaunchPad web page for more information and available
BoosterPacks. (http://www.ti.com/tiva-c-launchpad)
Kit Contents
1.3Features
Your Connected LaunchPad includes the following features:
•Tiva TM4C1294NCPDTI microcontroller
•Ethernet connectivity with fully integrated 10/100 Ethernet MAC and PHY Motion Control PWM
•USB 2.0 Micro A/B connector
•4 user LEDs
•2 user buttons
•1 independent hibernate wake switch
•1 independent microcontroller reset switch
•Jumper for selecting power source:
– ICDI USB
– USB Device
– BoosterPack
– For a complete list of BoosterPacks, see the TI MCU LaunchPad web page:
http://www.ti.com/launchpad
1.4BoosterPacks
The Connected LaunchPad provides an easy and inexpensive way to develop applications with the
TM4C1294NCPDTI microcontroller. BoosterPacks are add-on boards that follow a pin-out standard
created by Texas Instruments. The TI and third-party ecosystem of BoosterPacks greatly expands the
peripherals and potential applications that you can easily explore with the Connected LaunchPad.
You can also build your own BoosterPack by following the design guidelines on TI’s website. Texas
Instruments even helps you promote your BoosterPack to other members of the community. TI offers a
variety of avenues for you to reach potential customers with your solutions.
1.5Energīa
Energīa is an open-source electronics prototyping platform started in January of 2012 with the goal of
bringing the Wiring and Arduino framework to the TI LaunchPad community. Energīa includes an
integrated development environment (IDE) that is based on Processing.
Together with Energīa, LaunchPads can be used to develop interactive objects, taking inputs from a
variety of switches or sensors, and controlling a variety of lights, motors, and other physical outputs.
LaunchPad projects can be stand-alone (only run on the target board, i.e. your LaunchPad), or they can
communicate with software running on your computer (Host PC). Energīa projects are highly portable
between supported LaunchPad platforms. Projects written for your Connected LaunchPad can be run on
other LaunchPads with little or no modifications.
More information is available at http://energia.nu.
www.ti.com
1.6Specifications
Table 1-1 summarizes the specifications for the Connected LaunchPad.
ParameterValue
Board Supply Voltage
Dimensions4.9 in x 2.2 in x .425 in (12.45 cm x 5.59 cm x 10.8 mm) (L x W x H)
Break-out Power Output
RoHS StatusCompliant
Table 1-1. EK-TM4C1294XL Specifications
4.75 VDCto 5.25 VDCfrom one of the following sources:
• Debug USB U22 (ICDI) USB Micro-B cable connected to PC or other compatible
power source.
• Target USB (U7) USB Micro-B cable connected to PC or other compatible power
source.
• BoosterPack 1 (X8-4)
• BoosterPack 2 (X6-4)
• Breadboard expansion header (X11-2 or X11-97).
See schematic symbol JP1 for power input selection.
• 5 VDCto BoosterPacks, current limited by TPS2052B. Nominal rating 1 Amp.
Board input power supply limitations may also apply.
• 3.3 VDCto BoosterPacks, limited by output of TPS73733 LDO. This 3.3-V plane is
shared with on-board components. Total output power limit of TPS73733 is 1
Amp.
6
Board OverviewSPMU365A–March 2014–Revised March 2014
The Connected LaunchPad includes a TM4C1294NCPDTI microcontroller with an integrated 10/100
Ethernet MAC and PHY. This advanced ARM® Cortex™ M4F MCU has a wide range of peripherals that
are made available to users via the on-board accessories and the BoosterPack connectors. This chapter
explains how those peripherals operate and interface to the microcontroller.
Figure 2-1 provides a high-level block diagram of the Connected LaunchPad.
The TM4C1294NCPDTI is a 32-bit ARM Cortex-M4F based microcontroller with 1024-kB Flash memory,
256-kB SRAM, 6-kB EEPROM, and 120 MHz operation; integrated 10/100 Ethernet MAC and PHY;
integrated USB 2.0 connectivity with external high-speed USB 3.0 PHY capability; a hibernation module, a
multitude of serial connectivity and motion control PWM; as well as a wide range of other peripherals. See
the TM4C1294NCPDTI microcontroller data sheet for more complete details.
Most of the microcontroller’s signals are routed to 0.1-in (2.54-mm) pitch headers or through-hole solder
pads. An internal multiplexor allows different peripheral functions to be assigned to each of these GPIO
pads. When adding external circuitry, consider the additional load on the evaluation board power rails.
The TM4C1294NCPDTI microcontroller is factory-programmed with a quickstart demo program. The
quickstart program resides in on-chip Flash memory and runs each time power is applied, unless the
quickstart application has been replaced with a user program. The quickstart application automatically
connects to http://ti.exosite.com when an internet connection is provided through the RJ45 Ethernet jack
on the evaluation board.
SPMU365A–March 2014–Revised March 2014Hardware Description
The Connected LaunchPad is designed to connect directly to an Ethernet network using RJ45 style
connectors. The microcontroller contains a fully integrated Ethernet MAC and PHY. This integration
creates a simple, elegant and cost-saving Ethernet circuit design. Example code is available for both the
uIP and LwIP TCP/IP protocol stacks. The embedded Ethernet on this device can be programmed to act
as an HTTP server, client or both. The design and integration of the circuit and microcontroller also enable
users to synchronize events over the network using the IEEE1588 precision time protocol.
When configured for Ethernet operation, it is recommended that the user configure LED D3 and D4 to be
controlled by the Ethernet MAC to indicate connection and transmit/receive status.
2.1.3 USB Connectivity
The Connected LaunchPad is designed to be USB 2.0 ready. A TPS2052B load switch is connected to
and controlled by the microcontroller USB peripheral, which manages power to the USB micro A/B
connector when functioning in a USB host. When functioning as a USB device, the entire Connected
LaunchPad can be powered directly from the USB micro A/B connector. Use JP1 to select the desired
power source.
USB 2.0 functionality is provided and supported directly out of the box with the target USB micro A/B
connector. High-speed USB 3.0 functionality can be enabled by adding an external USB PHY. The USB
external PHY control and data signals are provided on the breadboard expansion header X11.
2.1.4 Motion Control
The Connected LaunchPad includes the Tiva C Series Motion Control PWM technology, featuring a PWM
module capable of generating eight PWM outputs. The PWM module provides a great deal of flexibility
and can generate simple PWM signals – for example, those required by a simple charge pump – as well
as paired PWM signals with dead-band delays, such as those required by a half-H bridge driver. Three
generator blocks can also generate the full six channels of gate controls required by a 3-phase inverter
bridge.
A quadrature encoder interface (QEI) is also available to provide motion control feedback.
See the BoosterPacks and Headers section of this document for details about the availability of these
signals on the BoosterPack interfaces.
www.ti.com
2.1.5 User Switches and LED's
Two user switches are provided for input and control of the TM4C1294NCPDTI software. The switches
are connected to GPIO pins PJ0 and PJ1.
A reset switch and a wake switch are also provided. The reset switch initiates a system reset of the
microcontroller whenever it is pressed and released. Pressing the reset switch also asserts the reset
signal to the BoosterPack and Breadboard headers. The wake switch is one way to bring the device out of
hibernate mode.
Four user LEDs are provided on the board. D1 and D2 are connected to GPIOs PN1 and PN0. These
LEDs are dedicated for use by the software application. D3 and D4 are connected to GPIOs PF4 and
PF0, which can be controlled by user’s software or the integrated Ethernet module of the microcontroller.
A power LED is also provided to indicate that 3.3 volt power is present on the board.
8
Hardware DescriptionSPMU365A–March 2014–Revised March 2014
The Connected LaunchPad features two fully independent BoosterPack XL connectors. BoosterPack 1, located around the ICDI portion of the
board, is fully compliant with the BoosterPack standard with the single exception of GPIO pin PA6 (X8-16), which does not provide analog
capability. PA6 is located near the bottom of the inner left BoosterPack XL header.
I2C is provided in both the original BoosterPack standard configuration as well as the updated standard location. Use of I2C on the bottom left of
the BoosterPack connections per the updated standard is highly encouraged whenever possible.
Motion control advanced PWM connections are provided on the inner right connector for motion control applications.
Table 2-1 provides a complete listing of the BoosterPack pins and the GPIO alternate functions available on each pin. The TM4C1294NCPDTI
GPIO register GPIOPCTL values are shown for each configuration. The headers in this table are labeled from left to right in ten pin columns. ‘A’
and ‘D’ make up the outer BoosterPack standard pins, ‘B’ and ‘C’ make up the inner BoosterPack XL standard pins.
The second BoosterPack XL interface is located near the middle of the board. This interface is fully compliant with the BoosterPack standard, and
adds features not covered by the BoosterPack standard that enable operation with additional BoosterPacks.
An additional analog signal is provided on the outer left header (X6-9). This signal can be used to monitor the touch panel on the popular Kentec
EB-LM4F120-L35 BoosterPack.
Using the jumpers JP4 and JP5, Controller Area Network (CAN) digital receive and transmit signals can be optionally routed to the BoosterPack 2
interface. The location of these signals is consistent with the CAN interface on the Tiva C Series TM4C123G LaunchPad and the Stellaris
LM4F120 LaunchPad. In the default configuration, UART0 is used for the ICDI virtual UART and CAN is not present on the BoosterPack headers.
In this configuration, the ROM serial bootloader can be used over the ICDI virtual UART. When the jumpers are configured for CAN on the
BoosterPack, then UART4 must be used for the ICDI virtual UART.
To comply with both the original and the new BoosterPack standard, I2C is provided on both sides of the BoosterPack connection. Use of I2C on
the bottom left of the BoosterPack connection is highly encouraged where possible, to be in compliance with the new BoosterPack standard. To
provide I2C capability on the right side of the connector, per the original standard, two zero-ohm resistors (R19 and R20) are used to combine the
SPI and I2C signals. These signals are not shared with any other pins on the LaunchPad and therefore removal of these zero-ohm resistors
should not be required. Software should be certain that unused GPIO signals are configured as inputs.
Table 2-2 provides a complete listing of the BoosterPack pins and the GPIO alternate functions available at each pin. The TM4C1294NCPDT
GPIO register GPIOPCTL values are shown for each configuration. The headers in this table are labeled from left to right in ten pin columns. ‘A’
and ‘D’ make up the outer BoosterPack standard pins, ‘B’ and ‘C’ make up the inner BoosterPack XL standard pins.
The breadboard adapter section of the board is a set of 98 holes on a 0.1 inch grid. Properly combined with a pair of right angle headers, the
entire Connected LaunchPad can be plugged directly into a standard 300 mil (0.3 inch) wide solder-less breadboard. The right angle headers and
breadboard are not provided with this kit. Suggested part numbers are Samtec TSW-149-09-L-S-RE and TSW-149-08-L-S-RA right angle pin
headers and Twin industries TW-E40-1020 solder-less breadboard. Samtec TSW-149-09-F-S-RE and TSW-149-09-F-S-RA may be substituted.
A detailed explanation of how to install the headers is available on the TI LaunchPad Wiki or at
Nearly all microcontroller signals are made available at the breadboard adapter holes (X11). These signals are grouped by function where
possible. For example, all EPI signals are grouped on one side of the connector. Many of the analog signals are grouped near VREF, and UART,
SSI and I2C signals are grouped by peripheral to make expansion and customization simpler.
Table 2-3 and Table 2-4 show the GPIO pin and signal muxing for the X11 breadboard adapter pads.
Table 2-3. X11 Breadboard Adapter Odd-Numbered Pad GPIO and Signal Muxing
JP1 is provided to select the power input source for the Connected LaunchPad. The top position is for
BoosterPack power; this position also disconnects both USB voltages from the board’s primary 5-volt
input. In the top position, the TPS2052B does not limit current so additional care should be exercised. The
middle position draws power from the USB connector on the left side of the board near the Ethernet jack.
The bottom position is the default, in which power is drawn from the ICDI (Debug) USB connection.
JP2 separates the MCU 3.3-volt power domain from the rest of the 3.3-volt power on the board allowing
an ammeter to be used to obtain more accurate measurements of microcontroller power consumption.
JP3 isolates the output of the TPS73733 LDO from the board’s 3.3-V power domain.
JP4 and JP5 are used to configure CAN signals to the BoosterPack 2 interface. In the default horizontal
configuration, CAN is not present on the BoosterPack. UART 4 goes to the BoosterPack and UART 0
goes to the ICDI virtual serial port to provide ROM serial bootloader capability. In the vertical CAN-enabled
configuration, UART 4 goes to the ICDI virtual serial port and CAN signals are available on the
BoosterPack. The ROM serial bootloader is not available to the ICDI virtual serial port while the jumpers
are in the CAN position.
Figure 2-2 shows the default configuration and relative location of the jumpers on the board.
Power Management
2.2Power Management
2.2.1 Power Supplies
The Connected LaunchPad can be powered from three different input options:
•On-board ICDI USB cable (Debug, Default)
•Target USB cable
•BoosterPack or Breadboard adapter connection
The JP1 power-select jumper is used to select one of the power sources.
In addition, the JP3 power jumper can be used to isolate the 3.3-volt output of the TPS73733 from the
board’s 3.3-volt rail.
A TPS2052B load switch is used to regulate and control power to the Target USB connector when the
microcontroller is acting in USB host mode. This load switch also limits current to the BoosterPack and
Breadboard adapter headers when the JP1 jumper is in the ICDI position.
SPMU365A–March 2014–Revised March 2014Hardware Description
The Connected LaunchPad demonstrates several low power microcontroller modes. In run mode, the
microcontroller can be clocked from several sources such as the internal precision oscillator or an external
crystal oscillator. Either of these sources can then optionally drive an internal PLL to increase the effective
frequency of the system up to 120 MHz. In this way, the run mode clock speed can be used to manage
run mode current consumption.
The microcontroller also provides sleep and deep sleep modes and internal voltage adjustments to the
flash and SRAM to further refine power consumption when the processor is not in use but peripherals
must remain active. Each peripheral can be individually clock gated in these modes so that current
consumption by unused peripherals is minimized. A wide variety of conditions from internal and external
sources can trigger a return to run mode.
The lowest power setting of the microcontroller is hibernation, which requires a small amount of supporting
external circuitry available on the Connected LaunchPad. The Connected LaunchPad can achieve
microcontroller current consumption modes under 2 micro-Amps using hibernate VDD3ON mode.
Hibernation with VDD3ON mode is not supported on this board. The Connected LaunchPad can be woken
from hibernate by several triggers including the dedicated wake button, the reset button, an internal RTC
timer and a subset of the device GPIO pins. The hibernation module provides a small area of internal
SRAM that can preserve data through a hibernate cycle.
2.2.3 Clocking
The Connected LaunchPad uses a 25 MHz crystal (Y1) to drive the main TM4C1294NCPDTI internal
clock circuit. Most software examples use the internal PLL to multiply this clock to higher frequencies up to
120 MHz for core and peripheral timing. The 25-MHz crystal is required when using the integrated
Ethernet MAC and PHY.
The Hibernation module is clocked from an external 32.768-KHz crystal (Y3).
www.ti.com
2.2.4 Reset
The RESET signal to the TM4C1294NCPDTI microcontroller connects to the RESET switch, BoosterPack
connectors, Breadboard adapter and to the ICDI circuit for a debugger-controller reset.
External reset is asserted (active low) under the following conditions:
•Power-on reset (filtered by and R-C network)
•RESET switch is held down.
•By the ICDI circuit when instructed by the debugger (this capability is optional, and may not be
supported by all debuggers)
•By an external circuit attached to the BoosterPack or Breadboard connectors.
2.3Debug Interface
2.3.1 In-Circuit Debug Interface (ICDI)
The Connected LaunchPad comes with an on-board ICDI. The ICDI allows for the programming and
debugging of the TM4C1294NCPDTI using LM Flash Programmer and/or any of the supported tool
chains. Note that ICDI only supports JTAG debugging at this time. It is possible to use other JTAG
emulators instead of the on board ICDI, by connecting to U6. When the ICDI detects an external debug
adapter connection on the JTAG connector U6 and disables the ICDI outputs to allow the external debug
adapter to drive the debug circuit. For more information, see Section 2.3.2.
Debug out of the ICDI is possible by removing resistors R6, R7, R8, R10, R11, R15, R16 and R40 from
the Connected LaunchPad and use the ICDI to drive JTAG signals out on U6 for the purpose of
programming or debugging other boards. To restore the connection to the on-board TM4C1294NCPDTI
microcontroller, install jumpers from the odd to even pins of X1 or re-install the resistors. Removal of R40
disables the detection of an attached external debugger. R40 must be installed to use an external debug
adapter to program or debug the Connected LaunchPad.
18
Hardware DescriptionSPMU365A–March 2014–Revised March 2014
The connector U6 is provided for the attachment of an external debug adapter such as the IAR J-Link or
Keil ULINK. This connector follows the ARM standard 10-pin JTAG pinout. This interface can use either
JTAG or SWD if supported by the external debug adapter.
2.3.3 Virtual COM Port
When plugged into a USB host, the ICDI enumerates as both a debugger and a virtual COM port. JP4 and
JP5 control the selection of which UART from the TM4C1294NCPDTI is connected to the virtual COM
port. In the default configuration, UART0 maps to the virtual COM port of the ICDI. In the CAN jumper
configuration, UART4 maps to the virtual COM port of the ICDI.
Debug Interface
SPMU365A–March 2014–Revised March 2014Hardware Description
This chapter provides general information on software development as well as instructions for flash
memory programming.
3.1Software Description
The TivaWare software provides drivers for all of the peripheral devices supplied in the design. The Tiva C
Series Peripheral Driver Library is used to operate the on-chip peripherals as part of TivaWare.
TivaWare includes a set of example applications that use the TivaWare Peripheral Driver Library. These
applications demonstrate the capabilities of the TM4C1294NCPDTI microcontroller, as well as provide a
starting point for the development of the final application for use on the Connected LaunchPad evaluation
board. Example applications are also provided for the Connected LaunchPad when paired with selected
BoosterPacks.
3.2Source Code
The complete source code including the source code installation instructions are provided at
http://www.ti.com/tool/sw-tm4c. The source code and binary files are installed in the TivaWare software
tree.
Chapter 3
SPMU365A–March 2014–Revised March 2014
Software Development
3.3Tool Options
The source code installation includes directories containing projects, makefiles, and binaries for the
following tool-chains:
•Keil ARM RealView®Microcontroller Development System
•IAR Embedded Workbench for ARM
•Sourcery Codebench
•Generic GNU C Compiler
•Texas Instruments' Code Composer Studio™ IDE
Download evaluation versions of these tools from the Tools & Software section of www.ti.com/tiva. Due to
code size restrictions, the evaluation tools may not build all example programs. A full license is necessary
to re-build or debug all examples.
For detailed information on using the tools, see the documentation included in the tool chain installation or
visit the website of the tools supplier.
20
Software DevelopmentSPMU365A–March 2014–Revised March 2014
The Connected LaunchPad software package includes pre-built binaries for each of the example
applications. If you installed the TivaWare™ software to the default installation path of
C:\ti\TivaWare_C_Series_<version>, you can find the example applications in C:\ti\TivaWare_C_Series<version>\examples\boards\ek-tm4c129xl. The on-board ICDI is used with the LM Flash Programmer tool
to program applications on the Connected LaunchPad.
Follow these steps to program example applications into the Connected LaunchPad evaulation board
using the ICDI:
1. Install LM Flash Programmer on a PC running Microsoft Windows.
2. Place JP1 into the ICDI position on the Connected LaunchPad.
3. Connect the USB-A cable plug in to an available USB port on the PC and plug the Micro-B plug to the
Debug USB port (U22) on the Connected LaunchPad.
4. Verify that LED D0 at the top of the board is illuminated.
5. Install Windows ICDI and Virtual COM Port drivers if prompted. Installation instructions can be found at
http://www.ti.com/lit/pdf/spmu287.
6. Run the LM Flash Programmer application on the PC.
7. In the Configuration tap, use the Quick Set control to select “TM4C1294XL LaunchPad”.
8. Move to the Program tab and click the Browse button. Navigate to the example applications directory
(the default location is C:\ti\TivaWare_C_Series_<version>\examples\boards\ek-tm4c1294xl\)
9. Each example application has its own directory. Navigate to the example directory that you want to
load and then into the sub-directory for one of the supported tool chains which contains the binary
(*.bin) file. Select the binary file and click Open.
10. Set the Erase Method to Erase Necessary Pages, check the Verify After Program box, and check
Reset MCU After Program. The example program starts execution once the verify process is complete.
Programming the Connected LaunchPad
SPMU365A–March 2014–Revised March 2014Software Development
NOTE: PB0 and PB1 are used in some
configurations with 5V signals especially in USB
Host or OTG mode. Be aware the 5V may be
present on these pins depending on system jumper
configuration
These pins are only 5V tolerant when configured for
USB mode applications.
This is the breadboard connection header.
Samtec TSW-149-08-F-S-RA and TSW-149-09-F-S-RE
can be used together to create a breadboard
connector
see the Users Manual for more information.
49.9
49.9
49.4
49.9
330
GND
330
GND
0.1uF0.1uF
GNDGND
0.1uF0.1uF
75
75
GNDGND
75
75
GND
4700pF
1M
1000pF
R21
R22
R23
R24
D4
R30
D3
R31
C16C17
C18C22
P$1
P$1
P$2
P$2
P$3
P$3
P$6
P$6
P$7
P$7
P$8
P$8
P$9
P$9
P$10
P$10
P$11
P$11
P$14
P$14
P$15
P$15
P$16
P$16
P$1
1
P$2
2
P$3
3
P$44P$5
5
P$6
6
P$7
7
P$8
8
R32
R43
CHASSIS
9
CHASSIS
10
RX+
3
RX-
6
TERM1A
4
TERM1B
5
TERM2A
7
TERM2B
8
TX+
1
TX-
2
R45
R46
C31
R47
C1
EN0RXI_N/5.3B
EN0RXI_P/5.3B
EN0TXO_N/5.3B
EN0TXO_P/5.3B
PF4/3.2CPF0/3.2C
MCU_3V3/5.2A
A
B
C
D
E
A
B
C
D
E
123456
U10
U13
U14
For Ethernet example Applications:
LED4 is default configured as Ethernet Link OK
LED3 is default configured as Ethernet TX/RX activity
User may re-configure these pins / LED's for any
application usage.
Place pull up resistors and C16-C17 near TM4C MCU.
Place C18 and C22 near pin 2 and pin 7 of U$10
U10 May be populated with either HX1188FNL or HX1198FNL.
HX1198FNL preferred for best Ethernet performance.
+3V3
+5V
GND
0.1uF
2.2uF
0.1uF
GND
330
GND
100k
4.87k 1%
GND
GND
0.1uF 1.0uF 2.2uF
0.1uF 0.1uF 0.1uF 0.1uF
GND
0
0
GND
1M
SWITCH_TACTILE
12pF
12pF
10k
0.1uF
12pF12pF
SWITCH_TACTILE
GND
MOUNT-HOLE3.2
MOUNT-HOLE3.2
GND
GND
GND
GNDGND
TPS2052B_DRB_8
+5V
10k
100k
GND
51
0.1uF
GND
+3V3
100k
TPS73733_DRV_6
OMIT
2k
MOUNT-HOLE3.2
100
CRYATL_32K_SMD
C19
C20
C21
D0
R9
R17
TP3
R25
C4C14C15
C40C41C42C43
TP9
TP10
TP11
TP12
R39
TP13
R41
R42
RESET
C44
C45
NC2
P$2
NC4
P$4
OSC0
P$1
OSC1
P$3
R44
C46
C47C48
WAKE
H4
H6
*EN1
3
*EN2
4
*OC1
8
*OC2
5
EPAD
9
GND
1
IN
2
OUT1
7
OUT2
6
VIAVVIA
V_2
VIA
V_3
VIA
V_4
VIA
V_5
VIA
V_6
U4
JP1
12
34
56
JP2
1
2
JP3
1
2
R35
R36
TP8
R38
C3
R26
EN
4
EPAD
7
GND
3
IN
6
NC
5
NR/FB
2
OUT
1
VIAVVIA
V_2
U5
R48
R49
H1
R51
HIB
P$65
RESET
P$70
WAKE
P$64
EN0RXIN
P$53
EN0RXIP
P$54
EN0TXON
P$56
EN0TXOP
P$57
GND
P$17
GND
P$48
GND
P$55
GND
P$58
GND
P$80
GND
P$114
GNDA
P$10
OSC0
P$88
OSC1
P$89
RBIAS
P$59
VBAT
P$68
VDD
P$7
VDD
P$16
VDD
P$26
VDD
P$28
VDD
P$39
VDD
P$47
VDD
P$51
VDD
P$52
VDD
P$69
VDD
P$79
VDD
P$90
VDD
P$101
VDD
P$113
VDD
P$122
VDDA
P$8
VDDC
P$87
VDDC
P$115
VREFA+
P$9
XOSC0
P$66
XOSC1
P$67
P$1
P$1
P$2
P$2
Y3
TARGET_VBUS/3.2C
TARGET_VBUS/3.2C
DEBUG_VBUS/6.4A
EN0RXI_N
EN0RXI_P
EN0TXO_N
EN0TXO_P
RBIAS
WAKE/3.3D
MCU_3V3/6.2A
MCU_3V3/4.1A
VBUS
VBUS
VBUS
PQ4/3.4D
PD6/3.2B
TARGET_RESET/3.2D
A
B
C
D
E
A
B
C
D
E
123456
Y1
25Mhz
U1G$2
Power Control Jumper:
1) To power from Debug install jumper on pins 5 - 6
2) To power from Target USB install jumper on pins 3 - 4
3) To power from BoosterPack 5V install jumper on pins 1 - 2
This is also the off position if BoosterPack does not
supply power
When powered from BoosterPack TPS2052B does not
provide current limit protection.
When powered by BoosterPack, USB host mode does not
supply power to connected devices
Primary 3.3V regulator
Disconnect JP3 to power device from 3V3 BoosterPack
JP2 can be used to measure MCU current
consumption with a multi-meter.
TPS2052B provides current limit for main 5V power.
Also provides power switching for USB host/OTG modes
For Host/OTG:
PD6 configured as USB0EPEN peripheral function.
PQ4 configure as individual pin interrupt. Indicates
power fault on the USB bus. USB0PFLT peipheral pin
not available due to pin mux and use on BoosterPacks.
USB Host mode does not supply power to devices
when powered from a BoosterPack
For Applications that do not use USB:
Configure PD6 as input with internal pull-down
enabled. Turns off power to TARGET_VBUS
R38 and C3 Used to meet
VBAT rise time requirements
R41 may be removed and precision
reference applied to TP13
OMIT
TSW-107-02-S-D
OMIT
+3V3
10k
0.1uF
OMIT
0.1uF 1.0uF
12pF
12pF
0.1uF 0.1uF 0.1uF 0.1uF
+3V3
+3V3
2.2uF
5.6k
OMIT
5.6k
OMIT
5.6k
OMIT
10k
10k
10k
10k
+3V3
0
0
0
0
0
0
0
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
0
+3V3
TPD4S012_DRY_6
5.6k10k
GND
2k
GND
1M
3300pF
GND
TRST
9
GND
3
NC
5
RESET
10
RTCK
7
TCK
4
TDI
8
TDO
6
TMS
2
VTREF
1
U21
X1-1X1-2
X1-3X1-4
X1-5X1-6
X1-7X1-8
X1-9X1-10
X1-11X1-12
X1-13X1-14
R3
C2
C5 C6
C8
C9
C10 C11 C12 C13
NC2
P$2
NC4
P$4
OSC0
P$1
OSC1
P$3
C7
R12
R13
R14
R1
R2
R4
R5
TP2
TP1
R6
R7
R8
R10
R11
R15
R16
EXTDBG
P3
RESET
P10
GND
P5
GND1
P9
P$7
P7
TCK
P4
TDI
P8
TDO
P6
TMS
P2
VTARGET
P1
R40
HIB
P$33
RESET
P$38
WAKE
P$32
GND0
P$12
GND1
P$27
GND2
P$39
GND3
P$55
GNDA
P$3
GNDX
P$35
OSC0
P$40
OSC1
P$41
PA0
P$17
PA1
P$18
PA2
P$19
PA3
P$20
PA4
P$21
PA5
P$22
PA6
P$23
PA7
P$24
PB0
P$45
PB1
P$46
PB2
P$47
PB3
P$48
PB4
P$58
PB5
P$57
PB6
P$1
PB7
P$4
PC0/TCK
P$52
PC1/TMS
P$51
PC2/TDI
P$50
PC3/TDO
P$49
PC4
P$16
PC5
P$15
PC6
P$14
PC7
P$13
PD0
P$61
PD1
P$62
PD2
P$63
PD3
P$64
PD4
P$43
PD5
P$44
PD6
P$53
PD7
P$10
PE0
P$9
PE1
P$8
PE2
P$7
PE3
P$6
PE4
P$59
PE5
P$60
PF0
P$28
PF1
P$29
PF2
P$30
PF3
P$31
PF4
P$5
VBAT
P$37
VDD0
P$11
VDD1
P$26
VDD2
P$42
VDD3
P$54
VDDA
P$2
VDDC0
P$25
VDDC1
P$56
XOSC0
P$34
XOSC1
P$36
DM
P2
DP
P3
GND
P5
ID
P4
VBUS
P1
D+
1
D-
2
GND
4
ID
3
N.C.
5
VBUS
6
U3
R28R29
R50
R34
C33
ICDI_TDI
ICDI_TMS
ICDI_TMS
ICDI_TCK
ICDI_TCK
ICDI_TDO
ICDI_TDO
ICDI_RESET
ICDI_RESET
VCP_RXD
VCP_RXD
VCP_RXD
VCP_TXD
VCP_TXD
VCP_TXD
DEBUG_PC1/TMS/SWDIO
DEBUG_PC1/TMS/SWDIO
DEBUG_PC1/TMS/SWDIO
DEBUG_PC1/TMS/SWDIO
DEBUG_PC1/TMS/SWDIO
DEBUG_PC3/TDO/SWO
DEBUG_PC3/TDO/SWO
DEBUG_PC3/TDO/SWO
DEBUG_PC3/TDO/SWO
DEBUG_PC3/TDO/SWO
DEBUG_PC2/TDI
DEBUG_PC2/TDI
DEBUG_PC2/TDI
DEBUG_PC2/TDI
DEBUG_RESET_OUT
DEBUG_RESET_OUT
DEBUG_RESET_OUT
DEBUG_RESET_OUT
EXTERNAL_DEBUG
EXTERNAL_DEBUG
ICDI_VDDC
VERSION_1
VERSION_1
VERSION_2
VERSION_2
VERSION_0
VERSION_0
DEBUG_ACTIVEDEBUG_ACTIVE
ICDI_USBD_N
ICDI_USBD_N
ICDI_USBD_P
ICDI_USBD_PTARGET_TXD/2.5D
TARGET_TXD/2.5D
TARGET_RXD/2.5D
TARGET_RXD/2.5D
TARGET_TCK/SWCLK/1.2A
TARGET_TCK/SWCLK/1.2A
TARGET_TCK/SWCLK/1.2A
TARGET_TMS/SWDIO/1.2B
TARGET_TMS/SWDIO/1.2B
TARGET_TMS/SWDIO/1.2B
TARGET_TDI/1.2B
TARGET_TDI/1.2B
TARGET_TDO/SWO/1.2B
TARGET_TDO/SWO/1.2B
TARGET_RESET/5.2A
TARGET_RESET/5.2A
DEBUG_VBUS/5.1B
DEBUG_VBUS/5.1B
DEBUG_VBUS/5.1B
DEBUG_PC0/TCK/SWCLK
DEBUG_PC0/TCK/SWCLK
DEBUG_PC0/TCK/SWCLK
DEBUG_PC0/TCK/SWCLK
DEBUG_PC0/TCK/SWCLK
MCU_3V3/5.6B
A
B
C
D
E
A
B
C
D
E
123456
Y2
16M
U6
JTAG_ARM_10PIN
U20
TM4C123GH6PMI
TM4C123xH6PMI
U22G$1
PE4 ETM_ENn Leave Open
use GPIO Internal weak pullup.
PE5 LS_PRESENTn Leave Open
use GPIO internal weak pullup
VERSION RESISTOR TABLE:
*use internal GPIO weak pullups.
ALL OMITTED: Legacy mode. (Stellaris ICDI)
ALL POPULATED: Everything enabled
Version 0 populated: UART CTS/RTS and Analog inputs
JTAG PULL-UPS
Jumpers to bridge from ICDI to Target portion of LaunchPad
EXTERNAL_DEBUG pull low to use external debugger
to debug the target. Causes ICDI chip to tri-state the JTAG lines
Use this for JTAG IN from external debugger. See X1
jumpers for information about debug out to an
external target.
R40 must be removed for debug out.
R40 must be instaled for debug in.
X1 omitted by default
To debug out from ICDI to off board MCU remove
0 ohm jumper resistors. To go back from debug
out to debugging the target MCU install X1 and
place jumpers on all pins.
Chapter 6
SPMU365A–March 2014–Revised March 2014
Revision History
This history highlights the changes made to the SPMU365 user's guide to make it an SPMU365A revision.
Table 6-1. Revision History
SEEADDITIONS/MODIFICATIONS/DELETIONS
Table 2-3, X11 Breadboard Adapter Odd-Numbered Pad GPIO and Signal Muxing:
• Updated/Changed Pin 1 from "5V" to "3V3"
• Updated/Changed Pin 25 from "PC4" to "PA6"
Section 2.1.6.3• Updated/Changed Pin 27 from "PA6" to "PA7"
Breadboard Connection
• Updated/Changed Pin 29 from "PA7" to "PG1"
• Updated/Changed Pin 61 from "EPI0S12" to "GND"
Table 2-4, X11 Breadboard Adapter Even-Numbered Pad GPIO and Signal Muxing:
• Updated/Changed Pin 2 from "3V3" to "5V"
SPMU365A–March 2014–Revised March 2014Revision History
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and other
changes to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per JESD48, latest
issue. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and
complete. All semiconductor products (also referred to herein as “components”) are sold subject to TI’s terms and conditions of sale
supplied at the time of order acknowledgment.
TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty in TI’s terms
and conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent TI deems necessary
to support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarily
performed.
TI assumes no liability for applications assistance or the design of Buyers’ products. Buyers are responsible for their products and
applications using TI components. To minimize the risks associated with Buyers’ products and applications, Buyers should provide
adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, or
other intellectual property right relating to any combination, machine, or process in which TI components or services are used. Information
published by TI regarding third-party products or services does not constitute a license to use such products or services or a warranty or
endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the
third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alteration
and is accompanied by all associated warranties, conditions, limitations, and notices. TI is not responsible or liable for such altered
documentation. Information of third parties may be subject to additional restrictions.
Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or service
voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice.
TI is not responsible or liable for any such statements.
Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements
concerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or support
that may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which
anticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might cause
harm and take appropriate remedial actions. Buyer will fully indemnify TI and its representatives against any damages arising out of the use
of any TI components in safety-critical applications.
In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TI’s goal is to
help enable customers to design and create their own end-product solutions that meet applicable functional safety standards and
requirements. Nonetheless, such components are subject to these terms.
No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of the parties
have executed a special agreement specifically governing such use.
Only those TI components which TI has specifically designated as military grade or “enhanced plastic” are designed and intended for use in
military/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI components
which have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for compliance with all legal and
regulatory requirements in connection with such use.
TI has specifically designated certain components as meeting ISO/TS16949 requirements, mainly for automotive use. In any case of use of
non-designated products, TI will not be responsible for any failure to meet ISO/TS16949.
ProductsApplications
Audiowww.ti.com/audioAutomotive and Transportation www.ti.com/automotive
Amplifiersamplifier.ti.comCommunications and Telecomwww.ti.com/communications
Data Convertersdataconverter.ti.comComputers and Peripheralswww.ti.com/computers
DLP® Productswww.dlp.comConsumer Electronicswww.ti.com/consumer-apps
DSPdsp.ti.comEnergy and Lightingwww.ti.com/energy
Clocks and Timerswww.ti.com/clocksIndustrialwww.ti.com/industrial
Interfaceinterface.ti.comMedicalwww.ti.com/medical
Logiclogic.ti.comSecuritywww.ti.com/security
Power Mgmtpower.ti.comSpace, Avionics and Defensewww.ti.com/space-avionics-defense
Microcontrollersmicrocontroller.ti.comVideo and Imagingwww.ti.com/video
RFIDwww.ti-rfid.com
OMAP Applications Processorswww.ti.com/omapTI E2E Communitye2e.ti.com
Wireless Connectivitywww.ti.com/wirelessconnectivity