Wi-Fi Combo Forum Discussions
Hi,
I am new to this platform, and have been evaluating WICED Wi-Fi EVAL KIT (BCM943362WCD4) for a project. The project aims at designing a schematic/layout with WICED module (using USI WM-N-BM-14) which can be added to the range of products we have already designed. Application part will be different from product to product.
At design/development stage, it is convenient to have a USB interface for JTAG and UART, to program and debug the application. But during the production, we will need a better way to be able to flash the application to the STM MCU.
WICED application note WICED-AN800-R on Factory Programming provides information from the software point of view of programming the modules, but there is little or no information provided regarding the hardware setup. What sort of hardware design will be required for the factory programming as mentioned in this application note?
Does it necessarily require JTAG-2-USB for programming? In this case, the Olimax JTAG USB programmer can be used.
Can we program using UART RX and TX from the breakout header using TTL-232R-3V3 UART to Serial (or any other converter)?
I have seen some responses regarding UART programming under WICED Smart forum. Do those responses also apply to WICED Wi-Fi, or are these two development systems completely different?
Our aim is to reduce the number of components that will be included in the design (so no FTDI chip if possible). What will be the bare minimum design in order to be able to program the WICED Wifi? Any design guide or schematic available?
My second concern is regarding the Over-The-Air (OTA) upgrade. From my understanding, it is the STM32F2xx MCU which is being programmed when flashing. Knowing that STM MCU has 1MB of flash and some of the applications have sizes > 512kB, so I do not understand how the OTA upgrade will take place. Does OTA require a separate Flash on-board?
I understand that some of these questions might have been answered somewhere else in the forum. If that is so, then please direct me to the specific discussion topic.
Show LessI like to enable and change the socket-tcp-keepalive option.
Here is my environments.
- WICED SDK 2.3.1
- ThreadX/NetX Duo, BCMUSI11
Here is my source for <TCP Keep Alive>.
.......................
wiced_tcp_create_socket(&socket_tcp, interface);
nx_tcp_socket_keepalive_enabled = 1;
nx_tcp_socket_keepalive_timeout = 10; // 10Sec
nx_tcp_socket_keepalive_retries = 1;
.......................
But, after this implementation, WICED module didnt send <Keep Alive Packet>.
Is it wrong?
Thanks in advance
Steve
Show LessHi,
I try to activate WWD_LOG traces on my BCM943341WCD1 EVB, by defining WWD_LOGGING_UART_ENABLE.
When first trace appears on UART, the board get stuck and finally resets.
Any tip?
Thanks
Julien
Show LessHello all,
My name is Saulo, I'm from Murata Brazil. We have launched a new Combo (WiFi/BLE) module that is using a BC43340 Broadcom IC.
We are working on a Brazilian customer and we would like to know if this IC it's a part of Broadcom WICED program or what should I do to take support from Broadcom ?
Many thanks.
Best Regards
Saulo Rodrigues
Show LessI'm using WICED/WICED-SDK-MFi-3.1.0/apps/snip/scan/ application on Inventek Systems ISM43362-M3G-L44-E
it runs fine and successfully discovers access points on channels lower than (including) 11,
but doesn't see access points on channel 13.
I understand it's not permitted in FCC area to use channel 13,
so I assumed I needed to change country_code and added:
#define WICED_COUNTRY_CODE WICED_COUNTRY_JAPAN
in WICED-SDK-MFi-3.1.0/include/default_wifi_config_dct.h
but this doesn't change anything.
What should I change to see access points on channel 13?
Thanks in advance.
Show Lesswhen call smartbridge_gatt_indication_notification_handler( uint16_t connection_handle, uint16_t attribute_handle, uint8_t* data, uint16_t length );
BLE controller central receive data from other BLE peripheral device not pass data to
wiced_rtos_send_asynchronous_event( WICED_NETWORKING_WORKER_THREAD, smartbridge_app_notification_handler, (void*)socket );
How can process data on smartbridge_app_notification_handler?
Show LessHi,
I want to replace STM32F415 to STM32f411RE on the plateform of BCM943362WCD6.The first question I can't download firmware to STM32f411RE.How to modefy the openocd script file make it download ok?
Show LessHi,
I'm trying to build my app using BSD socket layer.
I wrote
#include "netx_bsd_layer/nxd_bsd.h"
but ./make outputs following error:
% ./make snip.udp_sample-ISM43362_M3G_L44-ThreadX-NetX_Duo
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_udp_sample
Compiling Platform_ISM43362_M3G_L44
Compiling NetX_Duo
Compiling WICED
Compiling SPI_Flash_Library_ISM43362_M3G_L44
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 Ring_Buffer
Compiling STM32F2xx_Peripheral_Libraries
Making snip_udp_sample-ISM43362_M3G_L44-ThreadX-NetX_Duo.elf
build/snip_udp_sample-ISM43362_M3G_L44-ThreadX-NetX_Duo/libraries/App_udp_sample.a(UDPProtocol.o): In function `snip::openUDP()':
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:27: undefined reference to `socket(int, int, int)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:34: undefined reference to `bind(int, sockaddr*, int)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:37: undefined reference to `ioctl(int, int, int*)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:42: undefined reference to `inet_addr(char const*)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:46: undefined reference to `setsockopt(int, int, int, void const*, int)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:51: undefined reference to `inet_addr(char const*)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:53: undefined reference to `setsockopt(int, int, int, void const*, int)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:59: undefined reference to `setsockopt(int, int, int, void const*, int)'
build/snip_udp_sample-ISM43362_M3G_L44-ThreadX-NetX_Duo/libraries/App_udp_sample.a(UDPProtocol.o): In function `snip::sendUDP(sonycsl_openecho::Frame&)':
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:81: undefined reference to `socket(int, int, int)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:85: undefined reference to `inet_addr(char const*)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:110: undefined reference to `sendto(int, char*, int, int, sockaddr*, int)'
build/snip_udp_sample-ISM43362_M3G_L44-ThreadX-NetX_Duo/libraries/App_udp_sample.a(UDPProtocol.o): In function `snip::receive()':
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:145: undefined reference to `recvfrom(int, char*, int, int, sockaddr*, int*)'
snip/WICED/WICED-SDK-MFi-3.1.1/apps/snip/udp_sample/UDPProtocol.cpp:154: undefined reference to `inet_ntoa(in_addr)'
make[1]: *** [build/snip_udp_sample-ISM43362_M3G_L44-ThreadX-NetX_Duo/binary/snip_udp_sample-ISM43362_M3G_L44-ThreadX-NetX_Duo.elf] Error 1
make: *** [main_app] Error 2
%
Compiler successfully found header, but the actual functions don't exist.
The directory structure assumes WICED/WICED-SDK-MFi-3.1.1/WICED/network/NetX_Duo/ver5.7_sp1/netx_bsd_layer/nxd_bsd.c to exist but it doesn't.
How can I get nxd_bsd.c or it's compiled library?
Show LessHw-team asked me that tx-pwr adjust of wifi.
we adjusted wifi_nvram_image[] of wifi_nvram_image.h but it has been adjusted until 9dB.
we want to adjust more low tx-pwr.
Let me know how to adjust tx-pwr?
And can i choose mode 802.11 b or g or n ?
Hw-team tell me that b mode is high than g mode or n mode so b mode would ignore.
Show LessI set SOFT_AP_CHANNEL 1, and I connected a NETGEAR AP that is set to 11 channel
,then Soft ap channel is changed to 11 channel.( Wifi Analyer )
I checked soft_ap->channel variable, but Soft ap is working channel 11
Let me know why channel is changed
souce> in application_start function
{
const wiced_config_soft_ap_t* soft_ap = &wiced_dct_get_wifi_config_section()->soft_ap_settings;
WPRINT_APP_INFO(( "soft ap channel[%d]\r\n",soft_ap->channel ));
}
log>
soft ap channel[1]
Show Less