Go to file

Thomas Klaehn cc195babdb Update Readme and launch config		2019-10-16 10:46:44 +02:00
.vscode	Update Readme and launch config	2019-10-16 10:46:44 +02:00
common	Initial commit	2019-10-09 13:45:38 +02:00
driverlib	Initial commit	2019-10-09 13:45:38 +02:00
inc	Initial commit	2019-10-09 13:45:38 +02:00
src	Move srcs to src folder	2019-10-10 08:09:18 +02:00
.gitignore	Initial commit	2019-10-09 13:45:38 +02:00
gdbinit	Initial commit	2019-10-09 13:45:38 +02:00
gnu.ld	Initial commit	2019-10-09 13:45:38 +02:00
makedefs	Move srcs to src folder	2019-10-10 08:09:18 +02:00
Makefile	Initial commit	2019-10-09 13:45:38 +02:00
README.md	Update Readme and launch config	2019-10-16 10:46:44 +02:00

README.md

CC3200

Overview

All digital pins of the device can be used as general-purpose input/output (GPIO). GPIOs can be used for various purposes. The GPIO module on the CC3200 consists of four GPIO blocks:

GPIO A0
GPIO A1
GPIO A2
GPIO A3

Each GPIO block provides eight GPIOs. The GPIO module supports 30 programmable GPIO pins, depending on the peripheral used.

Application details

The objective of this application is to showcase GPIO control using Driverlib API calls. The LEDs connected to the GPIOs on the LaunchPad are used to indicate GPIO output. The GPIOs are driven high and low periodically in order to turn the LEDs on and off.

Source Files briefly explained

main.c: Contains the core logic to drive GPIOs and inturn blink the LEDs.
gpio_if.c: Contains the Driverlib API calls to drive the GPIOs
pinmux.c: Generated by the PinMUX utility. GPIO pins are brought out on the device boundry using the Driverlib Pinmux API calls.
startup_*.c - Initialize vector table and IDE related functions

Usage

Run the reference application.
- Open the project in CCS/IAR. Build the application and debug to load to the device, or flash the binary using UniFlash.
Verify the LaunchPad LEDs (D5, D6 and D7) toggle on and off.

Debug

Start debug server:

docker run --privileged -p 3333:3333 cc3200-env sh /bin/start_openocd.sh