1 Introduction
2 Network protocols
3 Features
4 Tools
5 GOAL with Code Composer Studio
- 5.1 Generate projects with GOAL
- 5.2 Import Projects into Code Composer Studio
6 Debugger
7 Downloads
8 FAQ and Known Issues

Introduction

The Tiva TM4C1294xl Evaluation Kit is a low-cost development platform for Arm® Cortex-M4F-based microcontrollers (MCUs). The connected LaunchPad design highlights the TM4C1294NCPDT MCU with its on-chip 10/100 Ethernet medium access control (MAC) and physical layer (PHY), USB 2.0, hibernation module, motion control pulse-width modulation and a multitude of simultaneous serial connectivity.

Network protocols

The following network protocols are supported:

Please follow the links for detailed stack description.

Features

High Performance TM4C1294NCPDT MCU:
- 120MHz 32-bit ARM Cortex-M4 CPU
- 1MB Flash, 256KB SRAM, 6KB EEPROM
- Integrated 10/100 Ethernet MAC+PHY
- Dual 12-bit 2MSPS ADCs, motion control PWMs
- USB 2.0 Full-speed Host, Device, and OTG (High-speed with external USB PHY)
Dual, stackable BoosterPack XL connection sites
Two Controller Area Network (CAN) modules (requires CAN transceivers)
On-board, in-circuit debug interface (ICDI)
Multiple development tool chain support: CCS and GCC

The general TM4C1294xl memory map is shown in following table. The addresses indicates the maximal reserved memory.

Address	Size	Region	Usage

Address	Size	Region	Usage
0x0000_0000 - 0x0010_0000	1024k	FLASH	GOAL image.
0x1000_0000		ROM	Tiva Bootloader: starts fallback application if Flash does not contain valid application.
0x2000_0000 - 0x2004_0000	256k	SRAM	Stores BSS segment

Tools

These software tools are required to run GOAL and its network protocol stacks.

GOAL with Code Composer Studio

The GOAL delivery contains several pre-built example projects for Code Composer Studio. The delivery also contains a fully functional project generator, to build projects on your own.

Please keep the path length as short as possible and extract the GOAL delivery in for e.g. a root directory to ensure proper project functionality. This is important as some windows versions have a restriction regarding path sizes.

Generate projects with GOAL

This step is optional as several pre-built example projects are provided within the delivery. This might be interesting, if you want to create your own projects.

To generate a project:

Choose an approriate project at commandline
user: ~ cd GOAL/projects/goal_eip/opener/01_simple_io/gcc
Invoke project generator and choose appropriate platform
user: ~/GOAL/projects/goal_eip/opener/01_simple_io/gcc make gen_project No platform selected, choose a platform - OR - press <CTRL+c> and set the PLATFORM environment variable. Choose platform: [ 1] ti_ek_tm4c1294xl (gcc,gdb,ocd) ... python3 /home/user/GOAL/projects/goal_eip/opener/01_simpleio/gcc/../../../../../tools/make/gen_project/gen_project.py gen_project ----------- Project: goal_eip__opener__01_simple_io__ti_ek_tm4c1294xl Templates: tools/make/gen_project/templates/ccstudio/ti/ti_ek_tm4c1294xl Generating: .ccsproject .cproject .project ti_ek_tm4c1294xl.ld tm4c1294ncpdt.cmd tm4c1294ncpdt_startup_ccs.c readme.txt Tiva TM4C1294NCPDT.ccxml Output dir: D:/msys64/home/user/GOAL/projects/goal_eip/opener/01_simple_io/gcc/../ccstudio/ti/ti_ek_tm4c1294xl

The created project can now be imported.

Import Projects into Code Composer Studio

Several pre-built GOAL example projects for ccstudio are provided with this delivery, these are located at projects/<protocol>/<application>/ccstudio/ti/ti_ek_tm4c1294xl/.project.

Importing the project is described here: GOAL Project Generator | Code Composer Studio

The project supports by default two different configurations:

Debug__TI: this configuration uses the provided TI compiler and libraries coming with the IDE.
Debug__GNU: this configuration uses the open-source GNU toolchain. This Toolchain is fully supported by GOAL and most of the supported targets.

The compiler is selected at build-time by hitting “Build…” at the toolbar. After the succesful build, the Debug Session is started by hitting “Debug…” at the toolbar.

Debugger

The provided GOAL examples make use of the In Circuit Debug Interface of the Development kit. However, it is possible to use any other supported Debugger setting the option “Connection” at “Properties”->”General”->”Project”.

The Debugger must be connected through the JTAG interface with the target, like shown below.

Downloads

Industrial Communication Explorer

FAQ and Known Issues

The Board does not start the flashed application.

Tiva Bootloader is started, instead of the properly flashed application. This behavior is controlled by the BOOTCFG register of the device. To start the flashed application, the GPIO PH0 must be connected to 3.3V with a Pull-Up resistor. To Debug the device, the resistor must be removed again.

GOAL - Tiva TM4C1294