Wi-Fi Combo Forum Discussions

All,

As you may know the current SDK has a temp control demo.  It allows you to talk to the xively cloud and send temp sensor information to the site from the eval board and vice versa.

As of May 1st xively is no longer creating new accounts (old accounts are "grandfathered" in), they claim to have a wait-list, but no estimate as to how long it would take.

We do have several Cloud Services supporting the Broadcom solution, so please reach out if you would like an introduction.

Apologize for the inconvenience. We will look into alternate solutions for our upcoming SDKs.

Hi,

wiced_network_up returns SET_BLOCK_ACK_WINDOW_FAIL in the both the modes STA as well as SoftAP. I'm not able to figure out why it is happening.

As per my debugging, its setting something in the network controller and its not able to do that.

Is it a known issue and are there any fixes to this?

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

Dear 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?

I 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.