Wi-Fi Combo Forum Discussions
Today Avnet introduced the Avnet BCM4343W IoT Starter Kit powered by the Broadcom® WICED™ SDK with included cloud connectivity support to Amazon Web Services (AWS) IoT. The kit enables designers to quickly prototype and develop cloud-connected devices and then rapidly move to production with a pre-certified wireless SoC module.
Avnet has also created a short video to give engineers a preview of the board’s capabilities:
The Avnet BCM4343W IoT Starter Kit is priced at $49.95
Landing Page: Avnet CloudConnectKits
Purchase: Avnet AWS (AES-EVB-BCM4343W-G): Avnet Design Services - Custom AES-EVB-BCM4343W-G, - Avnet Express
Show LessHi Guys, Where to download WICED SDK 3.3.0 ?
Thanks !
Hi,
My purpose is downloading my new SDK 3.1.2 codes (sflash.bin, waf_bootloader-NoOS-NoNS-BCM9WCDUSI09-SDIO.elf, Arwen_v4_01_03-BCM9WCDUSI09, DCT.elf) to the board which has my old SDK 2.4.1 codes.
I have 2 ways to do that.
1) using WICED IDE: after using Arwen_v4_01_03-BCM9WCDUSI09 JTAG=jlink download download_apps run, I see below messages. Unfortunately I cannot succeed downloading.
Downloading Bootloader ...
Building apps lookup table
Download complete
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. ****"
Downloading APP0 (build/Arwen_v4_01_03-BCM9WCDUSI09/binary/Arwen_v4_01_03-BCM9WCDUSI09.stripped.elf) at sector 1...
Downloading apps lookup table at 0x0000...
Resetting target
Target running
Build complete
17:19:57 Build Finished (took 1m:7s.797ms)
2) Batch file method (please see attached file we are using openOCD) : Our batch file is working good for SDK 2.4.1 codes. Unfortunately, when I want to use this way to upgrade board to the SDK3.1.2 codes, at first trial I see download failed message. After that I try again and even if I see download complete message, application code does not work. At the end my 3rd trial I succeed and and new SDK 3.1.2 application code works properly.
After downloading process succeeded, I try again WICED IDE, It works properly.
Waiting for your comments...
Best regards
Show LessHello Sir,
How about Max throughput of bcm943362 ?
have any project can do throughput test ?
I use sdk3.3.1 , modify the snip.udp_transmit and snip.udp_receive project
but I test throughput only 11k bytes.
I used wiced_rtos_register_timed_event(....) , setting UDP_MAX_DATA_LENGTH = 1024, UDP_TX_INTERVAL = 80ms
Can give me suggest ?
Thanks you Sir !!
Show LessHi,
I am getting the following error whenver i am trying to use interface stlink.... Please help
Licensed under GNU GPL v2
Downloading Bootloader ...
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Error: The specified debug interface was not found (stlink)
The following debug interfaces are available:
1: parport
2: dummy
3: ft2232
4: ft2232_swd
5: usb_blaster
6: amt_jtagaccel
7: gw16012
8: presto
9: usbprog
10: jlink
11: vsllink
12: rlink
13: arm-jtag-ew
Runtime Error: .//tools/OpenOCD/stlink.cfg:30:
in procedure 'script'
at file "embedded:startup.tcl", line 58
in procedure 'interface' called at file ".//tools/OpenOCD/stlink.cfg", line 30
tools/makefiles/standard_platform_targets.mk:44: recipe for target 'download_bootloader' failed
make.exe[1]: *** [download_bootloader] Error 1
make.exe[1]: *** Waiting for unfinished jobs....
Makefile:185: recipe for target 'main_app' failed
make: *** [main_app] Error 2
Show LessDear All:
My WICED device is always crash and reboot when web server is booted.
I check all system and no way to fix.
Can you give me a hint which cause a crash?
How can know crash is generated by hard fault, time out ....?
Is there any exception to printf a error message when crash?
hard fault, time out or any kind of reason why system is crash?
Show LessI understand the WICED SDK provides OTA for firmware upgrades. However, the STM 32 bootloader supports the DFU protocol (Device Firmware Upgrade) but it is not clear how to use it with the WICED.
I am wondering if I can get some directions and advise on how to use DFU in a WICED design. It seems very important not only in development, as DFU is a widely used protocol with host software available for a variety of OS.
Thanks.
Show LessI've downloaded the lated WICED SDK 3.3.1 . There is a usefull api.html file to search the documentation. Unfortunatly there is no .pdf files in the installed SDK\doc directory . How to get All the Documentation which should be in the doc directory ?
Thanks , Michel V.
Show Less
We are using a murata SN8000 module connected via SPI mode 0 operating with 25Mhz to a cortex m3 lpc1837. We are using a WWD ported from the SDK 3.1.2 (including matching patch from murata). We are using a custom PCB with SPI Flash, SDRAM, MSU and SN8000. The MCU is operating with 180MHz. We are using an older version of freertos and LWIP (not taken from the SDK). The SPI interrupt has the second highest interrupt priority and SPI DMA has the highest interrupt priority. The wwd task has the highest priority as a task. There should be no long interrupt processing during the test.
We have experienced rare cases where WLAN communication stops when continuously under heavy load.
In some cases the driver thread stalls in the line "result = host_rtos_get_semaphore( &wwd_transceive_semaphore, (uint32_t) WWD_THREAD_POLL_TIMEOUT, WICED_FALSE );" of wwd_thread_func(). Interrupt line can be high or low in this case.
In other cases the driver reported " Received a packet with a frametag which is wrong" or "gSPI underflow - packet size will be wrong".
After a modification to wwd_thread's wwd_sdpcm_process_rx_packet() function which ensures the driver never runs out of RX buffers the problem occures less frequently (after 8 - 70 hours). We now simply drop data for network stack if too many packets are queued.
Another test case that sends and receives ethernet frame without use of a network stack showed that the driver runs into errors after 3 to 10 minutes of operation when RX buffers are not freed.
Is there any specification for how long RX buffers might be unavailable without interfering with operation?
Are there any known issues when running out of RX buffers?
For the cases in which wwd_thread stops in the line "result = host_rtos_get_semaphore( &wwd_transceive_semaphore, (uint32_t) WWD_THREAD_POLL_TIMEOUT, WICED_FALSE );" of wwd_thread_func() the comment for the functions wwd_thread_func() indicates that interrupts could be missed.
> * It simply calls @ref wwd_thread_poll_all to send/receive all waiting packets, then goes
> * to sleep. The sleep has a 100ms timeout, causing the send/receive queues to be
> * checked 10 times per second in case an interrupt is missed.
In SDK 3.3.1 the timeout became override able:
#ifndef WWD_THREAD_POLL_TIMEOUT
#define WWD_THREAD_POLL_TIMEOUT (NEVER_TIMEOUT)
#endif
In some of the error cases we saw the interrupt line was still high when the bus was disabled and therefore an edge interrupt was never triggered again.
In the other code path the 100ms timeout should prevent the problem.
Is there a known problem with missed interrupts in the path where the bus is disabled?
Show Less