Skip to main content
Associate II
March 16, 2026
Question

STM32 Host with ST67W611 Wifi BLE

  • March 16, 2026
  • 2 replies
  • 280 views

Hello everyone, 


I'm using a host (STM32F7) communication with ST67W611 BLE WIFI via SPI.
So far, I can configure application P2P Client, T01 architecture, gen code and build pass.
The issue what I'm facing is I can't init SPI communicaiton with ST67W611. so Could you help me answer some question to debug what issue is?
1. I bought ST64W611, so Could I need to re-flash firmawre for this module?
2. the W6X_Init(0 function init failed, I checked the pin SPI_RDY alreay has level low (= 0).

so I hope if there is someone has worked with ST67W611 via SPI with a host STM32, please share me the experience?

 

Thank you very much!

2 replies

Andrew Neil
Super User
March 16, 2026

Welcome to the forum.

Please give more details of your setup - see: How to write your question to maximize your chances to find a solution

 

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Technical Moderator
March 16, 2026

Hi @GiangN 

It is indeed necessary to update the module binary as stated in the note here. The procedure is described in the same wiki page. Let us know if this solves your issue or if we need to look further into it.

Best regards,

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
GiangNAuthor
Associate II
March 16, 2026

Hi @TarikAb,

follow the process to flash the binary. I saw the note in below:
"If the host board is not included in X-CUBE-ST67W61, the NCP_Loader project must be migrated to generate above mentioned binaries"

My question is: how to migrate to generate the binary for my host ( STM32F7690.

Thanks,

Giang

Andrew Neil
Super User
March 16, 2026

@GiangN wrote:

how to migrate to generate the binary for my host ( STM32F7690.


The same way you'd migrate (aka "port") any other software from one microcontroller to another: identify which parts are specific to the particular microcontroller, and adjust them accordingly...

 

This is why we have layered architectures:

Image2.png

only the lowest layer - which deals directly with the SPI hardware - should be microcontroller-specific ...

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.