Wi-Fi Combo Forum Discussions

How to speed up association to a Soft AP which is configured for WPA2 or WPA2/WPA mixed mode security?

Before I start diving into learning WICED I figured I'd ask here if what we want to do is possible using the BCM43362.

Is it possible to build a WiFi application that operates in both AP and Client modes at the same time? In other words, it simultaneously connects to another AP and it broadcasts it’s own SSID and accepts connections from clients. I don’t need any TCP/IP bridging or switching between the two networks and it would be OK if the two networks operate on the same WiFi channel.

Let me know, thanks!

PS. I really appreciate this initiative by Broadcom to have these free tools and support forums.

This Forum warrants a thread specifically for those wishing to use WiFi SoCs and/or WICED SDK/APIs on Linux. So, here it is.

I have been wondering if a Linux port of the WICED SDK exists? Have an email into Broadcom about this and will update this post after I hear from them.

Read an interesting post in this forum (http://community.broadcom.com/message/1447#1447) that WICED SDK was created to deal with "non-Linux" based uCs and O/Ss, pointing out that a opensource Broadcom WiFi Linux Driver already exists (brcmfmac and brcmsmac). This got me thinking.

I was about to try and port the WICED SDK to Raspbian Linux (custom linux distribution for Raspberry Pi EVB which is based on the BCM2835).

Here are some thoughts on what may be to gained from a WICED Linux port versus a standard Linux WiFi SoC driver on a Linux platform:

1) O/S independence for your application code (by using the WWD (WICED WiFi Driver) layer). Then, later on, it would be easier to migrate from Linux to an RTOS of your choosing (FreeRTOS and ThreadX are available by default).

2) Looking at "..Wiced-SDK-2.4.0WICED-SDKDocWICED-SDK-Software-Stack.pdf":

a) Is OTA ("Over The Air" upgrade) suppored with the standard open source Broadcom Linux driver (which the open source community turned into a "brcmfmac" driver for SDIO and USB interfaces)?

b) Do the following WICED APIs (not sure yet if they work through WWD calls) have equivalent Linux APIs/calls?:

Note: I know Linux does have APIs and drivers for all of the following. But, you may have to do extra work to use APIs different than those defined in the WICED SDK?

1. MCU powersave

2. Wi-Fi Powersave (I have heard that the Linux driver has issues with low power stuff, maybe it has been fixed already?)

The WLAN chip requires an external 32kHz sleep clock input during powersave. Platforms that do not support Wi-Fi powersave (per the table above)

are not capable of driving the WLAN sleep clock. An external 32kHz clock is required for these platforms.

3. I2C API

4. ADC/PWM API

Does anyone know if a WICED SDK porting guide exists? If not, I may try and create one and post it.

Hi,

If i would like to debug the entire system memory usage, how would i do that? I was not able to find related API or defines that enable me to get or print logs that shows current system memory status.

Thanks in Advance.

/* Wait until the High Throughput clock is available */
    loop_count = 0;
    while ( ( ( result = wiced_read_register_value( BACKPLANE_FUNCTION, SDIO_CHIP_CLOCK_CSR, (uint8_t) 1, &csr_val ) ) == WICED_SUCCESS ) &&
            ( ( csr_val & SBSDIO_HT_AVAIL ) == 0 ) &&
            ( loop_count < (uint32_t) HT_AVAIL_TIMEOUT_MS ) )
    {
        (void) host_rtos_delay_milliseconds( (uint32_t) 1 ); /* Ignore return - nothing can be done if it fails */
        loop_count++;
    }
    if ( loop_count >= (uint32_t) HT_AVAIL_TIMEOUT_MS )
    {
        /* If your system times out here, it means that the WLAN firmware is not booting.
         * Check that your WLAN chip matches the wifi_image.c being built - in GNU toolchain, $(CHIP)
         * makefile variable must be correct.
         */
         WPRINT_WWD_ERROR(("Timeout while waiting for high throughput clock
"));
        return WICED_TIMEOUT;
    }