Programming the Connected LaunchPad

www.ti.com

24

SPMU365C – March 2014 – Revised October 2016

Submit Documentation Feedback

Copyright © 2014–2016, Texas Instruments Incorporated

Software Development

3.4

Programming the Connected LaunchPad

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.