Wi-Fi Combo Forum Discussions
Hello,
I am working on to design schematic to build proto boards using WICED WIFI modules. I am bit stuck on to decide what is needed for programming the module. If anybody has suggestion, please provide. I would like to know how to debug the final boards (using emulator or something) and what facility should be provided on the board.
Basavaraj
Show LessHi @ all,
I've found a mix security type for WPA2 called 'WICED_SECURITY_WPA2_MIXED_PSK'. As I can see, the encryption can be changed but allways WPA2 is used. Regarding IEEE 802.11 there are two configuration mandantory:
1) WPA + TKIP
2) WPA2 + AES-based CCMP
Is WICED_SECURITY_WPA2_MIXED_PSK designed for stations and/or access points?
But how can I use WICED_SECURITY_WPA2_MIXED_PSK? Or what is it good for?
Thanks for helping,
Jan Gottwald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The trigger of my question is:
When I configure WICED_SECURITY_WPA2_MIXED_PSK on my hardware (STA) and try to connect to an AP with WPA2+TKIP, the connection fails.
Show LessDear Broadcom team,
I use WiCED-WiFi Sip module from SPIL
I'd like to implement " No Tx Power" because I'll use "Passive scan mode" only.
Used "snip.scan-BCM943362WCD4". I modify source code to implement Passive scan mode and I already check it's passive scan mode. App is very simple which is scan and delay.
BTW, there is tx shoot when start Passive scan as below.
I htink below source code routine make Tx shoot.
"retval = wwd_sdpcm_send_ioctl( SDPCM_SET, (uint32_t) WLC_UP, buffer, 0, WWD_STA_INTERFACE );"
Could you please let me know how to remove this Tx shoot?
Regards,
Ryan.
Show LessHello,
I have a murata board which can be in AP and STA mode at the same time.
Now I want to advertise mDNS on both services at the same time with gedday.
But the gedday_init only allows one interface, and the code is not public.
Is it possible to get gedday to advertise on two interfaces?
Or do I need to make my own mDNS service to advertise on two interfaces at the same time?
Cheers,
Gerard
Show LessDear Team,
I am a MFI registered developer and will be using Murata wifi modules SN8205 and the Evaluation kit. I have downloaded the SDK WICED 3.1.2. Does that support Murata SN8205 modules. or should we add a patch.
Please Let me know of code sample for server, client to test the Evaluation Kit and modules for both MFI and Normal accessory.
Thanks.
Show LessI'm looking into the WICED WiFi platform for a product I'm looking to develop, but I have some pretty severe concerns about the licensing of the SDK v3.1.1.
It looks to me that the intention is that the actual libraries that are for use in application code should be licensed under a BSD license per the LICENSE.txt file. However, this is never explicitly stated anywhere that I can find, just a vague statement that says "Code/libraries that may be compiled and linked with the target application [...] This code is provided under license terms similar to FreeBSD" which seems legally useless. Furthermore all the files that would be needed to be part of my application have a rather scary copyright statement that seems to imply that this code isn't supposed to even be published:
/*
* Copyright 2014, Broadcom Corporation* All Rights Reserved.
*
* This is UNPUBLISHED PROPRIETARY SOURCE CODE of Broadcom Corporation;
* the contents of this file may not be disclosed to third parties, copied
* or duplicated in any form, in whole or in part, without the prior
* written permission of Broadcom Corporation.
*/
Can I get some clarification on the license terms of these files. If they are intended to be released under a BSD license when can I expect a SDK release that properly declares the license term statements?
Thanks
Show LessHi
I installed the WICED SDK 3.1.2 development kit using WICED-SDK-3.1.2-IDE-Installer.exe on my PC(Windows 8.1). I connenct my EVB to my PC. My make target is "demo.appliance-BCM943362WCD4 download run". I can compile, but can't download the image. Below are errors. Can you fix this?
Thanks
**** Build of configuration Default for project Wiced-SDK ****
C:\Users\zhong_000\WICED-SDK-3.1.2\Wiced-SDK\make.exe demo.appliance-BCM943362WCD4 download run
Making config file for first time
+-----------------------------------------------------------------------------------------------------+
| IMPORTANT NOTES |
+-----------------------------------------------------------------------------------------------------+
| Wi-Fi MAC Address |
| The target Wi-Fi MAC address is defined in <WICED-SDK>/generated_mac_address.txt |
| Ensure each target device has a unique address. |
+-----------------------------------------------------------------------------------------------------+
| MCU & Wi-Fi Power Save |
| It is *critical* that applications using WICED Powersave API functions connect an accurate 32kHz |
| reference clock to the sleep clock input pin of the WLAN chip. Please read the WICED Powersave |
| Application Note located in the documentation directory if you plan to use powersave features. |
+-----------------------------------------------------------------------------------------------------+
Making .gdbinit
Building Bootloader
Finished Building Bootloader
Processing resources
Creating security credentials
Making DCT image
Compiling App_Appliance
Compiling Platform_BCM943362WCD4
Compiling NetX_Duo
Compiling WICED
Compiling Lib_SPI_Flash_Library_BCM943362WCD4
Compiling WWD_ThreadX_Interface
Compiling WICED_ThreadX_Interface
Compiling WWD_NetX_Duo_Interface
Compiling WICED_NetX_Duo_Interface
Compiling Supplicant_BESL
Compiling Lib_HTTP_Server
Compiling Lib_DNS_Redirect_Daemon
Compiling Lib_DNS
Compiling WWD_for_SDIO_ThreadX
Compiling Lib_Wiced_RO_FS
Compiling STM32F2xx
Compiling Lib_DHCP_Server
Compiling Lib_base64
Compiling common_GCC
Compiling STM32F2xx_Peripheral_Drivers
Compiling Lib_Ring_Buffer
Compiling STM32F2xx_Peripheral_Libraries
Making demo_appliance-BCM943362WCD4.elf
Making demo_appliance-BCM943362WCD4.bin
demo_appliance-BCM943362WCD4
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
App | 731 | 3697 |
base64 | 520 | 0 |
DHCP_Server | 1550 | 132 |
DNS | 990 | 44 |
DNS_Redirect_Daemon | 645 | 0 |
Gedday | 4492 | 736 |
Host MCU-family library | 12356 | 2740 |
HTTP_Server | 2872 | 1272 |
Interrupt Vectors | 424 | 0 |
libc | 34067 | 3136 |
Networking | 4240 | 14318 |
NetX | 55054 | 536 |
NetX-Duo - Interfaces & Stacks | 0 | 12 |
Packet Buffers | 0 | 23142 |
platform | 1008 | 168 |
RAM Initialisation | 2424 | 0 |
resources | 51840 | 0 |
Ring_Buffer | 92 | 0 |
Startup Stack & Link Script fill | 31 | 11 |
Supplicant - BESL | 110372 | 556 |
ThreadX | 9176 | 396 |
Wi-Fi Firmware | 210412 | 0 |
WICED | 7375 | 860 |
WWD | 15173 | 1124 |
----------------------------------+---------+---------|
TOTAL (bytes) | 523420 | 52880 |
----------------------------------|---------|---------|
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 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. ****"
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. ****"
Resetting target
make.exe[1]: *** [run] Error 1
tools/makefiles/standard_platform_targets.mk:102: recipe for target 'run' failed
Makefile:185: recipe for target 'main_app' failed
make: *** [main_app] Error 2
Hi,
i saw in a post that it is possible to port wiced sdk to stm32f4 discovery board via jlink. but when i tried it out its giving me this error
"**** 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. ****"
I am using BCM943362WCD6 platform for building my project.
i had made changes in the " wiced sdk toolchain_common.mk" file --> JTAG = jlink
and made the necessary changes in the build string.
is there any thing else that i should be configuring for making it work ?
Show LessCan wiced wifi module BCM943362WCD4 be used for communicating with BLE Transciever as shown in the figure? If yes, is the feature integrated in SDK?
Show Less