On 11/16/24 8:57 PM, Marek Vasut wrote:
On 11/15/24 9:04 PM, Ajay.Kathat@xxxxxxxxxxxxx wrote:
Hello Ajay,
Can you explain how to prevent that or shall we disable uAPSD
altogether ?
Could you please share the test procedure and logs. I am occupied
at the
moment but I shall make some time to look into it and get a better
understanding.
The simplest test procedure is this:
$ while true ; do ifconfig wlan0 up ; ifconfig wlan0 down ; done
As for the logs, MMCI controller sporadically reports either Command or
Data CRC error, so likely the SDIO response (from WILC to Host) is
corrupted.
Are there any news ?
I did test the same procedure in my setup, but I couldn't reproduce
this issue
even after running it for a long duration. In my test setup, I used the
sama5d27-som1-ek1 host and wilc3000 firmware version 16.3.
I think this issue could be related to the host MMCI controller driver.
Normally, the wilc SDIO bus failures are captured by driver logs with
an error
code (e.g., timeout), but if the MMCI controller is outputting the
warning
message, then the error could be related to it. Does the MMCI
controller error
point to any specific function?
Either CMD52 or CMD53 errors out with CRC error, this is recognized by
the controller. That points to sporadic CRC error during SDIO transfer.
Which host was used to test this scenario, and
is it possible to test with different host or different configuration
on the
same host
I am observing sporadic command and data CRC errors on STM32MP157F
system with SDIO WILC3000.
, like disabling power save on the host?
I already tested disabling power save.
Can you explain why does uAPSD (iw ...set power_save off) adversely
affect SDIO bus stability ?
Can you explain how to prevent that or shall we disable uAPSD altogether ?
Is there any way to make the WILC firmware produce debug output , so we
can figure out what is going on "on the other side" ?
Are you able to provide me (maybe off-list) some debug firmware build ?
(or can I get firmware sources and build and debug my own WILC firmware
on the Cortus CPU?)
I can trigger the SDIO errors even without being connected to any AP ,
so this is something between the WILC and the SDIO host, the radio is
likely not involved , right ?
Any news ?
