06.09.2020
19
  1. Jun 09, 2017  We will use an MQTT protocol connection to interact with the IBM Watson Platform, so first step is to load and run the MQTT client application contained in the SimpleLink MCU Software Development Kit (SDK). This example application connects.
  2. The WISE-1520 SDK is based on TI CC3200 module to development. The user needs to install some TI packages before development and can find these packages in folder “packages” of source tree of WISE-1520 SDK.
  1. Cc3200 Sdk For Mac Pro
  2. Cc3200 Sdk For Mac Os
  3. Cc3200 Sdk For Mac Pro
  4. Cc3200 Sdk For Mac Free

Texas Instuments offers an evaluation kit for it's Single-Chip Wireless MCU CC3200: CC3200-LaunchXL

SIMPLELINK-SDK-TI-15-4-STACK-PLUGIN — The SimpleLink™ SDK TI 15.4 Stack Plug-in is a companion software package that enables the use of the IEEE 802.11.15.4 stack from TI on any standard SimpleLink microcontroller (MCU). This plug-in supports the SimpleLink Sub-1 GHz CC1310 wireless MCU as a network processor.

Citing from TI's Description:

The SimpleLink™ Wi-Fi® CC3200 LaunchPad evaluation kit is a development platform for the CC3200 wireless microcontroller (MCU), the industry’s first single-chip programmable MCU with built-in Wi-Fi connectivity. The board features on-board emulation using FTDI device.

This LaunchPad comes with driver support and a software development kit (SDK) with 40+ applications for Wi-Fi protocols, internet applications, and MCU peripheral examples.

The CC3200 MCU features a 802.11 b/g/n Station and Access Point, roles with fully integrated radio, baseband, and MAC Standards-based Wi-Fi solution Single-chip Wi-Fi MCU: Wi-Fi network processor + ARM® Cortex®-M4 MCU integrated into one chip including RF reference design.

This page will document my experiences with the CC3200-LaunchXL using Linux as development platform.

Index

Getting the SDK from Texas Instruments

For downloading the SimpleLink Wi-Fi CC3200 Software Development Kit (SDK) you need a 'myTI' account which you may create for free.

The SDK is a Windows executable which simply installs all the files needed for development on a Windows platform. To be able to use the files on Linux you may either run the SDK installer on a Windows box and copy the directory tree to your Linux system, or you may run the installer with wine directly under Linux.

Running the installer on Windows creates a directory tree under C:tiCC3200SDK_1.0.0.

As stated above, you may run the SDK installer under Linux with wine:

Running the installer with wine creates a directory tree under ~/.wine/drive_c/ti/CC3200SDK_1.0.0.
I symlinked ~/.wine/drive_c/ti/CC3200SDK_1.0.0/cc3200-sdk to ~/cc3200-sdk and used this in the examples below.

The CC3200 Software Development Kit consists of a collection of hardware and software documenting pdfs, a collection of example program sources, the sources of the hardware driver library/application development framework and some tools to support development with serveral IDEs and tool chains.
Of course the GNU toolchain (gcc) is the one interesting me.

Configuring the LaunchXL JTAG Debug Interface

The debug interface is provided by an FTDI FT2232 chip with custom vendor and product IDs. To make it accessible for the Linux system, there is an udev rule (from here) needed:
/etc/udev/rules.d/99-tiftdi.rules

(in kernel versions newer than 3.12 this doesn't work anymore, see here) Kasumi rebirth 3.1 crack key.

With the ftdi-sio module loaded (by the above udev rule or otherwise), I get two /dev/ttyUSBx devices when the Launchpad is plugged in.

In my setup, OpenOCD seems to write access /dev/bus/usb/<bus_num>/<node_num> which is owned by root:root. This ownership is not changed by a GROUP:='dialout' statement in the above udev rule.

So I had to add an additional rule to change group ownership of this device file.
My /etc/udev/rules.d/99-tiftdi.rules looks like this:

/usr/local/ftdi_chown.sh is a tiny script getting bus id and node id from udev via environment and changes the group ownership of the respective device file.

Running gdb/openocd as described below will remove the first of the two /dev/ttyUSB* for use as the debug interface.
The second /dev/ttyUSB* may be used as a serial console by the target program.

Build and install openOCD (Open On-Chip Debugger)

Building and installing openOCD is the standard './configure; make; sudo make install' procedure.

Make shure the ./configure run reports

Using OpenOCD in version 0.8.0, the configuration file for the debug interface needs to be changed.
(same has been successfully tried with OpenOCD version 0.9.0)

In ~/cc3200-sdk/tools/gcc_scripts/cc3200.cfg replace the following few lines

by

Starting OpenOCD with the following command:

shows the following message:

Stop OpenOCD by pressing Ctrl-C. In the future it will get started from the gdb debugger.

Cc3200 Sdk For Mac

arm-none-eabi Cross Tool Chain

Download the prebuilt binaries of thearm-none-eabi cross tool chain for Linux from launchpad.net. Unpack it to an appropriate directory and add the bin/ directory to the execution path.

You may want to add the last line from above to ~/.bashrc to have the path to the arm tool chain binaries available in every future shell.

The shipping system laytime calculator free download

Compile one of the examples from the CC3200 SDK:

This should produce blinky.axf in ~/cc3200-sdk/example/blinky/gcc/exe/.

To be able to upload, run and debug the compiled binary for the CC3200, you may need to move the jumper from P58-VCC to SOP2.
The jumpers should be set like in the picture below.

Edit the OpenOCD start command in ~/cc3200-sdk/tools/gcc_scripts/gdbinit to make shure OpenOCD finds it's appropriate configuration file.
Mine looks like this:

Run a gdb session

The gdb should upload the blinky binary to the CC3200 and print something like below:

Pressing 'c' (for continue), then 'enter' should run the uploaded program and you should see blinking the three LEDs D5 - D7 one after another in a one second interval.

Links

TI Manuals as PDFs

Hardware Examples

This site maintained by:
[email protected]
My public PGP key
last updated: 2014-05-08

This file contains the following information:

  • How to build the AWS SDK and the samples for the TI CC3200 launchpad.
  • How to run the samples.

THIS IS PRE-RELEASE SOFTWARE. CONTENTS AND DIRECTORY STRUCTURE ARE SUBJECT TO CHANGE.

Table of Contents

Prerequisites

Required hardware: CC3200 Launchpad with the latest firmware/service pack.

This procedure assumes you have already installed the AWS SDK on your development machine. These instructions refer to the folder that contains the AWS SDK on your local machine as <AWS_INSTALL_DIR>.

While not strictly required, we recommend that you install the following tools from TI in the same directory and that you use directory names without any whitespace. This documentation assumes that you install everything in a directory named C:/ti.

Cc3200 Sdk For Mac Pro

  • Install Code Composer Studio v6.1.1 or above

  • Install CC3200 SDK 1.1.0. Linux users can use a tool such as Wine to run the SDK installer.

  • Install TI-RTOS SDK for SimpleLink 2.14.01.20 or above

  • Install the NS package

Build the sample applications

  1. Edit the products.mak file in <AWS_INSTALL_DIR>/ using your favorite text editor. The variables XDC_INSTALL_DIR, TIRTOS_INSTALL_DIR, BIOS_INSTALL_DIR, UIA_INSTALL_DIR, CC3200SDK_INSTALL_DIR and NS_INSTALL_DIR must point to the locations where you installed these products. The variable TI_ARM_CODEGEN_INSTALL_DIR should point to the installation location of the TI ARM compiler in your CCS installation. After modification, these variable definitions should look similar to the following if you are working in Windows. (Windows users: note the use of '/' in the path).

  2. If you are using Windows, open a Windows command prompt. If you are using Linux, open a terminal window.

Before building a specific application, complete the following steps (we are referring to the subscribe_publish_sample application here, but the same procedure applies to other samples as well):

  1. Open the aws_iot_config.h file from the directory <AWS_INSTALL_DIR>/sample_apps/subscribe_publish_sample/ in a text editor and update the value of the 'AWS_IOT_MQTT_HOST' variable with the address to the AWS Icebreaker endpoint.

  2. Update the value of the 'AWS_IOT_MQTT_CLIENT_ID' and 'AWS_IOT_MY_THING_NAME' as per the AWS Developer Guide

  3. Verify the file names in the variables 'AWS_IOT_ROOT_CA_FILENAME', 'AWS_IOT_CERTIFICATE_FILENAME', and 'AWS_IOT_PRIVATE_KEY_FILENAME' match the ones in <AWS_INSTALL_DIR>/certs/platform_tirtos/cc3200/certflasher.c. If you are using the default paths in certflasher.c, no change should be required.

  4. From the directory <AWS_INSTALL_DIR>/sample_apps/subscribe_publish_sample/platform_tirtos/cc3200/, Open the file main.c. Search for 'USER STEP' and update the current date-time macros.

  5. Open the file wificonfig.h. Search for 'USER STEP' and update the WIFI SSID and SECURITY_KEY macros.

  6. TI ARM compiler builds the C runtime library during the first application build which requires gmake on the environment path. It is recommended gmake tool is installed on your machine and added to the path. Alternately, XDCtools product (C:/ti/xdctools_3_31_01_33_core) which also contains gmake can be added to the path. But note, it is recommended that the XDCtools is removed from the path after the libraries are built. This is to avoid conflicts when you use newer versions of XDCtools. For detailed information about building TI ARM C runtime library, please read the Mklib wiki.

On the command line, enter the following commands to build the application:

Obtain certificate files

Certificate files used by the samples need to be obtained from AWS using this procedure:

Mac
  1. Create a client certificate and private key, and attach a policy using the instructions in the section 'Securing Communication Between a Thing and AWS Iot' in the Icebreaker Developer Guide.

  2. Obtain the root CA certificate as specified in the section “Verify MQTT Subscribe and Publish” in the Icebreaker Developer Guide.

Build the certificate flasher tool

Before building the tool, complete the following:

Cc3200 Sdk For Mac Os

  1. Open the file certflasher.c from the directory <AWS_INSTALL_DIR>/certs/platform_tirtos/cc3200/.

  2. Search for 'USER STEP' and update the CA root certificate string, the client certificate string, and the client (private) key string. These should be extracted from certificate (.pem) files, or from the JSON data if you used the command line CLI tool in the previous section (remember to remove the newline 'n' characters in the JSON data). A typical string would be of this format:

On the command line, enter the following commands to build the application:cd <AWS_INSTALL_DIR>/certs/platform_tirtos/cc3200 C:/ti/xdctools_3_31_01_33_core/gmake all

Setting up Code Composer Studio before running the samples

  1. Plug the CC3200 Launchpad into a USB port on your PC

  2. Open a serial session to the appropriate COM port with the following settings:

  3. Open Code Composer Studio.

  4. In Code Composer Studio, open the CCS Debug Perspective - Windows menu -> Open Perspective -> CCS Debug

  5. Open the Target Configurations View - Windows menu -> Show View -> Target Configurations

  6. Right-click on User Defined. Select New Target Configuration.

  7. Use CC3200.ccxml as 'File name'. Hit Finish.

  8. In the Basic window, select 'Stellaris In-Circuit Debug Interface' as the 'Connection', and check the box next to 'CC3200' in 'Board or Device'. Hit Save.

  9. Right-click 'CC3200.ccxml' in the Target Configurations View. Hit Launch Selected Configuration.

  10. Under the Debug View, right-click on 'Stellaris In-Circuit Debug Interface_0/Cortex_M4_0'. Select 'Connect Target'.

Cc3200 Sdk For Mac Pro

Running the certificate flasher tool

All samples rely on a set of certificates from AWS. As a result, the certificates need to be stored once into flash memory prior to running the samples. To flash the certificates, simply run the flasher tool you have previously built using this procedure:

  1. Select Run menu -> Load -> Load Program.., and browse to the file certflasher.out in <AWS_INSTALL_DIR>/certs/platform_tirtos/cc3200/. Hit OK. This would load the program onto the board.

  2. Run the application by pressing F8. The output in the CCS Console looks as follows:

  3. Hit Alt-F8 (Suspend) to halt the CPU.

Running a sample

Cc3200 Sdk For Mac Free

  1. Select Run menu -> Load -> Load Program.., and browse to the file subscribe_publish_sample.out in <AWS_INSTALL_DIR>/sample_apps/subscribe_publish_sample/platform_tirtos/cc3200. Hit OK. This would load the program onto the board. (The same procedure applies to other samples by substituting subscribe_publish_sample)

  2. Run the application by pressing F8. Output would appear in your serial terminal session: