ST67W61 and H563ZI Nucleo

[alan239955_st]

H563ZI Nucleo and Nucleo-67W61.

Using the CLI Binary version 1.1.0 I get:

#### Welcome to ST67W6X CLI Application #####
# build: 20:14:53 Sep 25 2025
--------------- Host info ---------------
Host FW Version: 1.1.0
[ERROR] [575] [spi_xfer_engine] (spi_iface.c:297) Invalid magic 0x5501
[ERROR] [575] [spi_xfer_engine] (spi_iface.c:512) Invalid spi header from peer, magic 0x5501, len (0, 0x0), version 0, type 0flags 0x0, rsvd 0x1
[ERROR] [2575] [spi_xfer_engine] (spi_iface.c:448) waiting for spi txn ready timeouted
[ERROR] [4000] [ST67W6XTask] (w61_at_common.c:375) sem_if_ready not received
[ERROR] [4000] [ST67W6XTask] (w61_at_sys.c:314) Could not init Modem handler
[ERROR] [4000] [ST67W6XTask] (main_app.c:783) [ERROR] in W6X_Init API
[ERROR] [4000] [ST67W6XTask] (w6x_sys.c:101) W61 Init failed
[ERROR] [4000] [ST67W6XTask] (main_app.c:283) failed to initialize ST67W6X Driver, 2
##### Application end

Suggestions? Thank you.

[EPASZ.1]

A reason for this might be that the binary on the NCP is not updated to the same version as the host FW. I'd suggest updating the binary, using to the attached scripts in \Projects\ST67W6X_Scripts\Binaries - described in https://wiki.st.com/stm32mcu/wiki/Connectivity:Wi-Fi_MCU_Hardware_Setup#Flashing_the_ST67W611M1_using_QConn_Flash_with_an_STM32_host. 

[alan239955_st · Accepted solution]

Thanks.

Running "NCP_update_mission_profile_t01.bat" gave

w61/>info
--------------- ST67W6X info ------------
ST67W6X MW Version: 1.1.1
AT Version: 1.0.0
SDK Version: 2.0.89
Wi-Fi MAC Version: 1.6.44
BT Controller Version: 1.6.112
BT Stack Version: 1.9.56
Build Date: Sep 4 2025 11:32:47
Module ID: C6AFDBD111400004 (-B)
BOM ID: 2
Manufacturing Year: 2025
Manufacturing Week: 16
Battery Voltage: 3.314 V
Trim Wi-Fi hp: 4,4,4,4,4,4,4,5,5,6,6,7,7,8
Trim Wi-Fi lp: 3,4,4,5,6,6,7,8,9,9,10,11,12,13
Trim BLE: 3,3,4,6,7
Trim XTAL: 41
MAC Address: 40:82:7b:03:d7:5e
Anti-rollback Bootloader: 0
Anti-rollback App: 0
-----------------------------------------

[ChrisAlfred]

It is ridiculous that the firmware is not backwards compatible. It just fails and refuses to work without updating.

ST only provide examples for the STM32U family and so any other designs have to write an update just to get this module going. That is really dumb! It should operate out of the box without change. THEN you can worry about getting updates.

This this module is a real pain to get going on any processor other than the ST32U boards provided in the examples. Not recommended. Much easier to use other manufacturer modules.