
Example Applications
2.11 UART Echo (uart_echo)
This example application utilizes the UART to echo text. The first UART (connected to the USB
debug virtual serial port on the evaluation board) will be configured in 115,200 baud, 8-n-1 mode.
All characters received on the UART are transmitted back to the UART.
2.12 uDMA (udma_demo)
This example application demonstrates the use of the uDMA controller to transfer data between
memory buffers, and to transfer data to and from a UART. The test runs for 10 seconds before
exiting.
UART0, connected to the FTDI virtual COM port and running at 115,200, 8-N-1, is used to display
messages from this application.
2.13 USB Generic Bulk Device (usb_dev_bulk)
This example provides a generic USB device offering simple bulk data transfer to and from the host.
The device uses a vendor-specific class ID and supports a single bulk IN endpoint and a single bulk
OUT endpoint. Data received from the host is assumed to be ASCII text and it is echoed back with
the case of all alphabetic characters swapped.
A Windows INF file for the device is provided on the installation CD and in the C:/ti/TivaWare-for-
C-Series/windows_drivers directory of TivaWare C series releases. This INF contains information
required to install the WinUSB subsystem on Windowi16XP and Vista PCs. WinUSB is a Win-
dows subsystem allowing user mode applications to access the USB device without the need for a
vendor-specific kernel mode driver.
A sample Windows command-line application, usb_bulk_example, illustrating how to connect to
and communicate with the bulk device is also provided. The application binary is installed as
part of the ”Windows-side examples for USB kits” package (SW-USB-win) on the installation CD
or via download from http://www.ti.com/tivaware . Project files are included to allow the
examples to be built using Microsoft VisualStudio 2008. Source code for this application can be
found in directory TivaWare-for-C-Series/tools/usb_bulk_example.
2.14 USB HID Gamepad Device (usb_dev_gamepad)
This example application turns the evaluation board into USB game pad device using the Human
Interface Device gamepad class. The buttons on the board are reported as buttons 1 and 2. The
X, Y, and Z coordinates are reported using the ADC input on GPIO port E pins 1, 2, and 3. The X
input is on PE3, the Y input is on PE2 and the Z input is on PE1. These are not connected to any
real input so the values simply read whatever is on the pins. To get valid values the pins should
have voltage that range from VDDA(3V) to 0V. The blue LED on PF5 is used to indicate gamepad
activity to the host and blinks when there is USB bus activity.
10 July 25, 2016