no longer need. Also, move and
arrange windows for ease of use.
Once your screen is organized to
your satisfaction, you can begin to
edit source files and compile.
This example should compile
straight out of the box. However,
before we proceed, we should
check the project properties and
make sure they are appropriate
for our demonstration. These
projects are a carryover through
many CCS releases and sometimes
adjustments are needed. Following
are the changes we had to make
to compile CC3200_SDK v1.3.0
i2c_demo under CCS v8.
Right-click on the project name
in the Project Explorer and select
Properties. Select the General tab
and make sure the latest compiler
version is selected; see Figure 8.
Now, select the ARM Compiler tab and if flag --float_
support=fpalib is set, click on Edit Flags and change fpalib
to none (Figure 9). Click OK, Apply, and Close.
Go to Project and click on Build Project. The console
will open and if successfully compiled, you should get the
confirmation “Build Finished” as seen in Figure 10.
Before we proceed with the i2c_demo, let’s explore
what this code does.
The application communicates with the user (Terminal
Emulator) over UART. It accepts commands to read/write
registers on a specified I2C device and displays results on a
used the free
application Pu TTY.
The source code
of interest is in the
writes results to
uart_if.c - I2C/
API wrapper that
calls driverlib low level functions to open, close, read, and
Pinmux.c - Configures pins and peripherals.
Unpack your CC3200, remove the jumper on header
P1 between Vcc and pin P58 if installed, and make sure
jumpers J2 and J3 are populated. Connect your LaunchPad
to your PC, and the onboard LEDs will come to life.
In CCS under View, select Other. A new menu pops
up. Type “target” in the search box and select Target
Configurations as shown in Figure 11.
Figure 8. Compiler version.
September/October 2018 49