Open thom24 opened 1 month ago
From ST point of view, the issue comes from the SDIO Out Of Band interrupt implementation for the WIFI. A workaround is to pass from Out Of Band interrupt to In Band interrupt.
To do it we need to:
diff --git a/arch/arm/boot/dts/stm32mp135f-dk.dts b/arch/arm/boot/dts/stm32mp135f-dk.dts
index bee689f2ee8e..545697f43c7b 100644
--- a/arch/arm/boot/dts/stm32mp135f-dk.dts
+++ b/arch/arm/boot/dts/stm32mp135f-dk.dts
@@ -494,6 +494,7 @@ &sdmmc2 {
pinctrl-1 = <&sdmmc2_b4_od_pins_a &sdmmc2_clk_pins_a>;
pinctrl-2 = <&sdmmc2_b4_sleep_pins_a>;
non-removable;
--
* Comment the following line in the NVRAM configuration file of the WIFI module (/lib/firmware/brcm/brcmfmac43430-sdio.st,stm32mp135f-dk.txt):
```# muxenab=0x10```
The wifi module gets stuck during iper3 tests. The issue mostly appears using --reverse or --bidir options (client is running on the stm32).
The issue was reproduced on STM32MP135F-DK and STM32MP157F-DK2, but some other platforms should be impacted.
Note that this issue was also reproduce using the ST yocto (tag openstlinux-6.1-yocto-mickledore-mp1-v24.03.13).
The only way to recover the module is to reset the board.