[Re]When using wifi powersave, wiced_wifi_leave() return WICED_TIMEOUT value

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable
Hi

When I am attempting to use Wi-Fi Power save(wiced_wifi_enable_powersave() and wiced_wifi_disable_powersave), wiced_wifi_leave() function return WICED_TIMEOUT value.

This is why "wiced_wifi_is_reday_to_transceive(WICED_STA_INTERFACE)" function return WICED_SUCCESS after wiced_network_down.

This problem is always occurred. Why did it happen?

I am reporting about this problem at twice and I was waiting your reply during 2 month.

A quick response will be appreciated.

Relevant details:

RTOS : ThreadX

Net Stack : NetX_Duo

Processor: STM32F205

Wi-Fi Chip : BCM43362

WICED Version : WICED-SDK-2.4.0

[ATTACH]167[/ATTACH]
0 Likes
1 Solution
Anonymous
Not applicable
Hi,

Please REMOVE the following block of code to fix this issue:

<Wiced-SDK>/Wiced/WWD/internal/wwd_wifi.c function wiced_wifi_disable_powersave()

-----------------------------------------------------------------

<< line 1065 if ( result == WICED_SUCCESS )

<< line 1064 {

<< line 1065        host_platform_deinit_wlan_powersave_clock( );

<< line 1066 }

-----------------------------------------------------------------

A proper fix is already submitted to go into the official 2.4.0 release. Thanks.

Aji

View solution in original post

0 Likes
3 Replies
Anonymous
Not applicable
We are looking into this and will come back to you
0 Likes
Anonymous
Not applicable
Weve reproduced the issue and are fixing it now. Thanks for reporting.
0 Likes
Anonymous
Not applicable
Hi,

Please REMOVE the following block of code to fix this issue:

<Wiced-SDK>/Wiced/WWD/internal/wwd_wifi.c function wiced_wifi_disable_powersave()

-----------------------------------------------------------------

<< line 1065 if ( result == WICED_SUCCESS )

<< line 1064 {

<< line 1065        host_platform_deinit_wlan_powersave_clock( );

<< line 1066 }

-----------------------------------------------------------------

A proper fix is already submitted to go into the official 2.4.0 release. Thanks.

Aji
0 Likes