Wi-Fi connection(to wireless LAN AP) is lost immediately after 11 hours past with WPA3-SAE. We think it was caused due to Wi-Fi module is down. It's not disconnected by wireless AP. And we have already tried other wireless LAN AP from several vendors, and we confirmed that the same issue was reproduced in every case. However, if we choose WPA2-PSK, the issue doesn't happen. Wi-Fi connection is still alive after 11 hours past.
We are looking for some information on rough memory footprint data on simultaneous BLE/WLAN examples - using the ST+Cypress part (LBEE5PA1LD). Some t...
We are looking for some information on rough memory footprint data on simultaneous BLE/WLAN examples - using the ST+Cypress part (LBEE5PA1LD). Some things to note:
WLAN in STA or AP mode? (we would need both in the FW, but not simultaneously) BLE peripheral Are there some documents out there, or possibly examples we could use for a guestimate? I did find N1-4945_Type1LD-AppNote_Memory_Usage.pdf appnote, which looks like it is the https_server example, but the footprint data isn't broken down to a level that is meaningful from the question "How much space does the WLAN host stack/driver and BLE (HCI) host stack/driver take up?
As far as is understand is that when wiced_rtos_get_semaphore is called, it decrements the semaphore counter until the counter is zero. If the counter...
As far as is understand is that when wiced_rtos_get_semaphore is called, it decrements the semaphore counter until the counter is zero. If the counter is zero, it will wait until wiced_rtos_set_semaphore is called and increment the counter.
The problem I'm seeing is when wiced_rtos_get_semaphore will timeout. It looks like the semaphore counter will still decrement on timeout, thus making next call to wiced_rtos_get_semaphore be blocked even though wiced_rtos_set_semaphore is called.
So in case of multiple wiced_rtos_get_semaphore timeouts, a multiple wiced_rtos_set_semaphore calls are needed to get the semaphore counter above zero.
Is this normal behaviour?
Am I therefore responsible to call wiced_rtos_set_semaphore if a wiced_rtos_get_semaphore timeout happens?
Hi, we are developing software on CYW43907, power consumption is very critical for us. we put CYW43907 APP CPU into sleep mode when no data send, an...
we are developing software on CYW43907, power consumption is very critical for us. we put CYW43907 APP CPU into sleep mode when no data send, and WLAN CPU initialized with wiced_wifi_enable_powersave_with_throughput( 20 ). we have two serious bugs when testing software stabilities:
1. after long running, STA is disconnected from AP, and then STA keep sending probe request every 10 seconds, but without association request, WLAN is always down;
2. WLAN is down, and when APP CPU sending DATA or CMD to WLAN CPU, no response from WLAN CPU, no packets in air, measure the current, is about 60mA, no beacon receiving current pulse, looks like WLAN CPU can't wake up from sleep.
1.this two issues only found if APP CPU sleep on, if APP MCU is not sleep, everything is ok;
2.found many times when in 2.4G band, in 5G is very rare. and the channel utility is very high(~70%) by giving interference.(iperf UDP 10M)
SDK: WICED 6.4.
main sending loop:
1. send 1 packet;
2. read rssi and channel;
4.sleep 1 second;
we have work on these two issues for more than one month, and still no any clues.