Wi-Fi Combo Forum Discussions
text.format{('custom.tabs.no.results')}
Hi,
This is going to sound like madness but I can't really find a straight answer: Can you actually develop directly for the 43362? There is certainly a strong emphasis on using it as an SPI peripheral, but can it be run standalone?
Thanks,
Dave
Show LessI'm using 2.4. I'd like to continue the build despite a few warnings.
I am attempting to create an HTTP server that can service multiple persistent connections, but it is getting slowed down by the need to look for new connection attempts using wiced_tcp_accept(). Is there a way to make this non-blocking, or would it simply be easier to spawn a new thread to deal with new connection attempts?
Show LessWiConnect which is built on top of WICED is in actual fact part of a larger sophisticated application framework installed on all ACKme modules. The framework provides a hardened bootloader, read/write file system, safemode recovery mechanism, and secure over-the-air (OTA) upgrade capability.
Secure OTA Upgrade
ACKme manages a secure online OTA server that offers each ACKme module with the ability to securely upgrade individual files, applications or an entire firmware bundle. The OTA command is used to upgrade module firmware using the OTA server on this port.
The OTA process is secured by industry standard TLS1.0/HTTPS using server and client certificates that forces
- ACKme devices to verify the identity of the ACKme OTA server; and
- The ACKme OTA server to verify the identity of each individual ACKme device.
Each ACKme device is uniquely identified by a 128-bit hardware universally unique identifier (UUID).
HTTPS is the same security your web browser uses to make secure transactions with your bank over the internet. ACKme adds an additional layer of security, since the ACKme OTA server checks the unique security certificate and hardware UUID of each ACKme device that requests an upgrade.
This is actually a major step away from the typical and open FTP implementation found in other solutions. These other solutions run the risk malicious firmware replacement that could cause problems in the field.
Safe Mode
Safe mode operation is guaranteed in the unlikely event the module is configured in a way that causes repeated and/or unexpected reboots. The bootloader automatically switches to safe mode after eight exceptions occur with the offending boot application. Safe mode is indicated by the system.safemode variable.
Factory Reset
Once in safe mode, the module runs the upgrade application. The upgrade app provides the ability to upgrade the firmware, or switch back to WiConnect using the upgrade_app faults_reset
command andsystem.boot_app variable.
The module may be factory reset using the factory_reset command or by holding the factory reset pin (GPIO 0 on all ACKme modules) high for more than 10 seconds through a hardware reset. After a successful factory reset, all variables are set to factory defaults and the module reboots. To avoid accidental factory reset, the Wi-Fi MAC address must be provided when calling the factory_reset command.
More can be found on WiConnect at its dedicated site: http://wiconnect.ack.me
More can be found on ACKme modules at: http://ack.me
WICED Wi-Fi ForumsACKme Networks
Show LessI have this Bridge_1 board but got "OpenOCD failed" error when downloading the appliance sample. It seems that I am missing FTDI driver and someone in the forum mentioned about a batch file for installation. Could anyone share the link to that batch file? Or is there any other solution to this?
Show LessHi,
I am using BCM943362WCD4 module and SDK 2.4.0.
In my application, I am receiving commands through TCP and depending on the commands, I am doing a soft reset. I need to store some values in mcu flash before reset so that I can read them after reset. Does the SDK has any API for this ? Please help me in this regard.
Thanks.
Show LessWiConnect sits on top of WICED to enable a faster time to market through an easy to use API.
WiConnect runs as standard on all ACKme Networks Wi-Fi modules
WiConnect File System (WCFS)
Most connected applications require the ability to store configuration information or cache local data. WiConnect provides a reliable read/write filesystem and on-board flash storage to satisfy application storage requirements. With just a few simple commands, WiConnect provides your application with complete access to local and network connected storage.
Commands available to create, delete and open files are available here, and file contents can be easily accessed using one or more stream commands available here.
Here's a quick example showing how to create, manipulate then delete a file …
WiConnect Commands | Description |
---|---|
|
|
File Listing
Most ACKme Wi-Fi modules contain a microcontroller with internal flash, and an external (to the MCU) serial flash. To obtain a listing of all files on the MCU-internal flash and external serial flash, use the ls command. Users of WiConnect are permitted to write files to serial flash only.
> ls
!# | Type | Flags | Hnd | Size | Version | Filename |
---|---|---|---|---|---|---|
#00 | i-01 | 0009 | 0 | 191677 | 1.1.0 | wifi_fw.bin |
#01 | i-80 | 001B | 47 | 85556 | 1.1.0 | wiconnect.exe |
#02 | i-00 | 001B | 163 | 352516 | 1.1.0 | upgrade_app.exe |
#03 | e-FE | 0001 | 1 | 9641 | 1.1.0 | /setup/index.html |
#04 | e-FD | 0009 | 51 | 189 | 1.1.0 | default_setup.script |
#05 | e-FE | 0001 | 52 | 18067 | 1.1.0 | /setup/images.png |
#06 | e-FE | 0001 | 78 | 10525 | 1.1.0 | /setup/index.css.gz |
#07 | e-FB | 0001 | 81 | 27934 | 1.1.0 | command_help.csv |
#08 | e-03 | 0009 | 175 | 1162 | 1.1.0 | geotrust_ca.pem |
#09 | e-FE | 0001 | 176 | 38779 | 1.1.0 | /setup/index.js.gz |
#10 | e-FE | 0001 | 186 | 1853 | 1.1.0 | /favicon.ico.gz |
File Types
The file type of files on the MCU internal flash is pre-pended with 'i', and the file type of files on the serial flash is pre-pended with 'e'. WiConnect file types are enumerated in the following table.
File type | ID |
---|---|
UPGRADE_APP | 0x00 |
WIFI_FW | 0x01 |
SHARED_LIB | 0x02 |
TLS_CERT | 0x03 |
TXT_LOG | 0x04 |
DCT | 0x05 |
MISC_APP | 0x80 |
WICONNECT_APP | 0x81 |
TEMPORARY | 0xF9 |
GPIO_CONFIG | 0xFA |
COMMAND_HELP | 0xFB |
SDC_CAPS | 0xFC |
SETUP_SCRIPT | 0xFD |
MISC_FIX_LEN | 0xFE |
TYPE_INVALID | 0xFF |
File Checksum
The checksum used on individual files is calculated using a CCITT CRC-16 algorithm with polynomial 0x1021
WICED Wi-Fi ForumsACKme Networks
Show Less