Table of Contents

Introduction

The SimpleLink™ Wi-Fi® CC3200 device is a single-chip microcontroller (MCU) with built-in Wi-Fi connectivity. The CC3200 device is a wireless MCU that integrates a high-performance ARM® Cortex®-M4 MCU, allowing customers to develop an entire application with a single IC.

For more information, visit www.ti.com/simplelink.

This is v1.5.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.

What’s New

• New APIs added to the host driver.
  • API to mask supported rates in the RX and TX
  • API to extend scan duration on selected channels
  • API to configure the device to use NULL frames instead of PS-POLL frames when fetching packets from the AP in power save mode
• New event added
  • An unsolicited event to indicate the same 3rd EAPOL packet is received again during 4-way handshake

Updating the servicepack

It is recommended to update the service pack to the latest available, which can be downloaded from the CC3200 SDK download page.

For more information, see the CC3100 & CC3200 UniFlash Guide.

Dependencies

This release was validated with the following components:

• Code Composer Studio 8.3
  • Compiler TI 18.1.4.LTS
• IAR Code Generation Tools
  • ARM 8.20.2
• SimpleLink host driver 1.0.1.14
• CC3100/CC3200_ServicePack 1.0.1.14-2.12.2.6
• TI-RTOS 2.16.01.14
• FreeRTOS 10.0.1

Device Support

• CC3200R1 [ES1.33 Chip Id : 0x4000010]
  • CC3200-LAUNCHXL Rev3.2 onwards

Directory Structure

Examples

Networking Applications

MCU Only Applications

Fixed Issues

• WPA2 enterprise re-authentication issue. The client supplicant may get disconnected upon RADIUS server re-authentication.
• APs are not included in scan list in a congested environment since the device doesn’t stay on the channel too long. A new extended scan API is added as noted above.
• A very high L2 retry rate observed in congested environments, especially when high rates are used. A new rates masking API is added as noted above.
• Sudden drops in TX throughput during Bidirectional TCP data on the same socket.
• Bidirectional maximum TCP throughput may cause NWP abort when using TLS1.0 and TLS_RSA_WITH_AES_256_CBC_SHA or TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA.
• Data patterns may get injected into packets pulled from NWP causing integrity failure.
• Setting scan interval does not behave properly when using big-endian host processor.
• TCP fast retransmission is not triggered upon 3 duplicate ACK frames as expected.
• Rare disconnections from an AP with personal WPA2. A new unsolicited event is added as noted above.
• When working in non-blocking secured sl_Connect(), after some time the maximum 2 SSL sockets is reached although sockets are closed properly.
• Device may stay on SD although LSI is set.
• Once in a while, when AID0 and VBM are signaled simultaneously, the device may not send a PS-POLL or NULL frame.
• In case of AID0 and VBM are signaled simultaneously, the PS-POLL or NULL frame is transmitted immediately and not at the end of the broadcast/multicast chain.
• Specific APs like Engenius may occasionally disconnect the device. Fixed by using the new No Ps Poll feature as noted above.
• When RF conditions are poor and 1Mbps/2Mbps are used, the device may consume more power and loose synchronization with the AP.
• Device may stay stuck in awake (consuming constant high current) after disconnection from the AP.
• Device may stay stuck in awake (consuming constant high current) in congested environments where AP starts suppressing/deferring beacons.
• Device may consume high power when AP’s clock drifts forward.
• Failure to exchange data after full 4-way handshake rekey (either as a standalone or enterprise).
• High power consumption in connected idle if during first time connection, the AP beacons are missing.
• Device does not disconnect if beacons are missing and AP responds to Probes (150 consecutive missed beacons).

Host Driver

Known Issues

Network Processor / Host Driver

Notes for CC3200 Application Developers

SimpleLink library build: Release vs. Development

A core reset from the debugger will only reset the applications MCU and leave the networking subsystem active. This means while using the debugger on the CC3200 LaunchPad, the developer would have to manually reset the LaunchPad after every debug session before loading the new application image.

To improve the developer’s experience, the following was added to the implementation of sl_Start:

• sl_DeviceEnablePreamble defined as NwpPowerOnPreamble in cc_pal.c resets the networking services
• Delay in sl_DeviceEnable defined as NwpPowerOn introduced for proper operation
• With these changes, the networking engine has to be gracefully stopped and started again for the next debug session. This includes some additional delays which result in greater overall current consumption. As these additional steps and delays are required only for debug purposes, they should not be a part of deployment applications.

For ease of use, the latest CC3200 SDK provides separate configurations of the SimpleLink library for development (debug) and deployment scenarios.

Release libraries

• NON_OS – SimpleLink for NON-OS environment
• OS – SimpleLink for OS environment
• PM_Framework – SimpleLink with Power Management Framework for OS environment
• NON_OS_PM – SimpleLink with Power Management Framework hook

Development libraries

• NON_OS_debug – SimpleLink for NON-OS environment with debug support
• OS_debug – SimpleLink for NON-OS environment with debug support
• PM_Framework_debug – SimpleLink with Power Management Framework for OS environment with debug support
• NON_OS_PM_debug – SimpleLink with Power Management Framework hook with debug support

All the above configurations are pre-built in the SDK package along with their generated output library.

Note that the debug builds will result in overall greater current consumption. Developers should link to the release library builds for deployment by updating the library path to simplelink.a in their IDE.

Updating SimpleLink spawn task stack size

By default, the SimpleLink spawn task stack size is set to 2048 bytes. While this size is sufficient for the applications available in the SDK, this value may need to be changed depending on the callback implementation/call flows. In order to change the stack size, the oslib library must be rebuilt with the macro SPAWN_TASK_STACK set to the optimum stack size value (for example -DSPAWN_TASK_STACK=3072).

Implementation of osi.h is shown below:

#ifndef SPAWN_TASK_STACK
#define STACK_LEN (2048) /*Stack Size*/
#else
#define STACK_LEN (SPAWN_TASK_STACK)
#endif

Post-LPDS settings

PRCMCC3200MCUInit API must be called after coming out of LPDS. If this API is not called post-LPDS, then the interrupts and DMA requests for GPIO and I2C modules would not work since their initial configuration is lost after LPDS. PRCMCC3200MCUInit has these settings and will reconfigure these modules.

The Idle Profile example demonstrates this from the lp3p0_restore_soc_data implementation.

Default GPIO settings

All GPIO pins default to Mode 1 on power-up, unless programmed by the MCU. Set all unused pins except the serial flash SPI (pins 11, 12, 13, 14) and JTAG (pin 16, 17, 19, 20) to Mode 0 to prevent any bus contention.

Add following code snippet to void PinMuxConfig(void):

PinModeSet(PIN_X,PIN_MODE_0);

For example, by default I2C is muxed to pins 1 and 2. If the application assigns other pins to the I2C module, this would cause contention. To resolve contention on I2C lines, add following code snippet to void PinMuxConfig(void):

PinModeSet(PIN_01,PIN_MODE_0);
PinModeSet(PIN_02,PIN_MODE_0);

Technical Support

• TI SimpleLink Solutions
• E2E Forums
• www.ti.com