Wi-Fi Combo Forum Discussions

We are using the AVNET IoT development board with the BCM4343W, are any of these protocols supported by the WICED 3.5.2 SDK?

PAN/BNEP

PPP/RFCOMM

DUN

Is there a way to speed up re-association when powering up on the same network as used previously ??

I am thinking of a battery powered sensor that would wake up every ten minutes and transmit one UDP

packet then go back to sleep .... association tests we did using the console app show association times

running 5-10 seconds depending on the access point. This will run the battery down pretty quickly.

Can I cache all the connection state (WPA, etc) info in NVRAM and just resume where I left off when I powered down ??

(I was looking at the ping_deepsleep app but deep_sleep does not seem to be supported for any of the mass market platforms)

Hi,

Just a question about the consistence of managing networking thread while doing notification of link status.

Is anyone know the reason that why it doesn't need to *force wake up* networking thread at link_up case?

I happened to see the missing of link_up callback been called successfully to my application, is this related to this design?

static void link_up( void )
{
    if ( wiced_sta_link_up == WICED_FALSE )
    {
        wiced_network_notify_link_up( WICED_STA_INTERFACE );
        wiced_rtos_send_asynchronous_event( WICED_NETWORKING_WORKER_THREAD, wiced_wireless_link_up_handler, 0 );
        wiced_sta_link_up = WICED_TRUE;
    }
    else
    {
        wiced_rtos_send_asynchronous_event( WICED_NETWORKING_WORKER_THREAD, wiced_wireless_link_renew_handler, 0 );
    }
}
static void link_down( void )
{
    if ( wiced_sta_link_up == WICED_TRUE )
    {
        /* Notify network stack that the link is down. Further processing will be done in the link down handler */
        wiced_network_notify_link_down( WICED_STA_INTERFACE );
        /* Force awake the networking thread. It might still be blocked on receive or send timeouts */
        wiced_rtos_thread_force_awake( &(WICED_NETWORKING_WORKER_THREAD->thread) );
        wiced_rtos_send_asynchronous_event( WICED_NETWORKING_WORKER_THREAD, wiced_wireless_link_down_handler, 0 );
        wiced_sta_link_up = WICED_FALSE;
    }
}

product that we make is for united state market.

we need under spec.

1. we want to use 1~13 ch.

2. we want to use each mode(b/g/n)

if WICED_COUNTRY_UNITED_STATES is configured then 12, 13 ch can not use

if WICED_COUNTRY_KOREA_REPUBLIC_OF is configured then A connection to a 802.11n-only AP can not be established.

Depending on the country code changes, what is change?

Does anyone have an explanation for the behaviour?

I think that regardless of changing country code, wifi module must establish 802.11n-only ap

I have one more question

    *data = (uint32_t) GMODE_PERFORMANCE;

    retval = wwd_sdpcm_send_ioctl( SDPCM_SET, WLC_SET_GMODE, buffer, 0, WWD_STA_INTERFACE );

after applying upper code, i checked "probe request" packet

but this code dosent apply packet.

and if GMODE_B_DEFERRED, GMODE_ONLY is configured, wifi can not work

thanks

Hi,

We are developing an application based on 3.5.2 and it is suppose to use OTA feature.

The application size currently has enforced us to use external serial flash to keep downloaded copy of code.

For production flashing we do not want SDK kind of environment to be used.

Also h/w wise module will have option of only to be programmed through JTAG.

Is there any package of offline openocd using STLink available to solve the situation for us.

Cheers,

Shishir