Port from Avnet's Internet Of Things full WiGo demo: SmartConfig - WebServer - Exosite - Android sensor Fusion App
Dependencies: mbed CC3000_Hostdriver TEMT6200 TSI Wi-Go_eCompass_Lib_V3 WiGo_BattCharger
Fork of CC3000_Simple_Socket by
Information
This demo uses the old HostDriver.
A newer release using the mbed socket compatible API HostDriver is available at Wi-Go_IOT_Demo_MKII.
Wi-Go Reference Design Overview
For additional information on Wi-Go, please visit http://www.em.avnet.com/wi-go
For additional information on Freescale eCompass, please visit
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=E-Compass
Ported from Avnet's Wi-Go KEIL code.
Special thanks to Jim Carver from Avnet for providing the Wi-Go board and for his assistance.
Multiple Wi-Fi applications are provided within the latest version of Wi-Go software:
- SmartConfig App for auto-setup of Wi-Go network parameters.
- WebServer display of live sensor data.
- Exosite portal sensor data feed by Wi-Go.
- Freescale's Sensor Fusion App data feed by Wi-Go.
Wi-Go is intended for "untethered" portable operation (using it's high-capacity Lithium-Polymer battery). The serial terminal text interface is only required for initial setup, thereafter selection of an application from those available is via finger position on the Touch Slider during the initial 6 second startup period.
Running the Wi-Go Demo Suite
Warning
- We need a large amount of free RAM for the eCompass library:
Before compiling the code, check ifCC3000_MAXIMAL_RX_SIZE
is set to(511 + 1)
incc3000_common.h
.
- The on-board Firmware must be updated to mbed enable a Wi-Go system. Goto the Component page to get the FirmwareUpdate tool (scroll down to the FirmwareUpdate topic).
MAG3110 sensor and eCompass Calibration!
As with the other sensor applications, the eCompass function requires quality calibration data to achieve best accuracy.
For the first 15 seconds after power-up it is recommended that "Figure 8" movements with Wi-Go be done in a smooth, repetitive pattern. Don't touch the slider pad during calibration.
Startup
The RGB LED blinks in a GREEN-ORANGE sequence to inform the user the module is waiting for input.
The RGB LED color designates which of the following Apps to launch.
RGB LED Color | Application to Launch |
Purple | SmartConfig |
Blue | WebServer |
Red | Exosite Data Client |
Green | Android Server |
Swipe your index finger across the slider pad, the RGB LED color will change at approximately 25% intervals.
Removing your finger latches the last color displayed. After about 3 seconds, the selected app will start.
Another app can be selected when the slider pad is touched again within the 3 seconds timeout.
After launch of Exosite or Android Server Apps, the eCompass function then controls the RGB LED.
(not in WebServer mode where RGB LEDs are manually controlled by the User).
RGB LED Color | Direction Indication |
Blue | Near to North |
Green | North |
Red | East / West |
Purple | South |
__Note!__
The D1, D2 and D3 User LEDs on Wi-Go adhere to the following convention for the different Apps
User LED# | Description of function controlling the LED |
D1 | is the board heartbeat, derived from the timer interrupt |
D2 | indicates network activity as follows: Web Server Wi-Go webpage is being served. Exosite Client Wi-Go is sending data. Android App Wi-Go is sending data |
D3 | WLAN Network is Connected |
Detail of Wi-Go Applications
App #1: SmartConfig
See TI's pages on how to use the SmartConfig tool:
- Preferred method : Configuration using the SmartConfig tool
- SmartConfig download: Smart Config and Home Automation
- iOS app : available at Apple app store.
- Android app : download and install the Android SmartConfig Application on a PC.
This file contains the source code as well as the compiled APK file.
The APK file is stored inti\CC3000AndroidApp\SmartConfigCC3X\bin
.
- iOS app : available at Apple app store.
App #2: WebServer display of live sensor data
__Note!__
When using the WebServer for the first time on a Wi-Fi network you will need to determine the IP address that's assigned to Wi-Go by the DHCP Server. To do this, it is recommended you use one of the following two methods:
- While Wi-Go is initially tethered to a laptop via USB, launch of the WebServer Application and note the IP address that is reported on the terminal screen immediately after selection of this App.
- Alternatively, use a 3rd party LAN SCAN type tool to view Wi-Go's IP address.
eg.FING
, - available for free download from Google Play or iTunes App Stores…
Wi-Go's WebServer Application is selected as follows:
- Press RESET, followed by the
eCompass Calibration
(mentioned at the top of this page).
Then use index finger on slider to select the WebServer App (RGB LED = BLUE).
At end of the 3 second selection period the WebServer App shall launch.
- If you are tethered to a laptop and have a terminal open the Wi-Fi network connection confirmation will be seen, eg.
'*** Wi-Go board DHCP assigned IP Address = 192.168.43.102
- Once you have noted Wi-Go's reported IP address, the USB cable may be disconnected and Wi-Go then used as intended, running on it's own battery power.
- Use an Internet Browser on SmartPhone/Tablet/Laptop (connected to same Hot-Spot/Wireless Router subnet), to now connect to the noted Wi-Go IP address and view the WebServer output:
- the Webserver sensor data is auto-updated every 2 seconds a manual refresh (F5 on laptop).
- In the event of an error, press refresh to regenerate the screen.
- Use the mouse (or touch-screen) to exercise the RGB LED output.
App #3: Exosite Data Client
Wi-Go's sensor data gets transmitted via Wi-Fi to a cloud-based Exosite portal where the sensor measurements are displayed graphically on a "dashboard". Users can create unique customized dashboards using drag and drop GUI widgets from the library provided on the Exosite website.
__Note!__
For the Exosite application a "live" connection to the Internet is required !!!
- Press RESET, followed by the
eCompass Calibration
(mentioned at the top of this page).
Then use index finger on slider to select the Exosite Client App (RGB LED = RED) - On launching this App, note Wi-Go's MAC address displayed on your terminal
(if not running a terminal use FING or other WLAN Scan tool to determine Wi-Go's MAC address) - Using your computer's internet browser, go to avnet.exosite.com and sign-up for a free
Avnet Trial
Exosite Account: - On the next screen, click on the Sign-Up Now button in the displayed
Avnet Trial
account option. - Complete the Account Info and Contact Info then click on Create Account (make sure to use a valid email address!).
- Check for new incoming email from avnet.exosite.com to the address you provided and click on the link in this email to activate your new Exosite account.
- Once activated, login using the email address and password that you chose in your registration.
Your Exosite Portal and Dashboard should now display. The first time you log-in to your new account, the default Home dashboard will be displayed, pre-configured with two widgets. On the left is the Welcome widget for tips and information. On the right is the Device List widget.
Dashboards are configurable, so at any time this default dashboard can be changed, widgets deleted and added (Clicking the upside-down triangle icon in a widget's Title bar will allow you to edit it). - Before going further with the Dashboard, you need to connect your Wi-Go device to your Exosite account. Do this by going to the left sidebar and selecting Devices followed by selecting the +Add Device link (on right of screen).
- In the Setup screens that follow, enter the following
Select a supported device | Wi-Go |
Enter device MAC Address | nn:nn:nn:nn:nn:nn [your Wi-Go's MAC address including colons] |
Enter device Name | [choose a descriptive name] |
Enter device Location | [description of your location] |
- Once completed, under Devices the name chosen for the added Wi-Go device should now be listed.
- Click on this new Wi-Go device to examine (and edit if necessary) it's Device Information screen.
- Click the CLOSE button to exit the Device Information screen.
- On your Wi-Go kit now press RESET, followed by the
eCompass Calibration
(mentioned at the top of this page)
and again select the Exosite Client App (RGB LED = RED) using your index finger. - Refresh your browser (press F5) a couple've times until the Active indicator changes to On (Green).
- From the left sidebar click on Home and click on the recently named Wi-Go device which is located under the Device List.
This will bring-up a default dashboard display similar to what's shown below.
(Dashboards are typically accessed via the Dashboards menu entry). Check the dashboard is updating with live data by moving your Wi-Go Kit through different orientations.
- To create a custom dashboard, select Dashboards from the sidebar menu, followed by +Add Dashboard (on right side of Your Dashboards title bar). After completion of the initial configuration screen you will then be able to add Widgets to display the various Wi-Go data sources as well as pictures and text to support your application.
- More guidance on the creation, editing and sharing of custom dashboards is available under the Exosite support pages
App #4: Android Sensor Fusion App
- Press RESET, followed by the
eCompass Calibration
(mentioned at the top of this page)
, then use index finger on slider to select the Android App (RGB LED = GREEN)
- Freescale's ''Xtrinsic Sensor Fusion Toolbox'" will run on Android 3.0 or above phone or tablet. Free to download from Google Play, type Sensor fusion in the search box to find it. freescale.sensors.sfusion
- The Freescale App is well documented. To access the built-in documentation, press the NAV button at top of screen followed by Documentation from the scroll-down menu:
- Freescale's sensors site provides additional resources such as this overview:
free-android-app-teaches-sensor-fusion-basics
- Go to the Options Menu and select Preferences…
- The following items need to be taken care of:
Enter WiGo's IP address |
Enter the SSID (of the Hot-Spot or Wireless Access Point used by Wi-Go) |
- Press Save and Exit!
- Exit the Application completely then re-launch the Sensor Fusion Application.
- Select the ''Source/Algorithm'" menu and change the data source to Wi-Go mag/accel
- The Android App should now be displaying a 3-D image of Wi-Go that you can rotate and flip-over by moving the Wi-Go board accordingly…
- Use NAV > Device View to display if this view does not come-up by default.
- A Serial Terminal connection is not necessary but if you happen to have one open you should see the following messages as Wi-Go connects to the Android App:
"Server waiting for connection" followed by
"connected, transmit buffer size= 96", and then
"input = 0123456789"
at which time Wi-Go starts streaming data to the Android App.
cc3000.h@0:a8e46e27d041, 2013-08-11 (annotated)
- Committer:
- frankvnk
- Date:
- Sun Aug 11 09:46:26 2013 +0000
- Revision:
- 0:a8e46e27d041
- Child:
- 1:32d1ef95eceb
First release
Who changed what in which revision?
User | Revision | Line number | New contents of line |
---|---|---|---|
frankvnk | 0:a8e46e27d041 | 1 | /***************************************************************************** |
frankvnk | 0:a8e46e27d041 | 2 | * |
frankvnk | 0:a8e46e27d041 | 3 | * cc3000.h - CC3000 Function Definitions |
frankvnk | 0:a8e46e27d041 | 4 | * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/ |
frankvnk | 0:a8e46e27d041 | 5 | * |
frankvnk | 0:a8e46e27d041 | 6 | * Redistribution and use in source and binary forms, with or without |
frankvnk | 0:a8e46e27d041 | 7 | * modification, are permitted provided that the following conditions |
frankvnk | 0:a8e46e27d041 | 8 | * are met: |
frankvnk | 0:a8e46e27d041 | 9 | * |
frankvnk | 0:a8e46e27d041 | 10 | * Redistributions of source code must retain the above copyright |
frankvnk | 0:a8e46e27d041 | 11 | * notice, this list of conditions and the following disclaimer. |
frankvnk | 0:a8e46e27d041 | 12 | * |
frankvnk | 0:a8e46e27d041 | 13 | * Redistributions in binary form must reproduce the above copyright |
frankvnk | 0:a8e46e27d041 | 14 | * notice, this list of conditions and the following disclaimer in the |
frankvnk | 0:a8e46e27d041 | 15 | * documentation and/or other materials provided with the |
frankvnk | 0:a8e46e27d041 | 16 | * distribution. |
frankvnk | 0:a8e46e27d041 | 17 | * |
frankvnk | 0:a8e46e27d041 | 18 | * Neither the name of Texas Instruments Incorporated nor the names of |
frankvnk | 0:a8e46e27d041 | 19 | * its contributors may be used to endorse or promote products derived |
frankvnk | 0:a8e46e27d041 | 20 | * from this software without specific prior written permission. |
frankvnk | 0:a8e46e27d041 | 21 | * |
frankvnk | 0:a8e46e27d041 | 22 | * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS |
frankvnk | 0:a8e46e27d041 | 23 | * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT |
frankvnk | 0:a8e46e27d041 | 24 | * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR |
frankvnk | 0:a8e46e27d041 | 25 | * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT |
frankvnk | 0:a8e46e27d041 | 26 | * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, |
frankvnk | 0:a8e46e27d041 | 27 | * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT |
frankvnk | 0:a8e46e27d041 | 28 | * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, |
frankvnk | 0:a8e46e27d041 | 29 | * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY |
frankvnk | 0:a8e46e27d041 | 30 | * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
frankvnk | 0:a8e46e27d041 | 31 | * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE |
frankvnk | 0:a8e46e27d041 | 32 | * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
frankvnk | 0:a8e46e27d041 | 33 | * |
frankvnk | 0:a8e46e27d041 | 34 | *****************************************************************************/ |
frankvnk | 0:a8e46e27d041 | 35 | |
frankvnk | 0:a8e46e27d041 | 36 | #ifndef CC3000_H |
frankvnk | 0:a8e46e27d041 | 37 | #define CC3000_H |
frankvnk | 0:a8e46e27d041 | 38 | |
frankvnk | 0:a8e46e27d041 | 39 | #include "wlan.h" |
frankvnk | 0:a8e46e27d041 | 40 | |
frankvnk | 0:a8e46e27d041 | 41 | //***************************************************************************** |
frankvnk | 0:a8e46e27d041 | 42 | // |
frankvnk | 0:a8e46e27d041 | 43 | //! \addtogroup cc3000 |
frankvnk | 0:a8e46e27d041 | 44 | //! @{ |
frankvnk | 0:a8e46e27d041 | 45 | // |
frankvnk | 0:a8e46e27d041 | 46 | //***************************************************************************** |
frankvnk | 0:a8e46e27d041 | 47 | |
frankvnk | 0:a8e46e27d041 | 48 | /** CC3000 Functions |
frankvnk | 0:a8e46e27d041 | 49 | * |
frankvnk | 0:a8e46e27d041 | 50 | */ |
frankvnk | 0:a8e46e27d041 | 51 | #ifdef __cplusplus |
frankvnk | 0:a8e46e27d041 | 52 | extern "C" { |
frankvnk | 0:a8e46e27d041 | 53 | #endif |
frankvnk | 0:a8e46e27d041 | 54 | |
frankvnk | 0:a8e46e27d041 | 55 | extern DigitalOut ledr; |
frankvnk | 0:a8e46e27d041 | 56 | extern DigitalOut ledg; |
frankvnk | 0:a8e46e27d041 | 57 | extern DigitalOut ledb; |
frankvnk | 0:a8e46e27d041 | 58 | extern DigitalOut led1; |
frankvnk | 0:a8e46e27d041 | 59 | extern DigitalOut led2; |
frankvnk | 0:a8e46e27d041 | 60 | extern DigitalOut led3; |
frankvnk | 0:a8e46e27d041 | 61 | |
frankvnk | 0:a8e46e27d041 | 62 | #define RED_OFF ledr = 1; |
frankvnk | 0:a8e46e27d041 | 63 | #define RED_ON ledr = 0; |
frankvnk | 0:a8e46e27d041 | 64 | #define RED_TOGGLE ledr = !ledr; |
frankvnk | 0:a8e46e27d041 | 65 | #define GREEN_OFF ledg = 1; |
frankvnk | 0:a8e46e27d041 | 66 | #define GREEN_ON ledg = 0; |
frankvnk | 0:a8e46e27d041 | 67 | #define GREEN_TOGGLE ledg = !ledg; |
frankvnk | 0:a8e46e27d041 | 68 | #define BLUE_OFF ledb = 1; |
frankvnk | 0:a8e46e27d041 | 69 | #define BLUE_ON ledb = 0; |
frankvnk | 0:a8e46e27d041 | 70 | #define BLUE_TOGGLE ledb = !ledb; |
frankvnk | 0:a8e46e27d041 | 71 | #define LED_D1_OFF led1 = 1; |
frankvnk | 0:a8e46e27d041 | 72 | #define LED_D1_ON led1 = 0; |
frankvnk | 0:a8e46e27d041 | 73 | #define LED_D1_TOGGLE led1 = !led1; |
frankvnk | 0:a8e46e27d041 | 74 | #define LED_D2_OFF led2 = 1; |
frankvnk | 0:a8e46e27d041 | 75 | #define LED_D2_ON led2 = 0; |
frankvnk | 0:a8e46e27d041 | 76 | #define LED_D2_TOGGLE led2 = !led2; |
frankvnk | 0:a8e46e27d041 | 77 | #define LED_D3_OFF led3 = 1; |
frankvnk | 0:a8e46e27d041 | 78 | #define LED_D3_ON led3 = 0; |
frankvnk | 0:a8e46e27d041 | 79 | #define LED_D3_TOGGLE led3 = !led3; |
frankvnk | 0:a8e46e27d041 | 80 | |
frankvnk | 0:a8e46e27d041 | 81 | #define SOCKET_INACTIVE_ERR -57 |
frankvnk | 0:a8e46e27d041 | 82 | #define NUM_STATES 6 |
frankvnk | 0:a8e46e27d041 | 83 | #define MAX_SSID_LEN 32 |
frankvnk | 0:a8e46e27d041 | 84 | #define FIRST_TIME_CONFIG_SET 0xAA |
frankvnk | 0:a8e46e27d041 | 85 | #define NETAPP_IPCONFIG_MAC_OFFSET (20) |
frankvnk | 0:a8e46e27d041 | 86 | #define CC3000_APP_BUFFER_SIZE (5) |
frankvnk | 0:a8e46e27d041 | 87 | #define CC3000_RX_BUFFER_OVERHEAD_SIZE (20) |
frankvnk | 0:a8e46e27d041 | 88 | |
frankvnk | 0:a8e46e27d041 | 89 | // CC3000 State Machine Definitions |
frankvnk | 0:a8e46e27d041 | 90 | enum cc3000StateEnum |
frankvnk | 0:a8e46e27d041 | 91 | { |
frankvnk | 0:a8e46e27d041 | 92 | CC3000_UNINIT = 0x01, // CC3000 Driver Uninitialized |
frankvnk | 0:a8e46e27d041 | 93 | CC3000_INIT = 0x02, // CC3000 Driver Initialized |
frankvnk | 0:a8e46e27d041 | 94 | CC3000_ASSOC = 0x04, // CC3000 Associated to AP |
frankvnk | 0:a8e46e27d041 | 95 | CC3000_IP_ALLOC = 0x08, // CC3000 has IP Address |
frankvnk | 0:a8e46e27d041 | 96 | CC3000_SERVER_INIT = 0x10, // CC3000 Server Initialized |
frankvnk | 0:a8e46e27d041 | 97 | CC3000_CLIENT_CONNECTED = 0x20 // CC3000 Client Connected to Server |
frankvnk | 0:a8e46e27d041 | 98 | }; |
frankvnk | 0:a8e46e27d041 | 99 | |
frankvnk | 0:a8e46e27d041 | 100 | |
frankvnk | 0:a8e46e27d041 | 101 | /** Set basic controls and parameters for the HostDriver. |
frankvnk | 0:a8e46e27d041 | 102 | * @param none |
frankvnk | 0:a8e46e27d041 | 103 | * @return none |
frankvnk | 0:a8e46e27d041 | 104 | */ |
frankvnk | 0:a8e46e27d041 | 105 | extern void Init_HostDriver(void); |
frankvnk | 0:a8e46e27d041 | 106 | |
frankvnk | 0:a8e46e27d041 | 107 | /** |
frankvnk | 0:a8e46e27d041 | 108 | * Turn all LEDs Off |
frankvnk | 0:a8e46e27d041 | 109 | * @param none |
frankvnk | 0:a8e46e27d041 | 110 | * @return none |
frankvnk | 0:a8e46e27d041 | 111 | */ |
frankvnk | 0:a8e46e27d041 | 112 | void initLEDs(void); |
frankvnk | 0:a8e46e27d041 | 113 | |
frankvnk | 0:a8e46e27d041 | 114 | /** Return a pointer to the driver patch. |
frankvnk | 0:a8e46e27d041 | 115 | * Since there is no patch, 0 is returned\n |
frankvnk | 0:a8e46e27d041 | 116 | * (the patches are taken from the EEPROM and not from the host)\n |
frankvnk | 0:a8e46e27d041 | 117 | * @param pointer to the length |
frankvnk | 0:a8e46e27d041 | 118 | * @return NULL |
frankvnk | 0:a8e46e27d041 | 119 | */ |
frankvnk | 0:a8e46e27d041 | 120 | char *sendDriverPatch(unsigned long *Length); |
frankvnk | 0:a8e46e27d041 | 121 | |
frankvnk | 0:a8e46e27d041 | 122 | /** Return a pointer to the bootloader patch. |
frankvnk | 0:a8e46e27d041 | 123 | * Since there is no patch, 0 is returned \n |
frankvnk | 0:a8e46e27d041 | 124 | * (the patches are taken from the EEPROM and not from the host)\n |
frankvnk | 0:a8e46e27d041 | 125 | * @param pointer to the length |
frankvnk | 0:a8e46e27d041 | 126 | * @return NULL |
frankvnk | 0:a8e46e27d041 | 127 | */ |
frankvnk | 0:a8e46e27d041 | 128 | char *sendBootLoaderPatch(unsigned long *Length); |
frankvnk | 0:a8e46e27d041 | 129 | |
frankvnk | 0:a8e46e27d041 | 130 | /** Return a pointer to the firmware patch. |
frankvnk | 0:a8e46e27d041 | 131 | * Since there is no patch, 0 is returned\n |
frankvnk | 0:a8e46e27d041 | 132 | * (the patches are taken from the EEPROM and not from the host)\n |
frankvnk | 0:a8e46e27d041 | 133 | * @param pointer to the length |
frankvnk | 0:a8e46e27d041 | 134 | * @return NULL |
frankvnk | 0:a8e46e27d041 | 135 | */ |
frankvnk | 0:a8e46e27d041 | 136 | char *sendWLFWPatch(unsigned long *Length); |
frankvnk | 0:a8e46e27d041 | 137 | |
frankvnk | 0:a8e46e27d041 | 138 | /** Read Wlan Interrupt pin. |
frankvnk | 0:a8e46e27d041 | 139 | * @param none |
frankvnk | 0:a8e46e27d041 | 140 | * @return wlan interrup pin level |
frankvnk | 0:a8e46e27d041 | 141 | */ |
frankvnk | 0:a8e46e27d041 | 142 | long ReadWlanInterruptPin(void); |
frankvnk | 0:a8e46e27d041 | 143 | |
frankvnk | 0:a8e46e27d041 | 144 | /** Enable waln IrQ pin. |
frankvnk | 0:a8e46e27d041 | 145 | * @param none |
frankvnk | 0:a8e46e27d041 | 146 | * @return none |
frankvnk | 0:a8e46e27d041 | 147 | */ |
frankvnk | 0:a8e46e27d041 | 148 | void WlanInterruptEnable(void); |
frankvnk | 0:a8e46e27d041 | 149 | |
frankvnk | 0:a8e46e27d041 | 150 | /** Disable waln IrQ pin. |
frankvnk | 0:a8e46e27d041 | 151 | * @param none |
frankvnk | 0:a8e46e27d041 | 152 | * @return none |
frankvnk | 0:a8e46e27d041 | 153 | */ |
frankvnk | 0:a8e46e27d041 | 154 | void WlanInterruptDisable(void); |
frankvnk | 0:a8e46e27d041 | 155 | |
frankvnk | 0:a8e46e27d041 | 156 | /** WriteWlanPin. |
frankvnk | 0:a8e46e27d041 | 157 | * @param val (1: enable - 0: disable) |
frankvnk | 0:a8e46e27d041 | 158 | * @return none |
frankvnk | 0:a8e46e27d041 | 159 | */ |
frankvnk | 0:a8e46e27d041 | 160 | void WriteWlanPin( unsigned char val ); |
frankvnk | 0:a8e46e27d041 | 161 | |
frankvnk | 0:a8e46e27d041 | 162 | /** Connect to an Access Point using the specified SSID. |
frankvnk | 0:a8e46e27d041 | 163 | * @param ssidName is a string of the AP's SSID |
frankvnk | 0:a8e46e27d041 | 164 | * @return none |
frankvnk | 0:a8e46e27d041 | 165 | */ |
frankvnk | 0:a8e46e27d041 | 166 | int ConnectUsingSSID(char * ssidName); |
frankvnk | 0:a8e46e27d041 | 167 | |
frankvnk | 0:a8e46e27d041 | 168 | /** Handle asynchronous events from CC3000 device. |
frankvnk | 0:a8e46e27d041 | 169 | * @param lEventType Event type |
frankvnk | 0:a8e46e27d041 | 170 | * @param data |
frankvnk | 0:a8e46e27d041 | 171 | * @param length |
frankvnk | 0:a8e46e27d041 | 172 | * @return none |
frankvnk | 0:a8e46e27d041 | 173 | */ |
frankvnk | 0:a8e46e27d041 | 174 | void CC3000_UsynchCallback(long lEventType, char * data, unsigned char length); |
frankvnk | 0:a8e46e27d041 | 175 | |
frankvnk | 0:a8e46e27d041 | 176 | /** Initialize a CC3000 device and triggers it to start operation. |
frankvnk | 0:a8e46e27d041 | 177 | * @param none |
frankvnk | 0:a8e46e27d041 | 178 | * @return none |
frankvnk | 0:a8e46e27d041 | 179 | */ |
frankvnk | 0:a8e46e27d041 | 180 | int initDriver(void); |
frankvnk | 0:a8e46e27d041 | 181 | |
frankvnk | 0:a8e46e27d041 | 182 | /** Return the highest state which we're in. |
frankvnk | 0:a8e46e27d041 | 183 | * @param None |
frankvnk | 0:a8e46e27d041 | 184 | * @return none |
frankvnk | 0:a8e46e27d041 | 185 | */ |
frankvnk | 0:a8e46e27d041 | 186 | char highestCC3000State(void); |
frankvnk | 0:a8e46e27d041 | 187 | |
frankvnk | 0:a8e46e27d041 | 188 | /** Return the current state bits. |
frankvnk | 0:a8e46e27d041 | 189 | * @param None |
frankvnk | 0:a8e46e27d041 | 190 | * @return none |
frankvnk | 0:a8e46e27d041 | 191 | */ |
frankvnk | 0:a8e46e27d041 | 192 | char currentCC3000State(void); |
frankvnk | 0:a8e46e27d041 | 193 | |
frankvnk | 0:a8e46e27d041 | 194 | /** Sets a state from the state machine. |
frankvnk | 0:a8e46e27d041 | 195 | * @param None |
frankvnk | 0:a8e46e27d041 | 196 | * @return none |
frankvnk | 0:a8e46e27d041 | 197 | */ |
frankvnk | 0:a8e46e27d041 | 198 | void setCC3000MachineState(char stat); |
frankvnk | 0:a8e46e27d041 | 199 | |
frankvnk | 0:a8e46e27d041 | 200 | /** Unsets a state from the state machine. |
frankvnk | 0:a8e46e27d041 | 201 | * Also handles LEDs.\n |
frankvnk | 0:a8e46e27d041 | 202 | * @param None |
frankvnk | 0:a8e46e27d041 | 203 | * @return none |
frankvnk | 0:a8e46e27d041 | 204 | */ |
frankvnk | 0:a8e46e27d041 | 205 | void unsetCC3000MachineState(char stat); |
frankvnk | 0:a8e46e27d041 | 206 | |
frankvnk | 0:a8e46e27d041 | 207 | /** Resets the State Machine. |
frankvnk | 0:a8e46e27d041 | 208 | * @param None |
frankvnk | 0:a8e46e27d041 | 209 | * @return none |
frankvnk | 0:a8e46e27d041 | 210 | */ |
frankvnk | 0:a8e46e27d041 | 211 | void resetCC3000StateMachine(void); |
frankvnk | 0:a8e46e27d041 | 212 | |
frankvnk | 0:a8e46e27d041 | 213 | /** Obtains the CC3000 Connection Information from the CC3000. |
frankvnk | 0:a8e46e27d041 | 214 | * @param None |
frankvnk | 0:a8e46e27d041 | 215 | * @return none |
frankvnk | 0:a8e46e27d041 | 216 | */ |
frankvnk | 0:a8e46e27d041 | 217 | #ifndef CC3000_TINY_DRIVER |
frankvnk | 0:a8e46e27d041 | 218 | tNetappIpconfigRetArgs * getCC3000Info(void); |
frankvnk | 0:a8e46e27d041 | 219 | #endif |
frankvnk | 0:a8e46e27d041 | 220 | |
frankvnk | 0:a8e46e27d041 | 221 | /** Trigger a smart configuration process on CC3000. |
frankvnk | 0:a8e46e27d041 | 222 | * It exits upon completion of the process.\n |
frankvnk | 0:a8e46e27d041 | 223 | * @param None |
frankvnk | 0:a8e46e27d041 | 224 | * @return none |
frankvnk | 0:a8e46e27d041 | 225 | */ |
frankvnk | 0:a8e46e27d041 | 226 | void StartSmartConfig(void); |
frankvnk | 0:a8e46e27d041 | 227 | |
frankvnk | 0:a8e46e27d041 | 228 | #ifdef __cplusplus |
frankvnk | 0:a8e46e27d041 | 229 | } |
frankvnk | 0:a8e46e27d041 | 230 | #endif // __cplusplus |
frankvnk | 0:a8e46e27d041 | 231 | |
frankvnk | 0:a8e46e27d041 | 232 | //***************************************************************************** |
frankvnk | 0:a8e46e27d041 | 233 | // |
frankvnk | 0:a8e46e27d041 | 234 | // Close the Doxygen group. |
frankvnk | 0:a8e46e27d041 | 235 | //! @} |
frankvnk | 0:a8e46e27d041 | 236 | // |
frankvnk | 0:a8e46e27d041 | 237 | //***************************************************************************** |
frankvnk | 0:a8e46e27d041 | 238 | |
frankvnk | 0:a8e46e27d041 | 239 | #endif // CC3000_H |
frankvnk | 0:a8e46e27d041 | 240 |