cancel
Showing results for 
Search instead for 
Did you mean: 

STM32H723ZGT6 + ST67W611M1: Intermittent failure after reset in debug mode and Wi-Fi SoftAP start issue

Aashritha_Vuda
Associate III

I am using STM32H723ZGT6 as the host MCU with the ST67W611M1 Wi-Fi + BLE module.

Software details:

Firmware flashed on ST67: T01 binary

STM32 firmware package: X-CUBE-ST67W61(1.1.0)

Application selected: BLE P2P

Enabled parameters:

Wi-Fi SAP: Yes

Wi-Fi STA: Yes

BLE: Yes

NET: Yes

DHCP: STA+SAP

Issues observed:

Intermittent failure after reset in debug mode

When I reset the board while running in debug mode, the system sometimes does not work correctly(w6x init failed or other intiliazation failed in mainapp.c). The behavior is inconsistent—occasionally it works, but often it fails after reset.

 

Wi-Fi SoftAP start failure

The following API fails:

ret = W6X_WiFi_StartAp(&ap_config);

While debugging, the failure occurs due to a timeout in the following function:

/* Initialize the dual interface mode */

ret = TranslateErrorStatus(W61_WiFi_SetDualMode(p_DrvObj));

SPI clock configuration doubt

Could you please confirm the recommended SPI clock frequency for STM32H723ZGT6 when interfacing with ST67W611M1?

Should it be 40 MHz, or is a lower frequency required for stable operation?

DMA and linker script configuration

Is it necessary to modify the linker script for STM32H723ZGT6 to support DMA buffers (for example, placing buffers in non-cacheable memory)?

Could incorrect cache/DMA memory configuration cause the above intermittent failures or timeouts?

I have configured the board according to the document “How to use the X-CUBE-ST67W61 software package”, but the issue still persists.

Please let me know if any additional configuration, firmware version, or hardware constraint needs to be considered.

i attached the corresponding .ioc and mainapp.c files.

Thank you for your support.

 

1 REPLY 1
Louis AUDOLY
ST Employee

Hello  @Aashritha_Vuda ,

Thanks for pointing out this issue and sorry for the late reply.

This is not an SPI clock configuration issue but a memory shortage on the ST67 with T01 binary. We are working on providing a more complete description of the root cause of this issue.


In the meantime, I recommend you to switch to a T02 binary flashed on the ST67.
As the LwIP stack is moved to the STM32 host, this leaves more space on the ST67 to handle more complex use cases, with STA, soft-AP and BLE working in the same time.

I hope this will help

Regards
Louis