CC3000 Relase Notes
From Texas Instruments Embedded Processors Wiki
Contents |
Important information on CC3000
Description:
- SP-1.5 Release of CC3000 Host Driver and CC3000 chipset.
Upcoming changes:
- Enhancements to CC3000 Host Driver will include support for big endian processors and multiple byte alignment processors
- Enhancements to CC3000 Host Driver will include protection of NVMEM from misuse. Current version does not include protections and caution must be taken when considering to change NVMEM content.
- In current implementation of CC3000 host driver there is no way for application to figure out if all the data that was admited for transmission was transmitted.This information may be valueable when a mode of operation of CC3000 is On->Send Data -> Off at the stage where after sending data the application needs to shut down a device and has no indication when this can be done. This feature will be added to the upcoming releases while for now a static delay of 1 second may be used.
Introduction
CC3000 SP1.5 includes platform independent CC3000 Host Driver Code and example implementation of SPI driver for MSP430.
For additional information regarding the example implementation please refer to: CC3000 Basic Wi-Fi example application for MSP430
Please note that the current version of CC3000 host driver, which is 1.7.2.2 supports IAR 5.30.4 and CCS v5 IDE.
CC3000 Host Driver Package Content
This section describes the content of the Host Driver package:
- CC3000 Host Driver includes:
- Platform independent CC3000 Host Driver Code: Download
- Example implementation of SPI driver for MSP430 : Download - Basic Wi-Fi Application
CC3000 Features
Table 1: Host driver features Supported
| Feature | Description |
|---|---|
| API |
Fully supports CC3000 API's - for more details please refer to: programmers guide |
| BSD socket | Compliant API for application development |
| little endian |
Supports little-endian MCUs |
| SPI implementation |
SPI implementation example for the MSP430 FRAM (MSP-EXP430FR5739)platform |
| memory requirements |
As low as 6KB code size and 4KB data (RAM) size |
Table 2: CC3000 Wi-Fi features overview
| Feature | Description |
|---|---|
| Wi-Fi | Wi-Fi optimized for easy use with microcontroller applications (IEEE802.11b/g) |
| network stack | Embedded IPv4 Network stack |
| DHCP/DNS | DHCP/DNS Client/ARP/ICMP integrated |
| socket | Up to 4 concurrent open sockets |
| Wi-Fi b/g | Wi-Fi b/g band support |
| Security | Open/WEP/WPA/WPA 2 Personal support |
| Select working channel | Channels 1-13 supported |
| Profiles | Connection profile management |
| Preferred connection | Possible to automatically connect to preferred networks. The list of preferred networks is configurable. |
| Fast reconnect | Fast reconnection to specific Access Point |
| FirstTime Configuration | For easy first connection to Access Point - for more details please refer to: CC3000 First Time Configuration Guide |
| SPI | SPI host insterface |
Known Issues
| Headline | Scan doesn't stop after disabling "Auto Start" in configuration policy when no suitable profile was detected |
| Internal numbering | MCS00083108 |
| Description/Scenario | If the Auto Start was configured prior to disable of scans, and no profile found, CC3000 will stay in scanning state. |
| Headline | Scan fails to start |
| Internal numbering | MCS00094185 |
|
Description/Scenario |
Scan doesn't start when "GetScanResults" API command is invoked after reset without previous connection attempts. |
| Headline | Static IP is not correctly displayed after reconfiguration |
| Internal numbering | MCS00094102 |
| Description/Scenario | If the device is configured to use static IP, and connected to the IP, and the IP address is re-configured, the API command NetappIPconfig will return incorrect IP address. |
| Headline | "Packets Sent" in ping report is incorrect |
| Internal numbering | MCS00089990 |
| Description/Scenario | "Packets Sent" in ping report is incorrect: it counts both responses and requests. |
| Headline | "Connected Async Event" arise prior to completion of connection process when using WPA2 security |
| Internal numbering | MCS00091525 |
| Description/Scenario | "Connected Async Event" arise prior to completing 4-way handshake during WPA2 connection. |
| Headline | Get Sockopt API may return an incorrect value |
| Internal numbering | MCS00090753 |
| Description/Scenario | Get_sockopt API function returns an incorrect value of socket timeout and blocking state when the socket is closed. |
| Headline | Adding WPA profile causes disconnect |
| Internal numbering | MCS00086828 |
| Description/Scenario | Addition of WPA profile, during the connected state of CC3000, causes disconnect |
| Headline | Ping report Event reports incorrect number of responses sometimes |
| Internal numbering | MCS00090151 |
| Description/Scenario | Ping report Event reports incorrect number of responses received when some specific ping packet payload is used |
| Headline | Fail to connect to AP with low RSSI |
| Internal numbering | MCS00084892 |
| Description/Scenario | Connection is not initiated to AP with RSSI below -75dBm |
Known Interoperability Issues
| Headline | IOP Connection: Linksys WRT400N |
| Internal numbering | MCS00086252 |
| Description/Scenario | Not able to connect to an AP that is not supporting all basic rates such as Linksys WRT400N |
| Headline | Low throughput with Linksys WRT300N AP. |
| Internal numbering | MCS00086165 |
| Description/Scenario | TCP Tx jiggling 0.1Mbps-3.3Mbps instead of stable 3.3Mbps throughput, when testing with Linksys WRT300N AP. |
| Headline | WEP connection problem with TL-WR740N TP-LINK router |
| Internal numbering | MCS00105533 |
| Description/Scenario | Creating secured connection with the TP LINK wireless router of model TL-WR740N from CC3000, while security type is WEP will fail. |
| Headline | Low TCP throughput with Linksys 350N when operating with CTS protection |
| Internal numbering | MCS00086192 |
| Description/Scenario | TCP throughput is 0.5-0.9Mbps less than expected when operating with CTS protection with Linksys 350N |
| Headline | Low TCP throughput with Linksys 300N. |
| Internal numbering | MCS00086165 |
| Description/Scenario | The TCP throughput is 0.1- 3.3Mbps when running TCP TX traffic instead of stable 3.3Mbps |
| Headline | Periodic connection failure due to no ACK on Assosiation request from CC3000 device with Cisco1250. |
| Internal numbering | MCS00083765 |
| Description/Scenario | Periodic connection failure due to no ACK on Assosiation request from CC3000 device with Cisco1250. |
