This Blog will explain the sample application appliance.c that comes with the WICED SDK.
Thanks to David Armour for putting this together.
The Appliance application demonstrates how a simple web page can be used to send information to a UART when a button on the webpage is clicked. The application mimics a very basic user interface to control a home appliance such as a washing machine or dryer.
See attached presentation.Show Less
Wireless Internet Connectivity for Embedded Devices for Bluetooth SMART
The Cypress WICED SMART™ Software Development Kit eases development effort and simplifies the implementation of wireless connectivity in an array of consumer, medical, fitness and home automation devices. It is a complete cable replacement for connecting to smartphones, tablets and PCs.
Developers use the WICED SMART™ development kit to create secure Bluetooth SMART wireless applications. The development kit consists of:
The WICED™ SMART Development System enables Bluetooth SMART connectivity for:
WICED SMART™ Development Kits
Broadcom provides a WICED SMART™ Software Development Kit and is working with partners to deliver turnkey hardware solutions to enable Bluetooth Smart connectivity.
Wireless Internet Connectivity for Embedded Devices (Wi-Fi and Bluetooth SmartBridge™)
Use the WICED Development System to create secure embedded wireless networking applications on an existing product microcontroller, or on an additional WICED module that includes a microcontroller. Either way, the comprehensive and size-optimized WICED application library and embedded Wi-Fi driver work together with a Broadcom® embedded wireless LAN chip to provide seamless wireless connectivity. Apple MFi HomeKit ready and Universal Bluetooth Smart to WLAN bridge designs are also available.
If you need ultra low power wireless, use the included WICED SmartBridge™ API to provide seamless data aggregation and internet connectivity for WICED Smart devices as well.
The WICED™ Development System enables Wi-Fi connectivity and Bluetooth bridging for:
Find out more in our WICED™ Frequently Asked Questions section: View FAQShow Less
What is WICED?
What's included in WICED™ Studio/WICED SDK?
The WICED Studio/WICED SDK includes :
Which Operating Systems does WICED Studio/WICED SDK run on?
How much does the WICED Studio/WICED SDK cost?
Which RTOS & Network Stacks are available within WICED Studio/WICED SDK?
What if I want to use a different RTOS or Network Stack?
Does the SDK support Wi-Fi Protected Setup (WPS)?
How much Flash and RAM does my application need?
Where do I buy WICED™ evaluation boards?
Does WICED™ support SSL/TLS security?
Which Microcontrollers are supported by the SDK?
Does the WICED™ SDK support Wi-Fi Direct?
Does the Wi-Fi security supplicant run on the microcontroller?
Many "snips" or applications require you to associate to an existing router so you can obtain an IP address, ping devices, send traffic, and various other things.
This is simple to do by editing the wifi_config_dct header file.
In the directory on the left side of the IDE in the application you are running, there is a header file "wifi_config_dct.h" listed.
For example: <WICED-SDK>/apps/snip/apsta/wifi_config_dct.h
If you open this in the editor window and scroll down, you will see the CLIENT_AP_SSID and CLIENT_AP_PASSPHRASE" define values.
Simply edit these to match your router credentials and save the file.
In the example below, the SSID broadcasting is ASUS and the PASSPHRASE is 12345678.
Compile, download and run the target and you will have success associating the the AP.
In the terminal window you will see the association details and the IP address:
This allows you to use a terminal emulation application such as TeraTerm, PuTTY or CoolTerm (OS X) to communicate with the device from the USB port on your PC.
After installing the terminal emulator of your choice you will need to know which COM port it is on. In the device manager of Windows you can see this.
Next you will need to configure the emulator (PuTTY is used here). In the case above it is on COM5 so you will need to go to the Serial port settings of your Terminal Program and change it to COM5. The setting default is probably 9600-8-1-N but should be changed to 115200-8-1-N, shown below. Next go to the Session category on the left side and make sure that Serial is chosen as the connection type and then open the terminal.
When working correctly, you will see the ">" prompt and output to the terminal.
When you press the reset button on the module, you will see output to the terminal window, and some useful information depending on what you are running.
Note: Sometimes the terminal has to be reset. If you are not getting any output, close the terminal, reopen and setup serial port again.
From time to time we will blog useful information here related to WICED WiFi.
We would like to keep this interactive, so if you have suggestions on what you would like to see here, please comment or message me. We will keep things generic, so everyone can benefit.
What is WICED SMART™?
What is included in the WICED SMART™ SDK?
The WICED SMART™ SDK includes :
How much does the SDK cost?
Which Operating Systems does the SDK run on?
Which version of the Java Runtime Environment is Required?
Is the stack included with the SDK?
How much Flash and RAM does my application need?
Where do I buy WICED SMART™ evaluation boards?
Does WICED SMART™ support any Smartphone or Tablet applications?
Does the WICED SMART™ SDK enable Bluetooth Smart data aggregation and connectivity to the internet?
Where do I get support?
Answer: If the physical connections of the USB-UART Bridge (shown in Figure 1) are made before opening the COM port interfacing applications such as hyperterminal, PuTTY, TeraTerm, or any other software application that reads data from the KitBridge COM interface, you might run into a UART read buffer overflow condition in the Bridge. This condition occurs when there is continuous data transfer from the UART connections of the bridge, but the PC does not read this data until the COM port interface application is invoked. If buffer overflow happens, you will observe continuous inflow of data in the COM port interface software even if there is no communication on the UART side of the KitBridge. The current bridge firmware does not clear the buffer overflow flag when it is set and hence the inflow of data through the COM port interface continues even if the physical connections to the UART (Tx, Rx) are removed.
This issue is found in the KitProg firmware revision 2.02 and got fixed in the later version of the KitProg. It’s recommended that you upgrade to the latest version of the KitProg.Show Less