Wi-Fi Combo Forum Discussions
There are several code snippets within the SDK to demo the soft-access point feature (e.g. aptsa, udp_receive, udp_transmit). One crude form of WiFi network security (security through obscurity) is called "network cloaking". When cloaked, the 32-byte SSID information is not broadcast by the SoftAP in its beacon frames.
Question: What code changes do I make to hide the Service Set IDentification (SSID) information and thus become cloaked?
Solution: Modify the IOVAR called "closednet" as follows:
data = (uint32_t*) wiced_get_iovar_buffer( &buffer, (uint16_t) 4, "closednet" );
data[0] = (uint32_t) 1;
retval = wiced_send_iovar( SDPCM_SET, buffer, 0, SDPCM_AP_INTERFACE );
You can execute this after the soft AP is brought up or you can modify wiced_wifi_start_ap() to do it before the AP is brought up.
You cannot execute this before the start of wiced_wifi_start_ap() as the AP interface has not yet been created.
Note: Network cloaking by hiding the SSID is a fairly weak form of security because the SSID still gets sent in plain-text form by the station (STA) during an association request. It is trivial to reveal it with a packet sniffer operating in promiscuous mode.
Show LessHi Sir,
Does WICED(43362) support ADHOC feature? If yes, does it support in f/w or driver? Is there ADHOC API exposed? How to invoke the API? Thanks!
James
Show LessWICED could support i.MX28 Freescale? The OS is Linux 2.6
Best regards,
How many WiFi Direct clients can be connected to a single WICED Soft AP? Also, is the number of normal client connections the same? If not, how many of those are allowed?
Show LessI tried to test a release of the WICED SDK. But build error occurred while compiling the SDK. I attached error log, could you let me know why this happened to?
WICED SDK 2.4.0
Board: BCM943362WCD4_EVB
and errors:
CONSOLE:
**** Build of configuration Default for project Wiced-SDK ****
C:\Users\Documents\WICED\Wiced-SDK-2.4.0\Wiced-SDK\make.exe Default
Making config file for first time
wiced_config.mk:149: *** Unknown component: Default. Stop.
make: *** No rule to make target 'build/Default/config.mk', needed by 'main_app'. Stop.
Description | Resource | Path | Location | Type |
make: *** No rule to make target 'build/Default/config.mk', needed by 'main_app'. Stop. | Wiced-SDK | C/C++ Problem | ||
make: *** Unknown component: Default. Stop. | wiced_config.mk | /Wiced-SDK | line 149 | C/C++ Problem |
Invalid project path: Include path not found (Wiced-SDK\Tools\ARM_GNU\arm-none-eabi\include). | Wiced-SDK | pathentry | Path Entry Problem |
When I build show this:
Error exist in the active configuration of project "WICED-SDK"
Exception ocurred during launch. Reason: Program files does not exist.
Can we help me? Thanks!
Show LessHi,
Is cryptography functions in wicked_security.h thread safe? If say i'm calling aes_crypt_ecb on more than 1 different thread, will there be any issues (we have to assume there is a chance aes_crypt_ecb gets interrupted on one thread while another thread calls aes_crypt_ecb again)? thanks in advance.
Show Less[WICED-SDK-2.2.0]
I am trying to bring up a new eval board, but the USB does not enumerate
properly to show the WICED USB-JTAG and WICED USB-serial port.
Here is what is happening:
- Connect the USB cable to the USB interface to the PC.
- We can get normal system message after reset from one UART.
- Compile the target snip.scan-BCMUSI11 download run
The download failed with the following message:
Downloading Bootloader ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading Application ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading DCT ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Resetting target
make: *** [run] Error 1
So the the UART seems to work, but the USB-JTAG does not. Why?
I have attached a couple of pictures showing the USB ports in the Windows device manager
Show LessTo define a WEP key in an application wifi_config_dct.h you must:
- #define CLIENT_AP_SECURITY WICED_SECURITY_WEP_PSK
- #define CLIENT_AP_PASSPHRASE "x00x05""x01x02x03x04x05" // For a 40-bit key
where :
"x00" is the key index (ranging from 0 - 3)
"x05" is the length of the key being either x05 or x0D (for 40- or 104-bit WEP)
"x01x02x03x04x05" is the value of the WEP key (40-bit in this case)
NOTE: You can only define a single key in the DCT and for most WEP configurations the default key is index 0.
Show LessHello Team
We are considering to make JTAG device such as USB-TINY-H for our mass-production process,
So we have reviewed the WICED reference circuit for FT2232HQ-TRQY chipset.
But I understand that the FT2232 chipset require to update image in order to using WICED USB JTAG.
Is it correct? Would you please let me know how to update or how to do?
Thank you
Daniel
Show Less
From the WiFi FAQ doc, it's mentioned that currently the SDK supports MCUs from ST, Atmel and Freescale but that the support for additional vendors is in progress. Is there any plan to support Cortex-M3 MCUs from NXP? Or would it be possible to take the current SDK and port the WiFi stack to run on NXP devices (re-map the peripherals connections or simply call the WiFi related APIs in a transparent mode)? Or any other hint to use an SN8000 from Murata and the WiFi stack embedded in an NXP MCU?
Show Less