NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

CC3200 Mac OS X SDK simplelink library link issue. Prodigy 150 points Prasad De Zoysa Replies: 5. Hello, Recently i have installed CCS on my Mac. Wi-Fi, along with programming examples from the software development kit (SDK). This document explains both the platform and the framework available to enable further application development. 1.1 Overview The Texas Instruments royalty-free CC3200 Embedded Wi-Fi Foundation software development kit is a. This is version 1.4.0 of the CC3200 SDK. Getting Started. To get started using the CC3200 LaunchPad with the Out of Box experience, please see the CC3200 Quick Start Guide. To get started with your project development, please see the CC3200 Getting Started Guide. Bug fixes; Example maintenance and updates. 6.2 CC3200 SDK Install Notes. Close CCS for now. Next install the CC3200 SDK (it should now automatically create a new sub-folder inside your C: ti top-level folder). Click ‘Yes’ to install the FTDI driver when prompted. 6.3 UniFlash-SimpleLink, PinMux-V3 anf CC3200 SDK Service Pack Install Notes.

• 2Prerequisites

Objective[edit]

This application demonstrates Camera Application on a CC3200 LaunchPad setup. This application captures QVGA image in JPEG format and displays in a web browser.

Prerequisites[edit]

Hardware[edit]

• CC3200 LaunchPad Rev 3.0 onwards
• CC3200 Camera Booster Pack Rev 3.0 onwards
• MT9D111 Camera Module

Software[edit]

• CC3200 Camera Application
• Latest SDK Firmware Package

Application details[edit]

In this application, Simplelink device runs in Access Point Mode.

User needs to connect the Wi-Fi enabled device PC/Smartphone to the device AP (Default SSID: mysimplelink-MACAddr)

Using a web browser, access http://mysimplelink.net/camera_demo.html, the static pages stored on Serial FLASH will be displayed.

Press/Click 'Start' button to start capturing. The captured image will be written to Serial FLASH and displayed in the web browser.

The following picture illustrates the usage of the camera application:

Source Files briefly explained[edit]

• main.c - System Initialization, Spawns the Camera Service Task. HTTP server callback request to handle token from HTML page.
• gpio_if.c - Handles GPIO related operations
• pinmux.c - Generated by Pinmux utility pin to configure Camera Data and I2C
• camera_app.c - Handles DMA Configuration, Camera Capture and NVMEM File operations
• MT9D111.c - MT9D111 sensor related functions are implemented
• startup_*.c - Implements tools specific interrupt vector table

Usage[edit]

• Flash Example Content(html,image,Application binary)on serial flash by following below steps.

• Open <cc3200-sdk>examplescamera_applicationhtmlcamera_application.ucf session file in Uniflash.
• Flash the files to the device. Detailed instructions at Uniflash User Guide.

• Configure the device as described in next section
• Run the reference application
  1. Run From IDE (IAR/CCS)
     • Open the Project as mentioned in the <cc3200-sdk>docsCC3200-Getting Started Guide.pdf
     • Build and download the application to the board
  2. Run Flashed Binary file

Remove SOP Jumpers on Board and Press Reset. Refer <cc3200-sdk>docsCC3200-Getting Started Guide.pdf for detailed Information.

• Device started in AP mode, Connect your PC/SmartPhone to 'mysimplelink-<macAddress>'.
• Open 'mysimplelink.net/main.html' in browser of PC/MAC/Smartphone, goto 'Camera' tab and Control Camera Capture in the CC3200 device.

Configuring the target device[edit]

1. Remove J10 and J11 jumpers to cut off the TDI and TDO from FTDI.
2. Mount the jumpers J6 and J7 in the RX/TX mode. This enables the launchpad interface to the booster pack.
3. Remove SOP-2 Jumper. For Debug(Using IAR/CCS) Mode, Ensure SOP 0 is mounted on the CC3200 launchpad. Since, TDI and TDO are used for I2C interface, the JTAG is operational in SWD mode. # Remove Jumpers J2, J3 and J4. This disconnects the GPIO from on-board sensors.
   
4. Mount the Camera Booster pack on the launchpad as shown below. Make sure the VCC on P1 connector mates with VCC indication on the booster pack. Similarly, the GND on P2 connector should align with GND indication on the camera booster pack.

Please note that only one sensor has to be interfaced to the camera booster pack.

Limitations/Known Issues[edit]

• The application requires about 250 KB space in serial Flash. Downloading html/bin files using uniflash may fail if enough space is not available on serial flash. Try erasing older files from serial flash using Uniflash.
• There is significant lag in JPEG output since capture images are stored in serial flash and polled by web browser. For real time JPEG streaming, Refer to CC32xx Websock Camera Application
• This application uses TDI and TDO for I2C interface and so, the following configuration needs to be included in PinMuxConfig function in the pinmux.c file [Only required for SDK 1.0].

Links[edit]

Cc3200 Sdk For Mac Catalina

{{#invoke: Navbox | navbox }}{{#invoke: Navbox | navbox }}

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

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)

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)

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.

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.

Cc3200 Sdk For Mac Os

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.

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