TI Wi-Fi CC3200 LaunchPad & CC3100 BoosterPack

Table of contents

CC3200 LaunchPadThe 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 and includes sensors for a full out-of-the-box experience. This board can be directly connected to a PC using software development platforms including CCS and IAR.
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.
CC3200 is supported in v7.20 of IAR. There is free (limited time license) evaluation version available here.
For additional information about CC3200, visit http://www.ti.com/simplelinkwifi.
CC3200 LaunchPad Features
  • CC3200 Wi-Fi wireless MCU
  • USB interface to PC for CCS/IAR using FTDI USB drivers
  • Flash update over the USB using SimpleLink Programmer
  • 2 20-pin connectors enables compatibility with other TI LaunchPads with added functions
  • Standalone development platform featuring sensors, LEDs and push-buttons
  • Power from USB for the LaunchPad as well as external BoosterPack
  • Operates from 2 AA alkaline batteries
  • On-board antenna and U.FL connector selectable using a capacitor re-work
  • Supports 4 wire JTAG and 2 Wire SWD
  • GNU Debugger (GDB) support over Open On chip debugger (OpenOCD)
  • BoosterPack headers
CC3100 BoosterPack Features
CC3100 BoosterPack Features
  • 2 20-pin stackable connectors
  • On-board chip antenna with option for U.FL-based testing
  • Power from on-board LDO using USB OR 3.3V from MCU LaunchPad
  • 2 push buttons
  • 4 LEDs
  • Jumper with 0.1 Ohm resistor for current measurement
  • 0.8 megabit serial flash
  • 40 MHz crystal, 32 KHz crystal and oscillator
  • U.FL and chip antenna
  • USB
  • 4 Layer PCB with 6 mm spacing and track width
  • BoosterPack headers
Product Video
Terms & Conditions
  • Testers will be selected on the basis of quality of applications: we expect a full and complete description of why you want to test these particular products.
  • Testers are required to produce a full, comprehensive and well thought out review within 2 months of receipt of the products.
  • Failure to provide this review within the above timescale will result in the enrolee being excluded from future Road Tests.
Comment List
Anonymous
Parents
  • Actually Code restrictions are not as bad as they seem to be. If the target MCU has libraries already available pre-compiled for a booster pack / external device as a lot of the CCS samples do, then they don't count in the code size. It is only the stuff that has to be compiled

     

    so you can have a significant library for networking and the like, if you simply include it then call it from you code, the library does not count in the restriction

     

    when you look at the Tiva C Connected Launchpad and the Tiva C Launchpad. Libraries for all the internal workings are already included into an embedded ROM on the chip so libraries to use ADC, Interrupts, Ethernet and other on chip devices do not even need to be uploaded. How cool is that. Now for the ones that are not in the ROM, if they  are part of TivaWare and the likes, you will notice only the header files are showing in the folders, the rest is already compiled and will not count in your code size. The same basic principal goes for the smaller MSP430 chips, less the ROM. The irony is the Tiva C MCUs have masses of FLASH and RAM where as the MSP430s do not and could therefor do with the ROM image, ah well

  • Hey Peter,

     

    Asking not to be rude but because of my situation (have not asked on e2e yet) are you 100% sure. I can't get "get_time" and "get_weather" to run because of a size limit error, they are both demos for the CC3100.

  • As far as I am able to tell so I would say 99%, note this is the libraries supporting the internal components mostly, for instance I have been playing with he eZ430-Chronos-915 watch, there is no way it will compile completely with in the limits of CCS but as most of it is pre-compiled I am able to add menus and other items without hitting the limits. Now I did try to change one of the headers linked to a pre-compiled bits and immediately trigger a size error so had to find another way

     

    So yes in principal that's how it works. The pre-compiled libraries don't count in the size limit. This makes it much more palatable with the exception CCS is a pig to learn. Probably similar to going from the Arduino IDE to the Atmel Studio coding direct to the hardware vs via the Wiring abstraction layer

     

    also companies like AAeron who build the sub 1Ghz modules also put out pre-compiled libraries that can help a lot too.

     

    fire off an inquiry on the TI Forums and see what they say, but I'm pretty sure of my intel. I just cant guarantee it.

Comment
  • As far as I am able to tell so I would say 99%, note this is the libraries supporting the internal components mostly, for instance I have been playing with he eZ430-Chronos-915 watch, there is no way it will compile completely with in the limits of CCS but as most of it is pre-compiled I am able to add menus and other items without hitting the limits. Now I did try to change one of the headers linked to a pre-compiled bits and immediately trigger a size error so had to find another way

     

    So yes in principal that's how it works. The pre-compiled libraries don't count in the size limit. This makes it much more palatable with the exception CCS is a pig to learn. Probably similar to going from the Arduino IDE to the Atmel Studio coding direct to the hardware vs via the Wiring abstraction layer

     

    also companies like AAeron who build the sub 1Ghz modules also put out pre-compiled libraries that can help a lot too.

     

    fire off an inquiry on the TI Forums and see what they say, but I'm pretty sure of my intel. I just cant guarantee it.

Children
  • Posted on e2e and will update if I get any info on those two examples.

     

    Thanks image

  • Hey Peter,

     

    There response I got here is that there is a size issue with some of the demos, if I take this what you have said I would assume that they are not using built in libraries or that there is something else going on in this case.

     

    Kas

  • It does seem to imply that TI has not pre-compiled all of the libraries

     

    Im not sure, I will investigate over the weekend but some of the Micro-controllers have a ROM version of the Libraries built into the uController for all of the uController built in functions, I know this to be true of the Tiva C launch Pads, not too sure about this one. If it does then putting a "ROM_" in front of the include library name will make the compiler use the ROM saving significant space

     

    another thing in the interim you could try is to remove some of the code, how far over is it. I would imagine there are many web pages present in the samples, some of which could be removed to shrink the compiled code base

     

    As I said, if i get a chance, I will investigate over the weekend

     

    My CCS is now fully licensed so unless I can find a spare PC to install a limited version on it may be tough to check completely but I will see what I can do.

     

    Peter